Full SKILL.md

Execution Planning

Turns a chosen strategy into an executable programme — required behaviours, scored 7-S alignment diagnosis with the binding constraint, three to six initiative charters that reconcile to value at stake, RAPID decision rights for seam decisions, a 90-day plan of deliverables with done-tests, and a governance cadence the CEO chairs. Use whenever a strategy is agreed and the question is how the organisation will deliver it, or the user says "how do we actually implement this", "who owns what", "we agreed the strategy but nothing is happening", "transformation office", "decision rights are a mess", "first 90 days", "operating cadence", "the org is not aligned". Not for the scorecard and benefits ledger (kpi-architecture) or product roadmaps (product-strategy).

Diagnoses where the current organisation will pull the strategy back, then builds the charters, decision rights, 90-day plan and cadence that stop it. 7-S (Waterman, Peters and Phillips), RAPID (Rogers and Blenko) and Bossidy and Charan's disciplines are in references/frameworks.md; read it only when a step needs defending.

When not to use

  • Strategy not chosen: strategic-choice first.
  • Value not sized: value-driver-modeling first, or state assumptions.
  • Scorecard, strategy map, stage gates: kpi-architecture.
  • Risk register or pre-mortem: run separately; carry back only the top two mitigations per charter.
  • Competitor response: war-gaming. Product roadmap: product-strategy.

Inputs

