Every owner who has made a bad hire believed they knew what they were looking for. The problem is that “I’ll know it when I see it” is not a standard you can evaluate candidates against. By the time you realize someone isn’t working, the criteria you should have set at the start are written down nowhere.
A success definition is not a job description. A job description lists what the person will do. A success definition answers a different question: what does good look like in this role, in this business, in the first 90 days?
Those two documents serve different purposes. Only the second one is useful for evaluating whether a candidate will actually work out.
The founder who defines success before posting has an advantage at every stage that follows. The job post filters more accurately. The interviews measure the same thing. The 30-day check-in has a baseline.
The Role Success Standard gives you a practical structure for building that definition before the search begins.
Why “I’ll Know It When I See It” Keeps Failing
The obvious problem: you evaluate candidates against a feeling rather than a standard. You like someone, they seem right, you make an offer. Six weeks in, the gaps appear and you can’t name what you expected because you never wrote it down.
The less visible cost is what this does to everyone involved in the hire. Without a success definition, every interviewer evaluates differently. Culture fit here, technical depth there, energy and enthusiasm somewhere else. The candidate who performs best in the room wins, regardless of whether performing in a room is what the job requires.
The deepest cost is what happens when performance becomes a problem. Without a written standard set at hire, every difficult conversation becomes a dispute. The person says they’re doing what they were hired to do. You believe the job requires more, and neither has a document to settle it.
A success definition protects both sides. Without one, you’re operating on assumption from day one.
The Role Success Standard
The standard has four components. Together they answer the question the job description never asks: what does this person need to have accomplished to prove the hire worked?
Component 1 names the role’s primary output
Every role, when reduced to its core, produces one main thing. Not ten things. One primary output the business needs from this seat.
For a customer success manager, the output might be renewal rate. For an operations lead, it might be on-time delivery without the owner’s involvement. For a bookkeeper, it might be that the owner can answer cash flow questions from current records at any time.
Naming the primary output forces a real answer to “what is this job for.” It also tells you the first thing to probe in interviews. A candidate who can’t speak to producing that output is not right for the role regardless of what else they offer.
Before: Job description lists twelve responsibilities with no priority assigned. After: Role success standard names the one output the role exists to produce.
Component 2 defines what good looks like at 90 days
In their first 90 days, the new hire doesn’t need to have mastered everything. They need to have demonstrated that the hire was right. Component 2 names the specific, observable evidence of that.
“Settled in and building relationships” is too vague to be useful. Specific evidence sounds like: has taken ownership of client onboarding without the owner being involved, or has produced one client-facing deliverable without requiring revision. Concrete enough to be observable. Concrete enough to put in front of the person on day one.
The bookkeeper hired to “keep the books clean” will never meet a standard that wasn’t defined. Clean is not a standard. Reconciled by the 5th, flagging anything over $5,000 unusual, current as of yesterday: that’s a standard you can measure against.
Component 3 identifies the two or three non-negotiable traits
Most roles could be filled by several different profiles. But in a specific business, at a specific moment, two or three traits matter more than all others. Component 3 names them explicitly.
These are not generic soft skills. They are specific to the situation. An operations role in a business still figuring out its processes needs someone who builds systems from nothing, not someone who runs existing ones. A customer-facing role in a high-touch business needs someone who reads when clients need more, not someone who follows a fixed cadence.
Naming these upfront lets you design interview questions that actually test for them. Otherwise you hope they emerge from a conversation that was never designed to surface them.
Component 4 names the most common failure mode
For every role, there is a version of the hire that looks right in the interview and fails at the six-month mark. Name that version before you start.
The failure mode is usually visible from experience. The last person in that seat who didn’t work out, the candidate you almost hired who later failed elsewhere: write what they have in common. That’s the pattern to watch for.
When you’re down to two strong candidates and gut feel is all that’s left, the failure mode is a real tiebreaker. When you write the interview questions, building them around the failure mode surfaces the most useful signal. This connects to the role-sketch work in The Hiring Plan That Prevents You From Hiring in Panic Mode. When the planning came first, you’ve already named the failure mode before urgency arrives.
How the Conductor Builds Your Role’s Success Definition
The Living Library holds what your business has built up about past hires. Job descriptions, onboarding notes, performance records, and observations about what worked and what didn’t. The Conductor, Kiluma’s context-aware AI, reads from that record to build from your actual experience rather than a generic role template.
Ask it: “Based on what we know about this role and past hires, what should success look like in the first 90 days?” It reads the relevant records in your Hiring Collection and returns a draft success definition grounded in your business’s history. Not what a good hire for this type of role generally looks like, but what your hiring record actually shows.
You edit and refine it. The Conductor builds the first draft from what you have. Where a generic job post tool starts from nothing, this starts from what you’ve already learned.
Write the Standard Before You Write the Post
This week, before you draft a single job post, open a document and write the Role Success Standard. Four sections: primary output, 90-day evidence, non-negotiable traits, and the failure mode to avoid.
Give yourself thirty minutes. The goal is not a polished document; the goal is a document that exists. The job post, the interview questions, and the 30-day check-in can all come from the standard.
Do the standard first.
The Difference Between a Standard and a Hope
A standard is specific enough to put in front of a candidate and say: this is what we’re measuring you against. A hope is what you feel when the standard wasn’t set. If your success definition for this hire sounds more like a hope than a standard, go back and make it specific. Try Kiluma free for 14 days at kiluma.ai.