30 60 90 day plan, Customer Support Manager, Ledgerly
30 60 90 day plan template with one measure per phase
The first ninety days are a plan for learning, then building, then leading, and the plan fails when every phase has ten goals and no measure. This one gives each phase a page, four to five actions, the people to meet and one number that says the phase worked.
The document, page by page
Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.
Section by section
What each section is for, so you can keep the ones you need and drop the rest.
- Introduction
- Three sentences: the role, the team of 9, response time at 14 hours.
- Timeline
- Learn, build, lead as three dated entries from a 5 October start.
- Days 1 to 30, Learn
- Goal, five actions as a checklist, and the day 28 deliverable.
- People to meet
- Four rows with a why and a by when for every introduction.
- Days 31 to 60, Build
- Publish the 4 hour standard, write macros, start the huddle.
- What not to do
- A callout ruling out restructures and tool changes this phase.
- Days 61 to 90, Lead
- Monthly review, individual goals, the quarter plan, one hire if justified.
- Summary table
- Phase, goal, measure, target and a status column left not started.
- Sign off
- The manager and the head of operations sign side by side.
Learn, build, lead: what belongs in each phase
The three phase shape comes from Michael Watkins, whose book The First 90 Days made structured transitions standard practice. The learn phase is diagnosis: meet everyone, watch the work, write down what is actually broken. The build phase makes the two or three changes the diagnosis proved: standards, fixes, routines. The lead phase runs the machine and plans beyond it. The classic mistake is doing phase two in phase one, announcing fixes in week two before shadowing a single ticket. It feels decisive and it spends trust on guesses. The opposite failure is staying in learn mode past day 40, collecting context forever. The dates on the timeline are the cure for both: learning ends on day 30, in writing.
How to adapt this document
For an interview version, keep the three pages but state assumptions instead of facts, assuming a team of about 9, assuming response time is the pain, and present the measures as the kind of number you would commit to once inside. For an individual contributor role, swap the people table for a skills table, competent by day 30, autonomous by day 60, teaching by day 90, and keep one measure per phase. For a sales role, the measures are pipeline shaped: meetings by day 30, coverage by day 60, closed deals by day 90. In every version, resist adding goals; one measure per phase is the whole trick.
What makes this document work
One measure per phase, with a number and a day
The build phase ends at median first response under 8 hours by day 60; the lead phase ends at under 4 hours and CSAT at 85 percent by day 90. Because each phase closes on one number, the day 60 check in is a conversation about a figure on a dashboard, not a recital of everything that happened.
The build phase says what it will not do
The warning callout on page two, no restructure and no tool change, is the sentence a new manager most needs in writing. It spends the plan's credibility on the two ticket causes the data has proven, and it tells the team that the changes everyone fears are explicitly off the table for now.
The people to meet table has a why column
Head of product by day 10 to learn how support evidence reaches the roadmap; the two senior agents by day 5 to hear what they already fixed and gave up on. Because every introduction carries a reason and a deadline, the first month's meetings have agendas instead of being coffee with strangers.
Questions people ask
What should a 30 60 90 day plan include?
A goal, a handful of actions, the people to meet and exactly one measure for each phase. This example walks the three phases, learn, build, lead, with four or five actions each, a people table with a why column, and one closing number per phase. Anything longer becomes a job description rather than a plan.
How detailed should the interview version be?
The same shape, with assumptions labelled as assumptions. You do not know the team size or the response time before you start, so say so, and keep the structure: a goal per phase, a few actions, one measure. Interviewers are testing how you think, not whether you guessed the numbers.
Who sees the plan?
The manager and their manager. This example ends with a two party sign off on page three, the new support manager and the head of operations, because a plan the boss has signed is a shared definition of success, and the day 90 numbers stop being a surprise at review time.
Should the first 30 days have deliverables?
One: a written summary of what was learned, here the top five ticket causes with volumes, delivered day 28. Nothing else. The learn phase exists to stop a new manager fixing things before understanding them, and one deliverable proves the listening happened.
How do you pick the measures?
Use the number the role exists to move. A support manager exists to answer customers faster and better, so this plan uses median first response time, 14 hours down to 8 then 4, and CSAT at 85 percent. A sales version would use pipeline; an engineering version might use cycle time. One number per phase, never five.
When does the plan get reviewed?
At each phase boundary, day 30, 60 and 90, with the status column on the summary table filled in. Every status here reads "not started" because the plan is written in week one; the three reviews are where those cells change and the targets meet reality.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther document examples
Job description template with a measure against every responsibility
A job description that lists duties without measures is an advertisement; one that says how each duty is measured is the document the review will use a year later. This one gives six responsibilities, each with its measure, splits essential from desirable criteria, and puts the conditions in a block so the ad can be cut from page one.
Employee handbook
The handbook a new starter actually reads in their first week, written for a four clinic health provider with 61 staff. Eight sections, each answering a question in under a minute: what kind of employment you are on, when you work, what leave you get, how we expect people to behave in front of patients, what you may and may not do with a patient record, the five safety rules, and how notice works when you go. It says plainly that the award and the National Employment Standards win wherever the handbook differs from them.
Internship agreement
Twelve paid weeks at $32.50 an hour, three days a week, costing the host $9,828 including superannuation. The first clause says the intern is an employee, and the second explains the narrow cases where an unpaid arrangement would be lawful.
Want the steps in the builder? Read Create a document with AI, then Style text and add callouts, stats and lists. For everything this generator can do, see the document maker.
Written and checked by the OneCraft team. Last checked .