Your Team Isn't the Problem. Your Roles Are Undefined.

You hired for the job. Nobody ever wrote the job down.

You know who on your team is underperforming. You've had the conversation, maybe two. You've started wondering what a replacement would cost. Before you post the ad, answer one question: what would you tell the new hire on day one about what they own? If the answer is a title and a general direction, you are about to run the same experiment again.

Most roles stop at the title. Operations manager. Project lead. Office admin. A title says where someone sits. It doesn't say what result they answer for, how anyone would know they delivered it, or which calls they can make without checking with you. Leave those three blank and people fill them in with guesses. The good guesses get called talent. The bad ones get called attitude.

Then it compounds. Two people each assume the same result is theirs, or each assume it's the other's. Both do something reasonable and the thing that mattered falls between them. Every decision nobody spelled out comes to you, because asking is safer than guessing wrong. You decide you have a team that can't make a decision. You have a team nobody told what it could decide.

A role takes three lines to define. The result the person owns, written as a result and not a task. The number that shows it's happening without anyone asking. The calls they make alone, the calls they make and report, and the calls that still come to you. Most owners have never written those three lines for anyone. That includes the person they're about to replace.

A job nobody finished writing can't be done well or badly. It can only be guessed at.

A landscaping owner told me his crew lead had no initiative. I asked the crew lead what he was responsible for. "Getting the trucks out by seven." I asked the owner. "Every property looks right when we leave." Two years, and those two sentences had never been in the same room.

Hit reply and tell me why. I read every one.

Last week's poll asked who finds out first when something goes out wrong. 67% said they do, after it ships. 33% said their team, before it ships. Nobody said the customer. Issue 2 wrote decision rights for the tasks you had handed off in name only. Issue 8 priced the rework and traced the biggest pattern to a step nobody had written down. Both are in the archive if you joined late. This week turns to the people doing the work. Next week, with roles defined, Issue 10 asks who owns each outcome.

This week, one small move. It takes one role, about twenty minutes of yours and ten of theirs, and it shows you whether the person in it would describe the job the way you do.

If the two sheets don't match, you've found the job they've actually been doing.

The rest of this issue is Modern Operator Pro. It writes each role on one page, the result the person owns, the number that shows it, and the calls that are theirs, then lines the roles up against what the business needs so you can see what nobody covers and what two people claim. The Role Clarity Builder keeps the roles side by side, and four prompts you paste into ChatGPT or Claude write the pages and find the gaps. Everything above this line is free.

If any of this sounded like your business, Ground State is the fix. It's a fixed-fee diagnostic that finds where the structure is leaking and puts the answer in writing. See how it works.