You brought someone in to take work off your plate, and months later the week feels exactly as full as it did before you hired them. They’re busy: they run the reports, answer the client emails, keep the projects moving. What hasn’t changed is where the decisions land. Every approval, every judgment call, every “quick question before this goes out” still comes to you, and the person you hired for relief has become one more reason your calendar stays full.
You were right to hire. The work had outgrown the team, and whether to hire at all was settled long before you wrote the job post. What got skipped is the step between deciding and posting: defining what the role would own. Without a definition, the load had nothing to attach to, so it stayed where it always sits, with you.
Define what the role owns before the job goes up, and at day 90 you can check whether the decisions left your desk for good or still find their way back. If you’ve already hired and nothing lifted, the last section is written for you.
A Role Is What It Owns, Not What It Does
The same role can be posted two ways. One says “manages the client reporting process,” which changes nothing, because the person runs the process and you still approve what goes out. The other says “owns accurate, on-time client reporting and has final say on what goes into each report,” which moves the decision off your desk.
If you hand over the full task list, but keep sign-off on all of it, you’ve hired a pair of hands and kept the job.
If your team needs you to make all the decisions, you’ve accidentally trained dependence.
Maybe you already run on a system like EOS, where every seat gets a chart listing what it’s responsible for. You’re ahead of most, and those charts are right to lead with outcomes instead of tasks. What they stop short of is the decision itself. A chart will say a seat owns client reporting; it won’t say whether that person can change the report’s format, push a deadline, or tell a client no without coming to you first. The responsibilities end up fully documented, and every real decision still lands on your desk anyway.
Before you write the job post, settle three conditions: what the role owns, what success looks like at day 90, and where it fits against the team you already have.
Condition One: What the Role Owns
Write down the one or two results this role answers for, stated as results rather than duties. “The delivery team ships on schedule and clients renew” is an outcome. “Oversees delivery” is a duty wearing an outcome’s clothes.
Then write the decisions that come with the outcome, and put numbers on the ones that involve money or scope. “Approves out-of-scope work up to two thousand dollars without checking with me” is a real transfer of load, because it names the exact thing that used to interrupt your afternoon and hands it to someone else with a boundary drawn around it. A person can act on a number and can only guess at a sentiment.
Then write what the role does not own, which is the half most founders skip. Name the decisions that stay with you and the ones that belong to someone else, so the edges are visible from both directions. The disputes that surface in month four almost always live in the part nobody wrote down, where two people each assumed the call was theirs.
Before you post anything, make two lists. One is what sits on your plate today that this person will decide without you. The other is what will still come to you, and why. If the first list is thin, the role as you’ve drawn it won’t relieve you of much, and it’s better to learn that now, on paper, than nine months in.
Condition Two: What Success Looks Like at 90 Days
When founders do write down what success looks like, it usually comes out too vague to fail: settled in, up to speed, building good relationships with the team. Read those back and notice none of them can be false. Nobody is ever demonstrably not settled in. A picture of success you can’t prove wrong gives you nothing to check against, and it lets everyone skip the only question worth asking, whether anything changed for you.
Success at the 90-day mark is observable, and it’s observable on two sides at once. One side is the outcomes the role delivered, the concrete results the person answers for. The other side is the decisions you stopped making. Both are checkable. The client reports either go out without your review or they don’t. The scope calls under two thousand dollars either reach you or they’ve stopped.
The second side is the one nobody writes down, and for you it’s the one that matters. You can measure a hire entirely by what the person accomplished and still be exactly as busy as you were, because a person can accomplish a great deal while sending every judgment call back to you. The measure that tracks your relief is the list of decisions that used to be yours and now aren’t.
Write the 90-day picture before the job posting goes up, and hand it to the person in their first week. A picture of success written before anyone is hired is a design. The same picture written after someone starts is a negotiation with a real person who now has reasons and a mortgage, and you’ll soften it without meaning to.
Condition Three: Where the Role Fits Against What the Team Already Covers
A role never lands on empty ground. Whatever you’re hiring for, some of it is already being done, partly, by people already on the team, and the new person’s edges are going to touch theirs. Before you post the job, map that overlap. List what the current team already owns that sits next to the new role, mark the seams where the two will meet, and decide in advance who settles a disagreement when they do.
If you skip the overlap map, the new hire can easily become a second person doing a blurry version of a job someone else half-owns. Every time the two of them disagree about whose call it is, the tie gets broken by you. In this scenario, you’ve added a head count and a second stream of questions, and the bottleneck is still standing in the same spot, holding the same coffee.
The clearest signal of what this hire should take is a place where you’re sitting in two functions at once, doing the delivery lead’s job and the account director’s job in the same afternoon because neither seat fully exists yet. You can usually see it without any tooling. Look at the week you just had and find the two hats you kept swapping between. One of them is the job you’re about to define, and leaving it on your own head has a cost that compounds. If you want to see how far the same pattern runs across the rest of the business, the Growth Readiness Quiz maps where the dependence is concentrated.
If one person being busy stops the work, your systems aren’t built to scale.
The 90-Day Ownership Test
Most thirty-sixty-ninety day plans watch the new hire settle in. The 90-Day Ownership Test watches your calendar. You run it at three marks, and the questions below are yours to answer privately. Every one of them asks where the decisions went, not how fast the new person is learning the ropes. A hire can be sharp, warm, and well-liked and still leave your week exactly as full as it was.
None of what follows measures the person. All of it measures whether the load moved.
The 90-Day Ownership Worksheet lays these three marks out as a page you fill in for one role at a time.
Day 30
Does the person know which decisions are theirs without asking you first, and have they made any of them yet?
The marker to look for is small and specific: a scope change under the threshold that went through without reaching you, a scheduling call made and communicated, a client question answered on their own authority.
Day 60
Is work leaving your inbox and staying gone, or does it loop back a week later under a slightly different subject line?
When two people on the team disagree about priority, are they settling it between themselves? The marker here is a disagreement that a year ago would have produced a message to you, resolved in a conversation you never saw.
Day 90
Can you point to a block of time in this part of the business that you no longer spend?
When something goes wrong, does the person handle it and then tell you, or carry it to you and ask what to do? The marker is a client escalation that once would have reached your phone on a Saturday, handled by them, with the first you hear of it being the summary of how they sorted it.
If the answers at day 90 are mostly no, the reason the hire hasn’t taken anything off your plate is simple: the role was defined as a task list, so there was never a decision with a boundary for it to cross. The problem is fixable, and the next section is how.
If You’ve Already Hired
If you’ve read this far with someone specific in mind, the person already sitting in the seat you hoped would save you, you don’t need to start over. You need to do now what didn’t happen before the role went up, and you can do it in an afternoon.
Run the three conditions on the role as it exists today. Write down what it owns, watch where the decisions route over a normal week, and map what overlaps with the rest of the team. You’ll usually find the same thing: the outcome was never named, so the decisions never attached to anyone, so they kept flowing back to the person who’s been there since the beginning.
Do the work with the person, not around them. Most of the time, the person you hired has spent months sensing there were calls they could make, with no clear signal that they were allowed to make them. Sit down and be specific. Here’s the outcome you own. Here’s the dollar threshold under which you decide on your own and don’t check with me. Here’s what still comes to me, and here’s why. Three sentences like that move more than another quarter of hoping they’ll step up.
Match what you hand over to where the person is, not to the title on the offer letter. Someone eighteen months into their career and someone who’s run a function before can hold different weights, and the way you coach the handover changes with it.
The fix is a definition, and the person is very likely the right one. Most hires that relieved nothing were never handed anything real to hold, and a capable person with nothing to own looks, from the outside, exactly like a bad hire. Give them the outcome, the decisions, and the boundary. If the load is bigger than one role, a fractional COO can hold that redesign with you.
Get the Decisions Off Your Desk
When a hire doesn’t lighten anything, the story you tell yourself is usually about the person: wrong fit, not senior enough, couldn’t step up. Look again at the role they were handed. If it came with a task list and no decisions, they did exactly what you defined, and the definition kept you in every loop. The person was never the variable. The role was.
Activity isn’t impact. If your calendar is full and work is slipping, you’re stuck in motion.
Define one role around what it owns, and your week gets lighter. Define every seat that way, and you get what sets you free: a business that can make a decision when you’re not in the room. Doing this across every seat is its own project. The Leadership Multiplier Playbook is the step-by-step for it, how to move decisions down to the people who should own them, role by role. Or you bring in a fractional COO, an experienced operator who builds it with you.
If you already know which role is the bottleneck, book a Discovery Call.