By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres and Hope Gurion argue that teams new to outcome-oriented product management lack several hard skills, so leaders must deliberately build them for pilot teams to succeed during an organizational transformation. The core skills they identify are a grasp of business context (how the company makes money and how the product contributes), regular customer conversations to find the most important problems, testing whether proposed solutions are the right ones via assumption testing, and faster discovery cycles supported by qualitative and quantitative methods. They add cross-functional collaboration and knowing when to move from discovery to delivery as further competencies. The message matters because teams rarely learn these skills by reading a book; they require practice, observation, and targeted coaching from leaders.
01Key takeaways
- Confirm that your teams understand how the company makes money and how their work contributes to revenue or cost.
- Build regular customer conversations into the team's routine so problem selection rests on evidence, not stakeholder requests.
- Deconstruct proposed solutions into assumptions and test the riskiest ones with quick, decision-supporting experiments.
- Practice cross-functional collaboration by having people work individually first, then negotiate differences as a group.
- Treat skill-building as an explicit part of the transformation, observing where teams struggle and investing coaching there.
02Key sections
- Why pilot teams need upskilling
- Teams new to outcome-driven work typically lack business context, customer contact, fast de-risking methods, and speed. Leaders often pass down outputs rather than educating teams on strategy.
- Business context and customer discovery
- Teams should understand how the company makes money and translate business outcomes into product outcomes. They also need skills in customer interviews and opportunity mapping to find the right problems.
- Evaluating solutions with assumption tests
- Teams should break ideas into underlying assumptions and run quick but decision-supporting tests. Combined with qualitative and quantitative methods, this enables faster learning cycles.
- Collaboration and navigating discovery to delivery
- Cross-functional teams must learn to externalize thinking, explore perspectives rather than advocate, and recognize when evidence is enough to move into delivery. Reducing work in progress and shipping smaller increments supports this.
- Training as a leadership responsibility
- Pilot teams create a safe space to practice, and leaders can observe where skills lag and decide where to coach, train, or bring in outside help.
03From the post
“Change is exciting, but too much change can feel chaotic. When making a big change like adopting the product operating model or continuous discovery, how do you tap into the excitement while also controlling the chaos? This is a question that Hope Gurion and I have been exploring over the”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.