Approach
Four ideas that shape how the work gets done.
Start rough
A first draft on a napkin gets corrected. A polished document gets nodded at. We put something imperfect in front of people early, because the fastest way to learn how a team actually works is to describe it slightly wrong and let them fix it.
Write it down
Undocumented process is not process, it is habit. Habits are fragile: they break when the person holding them is unavailable, and they drift without anyone deciding to change them. Writing something down makes it reviewable, teachable, and possible to improve on purpose.
Measure a few things well
A scorecard with thirty numbers on it is a report nobody reads. A handful of measures, understood by everyone and updated on a predictable schedule, changes behavior. The discipline is in what gets left off.
Hold the rhythm
Most operating systems fail at the same place. Not at design, at week six, when the novelty is gone and the meeting could be skipped. A cadence only starts paying off once it is boring. We build for that stretch rather than for the launch.
What this is not
- A software platform, or a reason to buy one
- A restructuring exercise
- A framework applied the same way to every team
- A document that gets written once and never opened again