Ask for, or infer and label: the chosen strategy (choice record verbatim, with its two or three conditions); value at stake by driver with timing; the organisation as it is (structure, top team by name and tenure, incentive plan, review calendar, CEO's calendar last quarter); soft-S evidence (interviews, survey, capability headcounts); known contentious decisions and who thinks they own them; constraints (one-time budget, headcount, board or regulatory dates, works-council obligations).

Ask one round of questions if the strategy or value at stake is missing. Otherwise proceed on labelled defaults: unit P&Ls with unit heads owning customers; unit heads bonused on unit profit; monthly unit financial review, no initiative review; core capability held by a few individuals; CEO time spent with units not target customers; anything moving customers, budget, headcount or pay is contentious. Replace as evidence arrives.

Workflow

  1. Required behaviours. Three to six lines, "who will do what instead of the current behaviour", each tagged with the value driver it serves. More than seven means the strategy is not specific enough; send it back. Done when a branch manager would recognise a change to their own week and someone would object.

  2. 7-S diagnosis, scored (references/templates.md §2). Evidence per S before scoring: strategy (do the top 30 describe it the same way); structure (who owns customers, P&Ls, the critical activity); systems (what the incentive plan actually pays for, what the monthly deck actually reviews, approval workflows, data systems); style (CEO calendar, what gets celebrated, how conflict is settled); staff (tenure and seats for strategy-critical roles); skills (how many hold each assumed capability at level); shared values (what people say the company is for, with interview counts). Score 1–5 on alignment with the Stage 1 behaviours, not quality; thin evidence scores lower and says so. Summary in fixed order: which hard S's change by decision and when; which soft S is the binding constraint; what the first 90 days does about it. Score-to-plan rule: soft S at 1–2 needs a lever in weeks 1–2 or a gate on the value ramp; 3 needs a lever inside 90 days; hard S at 1–2 needs a charted decision with a date. Test: cover the hard rows; do the soft rows alone explain why this would fail?

  3. Initiative portfolio and charters (references/templates.md §3–4). One initiative per value driver (two only if the levers differ); an enabler initiative where one system change serves several; the transformation office as its own line, programme lead reporting to the CEO. Cap at three to six; defer the rest with a date and reason. Value column reconciles to the driver model. Charter per initiative: one named owner, sponsor, one-sentence objective, value with baseline and year-one target, scope in and out, milestones at day 30/60/90, month 6 and 12 with done-tests, resources, dependencies with dates, decisions required by ID, lead and lag measures (definitions left to kpi-architecture), top two risks with mitigations already in the milestones, review cadence. Interim owner named where the role does not exist; appointment is a dated milestone. Owner and sponsor sign; changes go through the decision log. Test: what exists at day 90 that does not today, and who is accountable if not?

  4. RAPID for seam decisions (references/templates.md §5). List year-one decisions (15–30). Chart only high-consequence ones on a seam (centre vs unit, function vs function, global vs local, inside vs partner): four to eight. Delegate the rest in writing. State each as a question with finite answers. Assign in order: one D, a person never a committee (two claimants means their common boss, for this decision only); R with standing to get input from the A's; A only where formal sign-off is genuinely required (legal, regulatory, safety, capital, a margin floor), everyone else gets I; I limited to people holding facts the R lacks; P named. Push D to the lowest level with both information and accountability. Deadline and forum slot per decision; decision log opened with the same IDs. Expect resistance from executives offered I instead of A and from a CEO asked to hold a D alone; input is consultation, agreement is veto, six vetoes is not a decision. Test: every D is one named person; every A has a sign-off that makes it a veto.

  5. 90-day plan (references/templates.md §6). Four blocks of three weeks. Weeks 1–2: governance set-up (programme lead, charters signed, twelve-month cadence calendar, decision log) and the style lever (what the CEO changes about their own review and calendar) before any org announcement. Charted decisions in their due block, preparation the block before. Charter milestones at 30/60/90. Every line a deliverable with a done-test and one owner. Day-90 review as a line with its own agenda: initiatives vs milestones, value ledger (identified, committed, realised), every decision closed or re-dated, 7-S re-scored where the plan claimed to move an S. Test: strike lines beginning "develop", "explore", "align", "engage"; if less than two-thirds survives, rewrite.

  6. Cadence and follow-through (references/templates.md §7). Four forums with chair, attendees, frequency, standing agenda, written output and deadline: weekly initiative stand-up (owner, 30 min); fortnightly transformation office review (CEO, 90 min: RAPID decisions closed, milestones, dependencies, ledger); monthly CEO operating review (CEO, 2 h: each owner brings one problem, customers, P&L vs plan); quarterly strategy and people review (CEO, half day: value assumptions, 7-S re-score, talent review of critical roles, action on non-performers). Board reporting named as one line only. Follow-through rules the CEO adopts personally: commitments note within 24 hours; every review opens with prior commitments, misses re-dated in the room with a reason; status as numbers against milestones, never colours; no-problems-twice gets asked why; bonus pool linked through the talent review. Test: if the CEO delegated every forum to the programme lead, would the organisation notice?

  7. Package and bound. Open the value ledger stub for kpi-architecture. No risk register, scorecard, OKRs or roadmap in this document; name where they go and stop.

Output

The binding constraint and the first two weeks in the first 150 words. Then, each once, 2,000 to 3,500 words:

  1. Required-behaviour list
  2. 7-S scoring table and alignment summary
  3. Initiative portfolio table reconciled to value
  4. Initiative charters (one page each)
  5. RAPID chart and opened decision log
  6. 90-day plan
  7. Cadence table and follow-through rules
  8. Value ledger stub

No method vocabulary, framework authors, skill names or the worked example's client in the deliverable. Full example: references/worked-example.md.

Quality bar

Run silently; fix, do not report.

  1. Every behaviour line names a change someone would resist.
  2. Every S has evidence and a source; every 1–2 score has a plan line or a gate.
  3. Portfolio value reconciles to the driver model; three to six initiatives.
  4. Every charter has one named owner and done-tests on every milestone.
  5. Every charted decision has one D, few A's, a deadline and a forum.
  6. Weeks 1–2 change the CEO's own review before any org announcement.
  7. Two-thirds or more of plan lines are deliverables with done-tests.
  8. The CEO chairs the operating forums.
  9. No risk register, scorecard, OKRs or roadmap inside the document.
  10. No leaked method vocabulary.

Anti-patterns

  • Diagnosing hard S's only; soft S's as commentary.
  • Charters with committees as owners, or milestones without done-tests.
  • A's handed out as courtesy; a D shared by two executives.
  • Org announcement before the CEO changes their own review.
  • Plans of verbs: develop, explore, align, engage.
  • Cadence delegated to the programme lead; status reported in colours.
  • A twelve-initiative portfolio the CEO cannot review.

Hand-offs

References

  1. Frameworks: the intellectual foundation of execution planning

    3,629 w
    references/frameworks.md7 sub-sections
  2. Templates and checklists for execution planning

    1,783 w
    references/templates.md11 sub-sections
  3. Worked example: Marlow Industrial Supply, from chosen strategy to a running programme

    4,113 w
    references/worked-example.md9 sub-sections