Reference
Frameworks: the intellectual foundation of execution planning
Part of the Execution Planning skill · loaded on demand from SKILL.md
Read this when you need the original method in depth: what each framework claims, how its authors built it, and where the judgment lives. SKILL.md gives the operating procedure; this file gives the reasoning behind it.
Contents
- Why execution planning exists as a separate discipline
- McKinsey 7-S (Waterman, Peters and Phillips, 1980)
- Bain RAPID decision rights (Rogers and Blenko, 2006)
- Execution as a discipline (Bossidy and Charan, 2002)
- How the three combine into one method
- Attribution notes and what was verified
1. Why execution planning exists as a separate discipline
Strategy work ends with a choice. Execution planning starts with the observation, made independently by all three sources below, that most chosen strategies do not get implemented as intended. Waterman, Peters and Phillips open by quoting a Fortune estimate that "as many as 90 percent" of carefully planned strategies do not work. Rogers and Blenko begin with a decision that never gets made because two functions both believe they own it. Bossidy and Charan describe CEOs who mistake a well-argued strategic plan for a commitment the organisation has actually made.
The three diagnoses are different and complementary:
| Source | Why strategies fail | What the remedy looks like |
|---|---|---|
| 7-S | The organisation's other six elements are still tuned to the old strategy, so behaviour reverts | Diagnose all seven elements together and change them in concert |
| RAPID | Nobody knows who decides, so decisions stall, get revisited, or are made by default | Assign explicit roles for the handful of decisions that matter |
| Execution | Leaders treat strategy, people and operations as separate rituals and do not follow through | Link the three processes, run them personally, and close every loop |
An execution plan that uses only one of these produces a recognisable failure. A plan built only on 7-S is a diagnosis without an engine. A plan built only on RAPID is a governance chart nobody runs. A plan built only on Bossidy and Charan's cadence produces a well-run set of meetings driving initiatives the organisation cannot absorb. The method in SKILL.md sequences them: diagnose (7-S), charter and assign (initiatives and RAPID), then run (cadence and follow-through).
2. McKinsey 7-S (Waterman, Peters and Phillips, 1980)
Provenance
The framework was developed inside McKinsey's San Francisco office from 1977, when managing director Ron Daniel asked Tom Peters to look at organisational effectiveness and implementation, the areas where the firm's strategy work kept failing in practice. Robert Waterman, Peters and Julien Phillips published it as "Structure Is Not Organization" in Business Horizons (volume 23, issue 3, June 1980, pages 14 to 26). Richard Pascale and Anthony Athos, who were working with the McKinsey team, shaped the alliterative naming and the interconnected diagram, and used the same model in "The Art of Japanese Management" (1981). Peters and Waterman then built "In Search of Excellence" (1982) on it. The seventh S was originally "superordinate goals" and was later renamed "shared values"; the two terms are interchangeable in practice.
The seven elements as the authors defined them
| Element | The authors' sense of it | What to look for in a diagnosis |
|---|---|---|
| Strategy | The actions a company plans in response to, or in anticipation of, changes in its external environment; how it intends to improve its position against competitors | Is the chosen strategy specific enough to be translated into unit-level targets? Do the top 30 people describe it the same way? |
| Structure | How tasks are divided and, more importantly, how they are coordinated: the organisation chart plus the coordinating mechanisms around it | Who owns the customer, the P&L, the product? Where does the new strategy's critical activity sit, and does that unit have the authority it needs? |
| Systems | All the procedures, formal and informal, that make the organisation go day by day and year by year: budgeting, planning, reporting, compensation, training, information systems | What does the incentive plan actually pay for? What does the monthly review actually review? Systems are where stated intent gets silently overridden |
| Style | How leaders spend their time and what they symbolically reward; the authors' point is that the organisation reads a leader's priorities from calendar and behaviour, not from statements | What does the CEO's calendar show? What gets celebrated? How is conflict handled: surfaced or smoothed? |
| Staff | The people in the organisation, and especially how the firm develops, socialises and deploys its managers over a career | Do the people who must run the new strategy exist? Are they in the seats? Is the pipeline being built? |
| Skills | The distinctive capabilities of the organisation as a whole, what it does best; the authors stress that a discontinuity in strategy often requires capabilities the firm has never had | Which two or three capabilities does the strategy assume? Are they present at the required scale, or only in a few individuals? |
| Shared values (superordinate goals) | The guiding concepts, often unwritten, that go beyond formal mission statements: the ideas around which the business is built | What do people say the company is for, when the slide deck is off? Does the new strategy fit or fight that? |
The authors divide the seven into "hard" S's (strategy, structure, systems: tangible, documentable, changeable by decision) and "soft" S's (style, staff, skills, shared values: less visible, slower to move, and in practice the ones that decide whether a change holds). The paper's argument is that consultants and executives over-attend to the hard three because they are easier to change, and that this is why strategies fail.
The four ideas the diagram conveys
The authors say the framework carries four messages:
- Multiplicity. Effectiveness depends on at least seven variables, not on strategy and structure alone.
- Interconnectedness. It is "difficult, perhaps impossible" to make progress in one area without progress in the others. Change one S and the other six pull it back.
- No obvious starting point. The diagram has no hierarchy. In one situation the driving variable is skills; in another it is systems. The diagnosis, not the model, tells you where to start.
- Alignment as the condition for change. Real energy to redirect an institution appears only when all seven are aligned. Partial alignment produces partial, and usually temporary, change.
The mechanism
7-S works because it treats an organisation as a system in equilibrium. Each S has been tuned, over years, to fit the others. A new strategy is a perturbation; the six untouched elements act as a restoring force. A branch-based distributor that announces a national key-account strategy but keeps branch P&Ls (structure), branch gross-profit bonuses (systems), and a CEO who celebrates branch heroes (style) will find, within two quarters, that key accounts are still being served branch by branch. Nothing was sabotaged; the system simply returned to its stable state.
The corollary for method: assess hard and soft together and change them in concert. Rate each S against the chosen strategy, not against "good practice" in the abstract, and treat the lowest-scoring soft S as the binding constraint on how fast the hard S's can be changed.
Getting evidence for the soft S's
The soft S's are scored badly when the evidence is the consultant's impression. Four sources produce evidence a partner will accept:
- Structured interviews, 15 to 25, across levels. Ask the same six questions of everyone ("what is this company for", "what does the CEO spend time on", "what gets you a bonus", "who decides X", "who here can do Y", "what happened the last time head office launched a programme") and count the answers. A phrase that appears unprompted in 17 of 22 interviews is evidence; a phrase the consultant heard once is not.
- The leader's calendar for the last quarter, coded by who they met and what they reviewed. This is the most reliable measure of style, because it is behaviour rather than intent.
- The compensation plan and the last two review decks, read for what they actually pay for and actually inspect.
- A count of named individuals who hold each strategy-critical capability at the level required. "We have good people" is not a skills assessment; "three people can design a site inventory programme, two of them in Ohio" is.
Where 7-S is weak
The framework is a diagnostic lens, not a change method. It says nothing about sequencing, ownership, or cadence, which is why this skill pairs it with RAPID and with Bossidy and Charan. It also invites a common error: producing seven paragraphs of description and calling it a diagnosis. The fix is scoring against the strategy and forcing a statement of the two or three misalignments that matter.
3. Bain RAPID decision rights (Rogers and Blenko, 2006)
Provenance
Paul Rogers and Marcia Blenko of Bain and Company published "Who Has the D? How Clear Decision Roles Enhance Organizational Performance" in Harvard Business Review, January 2006. Bain's later book "Decide and Deliver" (Blenko, Mankins and Rogers, 2010) extends the method. RAPID is a Bain trademark; the letters are a mnemonic, not the order in which the roles act.
The five roles
| Role | What the holder does | Rules of thumb from the article |
|---|---|---|
| Recommend | Gathers input, analyses options, consults stakeholders, and proposes a course of action. Does most of the work | One person or one team owns the recommendation; the R must actively seek input rather than wait for it |
| Agree | Reviews the recommendation and must sign off before it goes to the decider. Holds a veto. Negotiates with the R to resolve concerns; if they cannot agree, the issue escalates to the D | "Watch for a proliferation of A's". Each A is a veto point; too many and the process gridlocks. Assign the A only where a function's formal sign-off is genuinely required (legal, safety, regulatory, sometimes finance) |
| Perform | Executes the decision once made | Often the same people as the R; assign P explicitly so execution is not assumed |
| Input | Consulted for facts and feasibility. Their input must be sought, but it is not binding | "Avoid assigning too many I's". Input roles are where consultation inflates into consensus-seeking |
| Decide | The single point of accountability. Brings the decision to closure, resolves impasses between R and A, and commits the organisation to act | "Ensure only one person has the D". A committee cannot hold the D. If the D is held at the wrong level (too high, and decisions queue; too low, and they get revisited) the chart is wrong |
The four bottlenecks
The article observes that decisions stall predictably at four organisational seams:
- Global versus local: which decisions belong to the centre and which to the country or region.
- Centre versus business unit: what corporate owns versus what the unit owns.
- Function versus function: marketing versus product development on features, sales versus operations on service levels, and so on.
- Inside versus outside partners: decisions shared with franchisees, JV partners, outsourcers, distributors.
Most of the decisions that matter in an execution plan sit on one of these seams, which is why the RAPID chart is worth building for them and not for routine decisions.
The seven principles
Rogers and Blenko close with principles that the method in SKILL.md turns into checks:
- Some decisions matter more than others. Chart the few that do.
- Action is the goal. A decision that does not result in action is not a decision.
- Ambiguity is the enemy. Roles must be unambiguous, and everyone must know them.
- Speed and adaptability are crucial. Roles should let decisions be made fast and revised when facts change.
- Decision roles trump the organisation chart. The D need not sit with the most senior person.
- A well-aligned organisation reinforces roles through incentives, information flows and rituals.
- Practising beats preaching. Involve the people who will hold the roles in designing them.
The mechanism
RAPID works by separating the right to be heard from the right to block from the right to close. Most organisational gridlock comes from conflating those three: anyone consulted feels entitled to block, and anyone who can block feels entitled to decide. Naming one D removes the ambiguity about who can end the argument; limiting A's removes veto points; separating I from A tells consulted parties that their view will be taken seriously but will not stop the decision.
The common failure modes
| Failure | What it looks like | Fix |
|---|---|---|
| Two D's | Two executives each believe they decide; the decision is made twice or never | Name one D; if the two cannot agree who, the D is their common boss, for this decision only |
| Committee D | "The executive committee decides"; nobody is accountable | Name the chair as D and the members as A or I |
| A inflation | Six functions hold a veto; the R spends months negotiating | Demote each A to I unless a formal sign-off is legally or contractually required |
| I inflation | Forty people consulted; the R cannot synthesise; consultation becomes a proxy vote | Limit I to people with facts the R does not have |
| R without authority to recommend | The R is too junior to get input from the A's | Raise the R one level or give the R an explicit mandate from the D |
| D at the wrong level | CEO decides on discount approvals; decisions queue for weeks | Push the D down to the lowest level with the information and the accountability |
| Roles assigned, process not run | The chart is published, but the R never presents, the D never closes | Tie each charted decision to a dated slot in the cadence |
4. Execution as a discipline (Bossidy and Charan, 2002)
Provenance
Larry Bossidy (former chairman and CEO of Honeywell and AlliedSignal, and a long-serving GE executive) and Ram Charan, with Charles Burck, published "Execution: The Discipline of Getting Things Done" in 2002 (Crown Business). It is a practitioner's book rather than a research study, and the method reflects the operating-review culture Bossidy ran at AlliedSignal.
The three core points
The book's first chapter states three points, which the rest of the book elaborates:
- Execution is a discipline and integral to strategy. A strategy that cannot be executed is not a strategy; the test of a strategic plan is whether the organisation can actually do it.
- Execution is the major job of the business leader. It cannot be delegated to a chief operating officer or a programme office; the leader must be personally engaged in the substance.
- Execution must be a core element of culture. Culture changes through what the authors call social operating mechanisms: the recurring meetings, reviews and dialogues in which behaviour is shaped, not through values statements.
The book's Part II then names three "building blocks" of execution: the leader's seven essential behaviours (below), creating the framework for cultural change (the social operating mechanisms), and the job no leader should delegate, which is having the right people in the right place. The three core points and the three building blocks are different lists; do not conflate them in front of a client who knows the book.
The seven essential behaviours of the leader
| Behaviour | What it means in an execution plan |
|---|---|
| Know your people and your business | The leader engages in the detail of the initiatives, not just the summary; the review asks specific questions |
| Insist on realism | Plans are built on honest baselines and honest capacity; the review surfaces problems rather than reporting green |
| Set clear goals and priorities | A few priorities, stated so that everyone can repeat them; this is why the 90-day plan has three to five initiatives, not fifteen |
| Follow through | Every meeting ends with who does what by when, and the next meeting opens by checking it |
| Reward the doers | Differentiate compensation and recognition by delivery, not by effort or seniority |
| Expand people's capabilities | Coaching in the review, not just judgment; the review is where capability is built |
| Know yourself | The leader's own style is part of the system (which is where this framework meets 7-S "style") |
The three core processes
The book's structural claim is that a business runs on three processes and that execution fails when they are run separately.
| Process | What it must produce | Links to the others |
|---|---|---|
| People | The right people in the right jobs; a leadership pipeline; honest assessment; action on non-performers | It answers "who will execute the strategy?" and is therefore the first process to review when a strategy changes |
| Strategy | A plan that states where the business is going and how, tested against what the organisation can actually do; the strategy review asks whether the assumptions are realistic, whether the competition is understood, and whether the organisation has the capability to execute | Feeds targets to the operations process and capability requirements to the people process |
| Operations | An operating plan that breaks the strategy into short-term targets (earnings, revenue, margins, cash) with the programmes to hit them, built with explicit assumptions and contingency plans; reviewed quarterly and adjusted | The budget is an output of this process, not the process itself |
The execution planning method inherits from this: the initiative charters are the bridge from the strategy process to the operations process, and the "staff" and "skills" rows of the 7-S diagnosis are the bridge to the people process.
Follow-through and the social operating mechanism
Bossidy's practical discipline is simple and widely ignored: after every review, a written note goes to participants stating the decisions made, the commitments, the owners and the dates; the next review begins with those commitments. He treats the absence of follow-through as the most common cause of execution failure, because it teaches the organisation that commitments in meetings are optional.
The second discipline is candid, fact-based dialogue in the review. The review is not a presentation; it is a working session in which the leader asks questions, assumptions are tested, and disagreements are surfaced. A review in which every initiative reports green is a failed review.
The mechanism
Execution as a discipline works because it converts strategy into a set of recurring, dated, personally attended events with written outputs. Organisations do what is inspected. If the CEO reviews the initiatives monthly, asks specific questions, and checks last month's commitments, the initiatives get done. If the CEO delegates the review to a programme office, the organisation learns that the initiatives are the programme office's problem.
5. How the three combine into one method
| Stage in SKILL.md | Framework doing the work | What it prevents |
|---|---|---|
| Translate the strategy into required behaviours | 7-S (strategy row) and Bossidy's "insist on realism" | Vague strategy that cannot be diagnosed against |
| 7-S diagnosis with scores | 7-S | Changing the hard S's alone; missing the binding soft-S constraint |
| Initiative definition and charters | Bossidy and Charan (strategy-to-operations bridge; clear goals and priorities) | Fifteen initiatives with no owners |
| RAPID chart for the decisions that matter | Rogers and Blenko | Initiatives stalling on decisions nobody owns |
| 90-day plan and cadence | Bossidy and Charan (operations process; social operating mechanisms) | Plan without rhythm; reviews that report rather than decide |
| Follow-through mechanisms | Bossidy and Charan (follow through; reward the doers) | Commitments that evaporate between meetings |
6. Attribution notes and what was verified
- 7-S: Waterman, R. H., Peters, T. J. and Phillips, J. R., "Structure Is Not Organization", Business Horizons, 23(3), June 1980, pp. 14 to 26. Verified: the seven elements, the original "superordinate goals" naming, the hard/soft split (strategy, structure, systems hard; style, staff, skills, shared values soft), and the four ideas conveyed by the diagram. The "90 percent" figure is a Fortune estimate the authors quote in their opening, not their own finding and not a measured statistic; do not present it as research.
- RAPID: Rogers, P. and Blenko, M. W., "Who Has the D? How Clear Decision Roles Enhance Organizational Performance", Harvard Business Review, January 2006. Verified: the five role definitions, the "only one D", "watch for a proliferation of A's" and "avoid too many I's" rules, the four bottlenecks, and the seven closing principles. RAPID is a registered trademark of Bain and Company.
- Execution: Bossidy, L. and Charan, R., with Burck, C., "Execution: The Discipline of Getting Things Done", Crown Business, 2002. Verified: the three core points of chapter 1, the three building blocks of Part II (seven behaviours; framework for cultural change; right people in the right place), the seven essential behaviours in the order given above, the three core processes and their content, and the emphasis on follow-through and candid dialogue.
- Nothing in this file cites internal McKinsey or Bain material. Where the text describes "how firms do it", it is a paraphrase of the public sources above and of general practice.