news

Effective product organizations don't run on hierarchy—they run on five interlocking roles, each leading from where they stand. The Leader creates the container that makes everything else possible. The Product Owner leads outcomes, owning direction and ruthless prioritization. The Product Developer leads craft, engineering, and the realization of value. The Adaptiveness Guide co-leads change, building capability until they're no longer needed. And the Stakeholder engages actively, experiencing value firsthand and validating that what's built actually matters. Where these roles intersect, something rare emerges: happy people delivering exceptional products to happy stakeholders.

Leaders serve. They garden the climate daily, remove obstacles teams can't tackle themselves, and turn ambiguity into clear direction. They understand the work—not just what gets built, but how—and engage customers firsthand rather than through filtered reports. They coach when it's welcome, build autonomy through trust, and lead with evidence over gut. They think in systems, eliminate waste, and adapt strategy continuously. They grow people and plan succession by devolving real authority, not tokens. Leadership happens at all levels—but the distinct Leader creates the container within which every other role thrives.

Leaders serve. They look after how it feels to work here—happy people serving happy stakeholders is the most important work. They garden the climate daily, protecting it from toxicity and removing people who damage it even when productive. They acquire knowledge firsthand: pairing with the team, engaging customers directly rather than through reports, making waste visible. They treat strategy as continuous adaptation, not a fixed plan—adjusting weekly based on evidence, nurturing emergence with direction. They build responsiveness as competitive advantage: creating slack, removing friction, optimizing flow across the whole value network.

Adaptiveness Guides are catalytic change agents who serve people, not frameworks. They co-own change outcomes from cradle to grave—holding themselves accountable like sports coaches, with evidence and honest feedback. They sense complexity, navigate context, and read people; they facilitate conversations that surface diverse perspectives and enable real decisions. They start small, scale through pull, and create contagion through storytelling and visible success. They're voraciously curious, humble yet confident, and teach principles over practices. The truest measure of their work: they inspire others to become change agents, then make themselves unnecessary.

Adaptiveness Guides serve people by guiding teams, products, and executives through complexity—co-owning change outcomes from cradle to grave, never product outcomes. They sense complexity, read context, master facilitation, and practice Genchi Genbutsu by going to the source. They model empiricism, foster psychological safety, and start small to scale through pull rather than push. They balance deep confidence in principles with genuine humility about paths. They teach principles over practices and build lasting change. The truest measure: they inspire others to become change agents, then make themselves unnecessary.

If the 2001 Agile Manifesto gang got together again in 2026, what might they value? Perhaps People Empowerment Improvement over Individuals and Interactions; Value Improvement over Working Product; Insight Improvement over Customer Collaboration; and Capability Improvement over Responding to Change. In a nutshell: work climate, learning, outcomes, and impact—over outputs, over activities and 'resources.' Whatever approach is taken, teams need to be bold like a salmon swimming upstream—acknowledging obstacles, staying mission-driven, committing fully. Doing more than the minimum to achieve the maximum. And knowing when to quit, because grit is overrated.

Most teams face a Double Mandate: keep the lights on (BAU) and deliver a massive change portfolio—both non-negotiable. The instinct is to estimate BAU at 20% on average and plan on the remaining 80%. It's a trap. As Sam Savage warns in The Flaw of Averages, a commander who crosses a river of "average depth" 3 feet drowns his troops in the 10-foot hole. The fix: plan with P80 Net Velocity—your "bad day" number, the work you deliver 80% of the time even when things go wrong. Then attack the tax: keep critical BAU, automate high-value BAU, kill low-value BAU. The goal isn't a roadmap that looks green on Day 1—it's one still green on Day 365.

On paper, the matrix is a perfect grid of accountability. In practice, decisions stall, priorities conflict, busy work multiplies while delivery lags. Drawing on Goldratt, Barnard, Christensen, Martin, Ackoff, and Kotter, the diagnosis: the matrix optimizes parts at the expense of the whole and lets leadership avoid hard strategic choices. The antidote isn't better management of the grid—it's radical alignment around a Single Direction of Travel: external, measurable, the only thing that matters. Subordinate everything to it, build a coalition that holds, keep flow visible. Silos don't disappear; they just stop mattering.

The matrix promises flexibility and shared resources. In practice, it's where flow goes to die—no one can make decisions alone, so nothing much changes. One antidote: an archipelago of adaptiveness. Build a substantial team-of-teams that works semi-independently on a real product, using genuinely adaptive ways of working in a permanent island designed to radiate change outward—not get reabsorbed. Volunteers, not assignments. Distributed leadership. Customer-informed learning and flow. Protect it through coopertition, nested PDSA loops, and Avengers-style closed shields against silo pressure. The matrix must evolve. Networks result and thrive.