Runs on PeoplePlaybooks / Process
Agreements
Is our process owned by the people who use it?
Weak
Rules written elsewhere, quietly worked around, and handovers that drop things.
Strong
Process is people's agreements, written down, reviewed and cut when it stops helping.
Playbooks
In the works
- Handovers that don't drop things
- Estimates that aren't lies
What weak looks like in your industry
- Software and technologyA definition of done nobody checks and a release checklist nobody opens.
- Healthcare and practicesA triage protocol written by the partners and ignored at reception.
- Accountancy and professional servicesA file-review checklist that grows after every inspection and never shrinks.
- Manufacturing and operationsA safety step skipped because it was written for a different machine.
- Small businessThe way to quote a job exists only in the owner's head.
In the frameworks you already use
Every framework touches this dimension somewhere. Here's where.
All frameworks →- SAFeCapacity allocationAgree up front how much capacity goes to new features versus enablers and tech debt.
- Disciplined AgileChoose your WoWTeams choose and evolve their own way of working, from a range of proven options.
- Shape UpThe betting tableA small group bets on shaped pitches for the next cycle. No backlog.
- KanbanExplicit policiesWrite down how work moves, so everyone plays by the same rules.
- Lean and the Toyota WayKaizenSmall, continuous improvements by the people doing the work.
- Team TopologiesInteraction modesCollaboration, X-as-a-Service, facilitating: be explicit about how teams work together.