Most 30/60/90-day plans are written backwards. They open with a flurry of new initiatives — a platform to stand up, a team to hire, a tool to roll out — designed to show momentum to a CEO who wants to see action. By Day 30 there is a slide full of green checkmarks and a leadership team that feels busy. And almost nothing of consequence has changed, because the plan never addressed the one question that determines whether any treatment will work: what should we stop?
A prescription that only tells you what to start is not a prescription. It is a wish list. A real prescription, like a real medical one, begins by removing what is making the patient worse before adding anything new. The first thing a good doctor does is take you off the drug that is causing the problem.
So here is the test for any 30/60/90 plan a CEO is handed: if Day 30 is full of new things to do and contains nothing the company has decided to stop, the diagnosis underneath it was either skipped or ignored.
Day 0–30 is for stopping, not starting
The first thirty days are the most counterintuitive, because the instinct — and the pressure — is to launch. Resist it. New initiatives layered on top of an undiagnosed system simply add load to the thing that is already failing. The job of the first month is the opposite: subtraction, baseline, and cadence.
- Stop the wrong investments. Almost every growth-stage company is funding at least one initiative that is actively working against the diagnosis — a migration heading the wrong way, a feature factory producing complexity faster than value, a tool nobody adopted. Stopping these frees capacity and money before a single new rupee is spent.
- Set the baseline. You cannot prove a treatment worked if you never measured the disease. Day 30 should establish the small set of honest metrics — technical and operational, not vanity — against which the next sixty days will be judged.
- Establish the leadership cadence. The decision-rights, the review rhythm, the single owner per outcome. Most technology diseases survive because no cadence exists to surface and resolve them. The cadence is itself a treatment.
What a CEO should actually see on Day 30 is not a launch. It is a shorter list than the company started with, a clear baseline, and a functioning rhythm of decisions. That is real progress, even though — perhaps because — it looks like restraint.
Stop / Start / Continue / Delay: the structure of an honest prescription
The reason most plans skip the hard part is that they lack a structure that forces the four decisions a real prescription must make. The Growth Accelerator Rx™ sorts every existing and proposed investment into one of four buckets, and the discipline is in being honest about all four:
- Stop. Things actively making the disease worse, or consuming capacity the treatment needs. The hardest and most valuable column — and usually the emptiest in a weak plan.
- Start. The foundational moves the diagnosis demands. Few, deliberate, and sequenced — not a buffet.
- Continue. The things already working, explicitly protected so the change programme doesn't accidentally kill them.
- Delay. Good ideas that are simply out of order. Naming them as delayed — not rejected — is what keeps the team disciplined without losing the idea.
A prescription is defined as much by its Stop and Delay columns as by its Start column. Anyone can add. The discipline is in what you remove and what you refuse to do yet.
The Delay column deserves special attention, because it is where ambition goes to be sequenced rather than killed. Most companies fail not because they pick bad initiatives but because they run all of them at once. Delay is how you protect the treatment from the organisation's own enthusiasm.
Days 31–60 lay the foundation
Only once the wrong things have stopped and the baseline exists does building begin — and even then, foundations before features. The second month is where the few "Start" items are executed in dependency order, not preference order.
This is the layer where structural fixes go in: the service boundary that unblocks three teams, the data contract that stops the recurring defect at its source, the platform consolidation that lowers the cost floor. None of these are visible to a customer. All of them are the ground the visible wins will stand on. A CEO should expect Day 60 to feel quieter than Day 30 felt — the loud decisions are made, and the patient, structural work is underway.
The temptation in this window is to declare victory because something shipped. Hold the line. The job of Days 31–60 is not to produce a demo. It is to make the next sixty days cheaper and faster than the last sixty were — to bend the cost of change itself.
Days 61–90 compound
If the first sixty days were done with discipline, the final thirty are where the prescription starts to pay for itself. Because the wrong investments were stopped, capacity is now free. Because the foundations are in, new work moves faster and breaks less. The same team produces more, not through heroics, but because the structure stopped fighting them.
This is the compounding window, and it is the proof that the diagnosis was correct. You should see velocity rising without headcount rising, defects falling at the source rather than being patched, and the cost line beginning to flatten. These are the signatures of treatment working — and they only appear because the first thirty days were spent stopping, not starting.
A prescription is the bridge between a diagnosis and a treatment, which is why it sits at the centre of the three frameworks. Skip the Stop column and you do not have a prescription — you have a louder version of the disease. The CEOs who get real results are the ones who can look at Day 30 and feel comfortable seeing fewer things happening, done deliberately, rather than many things happening, done on hope.
On Day 30, demand to see what your team has stopped, the baseline they've set, and the cadence they've established — if the plan is all new initiatives and no Stop column, the diagnosis was skipped.