Aug 16, 2024

Lead with Problems, Not Solutions

Protecting Discovery: A Playbook for Product Managers

Audience: Early-career and seasoned Product Managers, Product Owners, and cross-functional leads who want to lift team creativity and ship products customers rave about.

Why Rushing to Solutions Backfires

  • Solution-first thinking kills curiosity. The instant you pitch a fix, the room defaults to critique rather than exploration.
  • Creativity needs slack. When discovery is compressed, edge cases, fresh perspectives, and customer nuance vanish.
  • Ownership drives quality. Teams fight for ideas they helped shape; they resist ideas handed down.

Common Scenarios Where Discovery Gets Short-Circuited

Scroll to view more
Situation Typical Reaction Better Move
Stand-up uncovers a blocker PM offers a quick workaround Pause: ask “What does great look like?”
Stakeholder demands a feature PM drafts the PRD overnight Run a lightning discovery workshop
Designer shows early mock PM requests tweaks Invite engineers to stress-test assumptions

The Discovery-First Framework

  1. Frame the Problem, Not the Fix

    • Clarify the friction: user pain, market gap, or workflow snag.
    • Share constraints: budget, timeline, regulatory, tech stack.
    • State the desired outcome: measurable impact or customer behaviour change.
  2. Hold the Space

    • Use open prompts:
      • “Where does this break for users?”
      • “What edge cases worry you?”
    • Embrace silence - ideas bloom in the gap.
    • Capture themes, not verdicts.
  3. Invite Diverse Voices

    • Engineers for feasibility checks.
    • Designers for journey mapping.
    • Sales/Support for frontline insights.
    • Reference models like Atlassian's Team Playbook “Discovery Play” for facilitation.
  4. Convert Insights into Experiments

    • Draft thin-slice prototypes or assumption tests.
    • Prioritise by risk vs. learning value.
    • Track outcomes in a shared dashboard (e.g. Productboard, Jira).
  5. Guard the Vision, Not the Path

    • Keep goals visible: OKRs, North-Star metric.
    • Let the team iterate on execution details.
    • Step in only to re-align on purpose, not on pixel placement.

Quick Reference: Discovery-Boosting Questions

  • “What's the riskiest assumption here?”
  • “If we had unlimited time, what would we explore first?”
  • “How might a power user break this?”
  • “Which customer quote captures the pain best?”

Keep reading

Relevant posts

About Max Antonov
I'm a father of three from Sydney, a Product Director and a Product Coach. I write about product management and run the Product Manager community.

Get the monthly digest

Best posts on product, strategy and AI. One email a month.