Ninety day plans that are not fiction

The standard thirty sixty ninety plan is written by the manager the night before someone starts, contains the words learn, contribute and lead, and is never opened again.

A useful plan has three properties. It names deliverables, it names people, and it gets revised.

Write outcomes, not activities

Attend team meetings is not an outcome. Own the weekly pipeline report end to end is. Meet the sales team is not an outcome. Produce a written summary of the three biggest objections sales hears, from six conversations, is.

Three to five outcomes per phase is plenty. More than that and you are describing a year.

Name the people, not the departments

For each outcome, who does the new joiner need and what do they need from them. This turns a plan into a set of introductions, which is the part managers usually forget to make.

Make it a two way document

Give the draft to the new joiner in week one and ask them to change it. They will spot things that are impossible, things that are missing, and things that were sold differently in the interview. That last discovery is uncomfortable and enormously valuable, because it is the moment you can fix the expectation gap instead of discovering it at month five.

Revise it out loud

At thirty and sixty days, review the plan explicitly. What changed, what was wrong, what moves. A plan that has been visibly revised twice is a plan people trust. One that has not been touched is decoration.

Judge ramp, not output

At ninety days you are assessing trajectory, not productivity. Are they asking better questions, needing less context, being pulled into work by others. Those signals appear well before output does, particularly in complex or regulated environments where a real contribution takes six months.

And if the answer at ninety days is genuinely no, say so then. Managers who wait until month nine to raise a concern have usually made a hiring problem into a performance management problem.