Managing Product Teams for Success

Teresa Torres argues that managing product teams by outcomes rather than outputs is necessary for real autonomy, but it is hard because leaders struggle to trust teams and teams struggle to communicate progress on uncertain goals. She proposes a model where outcomes are negotiated collaboratively between leadership and the product team, and where teams maintain a steady cadence of customer interviews, prototype tests, and assumption tests. Managers should monitor that cadence and critique the team's discovery thinking through the opportunity solution tree rather than dictate solutions or manage the delivery backlog. Outcomes are then judged at the end of a term, with attention to trends and the quality of the team's activities rather than single results. The piece matters because it gives leaders a concrete way to balance accountability with the freedom teams need to discover what works.

01Key takeaways

• Communicate the intent behind goals, not just the features or deliverables you want built.
• Negotiate outcomes collaboratively so leadership strategy and team customer insight both shape the goal.
• Track whether the team keeps a weekly rhythm of customer interviews, prototype tests, and assumption tests.
• Use the opportunity solution tree to question whether opportunities, solutions, and experiments truly connect.
• Give feedback on discovery thinking, but leave delivery backlog decisions to the product team.
• Judge teams on outcome trends and activity quality over time, not on hitting every target.

02Key sections

Why outcomes require autonomy

Shifting from output-oriented roadmaps to outcome-oriented goals means communicating intent and letting teams choose how to reach it. Leaders can suggest strategies but should leave room for better options.

Negotiating outcomes together

Outcomes should be set through a two-way negotiation, combining leadership's cross-business view with the team's closeness to customers and technology. Teams need training to set measurable, time-appropriate, focused outcomes.

Building a discovery cadence

Good teams regularly run customer interviews, prototype tests, and assumption tests, plus zoom-out and alternative-solution exercises. Managers should monitor this cadence and help remove obstacles when activities lapse.

Connecting research to decisions

Research should change what the team builds, leading to abandoned ideas and new directions. Managers use the opportunity solution tree to question links and give feedback without imposing their own opinions.

Leaving delivery to the team

Leaders should focus feedback on the discovery roadmap and step back from backlog management, which the product team should own, especially for senior teams.

Evaluating outcomes over time

At term end, teams present progress, and leaders judge both outcome results and activity cadence. Missing an outcome despite good work is not failure, and overall trends matter more than single terms.

03From the post

“I’ve been thinking about the challenges of managing product teams by outcomes. Most leaders want their teams to have the autonomy to go after an outcome, but they struggle with trusting that their teams will do the right things. Most teams want that autonomy, but they struggle with communicating”

04Frameworks mentioned

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