The first 90 days

Written by a person. Last read by a person on 2026-09-07, 1 day ago. Its facts were checked by the eval suite on 2026-09-07.

You want the stance the documents are written from, or you are judging a 90-day plan.

Scenario-based sample. Halden Systems is invented, and so is every figure about it.

The entry plan for a director newly hired into Halden Systems.

Bottom line. The first 90 days end with a funding decision made and procurement in flight, not with a signed contract. 10 days to find out what is true, 20 to gather evidence, thirty to build the case, thirty to ask for the money.

Why a newly hired director writes this

These documents are written by somebody hired into the situation, not by an observer describing it. That frame is worth adopting for three reasons, and the third is the one that matters.

It is the frame a director interview already uses. Some version of "what would you do in your first 90 days" is asked in nearly every one, and answering it with artifacts rather than assertions is a better answer than the question expects.

It sequences the set. Ten documents with no narrator arrive in an arbitrary order. With a start date they arrive in the order somebody would actually produce them, and the sequence is itself an argument about how this work should be done.

It also answers the question the set would otherwise raise. A reader looking at a strategy document with a survey of 1,237 people in front of it will ask where that came from and who authorized it. The answer is that it was the first month's work, and that a proposal written before it would have been an opinion.

Ten, thirty, sixty, ninety

The usual plan has three phases. This one has four, and the extra phase is at the front.

Days 1 to 10 produce nothing that proposes anything. The output is a written list of what is not yet known. The sponsor, the VP of Engineering, all 9 site directors, and a sample of the population. Read the prior rollout materials, the ticket queue, and every line of regional training spend, and ask each site director what they bought and why without implying it was wrong, because it was not.

10 days is deliberately short. A plan produced inside it is one that arrived in the new director's luggage, and the fastest way to lose the 5 site directors who decide whether this program reaches their people is to arrive holding the answer.

Days 11 to 30 are evidence, and it arrives on day fifteen.

A thirty-day survey is a hard thing to ask a sponsor for, and it was the wrong design. Here is the replacement.

The pilot starts on day 11 at 1 site with a local expert and one without. It already exists and costs nothing to begin, and that comparison is what the scaling case will need.

The long instrument is a second pass. It deepens the picture rather than gating it.

What does not happen here is committing to a number in front of the Chief Operating Officer before the pulse lands. The cost of guessing early is that the evidence then has to agree with the guess.

Days 31 to 60 are the case. The survey closes on day 41; analysis and personas to day 46; the strategy document to day 53; the project plan to day 58. Early pilot data arrives across the same period and goes into both.

No hiring. The shape of the team follows from the strategy and the procurement decision, and a requisition opened in month two is a guess that gets defended for two years.

Days 61 to 90 are the ask, with procurement started and not finished. Deck to day 64, readout around day 65, statement of work to day 70. The request goes to vendors around day 70 with responses due near day 100, and the evaluation weights are fixed and written down before any submission is opened. The scaling proposal completes by day 76.

The two things this plan will not claim

It does not close a vendor contract. A response window is 40 days and reference calls take longer than that. A ninety-day plan that ends with a signature tells anybody who has run a procurement that the writer has never run one, and it is the most common way these plans give themselves away.

It does not centralize regional budgets in year one. Roughly $410,000 a year is being spent twice across 9 sites, and it is the most obvious saving in the case. It is also the one that would cost the program the regional site directors, who are buying locally because waiting for a central answer costs them more. They stop when something arrives faster than their own procurement does, and not before.

Both refusals are in the plan on purpose. A ninety-day plan is read for what it promises, and the two most informative lines in one are usually the promises it declines to make.