• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Product Mastery Guilds

Purpose and Strategic Importance

Product Mastery Guilds are communities of practice where product people share skills, knowledge, and techniques. They accelerate mastery, spread good practice, and build collective capability.

Without guilds, learning stays siloed, expertise is unevenly distributed, and teams repeat mistakes.


Description of the Practice

  • Guilds are voluntary, peer-led groups.
  • They focus on topics like discovery methods, measurement, or facilitation.
  • Outcomes include shared resources, mentoring, and improved craft.

How to Practise It (Playbook)

1. Getting Started

  • Identify champions to initiate a guild.
  • Start with a shared focus (e.g., outcome-driven roadmaps).
  • Run regular meetups or workshops.

2. Scaling and Maturing

  • Expand guilds across disciplines and geographies.
  • Create repositories of shared tools and templates.
  • Link guild outcomes to portfolio standards and practices.

3. Team Behaviours to Encourage

  • Peer mentoring and openness.
  • Pride in continuous improvement.
  • Curiosity about evolving practices.

4. Watch Out For…

  • Guilds becoming social only, with no impact on practice.
  • Participation limited to enthusiasts.
  • Lack of visibility into business outcomes.

5. Signals of Success

  • Qualitative: Teams reference guild insights in decision-making.
  • Quantitative: Increase in adoption of modern practices across teams.
Associated Standards
  • Craftsmanship and mastery are nurtured
  • Product teams are empowered and accountable
  • Evidence is the basis for decisions

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering