Every owner has run this experiment without meaning to: hire a genuinely good person, watch them struggle for three months, and quietly conclude the hire was a miss. Sometimes it was. More often the person was fine and the seat was the problem, because the seat did not exist yet. It lived in your head, and you cannot onboard a new hire into your head.
A role is a written job, not a job title
“Operations Manager” is not a role. It is a label on a box that could hold forty different jobs. A role is the answer to four questions:
- What outcomes is this seat accountable for? Not tasks, outcomes. The results that get worse if this person leaves.
- What decisions can they make without you? Written down, with the guardrails.
- What does good look like, measured? The one or two numbers that tell everyone, including them, whether the seat is winning.
- What recurring workflows do they own? The documented processes that come with the chair.
If you cannot answer those before the interview, no candidate can succeed once they sit down. You will spend the first quarter reverse-engineering the job while paying a new hire to guess at it.
Build the seat, then fill it
The move that changes hiring outcomes is boring and it works: write the role down before you write the job post. Define the outcomes, the decision rights, the scoreboard, and the core workflows. Now the interview has a real standard to test against, onboarding has a destination, and the new person has a way to know they are winning that is not “does the owner seem happy today.”
This is also how you find out whether you need a person at all. Half the time, writing the seat down reveals that the “role” is actually two or three unowned workflows that belong on the Ownership Map under people you already have. That is a process fix, not a headcount fix, and it is a lot cheaper.
The test before you post the job
Could you hand a one-page document to a competent stranger and have them understand what they are accountable for, what they can decide, and how they will be measured? If yes, you are ready to hire. If no, you are not hiring a person yet, you are building a seat. Do that first, and the hire gets far easier, because you are no longer asking a new hire to read your mind for a salary.
The Origin Score is twenty-seven questions, about five minutes, and shows where your business is narrowest right now, including whether your roles are actually defined or the business is still holding together on you. For most teams at this stage, the seat is what is missing, not the person.
