The mechanics do not change at all. What changes is that the plan now crosses boundaries, and every boundary is a place a commitment can sit unowned for a quarter without anyone noticing.
Scale does not make execution harder by making the work harder. It makes it harder by multiplying the seams.
The three things that actually change
The plan crosses boundaries. In a team of twenty, almost every commitment sits inside one group and one person obviously owns it. At two hundred, the commitments that matter most are the ones spanning functions, and those are precisely the ones where ownership evaporates. Sull, Homkes and Sull made this point in Harvard Business Review in 2015 and it is the single most reliable finding in the field: cross-unit commitments fail at a far higher rate than hard ones.
Nobody can see all of it. Below a certain size the leadership team genuinely holds the whole plan in their heads. Above it, they hold a summary of it, and the summary is assembled by someone from reports that are a fortnight old. Decisions get made against a picture that was true a fortnight ago.
The chase becomes arithmetic. Fifteen commitments is a person sending a few messages. Eighty commitments across six teams and three sites is a part time job, and it is the first thing dropped when that person gets busy. The system then decays without anyone deciding to stop it.
What does not change
| Still true at any size | Why people assume otherwise |
|---|---|
| One named owner per commitment | At scale it feels natural to assign to a function, which means nobody |
| A measure that can go down | Bigger organisations report more and measure less |
| Fortnightly review on commitments | Scale is used to justify monthly, which guarantees stale data |
| Three to five company priorities | Size is treated as permission to have fifteen |
| Write the decision, not the discussion | More attendees produce longer notes and fewer decisions |
The priorities row is where most large plans go wrong. The argument is always that a bigger organisation has more to do, which is true and irrelevant. The constraint is recall, not capacity. If nobody can name the company priorities unprompted, they are not steering anything, whatever the headcount.
The handoff is the unit of failure
The practical move that matters most at scale, and that almost nobody makes: name an owner for the handoff, not only for the two ends.
When marketing owes sales a qualified list, there is an owner of the list and an owner of the follow up. Nobody owns the moment it passes between them, which is the exact point where things sit for three weeks. The same pattern repeats at every seam in the business, and it is why cross-functional commitments stall in ways that are invisible in a status report, because both ends are honestly reporting that their part is fine.
Name the seam. Give it a person and a date. It costs nothing and it removes the most common failure in large plans.
Cascade less than you think
The instinct at scale is to push every company goal down through every level until each person has a version of it. This produces a large number of commitments that nobody chose, and volume is what makes a set of priorities unmemorable.
The pattern that works better: cascade the few company commitments as they are, and let each team write its own contribution in its own words. The wording matters more than it sounds. An owner who drafted the sentence can tell you what it means in week seven. An owner who inherited it reads it back to you.
Where the tooling line sits
A plan can be run on a spreadsheet at almost any size. What cannot be run on a spreadsheet at scale is keeping it current, because currency depends on collection and collection is the thing that breaks.
That is the specific job Empiraa GPS does for established organisations whose plan crosses several teams or sites: owners and measures in one place, progress gathered from where the work happens rather than chased, and a stalled commitment surfaced while there is still time to act on it. Advisory firms running plans on behalf of client organisations use GPS for Professional Services, where each client has their own workspace and the firm sees every engagement at once.
Related reading: why strategy execution fails, and strategy execution best practices that survive a quarter.
Strategy execution has a definition on this site. See strategy execution software for what the category does and who should not buy one.
