PLAYBOOK PREVIEW

See how the planning system connects.

A controlled 15-page preview demonstrates the point of view, planning architecture, capacity logic, commitment design, dependency management, operating rhythm and Northstar example without exposing the full method.

01 / CREDIBLE COMMITMENT

A plan is credible only when demand and usable capacity meet.

Nominal headcount is not capacity. Leaders must account for business-as-usual demand, mandatory work, scarce skills, interruptions and coordination overhead before choosing what the organisation can genuinely commit to.

USABLE CAPACITY100%

RunMandatoryChangeBuffer

Commit only after operational demand, mandatory work and interruption buffer are visible.

NORTHSTAR EXAMPLEThe decision

Northstar cannot add a new priority without naming which existing commitment moves, reduces or stops.

The evidence

One demand view, an explicit capacity envelope and a visible trade-off make the consequence discussable before commitment.

02 / 90-DAY PLAN

Turn priorities into a small set of protected commitments.

Each commitment needs a clear outcome, accountable owner, realistic capacity allocation, known dependencies and decision boundaries. The plan becomes a leadership contract, not a collection of hopeful activities.

01OutcomeOne measurable change

02OwnerOne accountable leader

03CapacityProtected allocation

04DependenciesAgreed before start

05EvidenceReviewed in rhythm

WWeekly execution

MMonthly portfolio

QQuarterly reset

03 / RE-PLANNING

New demand must displace something.

When evidence changes, leaders can re-plan deliberately. The Decision Log records what changed, what was protected, what moved and why, keeping the plan credible under real operating pressure.

New demand→Impact visible→Move, reduce or stop→Decision logged