Live data from Hacker News

How many of you know that the team is working on something that no-one wants?

iism.org

11–20 of 428 posts

Re: How many of you know that the team is working on something that no-one wants?

#11

> Don't just build Something™, build an industry leading product that customers want and love! One of the biggest challenges is that someone eventually has to say "no" for that to happen. It is easier to just say yes to whatever is wanted than fight with someone about doing it.

Words of wisdom and experience - I am with you on that one

Re: How many of you know that the team is working on something that no-one wants?

#13
Obviously using a throwaway here. Our board members got it into their heads that successful companies must have an AI "play", so they instructed the CEO to invest about 10% of our development budget on AI.

We are doing absolutely inane projects that have no hope of succeeding.

We serve a niche industry where certified professionals have to do certain tasks personally, instead of being able to delegate to secretaries. Somehow our CEO has been convinced that AI can be trained to do these tasks, at a reliability level not achievable by other humans.

Team motivation is in a weird space: everyone is relaxed because there is no pressure to succeed - we all know the project will fail unless someone develops well-perfoming, human-level AGI before Q4/2020. Lots of long lunches and checking out early in the afternoon.

At the same time, everyone is worried how terrible the fallout is going to be once the project reaches its inevitable conclusion.

Interesting times, but at least we can now tell investors we are a keen company with an AI play up our sleeve!

Re: How many of you know that the team is working on something that no-one wants?

#14
Many of the features can be a total waste of time, true, once we spent 3/4 of a budget building UI for the product whose biggest customers (95% profit) never used UI. But then again, business plans change, some features need to be customer-tested, etc.

Re: How many of you know that the team is working on something that no-one wants?

#15

“Agile teams that truly iterate with the customer can often avoid these problems because the customer is there the whole way through and the team continuously pivots to close gaps discovered by the customer throughout the project, thereby building something the customer actually needs and wants.” I‘m 2 years into my first role as a product owner (made the switch from design) and working at a fortune 100. The thing th…

This problem isn’t unique to big tech. It’s much easier to tell each other you are customer driven than to actually pick up the phone.

I’m in b2b SaaS, and the best approach I’ve found to combat this is to get involved in sales meetings. Salespeople look at you funny if you ask to come along, but if you convince them you aren’t weird it usually works. And you tend to make the meeting more successful, as well as getting actual useful insights into what prospects actually want.

Re: How many of you know that the team is working on something that no-one wants?

#16
I have a weird story of the same type, I developed a new module on the product (Quite an obvious one, no need to educate users), and got very little traction, but after 2 years, but reports and support started piling in. My new interpretation is that we just had to let the market pick up on it and do its transition at its own pace (I don’t know if development is paid for yet).

Re: How many of you know that the team is working on something that no-one wants?

#17

Obviously using a throwaway here. Our board members got it into their heads that successful companies must have an AI "play", so they instructed the CEO to invest about 10% of our development budget on AI. We are doing absolutely inane projects that have no hope of succeeding. We serve a niche industry where certified professionals have to do certain tasks personally, instead of being able to delegate to secretaries.…

Just pivot to "assisted-AI" where your solution is really bad but it adds "super-powers" to all their existing employees. It may give cover to some other businesses to fire staff under the "force-multiplier" argument that your software adds ("If their software makes every employee 33% better, we can fire 33% of our staff!").

Re: How many of you know that the team is working on something that no-one wants?

#19

“Agile teams that truly iterate with the customer can often avoid these problems because the customer is there the whole way through and the team continuously pivots to close gaps discovered by the customer throughout the project, thereby building something the customer actually needs and wants.” I‘m 2 years into my first role as a product owner (made the switch from design) and working at a fortune 100. The thing th…

The problem is the definition of customer and the actual commitment to a customer focus, in my experience.

It's usually hijacked away from the actual customer - that is to say, a person who pays your company for products and/or services - to various internal "customers" who are nothing of the sort.

Spotify are ostensibly the Gods of Agile, but how many Spotify music customers were actually begging for podcasts? How many of them were begging for Spotify to lock podcasters behind their paywall and stop podcasts working with any tool? Was there even a single paying Spotify customer demanding that?

Post reply on HN