Why doesn't my team follow the process I wrote?

You spent a Sunday on it. Twelve pages, screenshots, the whole thing. You sent it around. Two people said thanks.

Three weeks later somebody did the job the old way and broke something, and when you asked why, they said they weren't sure that document was the current one.

You are not dealing with a discipline problem. You're dealing with a document that can't be followed.

The test that tells you which one you wrote

Hand it to the newest person you employ. Don't explain anything. Don't hover. Ask them to do the task using only what's on the page.

Watch where they stop.

They'll stop at the first place the document says what to do but not how to decide. "Confirm the order looks right." Right compared to what. "Escalate if it's urgent." Urgent by whose definition. "Use the usual supplier." Which one is usual on a Tuesday when the first one is out.

Every one of those gaps is a decision you make without noticing you're making it. You've made it ten thousand times. It doesn't feel like a step, so it didn't get written down. And that's precisely the part the other person cannot supply, because supplying it is the actual job.

A process that skips the decisions isn't a process. It's a list of the parts that were already easy.

Why this keeps happening to good owners

You're the worst possible person to document your own work, and you're usually the only one who will do it.

The better you are at something, the less of it you can see. The judgment compressed into twenty years of doing the work stops being visible to the person holding it. Ask a great estimator how they price a job and they'll say they just know when it's off. That's not evasion. They genuinely can't see the rules anymore.

So the owner writes down the visible half, the half that was never the bottleneck, and then wonders why handing it over didn't work.

What a followable process actually contains

Three things, and most written procedures have only the first.

The steps. What happens, in order. Everybody gets this part.

The decisions. Every point where the person has to choose, with the rule they choose by, written as an if-then. Not "use judgment." If the deposit is under this much, do that. If the client has asked twice already, do this other thing. If you can't tell, here's who to ask and how fast.

The failure cases. What it looks like when it's going wrong, and what to do then. This is the part that decides whether the person calls you at nine at night. If the document says what a bad outcome looks like, they catch it. If it doesn't, you catch it, which means you're still the safety net and nothing has actually been handed off.

Write those three and the same twelve pages become usable. Usually shorter, too, because writing the decisions down exposes how many of the steps were just you double-checking yourself.

The harder version of the problem

Sometimes the document is fine and people still don't follow it. That's a different diagnosis and it's worth naming, because the fix is the opposite.

If the written way is slower than the way people actually work, they'll use theirs. Every time. A procedure that adds four steps to protect against something that happens twice a year will lose to the shortcut, and the people taking the shortcut are not being difficult. They're being efficient at the thing you're actually measuring them on.

So before you enforce it, check whether the process is losing on merit. Ask the person who ignores it to walk you through their way. Half the time their way is better and nobody told you, which is its own finding. See why your team won't tell you what's wrong.

How to tell which one you have

Two questions, and they separate cleanly.

Did people try it and go back? Then the process is losing to the real work. Fix the process.

Did people never really start? Then the document isn't followable, or nobody believes it's the current version, or there was never a moment where following it became the expectation. Fix the document, then the expectation.

What doesn't work is repeating the announcement louder. If the third email about the new procedure is on your list this week, the problem isn't awareness.

The part nobody says out loud

A written process only holds if somebody other than you owns whether it's followed.

That's the piece owners skip, and it's not an accident. Handing over the document feels like delegating. Handing over the authority to enforce it feels like losing control, so the owner keeps that bit, and then the owner is the enforcement mechanism forever. Which is the same position you were in before you wrote anything, except now there's a document making you feel like it should be working.

If nobody but you can say "we don't do it that way here," you don't have a process. You have a preference, and everyone is waiting to see how strongly you hold it this month.

Where this usually sits

People is the constraint owners name most often in the Platform One Index, 46 percent, more than marketing and finance combined. It's also the area that scores worst when we measure all five separately.

The interesting part is what "people problem" turns out to mean. Owners say it and mean their team isn't good enough. The measurement usually says the work was never specified well enough for anyone to be good at it.

Those two readings point at completely different next moves, which is why guessing is expensive. See is it a people problem or a process problem.

Start with the measurement

Twenty questions, about ten minutes, free.

You'll get scored in five areas and see the one your answers point at. If it comes back saying what you already believed, you've lost ten minutes. If it doesn't, you just found the thing you've been solving around.