--- title: The Golden Path: Why Your Teams Need a Framework, Not a Playbook description: Introducing the Golden Path concept, how it differs from conventional Playbooks, and how it's core 'comply or explain' principle is more adapted to empowered teams. The Golden Path helps the organization adapt and innovate practices to navigate their ever evolving context. date: 2025-11-06 author: Christophe Achouiantz, Joakim Sundén keywords: empowered product team, empowerment, leadership, transformation, autonomy, golden path, playbook category: Empowered Teams lastModified: 2025-11-06 slug: why-your-teams-need-a-framework-not-a-playbook publish: yes --- ## How to guide product teams without removing their autonomy Every effort to improve how teams work starts with good intentions. Leadership invests in consultants, creates detailed playbooks, and rolls out "the new way of working." Teams attend training, nod along, and then... nothing changes. Sound familiar? The problem isn't that teams don't want to improve. It's that most guidance comes in the form of rigid playbooks that ignore context, remove autonomy, and eventually get abandoned. Teams either blindly follow prescriptive steps without understanding the why, or they quietly ignore the playbook altogether because it doesn't fit their reality. > Teams either blindly follow prescriptive steps without understanding the why, or they quietly ignore the playbook altogether because it doesn't fit their reality. ![Playbook are guidance from above that ignore context, remove autonomy, and eventually get abandoned](playbook-way.png) We've seen this pattern repeatedly across companies attempting product transformation, but also in growing organizations simply trying to improve consistency or raise the bar on how teams work. As we discussed in [Using Product Thinking to Improve Your Organization](https://betterproductwork.com/), treating organizational change like a traditional project, with fixed plans and one-size-fits-all solutions, rarely works. The same applies to how we guide teams on ways of working. ## **What If There's a Better Way?** Here’s the paradox: many organizations say they want empowered teams because empowered teams are more innovative, take ownership, and find better solutions for customers. But then they deny those same teams the freedom to discover better ways of working. If we believe empowerment leads to better products, why wouldn’t it also lead to better practices? ![Product Teams are empowered to find product-market fit by adapting the product to the context they work in](product-fit.png) Teams that can experiment with how they work are more likely to find faster, more effective, and more engaging ways to deliver outcomes. That’s why teams need to treat their practices as a product in themselves \- something to continuously discover, test, and evolve \- not a fixed process to comply with. So what if there's an alternative between rigid playbooks and “do whatever”? What if you could provide teams with clear, proven practices while preserving their autonomy? What if teams could benefit from organizational consistency while keeping the flexibility to adapt to their unique contexts? This is the thinking behind the Golden Path. The Golden Path isn't a playbook. It's **a recommended and supported way of working**: a clear, proven path that teams can follow to plan, build, and learn. But unlike traditional playbooks, it's built on a fundamental philosophy: **comply or explain.** Teams can either follow the recommended practices or, if they choose a different approach, explain why and how they'll still achieve the intended outcome. This simple shift changes everything. ![The Golden Path shows the path of least resistance and allows teams to adapt practices to their context](practices-fit.png) Spotify pioneered this approach with their Golden Paths for engineering practices, and Netflix developed similar concepts they called "Paved Paths." Both companies found that this approach reduced fragmentation and improved outcomes without sacrificing the autonomy that drives innovation. ## **The "Comply or Explain" Philosophy** "Comply or explain" is not about giving teams permission to ignore standards. It's about requiring teams to take ownership. It’s about understanding the outcome each practice is designed to achieve and to take responsibility for achieving it, whether by adopting, adapting, or replacing the practice. > It's about requiring teams to take ownership. This approach promotes "clarity over conformity." Teams don't have to follow every recommended practice, but they must understand what problem each practice solves. With that understanding, teams have options. They might find a different practice better suits their context, so they document their reasoning and track results. They might discover the problem doesn't exist in their context at all. Or they might find the recommended practice isn't relevant and an alternative approach is needed. The key is ownership: teams must make deliberate choices and take responsibility for the outcomes. ## **Golden Path as a Catalyst for Practice Innovation** This is what makes the Golden Path powerful: it isn't about adapting existing practices. **It's about enabling organized innovation of the ways of working.** When teams have the mandate to test alternative methods to achieve outcomes, the organization can: * **Learn from experiments in context**, not theory * **Capture new practices that work** and spread them across teams * **Evolve the Golden Path itself** as teams discover better approaches **A team's experiment might prove so effective that it becomes a recommended practice for others.** In some cases, it might even become a new essential practice. The Golden Path becomes a living system and not just a tool for alignment. It’s a catalyst for continuously improving how teams work. ![The Golden Path help the organization adapt and innovate practices to navigate their ever evolving context](golden-path2.png) To summarize: ### Traditional Playbook Approach * Prescriptive and rigid: "Do these exact steps" * One-size-fits-all solutions * Compliance-focused: "Follow the rules as written" * Static documentation that becomes outdated * Teams become passive executors * Innovation happens despite the playbook ### Golden Path Approach * Flexible framework: "Here's what works, adapt as needed" * Context-aware: Different team types need different approaches * Outcome-focused: "Achieve this result, using methods that work for you" * Living document that evolves with learning * Teams become active owners * Innovation feeds back into the path ## **How It Works** The Golden Path provides essential and recommended practices. **Essential practices** are foundational practices teams benefit from having in place. They form the baseline needed for teams to succeed in the organization's context. Essential practices are expected to be adopted by most teams, with strong support from leadership and coaches to help them succeed. **Recommended practices** are more advanced or context-specific approaches that have proven valuable for some teams but may not fit everyone. These are more à la carte and teams are encouraged to pick what makes sense for their context and experiment with what might work. For example: Essential team practices include maintaining stable cross-functional teams, conducting regular customer conversations, and limiting work-in-progress; while Recommended practices include using Opportunity Solution Trees, practicing test-driven development, and implementing continuous deployment pipelines. The Golden Path is opinionated and supported, so teams aren't left to figure things out alone. Essential practices come with clear instructions, examples, training, and coaching. **This makes the path of least resistance the path of consistency:** following proven practices is easier than reinventing the wheel. The process includes: * **Collaborative workshops** to understand the why behind each practice and how to implement it * **Ongoing coaching support** as teams adopt and adapt practices * **Regular team reviews** (typically quarterly) to assess: Are our current practices helping us achieve our goals? * **Documentation of alternative approaches** when teams diverge from recommended practices, including the reasoning and expected outcomes ## **What's Coming in This Series** In future articles, we will explore how the Golden Path concept applies for different types of teams: from **individual squads** to **leadership teams** and **Tribes (team-of-teams)**. These Golden Paths will cover practices for teams to grow into empowered product teams, for leadership teams to create the strategic context that enables others to succeed, and for coordinating multiple teams while preserving individual team empowerment. The Golden Path isn't about perfection. It's about giving teams a well-marked trail they can follow, with the freedom to blaze their own when context demands it. Sometimes the best way forward is the well-trodden path. Sometimes it's not.