Why does nobody follow your processes?

Processes and procedures are one of those things every business focuses on, and rightly so. They are the governance of your business. They protect you legally, and they make sure everyone is moving in the same direction and knows what to do.

So here is the uncomfortable question. How many of us actually get them right?

Written, filed and forgotten

It is a familiar story. You bring in a consultant, a coach or a team member who knows their craft, and they write the processes for you. The document is thorough. Everyone agrees it is a good idea.

And then… crickets.

Nobody follows it. It sits in a binder on a shelf or in a folder nobody opens. For all anyone knows, it was written by AI. The procedure exists on paper, but the work carries on exactly as it did before.

Writing the process was never the hard part. What decides whether it works is everything that happens after it is written.

Five questions that decide if a procedure gets followed

  • What happens to the procedure once it is written?
  • Was anyone trained on it, or was it simply sent around?
  • Is there a short version that is easy to follow on a busy day?
  • Has it been revisited and adjusted since it was written?
  • Were the people who carry it out ever consulted, or part of putting it together?

Your answers to these questions are the difference between processes your team follows and processes that collect dust in the filing cabinet.

Signs your processes are collecting dust

  • The same mistakes keep happening, even though “there is a procedure for that”.
  • Two people do the same job two different ways.
  • New starters learn from whoever sits next to them, not from the process.
  • Nobody can tell you when the procedure was last updated.
  • Questions still come to you, because asking is easier than looking it up.

Four steps to processes your team actually follows

1. Build them with your team

Make the people who do the work part of writing the process, and take on even their smallest input. People back what they help create. Hand them a finished bible and they are more likely to question it, and probably not follow it as intended.

2. Don’t talk over their heads

Use simple language. Keep the full, detailed version for the file, where it protects you, and create a short, bite size version for day to day use: a one page guide or checklist people can follow in the moment.

3. Review and adjust

Procedures change with testing, the economy and new laws. Revisit them at least every six months for the first year or two, then every year once they have settled. A process that no longer matches reality is quickly ignored.

4. Train, then check understanding

People don’t read minds, and clarity is your best friend. A link in the HR handbook is no longer enough. Train your managers and your team on each process, then confirm they understand it, for example by asking them to walk you through it. Without that, you are guessing.

One process, two versions

The full procedure

Detailed, complete and kept on file. It covers compliance, legal protection and every exception. You need it, but nobody reads it on a busy Tuesday.

The quick guide

One page, plain language, the steps that matter most. It lives where the work happens, and it is what your team actually uses.

One thing to do this week

Pick the one process that causes the most mistakes or the most questions. Sit down with the people who use it, ask what gets in the way, and turn it into a one page quick guide together.