The First 100 Days Need an Execution Architecture

Private equity has standardised the 100-day plan to the point that it is assumed rather than questioned. A new CEO arrives, a plan gets built, workstreams are named and the clock starts. Ambition is rarely the problem. The architecture required to carry it through the remaining weeks is treated as something to figure out along the way.

Why the plan survives and the system does not

A 100-day plan is a strategy document: priorities, sequencing and target outcomes. What it is not, by construction, is a governance system — a structure that determines who decides, how spend is authorised and what happens when the plan meets an obstacle nobody scoped.

Strategy answers, “What are we doing?” Execution architecture answers, “What happens when this does not go as planned?” In a 100-day sprint, something never goes as planned.

Operating Partners understand why value-creation discussions have shifted from the plan itself to who owns delivery. But ownership without architecture is only a name attached to a slide. It does not show whether the executive has real decision rights, visibility over the inherited cost base or an internal owner for the capability being built.

Mapping the 100 days to The S.T.E.P. Execution Architecture™

The S.T.E.P. Execution Architecture™, developed by Stefano Rosa Rosso, is not a parallel plan. It is the operating layer beneath the 100-day plan.

Days 1–30 — Strategy

Define explicit boundaries: what will not be pursued in this window, and which two or three metrics the leadership team will be held to. Most plans list priorities. Few list exclusions. Yet exclusions protect the plan from dilution when quarter-end pressure arrives.

Days 20–60 — Trust

Decision rights and escalation paths must be explicit before the first disagreement. This overlaps deliberately with Strategy: a boundary that nobody has authority to enforce is only a suggestion. The phase tests whether new leadership possesses the mandate assumed in the deal thesis, not merely the title shown on the organisation chart.

Days 30–80 — Economics

The supplier and spend base inherited at close is rarely as visible as assumed. This window challenges demand, re-anchors contracts to outcomes and identifies savings that can self-fund the remaining transformation. Treated as compliance rather than a source of capital, this phase is a common reason budgets run out before month six.

Days 60–100 — Performance

The final phase determines whether the plan becomes durable or reverts to dependency on the transformation team. Internal owners must demonstrate what works, which capability now sits inside the organisation and how the next 100 days will be governed without restarting from zero.

The cost of skipping a pillar

Skip Strategy and the plan fills with activity disconnected from the value-creation thesis. Skip Trust and every decision that matters gets relitigated when it meets resistance. Skip Economics and the transformation spends capital it does not have because savings were never identified or banked. Skip Performance and the plan succeeds on paper but starts unwinding when the external team leaves.

None of those failures necessarily appears as a missed milestone. All eventually appear as a re-scoped programme at month six.

What Operating Partners should ask differently

The standard question at day 100 is, “Did we hit the plan?” The more useful question is, “Which pillar was treated as an afterthought?” In portfolio companies where the programme stalls, the answer is often Trust or Performance — the two dimensions that fit least neatly on a delivery tracker.

An execution architecture does not replace the 100-day plan. It determines whether the plan is still standing on day 101 as a system the organisation can run without the transformation team in the room.

FAQ