Readiness Planning
Turn a reading into a period of work the people doing it own.
This is not training and not a scenario. It runs against your real capacity, with your real people, and what comes out of it is a commitment.
What is here
5 surfaces, and what each one leaves you holding.
Quarterly Readiness Planning
a facilitated session
A quarter of committed work with an owner on every line, built against the conditions the diagnostic measured. The agenda and the scripts are published, so it can be run without us.
Written for: Senior manager, Senior leadership, C-level
The Readiness Workspace
The period in progress: commitments, the condition each one leans on, and what has moved.
Written for: Manager, Senior manager, Senior leadership
The Readiness Board
The visible state of the period, arranged so a condition at risk is legible before it is late.
Written for: Manager, Senior manager, Senior leadership
The Debrief
What the period actually taught, separated from what it delivered, and carried into the next one.
Written for: Manager, Senior manager, Senior leadership, C-level
Facilitated Engagements
The four ways to run any of this with us in the room, and who has to be there.
Written for: Senior leadership, C-level, Board member
Not built yet
What is missing here, and why it is missing.
Stated on the page rather than left blank. A roadmap kept private is how a gap becomes a surprise, and a reason written down is what stops the next version being the wrong one.
- Cycle Planning
- The short loop inside the quarter: what this cycle commits to, what it deliberately is not doing, and which condition each commitment depends on.
- THE QUARTER HAS A HOME AND THE LOOP INSIDE IT DOES NOT, which is the gap this registry was written to make visible. A quarterly plan that is never re-cut against what happened is a forecast, and the levels closest to the work are exactly the ones the quarterly session does not reach. Called a CYCLE and not a sprint on purpose: "sprint" files the product into agile delivery, which is the same category mistake CLAUDE.md refuses when it forbids calling an organizational instrument an "Assessment". The house word is already "cycle": it appears in 24 places and in lib/pricing.ts's own offer key, quarterly-cycle.
- For: Team contributor, Manager, Senior manager
- Board Oversight Cycle
- The oversight calendar: what the board asks for each period, and what it does when the answer does not arrive.
- A board does not plan the work, so an implementation surface for it is a rhythm of questions rather than a set of commitments. That is a real product and a different shape from the other two, and designing it on the assumption that a board plans like an operator is how governance theater gets built.
- For: Board member
Coverage
Every level, three ways in
A diagnosis nobody was trained to read changes nothing, and training with no period of work behind it is a seminar. Each row is a seat in an organization; each column is one of the three things you can do from it.
| Seat | Train | Diagnose | Implement |
|---|---|---|---|
| Team contributoron a team, without formal authority over it |
Also open to everyone: The Builder's Library Planned: One Team, One Quarter | Also open to everyone: Executive Organizational Diagnostic: Short Form | Nothing for this seat yet Planned: Cycle Planning |
| Managerone team and the people on it |
Also open to everyone: The Builder's Library Planned: One Team, One Quarter |
Also open to everyone: Executive Organizational Diagnostic: Short Form | Planned: Cycle Planning |
| Senior managerseveral teams, as one group |
Also open to everyone: The Builder's Library |
Also open to everyone: Executive Organizational Diagnostic: Short Form |
Planned: Cycle Planning |
| Senior leadershipa function or a portfolio |
Also open to everyone: The Builder's Library |
Also open to everyone: Executive Organizational Diagnostic: Short Form | |
| C-levelthe enterprise |
Also open to everyone: The Builder's Library |
Also open to everyone: Executive Organizational Diagnostic: Short Form |
|
| Board memberoversight, without operating authority | Nothing for this seat yet Also open to everyone: The Builder's Library Planned: Board Oversight Simulation | Also open to everyone: Executive Organizational Diagnostic: Short Form | Planned: Board Oversight Cycle |
The 2 gaps, and why they are open
These are stated rather than hidden. A matrix with a quiet blank cell reads as an oversight, and one that shows only what exists is a brochure.
- Team contributor, implement: Cycle Planning
- THE QUARTER HAS A HOME AND THE LOOP INSIDE IT DOES NOT, which is the gap this registry was written to make visible. A quarterly plan that is never re-cut against what happened is a forecast, and the levels closest to the work are exactly the ones the quarterly session does not reach. Called a CYCLE and not a sprint on purpose: "sprint" files the product into agile delivery, which is the same category mistake CLAUDE.md refuses when it forbids calling an organizational instrument an "Assessment". The house word is already "cycle": it appears in 24 places and in lib/pricing.ts's own offer key, quarterly-cycle.
- Board member, train: Board Oversight Simulation
- The board diagnostic shipped first because it could be written from the governance literature. A simulation needs a scenario with a real information asymmetry in it, and writing one that a director recognizes is authorship rather than a build step.