6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article examines why many teams in large organizations struggle to be genuinely empowered, despite claims to the contrary. It highlights issues like interdependencies, organizational structures, and executive demands that undermine team autonomy and lead to fragmented user experiences.
If you do, here's more
Empowered teams are often touted as the key to better products and faster delivery. Marty Cagan defines empowered teams as those given problems to solve rather than tasks to complete, holding them accountable for outcomes instead of mere outputs. However, the reality is that most teams in larger organizations struggle with true empowerment. This disconnect arises not from deceit but from the inherent structures and dependencies within these organizations.
When a product manager at a mid-sized fintech company identifies a solution to improve the onboarding experience, they quickly hit roadblocks. Changes to shared components, like navigation, require coordination with multiple teams, each with their own priorities. What begins as a straightforward fix spirals into a lengthy process involving numerous meetings and compromises, ultimately diluting the original solution. This scale problem illustrates how interdependencies among teams can stifle the very autonomy that empowered teams need to thrive.
The challenge intensifies with organizational structures that often prioritize engineering efficiency over user-focused solutions. For instance, in a large ecommerce company, teams responsible for different sections of a product page may struggle to collaborate effectively. Each team can only make minimal changes without affecting others, limiting their ability to drive significant improvements. Similarly, in a healthcare marketplace scenario, multiple teams may find their goals conflicting due to dependencies, leading to delays and frustrations.
Executives amplify these issues by demanding certainty in timelines and outputs. They prefer clear roadmaps and fixed release dates, which clash with the iterative nature of empowered teams that pivot based on user feedback. Leadership often imposes strategic priorities that can redirect teams away from what users actually need, forcing them to build features that donβt address core problems. This constant tug-of-war between flexibility and the need for predictability undermines the empowerment that organizations aim to achieve.
Questions about this article
No questions yet.