5 ms·
Ego killed the empowered product team
- najork 3y agoI agree with the author’s sentiment that product teams fail because of a lack of trust, but don’t think it’s necessarily ego-driven. It’s challenging to build a company with a high-trust culture. While many companies say it’s one of their values, I’d bet it only holds true for a small minority of them in practice, especially when things aren’t going according to plan. When an organization is failing to execute against its goals, regardless of the root cause, the natural tendency is to introduce more process and exert more top-down control. Ironically, this drives away the most capable, creative problem solvers, who’ll look elsewhere for fulfillment.
- deleted 3y ago[deleted]
- gtirloni 3y ago> especially when things aren’t going according to plan. Exactly my experience. The first misstep and it reverts back to top-down micromanagement and the actual product roadmap is the last priority... then it's downhill from there.
- codemac 3y ago> [top down control] drives away the most capable, creative problem solvers [..] Eh, I think it's the lack of execution that drives them away, in fact if you're not executing many times it's because they're not even there.
- karmakaze 3y agoNot necessarily ego-driven but in my experience they usually come together. If there was trust, all that would be needed is more communication. Without it reporting teams are not given autonomy. Now if execs issue top-down direction, it's because 'they know better' aka ego, not the kind for collecting wins, but simply believing they know more than those that are closer to the problem and data.
- LargeTomato 3y agoInteresting article but in my company the shifting priorities aren't ego driven, it's driven by the rapidly changing technical requirements of the company. Maybe at Google it was ego but at the startup I work at it's just pivoting to capture market share. A lot of my peers have trouble with this constant shift and I think that's ego. They are wrapped up in their own work and are ignorant of the company's priorities.
- janejeon 3y agoI mean also just adapting to rapidly changing environment and requirement is hard. It's a skill, just like anything else. Best not assign reason to why others have trouble doing a thing (not just this) based on our own experiences (referring to "that's ego" bit).
- CharlieDigital 3y ago> A lot of my peers have trouble with this constant shift and I think that's ego. They are wrapped up in their own work and are ignorant of the company's priorities. I'd say that it's not necessarily ego but perhaps one part coherency and one part skepticism. And it can often be exacerbated by lack of communication of those priorities and why they are shifting. If the previous strategy was validated, then why is the strategy shifting? Is the product design process fundamentally broken in the org? "If I dump my in progress work now, how long before my next effort gets short circuited?" Rapidly shifting priorities without clear reasoning raises questions on whether the leadership team knows what they are doing. In both cases, my own experience is that open dialog and communication from the leadership team on how the decision was made and sharing the data points can reduce the friction. From the technical leadership, communicating the right mindset also helps -- especially with more senior resources.
- happymellon 3y ago> Rapidly shifting priorities without clear reasoning raises questions on whether the leadership team knows what they are doing. It also leads to wasted work. What was the point of of working hard when it gets thrown away? If alternative views were expressed earlier then perhaps the work could have been made generic to handle both use cases in case of a pivot.
- bjornsing 3y agoAn early stage startup is an empowered product team, I would say. I would never found a company, take on the CEO role, and then hand off responsibility for customer value and business viability to a newly hired “empowered product manager”. That makes no sense to me. For a later stage company I fully agree with this model though. I tend to think of these “empowered product teams” as sort of internal startups, each with a “mini-CEO” and a “mini-CTO”.
- karaterobot 3y agoIn my experience, it's fear over ego. At the last company I worked for, the CEO discovered Marty Cagan and immediately switched the entire company over to following his recommendations. I was on a product team, and we came up with our own strategy to meet our OKRs. The CEO didn't like our approach, and decided that, actually, he was going to both set the objectives, and results, and tell us how to achieve them. We were basically a feature team. But it wasn't ego, it was fear. The company was running out of runway, we just hadnt been told yet. The CEO adopted the product team strategy as a Hail Mary, out of sheer panic, and he sabotaged it for the exact same reason: he was terrified of not trying it, and then terrified of it not working. Not only because of this anecdote, but because of several other important ones, I view leadership as being generally fear-driven in their decision making. Ducklike, they appear calm and even confident on the surface, while desperately thrashing and failing below the surface. Or, like someone falling down a hill and reaching out for anything to hold on to.
- AnimalMuppet 3y ago"We're running out of runway; let's change our development approach"? Talk about counterproductive...
- kabouseng 3y agoNot to pick a fight, but there is this misconception from salaried employees that the running of a company is mostly calm and relaxed, and there are certainty where next months salary is going to come from. Or at least that good management achieves this. But in reality, leadership of a company is constant chaos, the image of the dog with room on fire saying everything is fine comes to mind. Who knows what the right decisions is, everybody has feet of clay.
- Aperocky 3y ago> The short summary of Cagan’s definitions is that feature teams are told what to do and are measured on delivering output. They’re incentivized to ship products, have low levels of collaboration and almost no autonomy. Product teams, on the other hand, are empowered to solve problems. Seems like author's product team has quite an ego of itself, having feature team only ship products and not solve or point out problems is a recipe for tech debt and disaster.
- apineda 3y agoThe feature team is as a comparison, not in addition to the product team.
- DyslexicAtheist 3y agoall the digital and agile transformations I've seen had 1 thing in common: they missed to get buy in from middle management. Instead there are agile coaches preaching[1] to the choir while the rest of the org is betting against their success. [1] Art imitating life in that regard: https://www.youtube.com/watch?v=bB340S0tGf8 https://www.youtube.com/watch?v=bB340S0tGf8
- sumtechguy 3y agoYou can also have the whole org go all in on agile. I am not sure which way is worse now. But we sure have tons of forms to make sure our rituals are properly done.
- j4yav 3y agoMiddle management and agile almost seems like a contradiction in terms in the first place. Although I guess that's what SAFe is for.
- orochimaaru 3y agoI would also add buy in from rank and file engineering team members. Also, not being sensitive to concerns of those teams. If you make life hard for folks implementing, they will find loopholes that will eventually crater your plan.
- al_borland 3y agoI’ve also seen where upper management dictates those below them to use it, but they want to be exempt from all of it, forcing teams to do double (or worse) work to handle the paperwork around agile, while also preparing bespoke reports to feed up the chain in each leader’s preferred format.
- j4yav 3y agoI think some people are talking about startups here and some people are talking about enterprises and it's confusing the issue a bit. Apart from that, I think there's an element of "skin in the game" that benefits startups - there's a natural tendency for people at companies big or small to lose track of the big picture and start working on pet projects. At a startup at least you have a chance of things being aligned, everyone has equity and things are (relatively) simple enough that everyone can sort of tell what needs to be done. But at a big enterprise company, an entire department can spend millions on some pet project before anyone even realizes what's happening, and things are so complex that you can make a reasonable case for anything being a valid bet. And to the people in the department, it will appear that some egocentric executive showed up out of nowhere and disrupted their idea. In the end, though, I don't think it's really mostly executive ego being inflicted on a group of people, although I am sure that sometimes happens. And I especially don't believe that demonstrating small incremental value will protect you from anything. I think if you really want to be on an empowered product team, for real, work at startups. But that comes with its own downsides.