Home/Blog/Early Hiring/Write a Ninety Day Role Outcome Before Y…
Early Hiring

Write a Ninety Day Role Outcome Before You Hire Anyone

How to write a ninety day role outcome: describe what will exist, what will be different and what they will own if the hire goes well, not a list of tasks.

Cover of the FIKR Space guide: Write a Ninety Day Role Outcome Before You Hire Anyone

To write a ninety day role outcome, describe what will be true after three months if the hire goes well: what will exist, what will be different and what the person will own. It is a description of results, not a list of responsibilities.

This one document does more work than anything else in the hiring process. It tests whether the role is real, gives candidates something concrete to react to, and becomes the spine of the first three months. If you cannot write it, you are not ready to hire. You are ready to think about what you need.

How to write a ninety day role outcome in three parts

Responsibilities describe activity. An outcome describes the state of the company once the activity has paid off. The difference sounds small and changes everything, because a list of duties can be satisfied by someone who is busy, while an outcome can only be satisfied by someone who has produced something.

Build the document from three questions, answered in plain sentences.

QuestionWhat the answer should be
What will exist?Something that is not there today, which you could point at
What will be different?A change in how the company works or what it can do
What will they own?The decisions and the area that are theirs without asking you

Write each answer as if looking back from day ninety. The test of a good sentence is whether two reasonable people reading it would agree afterwards on whether it had happened.

Start from the constraint

The outcome only makes sense if it connects to the reason the role exists. Before you write, return to the sentence that names what is limiting the company this quarter. The outcome should describe that constraint being lifted. The earlier post on who to hire first at a startup explains how to find it.

If your outcome describes something pleasant but unrelated to the constraint, one of the two is wrong. Either the constraint was not the real one, or the role is not the answer to it. Finding that out on paper costs a morning. Finding it out after an offer costs far more.

Free guide, 33 pages: The First Ten Hires Playbook. Send me the guide.

Why the document forces honesty

Many founders open a role because they feel overstretched. The feeling is real, but a feeling is not a job. Writing the outcome is how you find out which one you have. If the page stays blank, or fills with vague phrases, the role is probably a sensation of being busy and not yet a position.

That is not a failure. It is the document doing its work. A blank page tells you to spend more time on what you need before you spend months of runway on someone to provide it.

What a candidate does with it

A concrete outcome gives candidates something to react to, and that reaction is itself a filter. Strong candidates will push back usefully. They may say a part is unrealistic, that something is missing or that the ownership is unclear. Treat that as a good sign. A candidate who reads a specific document carefully and argues with it is already behaving like someone who will own the work.

Weak candidates tend to nod. That is useful information too, and it is one more reason to share the document before the process is far along and not only at the offer.

How the document is used later

The outcome is written once but used four times, and each use is a reason to take care over the wording.

  1. In selection. You score candidates against it instead of against an overall impression, as described in how to run a work sample test.
  2. On day one. You share it with the new person, so they have something unambiguous to aim at. That is exactly what is missing from most early roles, and how to onboard your first employees builds the first three months around it.
  3. In feedback. It gives you something specific to refer to when you say what is going well and what is not.
  4. At the first review. The evaluation becomes a comparison against something agreed in advance, not an argument about expectations that were never stated.

The last use is the most valuable. Without a written outcome, the honest first review tends to be a disagreement about what was meant. With one, it is a conversation about what happened.

A template built from the three questions

You can start from a simple skeleton and fill it with your own facts. The blanks below are deliberately left empty, because the content has to come from your company.

  • By the end of ninety days, this will exist: ____
  • The company will be different in this way: ____
  • They will own this area and these decisions without asking me: ____
  • I will know it has gone well because: ____
  • I will know it has not because: ____

The last two lines are the ones people skip, and they are the most useful. A role that has no stated sign of failure cannot be reviewed honestly. It is also worth writing them before you have met anyone, for the same reason you agree the bar in advance: once you like a person, your standard begins to move.

FIKR People, team and HR for founders: hiring, onboarding and reviews in one workspace. See FIKR People.

Keep ownership explicit

Of the three questions, ownership is the one most likely to be left vague. It is also where the delegation problem hides. If the document says the person owns an area but your habits say otherwise, a capable hire will notice within weeks.

Write down which decisions are theirs. Then keep to it. A new person who knows what is theirs without asking you can work at pace. One who has to ask about everything is not being given a role, only a task list with extra steps.

Two readings before you finalise it

Once the draft exists, read it twice, from two different positions. The first reading is as the candidate you most want. Would that person find something concrete to aim at, or would they have to guess what you meant? A strong candidate has options and little patience for vagueness, so a document that makes them guess will lose them.

The second reading is as yourself on day ninety. Imagine sitting down with the new person and the page. Could the two of you agree, without argument, which lines have happened? If any line would start a debate about what it meant, rewrite it now, while the debate costs nothing.

It also helps to ask someone else to read it cold. A person who has not heard you explain the role will see immediately which sentences depend on context that exists only in your head. That context is worth transferring in any case, and the gaps they find tell you what to include in the first week.

Common ways the document goes wrong

ProblemWhy it hurtsFix
It is a list of dutiesAnyone busy can satisfy itRewrite each line as something that will exist or change
It describes everything the company needsIt is the wish list againTie it to the single constraint
Ownership is missingThe person waits for permissionName the decisions that are theirs
It is written after the offerIt cannot filter or guide selectionWrite it before the first conversation
It is never sharedExpectations stay in your headHand it over on day one

The common thread is that the document is only useful when it exists in time, is specific enough to be disputed and is shared with the person it describes.

Free guide, 33 pages: The First Ten Hires Playbook. Send me the guide.

Revising it without moving the goalposts

The company changes, and a ninety-day outcome may need adjusting. The way to do that honestly is to change it openly and together, and to say so, not to quietly judge against a different standard. If both of you can see what was agreed and what was amended, the review remains fair.

What you should avoid is the slow drift in which the real expectation moves and the document does not. That is how a hire ends up being judged on something never stated, which is the exact situation the document exists to prevent.

FIKR People, team and HR for founders: hiring, onboarding and reviews in one workspace. See FIKR People.

Frequently asked questions

How long should the document be?

Short enough to be read in a few minutes and remembered. A page is plenty. Its job is to be specific, not comprehensive.

What if I cannot write it?

Then the role is not ready. Spend the time on understanding what you need, using the constraint as your starting point, and come back to the page when you can say what will be true if this goes well.

Should candidates see it before they accept?

Yes. A concrete document is something candidates can react to, and strong ones will push back usefully. Hearing that before an offer is much better than hearing it in month two.

Is this the same as a job description?

No. A job description lists responsibilities. This document describes what will exist, what will be different and what the person will own if the hire goes well, which is a more demanding thing to write and a more useful thing to hold.

The full method, with the checklists, is in The First Ten Hires Playbook, a free 33-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us