Ninety Day Outcome:How to Write One for a Role
Ninety day outcome for a role: three sentences on what will exist, what will change and what they own, plus a quick check for whether you are ready to hire.
To write a ninety day outcome for a role, describe what will be true if it goes well: what will exist, what will be different, and what they own. Do not list responsibilities. If you cannot write it, you are not ready to bring anyone in.
How to write a ninety day outcome for a role: describe the future, not the job
This one document does more work than anything else in the hiring process. And almost nobody writes it.
Here's why it matters. Without it there's no shared expectation. There's no basis for onboarding. And there's no honest first review, just a growing sense, somewhere around week six, that it isn't working. You can't say why, because you never said what working looked like.
A job description tells people what to do all day. A ninety day outcome tells them what has to be true at the end. Those are different documents, and only one of them is useful when things get hard.
The test: can you write it?
Treat the writing itself as a diagnostic. Sit down and try.
If the words come, good. You've confirmed the role is real and not just a feeling of being overstretched. If they don't come, that's the most valuable information you'll get this month. You aren't ready to bring anyone in. You're ready to think about what you need.
That isn't a failure. It's a cheap way to avoid an expensive one. Better to find the gap with a pen in your hand than in a conversation with someone you've just made an offer to.
Free guide · 22 pagesThe first few decide the rest.The First Ten Hires Playbook: who to bring in, in what order.Get the free guide →The three sentences
Keep it to three parts. Each one is a plain statement about the future.
- What will exist. Something you could point at that isn't here now. A thing built, a channel running, a process written down.
- What will be different. Something in how the business behaves. A task that no longer lands on you. A delay that's gone.
- What they own. The decisions and the results that are theirs, without asking you.
The third is the one people skip. Skip it and you'll hire a pair of hands and wonder why you're still making every call. Ownership is what turns help into relief.
Weak and strong ninety day outcome, side by side
Say you run a productised service and you want help with client onboarding. The responsibilities version and the ninety day outcome version of the same role look completely different.
| Part | The responsibilities version | The outcome version |
|---|---|---|
| Shape | "Handle client onboarding" | "New clients are onboarded without me in the room" |
| What will exist | Not stated | A written onboarding sequence that someone other than me can follow |
| What will be different | Not stated | I no longer answer the first round of setup questions |
| What they own | "Support the team" | The onboarding process and the decision on when a client is ready to start |
| How you'd know on day ninety | You can't | You can look at it and say yes or no |
The left column describes activity. The right describes a state of the world. You can argue about activity forever. You can only agree or disagree about a state.
Write it so a stranger could judge it
A good outcome passes a simple check. If someone who has never met either of you read it on day ninety, could they say whether it happened?
"Improve our content" fails. "Be proactive" fails. Those are moods. "A weekly publishing routine exists and runs without me chasing it" passes, because somebody can look and see.
Aim for fewer outcomes, not more. A short document that you both remember beats a long one nobody reads. If you've written a page of them, you've written a wish list again. Go back to the single constraint you named and cut everything that isn't pointed at it. If you haven't named one yet, when a solopreneur should make a first hire starts there.
Why strong people push back on it
Show the document to candidates, early. It gives them something concrete to react to, and that reaction is a filter.
Good people push back, usefully. They ask what "owns" really means. They say the timeline is too short, or that the outcome depends on something you haven't mentioned. That's a gift. You're getting an honest preview of how they think, and a free correction to your own document.
Weak fits tend to nod. Nothing in the document costs them anything to agree with. That's worth noticing too.
You can take the conversation further with a real task. How to run a paid work sample makes the next step concrete.
What the document does after yes
The offer is the midpoint, not the end. This is where the document earns its keep.
Share it on day one. Use it as the spine of the first three months. It gives them something unambiguous to aim at, which is exactly what is missing in most early roles. They know what winning is, so they don't have to guess what you'd like.
It also makes your first evaluation a comparison against something agreed in advance, not an argument about expectations that were never stated. Nobody likes that second argument, and it's avoidable.
The same document sets up your first weeks, covered in how to onboard your first hire.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Use it to score people, too
There's a second use, while you're still interviewing. Score every candidate against the ninety day document, not against an overall impression.
Impressions mostly measure how much you enjoyed the conversation, and that correlates with similarity, not performance. The document gives you a fixed yardstick. Write your scores down while you talk, not afterwards, because memory reshapes itself toward whoever you liked.
Five questions to check your draft
Read your draft and ask these. Be a little hard on it.
- Is there something I can point at? If not, it's a duty list.
- Is it clear what changes for me? If nothing leaves your plate, the role is decoration.
- Is ownership named? If not, they'll wait for you to decide everything.
- Could a stranger judge it? If not, it's a mood.
- Does it point at the real constraint? If not, you're adding a wish.
Fail any of these and rewrite. It takes minutes. The alternative is a growing sense that it isn't working, with nothing to measure it against.
The first review writes itself
Schedule an honest review against the outcomes. Don't leave it to chance and don't save significant feedback for later. Put the document on the table and go through it plainly: this exists, this doesn't yet, this you own and this you don't.
When it's working, that conversation is short and happy. When it isn't, you have something specific to point at, which makes the hard conversation easier for both of you. Delay is not kindness. You'll usually know within a couple of months, and the document is what lets you say so without drama.
For the other side of this, where you're the one who needs to loosen your grip once the outcomes are theirs, see how to let go of work as a solopreneur.
Free guide · 22 pagesThe first few decide the rest.The First Ten Hires Playbook: who to bring in, in what order.Get the free guide →Three ways this goes wrong
You write it after you've fallen for someone. Then it describes their strengths, not your need. Write it first, before you've met anyone likeable, because your standard moves under time pressure and social warmth.
You write it and never look at it again. A document in a drawer is a wish with better formatting. Put the review in the calendar the day you share it.
You write it for the role you wish you had. The outcome has to point at the actual bottleneck, not the ambition. If the page could describe any business, it describes none of yours.
Each of these is a failure of definition and nerve, not of judgment about people. That's good news, because both are fixable before you speak to a single candidate.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
What is a ninety day outcome for a role?
It's a short description of what will be true if the role goes well: what will exist, what will be different and what the person owns. It describes results, not a list of tasks, so you can check it on the last day.
How is it different from a job description?
A job description lists responsibilities. A ninety day outcome describes a state you could verify. It also gives candidates something to push back on and gives you something to onboard and review against.
What if I can't write it?
Then you're not ready to bring anyone in. You're ready to think about what you need. That's useful to learn before an offer, when finding out costs you an hour instead of months.
When should I share it with the person?
Early with candidates, because their reaction is a filter, and on day one with the person you hire. After that it's the spine of the first three months and the basis for your first honest review.
Write the ninety day outcome first, then open the role.
The full method, with the checklists, is in The First Ten Hires Playbook, a free 22-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.