Reference
Templates and checklists for execution planning
Part of the Execution Planning skill · loaded on demand from SKILL.md
Read this when you are producing the deliverables and want the copy-ready structure. Placeholders in angle brackets are allowed here and nowhere else. Every template below has a filled version in worked-example.md.
Contents
- Strategy-to-behaviour translation
- 7-S diagnostic scoring sheet
- Initiative portfolio summary
- Initiative charter
- RAPID chart and decision log
- 90-day plan
- Governance cadence
- Commitments note (post-meeting)
- Value ledger stub (hand-off to kpi-architecture)
- Partner review checklist
1. Strategy-to-behaviour translation
Write this before the diagnosis. Each line is a behaviour the strategy requires that the organisation does not currently exhibit.
Chosen strategy (verbatim from the choice record):
"<one paragraph>"
Value at stake: <total> by <date>, from <driver 1: amount>, <driver 2: amount>, <driver 3: amount>
The strategy requires the organisation to:
1. <Who> will <do what> instead of <current behaviour>.
2. ...
(3 to 6 lines. If you have more than 6, the strategy is not yet specific enough; go back to strategic-choice.)
2. 7-S diagnostic scoring sheet
Score 1 to 5 on alignment with the chosen strategy. 5 = already fully consistent with what the strategy requires; 3 = partially aligned, changeable with effort; 1 = actively works against the strategy. Every score needs an evidence cell that names its source (interview count, document, data extract, calendar analysis).
| S | Score (1 to 5) | Evidence and source | Misalignment with the strategy | Lever in the plan |
|---|---|---|---|---|
| Strategy | ||||
| Structure | ||||
| Systems | ||||
| Shared values | ||||
| Skills | ||||
| Style | ||||
| Staff |
Alignment summary (one paragraph, in this order):
- Which hard S's can be changed by decision, and by when.
- Which soft S is the binding constraint on the hard changes holding, and why.
- What the plan does about that soft S in the first 90 days.
Rule: never present the hard-S rows without the soft-S rows. If the evidence for a soft S is thin, say so in the evidence cell and score conservatively (lower).
3. Initiative portfolio summary
| Initiative | Owner | Sponsor | Value at stake (run-rate, by year N) | Main 7-S levers | Decisions required |
|---|---|---|---|---|---|
| 1. | |||||
| 2. | |||||
| ... | |||||
| Transformation office | n/a | Style, follow-through |
Rules: three to six initiatives; the sum of the value column must reconcile to the value-driver model; every initiative has one named owner (a person, not a function); an "enabler" initiative may carry no direct value but must name which initiatives it enables.
4. Initiative charter
One page per initiative. The owner and sponsor sign it. It changes only through the decision log.
| Field | Content |
|---|---|
| Initiative | <name> |
| Owner | <one named person; accountable for delivery> |
| Sponsor | <executive who removes obstacles and holds the owner to account> |
| Objective | <one sentence: what changes, for whom, by when, measured how> |
| Value at stake | Baseline <metric and value>; target <value> by <date>; EBITDA (or equivalent) contribution <run-rate>. Year 1 target: <specific> |
| Scope in | <what this initiative owns> |
| Scope out | <adjacent things it explicitly does not own, and which initiative does> |
| Milestones | Day 30: <deliverable, done-test>. Day 60: ... Day 90: ... Month 6: ... Month 12: ... |
| Resources | <people, budget, systems; and whether they are already in the value model> |
| Dependencies | <decisions and other initiatives this needs, with the date it needs them by> |
| Decisions required | <decision IDs from the RAPID chart> |
| Measures | Lead: <2 to 4>. Lag: <1 to 3>. Formal definitions in the kpi-architecture scorecard |
| Top risks | <two, each with a mitigation already in the milestones>. Full pre-mortem run separately |
| Review cadence | <which forums, how often> |
Done-test for a charter: a person outside the team can read it and say what will exist at day 90 that does not exist today, and who is accountable if it does not.
5. RAPID chart and decision log
RAPID chart
Chart only the decisions that are high-consequence and sit on an organisational seam (global versus local, centre versus unit, function versus function, inside versus outside partner). Delegate the rest to initiative owners within their charters.
| ID | Decision (stated as a question with a finite set of answers) | R | A | P | I | D | Deadline | Slot in cadence |
|---|---|---|---|---|---|---|---|---|
| D1 | ||||||||
| D2 |
Assignment rules, applied in this order:
- Name one D. A person, never a committee. If two executives both claim it, the D is their common boss for this decision only.
- Name the R and confirm the R has the standing to get input from the A's and I's.
- Assign A only where a formal sign-off is genuinely required (legal, regulatory, safety, capital, sometimes margin). Everyone else who wants an A gets an I.
- Limit I to people who hold facts the R does not. Consultation is not a vote.
- Name the P explicitly, even when it is obvious.
- Push the D to the lowest level with both the information and the accountability.
- Give every decision a deadline and a named slot in a scheduled forum.
Decision log
| ID | Decision | D | Date due | Date decided | Outcome (what was decided, in one sentence) | Commitments triggered |
|---|
6. 90-day plan
Four blocks of roughly three weeks. Each line is a deliverable with a done-test and an owner, not an activity.
| Weeks | Initiative | Deliverable and done-test | Owner |
|---|---|---|---|
| 1 to 2 | Transformation office | <programme lead appointed; charters signed; cadence calendar issued; decision log opened> | |
| 1 to 2 | Style lever | <what the CEO changes about their own review and calendar, first> | |
| 1 to 4 | |||
| 3 to 6 | |||
| 5 to 8 | |||
| 7 to 10 | |||
| 9 to 13 | |||
| 13 | All | Day-90 review: each initiative against charter milestones; value ledger committed versus realised; every charted decision closed or explicitly re-dated | Programme lead |
Rules: the first two weeks contain the governance set-up and the style lever; every charted decision appears in the block where it is due; the day-90 review is a line item with a done-test, not an afterthought.
7. Governance cadence
| Forum | Frequency and length | Chair and attendees | Standing agenda | Written output and deadline |
|---|---|---|---|---|
| Initiative stand-up | Weekly, 30 min | Owner; team leads | Next milestone; blockers; asks | Blocker list to programme lead same day |
| Transformation office review | Fortnightly, 90 min | CEO chairs; owners; CFO; programme lead | Decisions due (from RAPID chart); milestones; dependencies; value ledger | Decision log entry and commitments note within 24 hours |
| CEO operating review | Monthly, 2 h | CEO chairs; executive team; owners | Initiatives (owner brings one problem); customers or markets; P&L versus operating plan | Commitments note within 24 hours; next review opens with last month's commitments |
| Strategy and people review | Quarterly, half day | CEO chairs; executive team; CHRO leads people half | Value-model assumptions; 7-S re-score; talent review of strategy-critical roles; non-performers | Updated 7-S scores; people actions with dates; charter changes logged |
| Board update | Quarterly | CEO | Value ledger; milestones (format from the operations skill) | n/a |
Rules: the CEO chairs the reviews personally; status is reported against milestones, not colours; each forum has a named written output with a deadline.
8. Commitments note (post-meeting)
Sent by the programme lead within 24 hours of every transformation office review and CEO operating review.
<Forum>, <date>
Decisions made
- <ID>: <one sentence stating what was decided>. D: <name>.
Commitments
| Who | What | By when | Status at next review |
|---|---|---|---|
Re-dated from last meeting (with reason)
- <commitment>: was <date>, now <date>, because <reason>.
Problems raised that need help
- <initiative>: <problem>; <who is helping>; <by when>.
9. Value ledger stub (hand-off to kpi-architecture)
The execution plan opens the ledger; kpi-architecture defines the stage gates, measures and tracking cadence.
| Initiative | Value at stake (run-rate) | Identified | Committed (charter signed) | In delivery | Realised in P&L | Owner |
|---|
10. Partner review checklist
Run before the plan goes to the client. Each is pass or fail.
- The strategy-to-behaviour list has 3 to 6 lines and each names a specific change from current behaviour.
- All seven S's are scored, each with an evidence source, and the alignment summary names the binding soft-S constraint.
- The plan contains at least one lever aimed at the lowest-scoring soft S in the first 90 days.
- Three to six initiatives; value reconciles to the value-driver model; every owner is a named person.
- Every charter states what will exist at day 90 that does not exist today.
- Every charted decision has exactly one D, at most two or three A's, a deadline and a slot in the cadence.
- No decision's D is a committee or "the executive team".
- Every 90-day plan line has a done-test, not an activity verb.
- The cadence names the chair, the standing agenda and the written output with a deadline for each forum.
- The CEO's own review or calendar changes in the first two weeks.
- The document does not contain a risk register, OKRs, a scorecard or a product roadmap; each is handed off to its skill by name.
- No placeholders, no emojis, no em dashes, none of the banned words.