The 30/60/90 plan
Updated
BeginnerWhat you'll learn
~12 min- Name the four things that must exist by day 30: a chosen workflow with its recorded baseline, an empowered team, a named decision owner, and one obstacle to remove
- Decide at day 60 whether the pilot met its pass bar, and when it did not, record the stop-or-revise decision with its cost and reason
- Record the day-90 adoption decision as expand, revise, defer or stop, and fill the worksheet fields in order
You leave this lesson with: the filled action-plan worksheet, a printable decision record with three review dates and one named decision owner.
Why a calendar
Most of this course has been about decisions: what to test, what to ask for, which controls to keep, who to trust with room to try. A plan turns those decisions into dates. Without dates, a pilot is a project with no end, and the only decision it ever produces is to keep going.
The 30/60/90 plan is a review cadence, not a build schedule. It does not say how fast the team should work. It says when the leader looks at evidence and what the leader must be able to decide on that day.
By day 30: a workflow, a baseline, a team, one obstacle
Four things exist by the first review.
A valuable workflow, with its current performance recorded. Pick one workflow that is frequent, slow, bounded, and has someone who knows what good looks like (Lesson 2.1). Record how it performs today: elapsed time from request to finished result, error and rework rate, and cost. Write down where each baseline number came from, such as a ticket system export, a sample of recent comparable cases, or a supervisor’s estimate. If you only have an estimate from memory, label it as an unverified estimate for initial planning and collect a timed sample of current cases before the pilot starts, because a remembered figure cannot establish a measured day-60 improvement.
An empowered team. The people who do the work, plus someone who can approve a change to it. Empowered means they can try the proposal within stated boundaries without escalating each step.
A named decision owner. One person who will make the day-90 decision, and who is told so now. A committee can advise. It cannot own the decision. Someone must be named to get the decision made and record it, even when a group makes it.
One organizational obstacle, named for removal. Choose one obstacle, such as a review or data-access queue with no owner or decision date, or a hand-off that loses requests between inboxes. Name who will remove it and by when; for a review queue, that person keeps the purpose the review serves while resolving the request.
By day 60: the pilot meets its bar or it does not
The pilot has boundaries written before it starts: which users, which data, which policy or compliance constraints apply, and who the accountable reviewers are. Its pass bar and stop condition come from the pilot charter (Lesson 5.1’s five lines: owner, bar, stop condition, review date, routine-use conditions), written before day one. The charter also names the operating owner, the person who runs it after the pilot.
At day 60 the decision owner compares the evidence available to the pass bar and the stop condition. The question is not whether people liked the tool. It is whether the workflow measurably improved on the baseline and whether anything triggered the stop condition.
When the evidence settles the bar, each review ends in one of four outcomes: expand, revise with one named change, defer until a missing condition is in place, or stop (Lesson 5.1, Evaluate and decide, says when each fits and covers a review that cannot judge the bar). A pilot that missed its bar at day 60 stops, or is revised if one change would plausibly close the gap, and the record says what was spent and learned.
A mid-sized manufacturer piloted AI-assisted drafting of supplier quality reports at one plant, with an agreed pass bar of a shorter elapsed time from defect report to sent response and no rise in rework. At day 60 the pilot has met that bar against its baseline, measured end to end, and the plant manager asks to roll it out to the company’s other plants straight away.
- Extend the pilot another sixty days before deciding anything, to be sure the result holds.
- Record the day-60 result as met, keep the day-90 decision on its date, and ask the operating owner named in the charter to bring the support route, the training and the budget for a second plant to that meeting.
- Expand to every plant now, since the bar has been met.
Pick one before you open What happens.
ℹWhat happensclick to expand
- Extend the pilot another sixty days: It gathers more data, which feels careful, but the bar written in advance has already been met, and moving the date teaches the team that meeting a bar does not lead to a decision.
- Keep the day-90 decision on its date: The pilot proceeds toward expansion on the date the plan set.
- Expand to every plant now: It acts on the evidence quickly, but the other plants would start without a named support route, training or budget, the conditions Lesson 5.1 sets for routine use.
Choice 2 holds up, because it keeps the date the plan set, and the conditions for routine use are in place before a second plant depends on it.
By day 90: the decision, on time
The decision owner chooses one of the four outcomes and writes it down with the reason. Before an expansion starts, confirm the operating owner named in the charter, and name the support route, the training (the course page lists routes for your staff, by role) and the operating budget.
A day-90 meeting that ends with none of the four outcomes recorded has made no decision.
The worksheet fields, in order
The worksheet opens with the pilot name and the three review dates, then uses the same fields, in this order:
- Problem and affected users
- Current workflow and baseline, with source
- Proposed change, and the non-AI alternative
- Unknowns to test
- Team and named decision owner
- One obstacle to remove
- Pilot boundaries
- Applicable policy or compliance constraints
- Accountable reviewers
- Pass bar and stop condition
- Total cost by category (implementation, review, training, support, ongoing operation)
- Operating owner
- Measured pilot results at day 60 and day 90, against the baseline
- Final decision: expand, revise, defer or stop
Fields 1 to 6 are complete by day 30. Fields 7 to 12 are agreed before pilot day one, and the operating owner in field 12 is confirmed again before any expansion. Field 13 is filled at each review. Field 14 is filled at day 90, or at day 60 if the pilot stops then.
Key takeaway
- LEADERSHIP DECISION
- Name the decision owner and set the three review dates before the pilot starts
- IMMEDIATE ACTION
- Ask the team this week for the workflow's current elapsed time, error and rework rate, and the source of each number
- SUCCESS MEASURE
- Calendar days from pilot start to a recorded expand, revise, defer or stop decision, against the day-90 date on the worksheet