Skip to main content
Case Study

Scaling Discovery Across 12 Product Teams

How a growing product organization built consistent discovery practices without creating process overhead.

10 min readAxial TeamPublished: 2026-01-28
Case Study Draft

Content Structure

Client Context

[B2B SaaS, growth stage, 200-500 employees, multi-country]
12 product teams across 3 business units, varying maturity levels. Recently transitioned from founder-led to professional product leadership.

The Challenge

Discovery practices varied wildly across teams. Some teams did extensive customer research; others shipped based on stakeholder requests. Quality was inconsistent. Best practices stayed siloed. Leadership wanted consistency without bureaucracy.

Our Approach

  • • Assessed current practices across all 12 teams
  • • Identified what worked and what didn't
  • • Designed a lightweight discovery framework adaptable to team context
  • • Trained teams in cohorts with hands-on practice
  • • Provided embedded coaching during initial application
  • • Established cross-team learning forums

Outcomes

  • • All 12 teams adopted minimum discovery practices
  • • Weekly customer touchpoints increased from 30% to 90% of teams
  • • Feature invalidation rate improved (caught problems earlier)
  • • Cross-team knowledge sharing became self-sustaining

Client Quote

"[Placeholder for client testimonial about building discovery capability]"

Key Lessons

This engagement highlighted what works when scaling product practices across multiple teams without creating bureaucracy.

One Size Doesn't Fit All

Different teams had different contexts—different customers, different technical environments, different maturity levels. The operating model framework provided principles and minimum expectations while allowing teams to adapt execution.

Training Without Coaching Fails

Workshop-based training alone didn't change behavior. Embedded coaching during the first application cycles bridged the gap between knowing and doing.

Once teams experienced success, the new practices stuck. This approach to building product capability creates lasting change.

Internal Champions Sustain Change

We identified and invested in internal champions—practitioners who were curious about better practices. These champions continued spreading and adapting the framework after our engagement ended.

Peer Learning Scales Better Than Central Mandates

What Worked

Cross-team forums where practitioners shared successes and challenges drove adoption better than top-down requirements. People learn from peers they respect.

Related Resources

To learn more about building product capability, explore our guides:

Need help scaling discovery practices? Contact us to discuss your specific challenges, or learn about our product capability building services.

Need Help Implementing These Ideas?

We help product organizations put these frameworks into practice.

Schedule a 30-Minute Call