How to prepare a 30-60-90 change program

A 30-60-90 change program turns organisational improvement into three sequential horizons: the first 30 days, the first 60 days and the first 90 days. Each horizon has a small number of observable goals, and each goal prepares the conditions for the next. The format is useful because most SME change efforts do not fail from lack of ideas. They fail from lack of sequence.

What this guide is for

A 30-60-90 program forces three disciplines at once: few things at a time, in the order in which they enable each other, with a fixed review gate before the next block is loaded.

This guide helps build and run the program without turning it into a list of wishes. It also clarifies which part should come from a proper diagnosis rather than internal improvisation.

When to use it

Use it after a diagnosis, assessment, stress test or process map that produces more improvements than the organisation can absorb at once.

Use it in the first hundred days of a new role, new ownership or new leadership mandate, when the temptation to touch everything is strongest.

Use it after an acquisition, when the integration plan risks becoming a list rather than a sequence.

Use it when the company has already seen change programs evaporate after announcements, workshops or motivational meetings. The 30-60-90 format is an operating antidote to change by declaration.

Before starting

Three checks determine the outcome more than the plan itself.

First, check the raw material. A 30-60-90 program is only as good as the diagnosis that feeds it. If priorities come only from internal opinions, the program inherits the blind spots of the people who wrote it. At minimum, triangulate priorities with people outside the top team.

Second, check bandwidth. Change is cognitive load added on top of current work. If key people are saturated, the program needs an initial relief move before asking for improvement. Without cognitive margin, the plan is a dated announcement.

Third, check sponsor and rhythm. The program needs one overall owner with protected time. Half a day per week is a reasonable minimum for a serious SME change program. It also needs a short fixed review rhythm. Without these, the program competes with urgency, and urgency wins.

Operational sequence

Step 1 — Order by dependencies, not by importance.

This is the core of the method. The common mistake is to start from what is urgent, visible or emotionally attractive. The better question is: what must already work for this intervention to take root?

Delegation requires minimum information. KPIs require clean data. Software requires a decided process. A pricing rule requires decision rights. A new role requires scope and autonomy.

Draw a simple dependency map. Even a hand-drawn map is enough. It will produce the order. It will also produce a second list as valuable as the plan: what not to do yet, with the reason written.

A program without a list of justified postponements has not selected. It has only distributed too much work across three months.

Step 2 — Load the first 30 days with foundations and one visible win.

The first block should contain two or three enabling interventions and one visible quick win.

Enabling interventions might be the RACI for the critical flow, a margin number made visible, a first delegation threshold, or a cleaned data set.

The quick win should remove a daily annoyance people recognise. It is not cosmetic. It signals to an organisation that has seen other programs die that this time something actually happens.

Step 3 — Write each goal as an observable result with owner and evidence.

Do not write “improve delegation”. Write: discount decisions up to 12% are taken by the sales manager without founder approval; the decision register is active; no bypass occurred in the last two weeks of the block.

Each goal needs three lines: observable result, single owner and evidence that will prove completion.

Limit the block. Three to five goals in total is usually enough. Every goal beyond the fifth is borrowed from the failure of the others.

Step 4 — Put gates between blocks, with stop rules.

Day 30, day 60 and day 90 are not only calendar milestones. They are gates.

At each gate, review what is done against evidence, not impressions. Decide what slips, what changes and what has been learned.

If an objective is not achieved, the next objective that depends on it must be blocked, delayed or redesigned. Dependencies still apply during execution.

Define stop rules at day zero. If an initiative fails to take hold after two blocks, it is stopped or reframed deliberately, not allowed to drift until day 120.

A program where everything is always green has probably stopped measuring.

Step 5 — Govern load during the program.

Every week, run a short progress ritual with the owners and only the current block goals. Review evidence, obstacles and one fixed question: what new demand is arriving that was not in the plan?

New urgency and new ideas will enter. The rule is exchange, not addition. If X enters, Y leaves or moves. The sponsor decides this openly.

This is WIP discipline applied to change. Violating it silently is how programs drown while remaining formally open.

Step 6 — Close day 90 with institutionalisation and a new horizon.

The final review has three jobs.

First, consolidate. Successful interventions are fixed into devices: SOP, rhythm, threshold, review, dashboard, or meeting rule. Without institutionalisation, habits pull the company back.

Second, account for the program. Compare the day-zero plan with what was achieved, including slippage. This builds credibility for the next program.

Third, decide whether to launch a new 30-60-90 or pause for absorption. Organisations do not digest continuous change indefinitely. A consolidation quarter may be the mature decision.

Expected output

The expected output is a short document: dependency map, three blocks with three to five goals each, goal-owner-evidence format, justified postponements, stop rules, weekly rhythm and gate calendar.

At day 90, the real outputs are two: goals verified against evidence, and an organisation that has regained some trust that programs here actually close.

Mistakes to avoid

Do not order by urgency or enthusiasm instead of dependency.

Do not create a list-program with twelve goals per block.

Do not start without bandwidth.

Do not skip the visible win, but do not do only visible wins.

Do not run ceremonial gates where everything is always green.

Do not add work during execution without removing work.

Do not close day 90 without institutionalising what worked.

Example

A 41-person machining company exits an assessment with fourteen improvement areas and the usual temptation to start everything.

The 30-60-90 reduces the program to eight interventions in sequence and postpones six with written reasons. The MES the founder wanted immediately is postponed because it depends on a unified order flow and actual time records. The organisation chart redesign is postponed because delegation pilots must come first.

The first 30 days include a RACI on the order flow, weekly visibility of job margin, a pilot discount delegation and one visible win: eliminating double order entry that everyone had hated for three years. The visible win is completed in nine days and buys attention for the less visible foundations.

At the day-30 gate, three of four goals are verified. Time recording is weak, so the pre-written stop rule blocks the KPI dashboard planned for day 60. The sponsor states the reason clearly: better a late dashboard than a false one.

The 60-day block is recalibrated. Time recording is simplified from four minutes to 40 seconds at the workstation, and the second delegation starts. By day 90, the dashboard runs on real data, two SOPs are institutionalised, the Monday review becomes permanent and delegation thresholds are written.

The public review shows seven objectives achieved and one delayed honestly. A second 30-60-90 starts one month later, with the MES now in scope because its prerequisites exist.

MARTRO connection

In MARTRO’s reading, the 30-60-90 is the format through which diagnosis becomes execution without losing the ordering principle: priorities by structural dependency, not by noise.

A third-party multi-role assessment can provide the difficult part: ordering priorities by evidence rather than by the blind spots of the top team. The 30-60-90 discipline then governs execution: blocks, gates, load and stop rules.

Next step

If the starting diagnosis is weak or only internal, reinforce it before planning through triangulation or a structured organisational stress test.

If the program struggles because people are saturated, address cognitive margin before adding more change.

For gates and stopping conditions, continue with stop rule.

For regression after day 90, continue with organisational hysteresis.

Frequently asked questions

Why 30-60-90 instead of a normal project plan? Because the format forces sequencing, evidence and review gates. It is short enough to create traction and long enough to test whether change is taking hold.

How many goals should each block contain? Three to five total, not per department. More usually means the company is loading change beyond its absorption capacity.

What is a good quick win? A visible, cross-functional irritation removed quickly without undermining the foundations. It should build credibility, not distract from structural work.

What happens if a day-30 goal is not achieved? Anything depending on it should stop, move or be redesigned. The gate exists to protect sequence, not to preserve the original plan.

Should the program always continue after day 90? No. Sometimes the correct next step is a consolidation period so new routines can stabilise before the next block of change.