On Monday, explain the company's strategy, its trade-offs and its risks to a colleague without slides, and note where you falter.
Days 0–30Phase 1 · Diagnose and commit
Find out how much of the strategy survives the trip from boardroom to front line today.
- Sample front-line staff across levels and regions and score their restatement of the top priorities against the board's version.
- The CEO explains the strategy, its trade-offs and risks to a small group without slides and notes where they falter (Master the source).
- Collect current strategy messages and mark the jargon a front-line employee would need translated.
- Choose one unit, and the working languages its teams use, for the pilot.
Deliverable: A strategy recall baseline by level and region, and a jargon list.
Gate: Baseline recorded for every KPI, the CEO has explained the strategy without slides, and one unit head has agreed to pilot.
Days 31–90Phase 2 · Pilot and prove
Prove that restating strategy in a unit's own language raises understanding without diluting substance.
- The unit head restates the strategy in the team's own language, and the CEO checks it for meaning and trade-offs (Translate to the people's language).
- Test the restatement with front-line staff who were not involved in writing it, sceptics included (Test with the front line).
- Revise every message that fails the test and log the revision.
- Run a stakeholder review on one plan, covering rivals and critics, and write down the hard choices it still requires (Pasayadan).
Deliverable: A tested and revised unit restatement and one completed stakeholder review.
Gate: Restatement accuracy in the pilot unit has improved against baseline, messages have been revised after tests with unfamiliar or sceptical audiences, and the stakeholder review records hard choices alongside goodwill.
Days 91–180Phase 3 · Embed and scale
Make restatement and stakeholder review standard for every unit and every major plan.
- Require each unit head to restate the strategy in each planning cycle.
- Train managers with internal communications to translate and test messages themselves.
- Make a documented stakeholder review a condition for announcing any major plan.
- Translate restatements into the regional languages teams actually work in.
Deliverable: A restatement library by unit and language, and a stakeholder review template attached to major plans.
Gate: Every unit has a tested restatement on file, and every major plan announced in the period went through a documented stakeholder review.
Month 7 onwardsPhase 4 · Sustain and renew
Keep translation faithful to the source as the strategy changes.
- The CEO re-reads the full strategy and its reasoning each quarter and checks restatements against it.
- Repeat the recall test across levels, regions and languages each year.
- Refresh restatements whenever the strategy shifts.
- Review a sample of messages for dilution, checking that trade-offs and risks survived.
Deliverable: An annual translation quality report.
Gate: Restatement accuracy holds across regions after a strategy change, and the revision log shows testing is still finding gaps.
Governance
sponsor: The CEO, because only the author of the strategy can judge whether a translation keeps its meaning.
lead: The head of internal communications, working with the strategy team.
forum: Monthly in the leadership meeting for message revisions; quarterly at the board for restatement accuracy and stakeholder review coverage.
decision_rights: The lead can send back any restatement that fails front-line testing; changes to the substance of the strategy, and any decision to proceed with a plan despite a hard stakeholder finding, go to the CEO.
Cadence
Weekly: Managers link one piece of the week's work to a strategic priority, in the team's own words.
Monthly: A front-line test session where staff say what the strategy changes in their work that month.
Quarterly: The CEO returns to the full strategy and checks restatements against it, and the board receives the translation KPIs.
Annually: A recall survey across levels, regions and languages, followed by a refresh of the restatement library.
startup
The founder explains the strategy without slides at the all-hands and asks each person to say it back in their own words. Testing happens in conversation each month while everyone still works closely together.
scaleup
Unit heads write restatements in their teams' language, and internal communications tests them with front-line staff before release. Major plans carry a short stakeholder review that names who gains and who loses.
enterprise
Restatements are maintained in each working language and region, and recall is surveyed across the group every year. The board asks for stakeholder reviews on major plans and checks that front-line understanding matches what was presented to it.