The 4 Most Common Barriers to Outcome-Based Product Management (And How You Can Overcome Them)

Teresa Torres responds to readers who want to adopt outcome-based product management but face obstacles in their organizations. She identifies four common barriers: fast development cycles that leave no time to evaluate ideas, product managers being assigned features rather than problems, lack of access to data, and teams missing key skills. For each, she offers guidance split between product leaders, who can change team structure and investment, and individual product managers, who can start small and build habits. The core message is that waiting for perfect conditions or permission is a mistake, and that small, consistent steps toward evaluating ideas will gradually shift how a company does product work.

01Key takeaways

• Set aside even a small block of time each week to test assumptions before adding ideas to the backlog.
• Engage engineers in discovery work, since they bring technical insight into mapping problems and designing experiments.
• Treat every idea the same way regardless of who proposed it, and let the evidence decide what gets built.
• Start gathering evidence now with the data you have, such as customer calls and existing logs, rather than waiting for perfect data.
• Pick one skill at a time, such as experiment design, and practice it through small, regular investments.
• Leaders should protect time for discovery and invest in team development, since change in process is gradual and persistent.

02Key sections

Fast development cycles leave no time to think

Product managers become backlog groomers instead of problem solvers. Torres argues that engineers can join the discovery process and that it is better to invest in a few ideas that work than to build many that don't.

Ideas are assigned rather than discovered

When leadership hands down feature lists, product managers lose the chance to evaluate problems. Torres advises leaders to push back consistently and to treat all ideas, regardless of origin, through the same process.

Data access is a real but overstated barrier

Perfect data never arrives, and waiting for it blocks progress. Torres suggests leaders improve data access while individuals gather whatever evidence they can, such as talking to customers and analyzing existing logs.

Teams lack the necessary skills

The process demands systems thinking, experiment design, and reliable data collection. Torres recommends that leaders invest in training and that product managers deliberately practice these skills over time.

Final word on persistence

Torres acknowledges the field changes quickly and encourages small, daily investments that compound into organizational change.

03From the post

“If you read my last post on outcome-based product management and thought how do I get there, you aren’t alone. I received dozens of emails, tweets, and comments from product leaders just like you asking this very question. In an ideal world, every product manager would start at”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.