Why Employees Don’t Follow Processes (Even When the Process Actually Works)

I was on a team call this morning. Five people. Same company. Same SOP. Same outreach playbook sitting in the same shared doc.

Two of them had booked podcast guest appointments within weeks.

The third hadn’t booked a single one.

Same process. Same team. Completely different results.

And I’ll be honest, this scenario used to confuse me. I used to think if you gave people a clear plan, they’d just... do it. 

Build the SOP, hand it over, and watch results come in.

That’s what most operations leaders believe too. It’s also why most SOPs end up collecting dust in a Google Drive folder no one opens after week two.

Here’s what I’ve learned running teams across multiple businesses: the gap between “having a process” and “actually executing that process every single day” is where 80% of team performance dies.

And almost nobody talks about it.

What Actually Happened on That Call

Let me walk you through what I saw this morning because it’s a textbook case of why employees don’t follow processes even good ones.

We have a LinkedIn outreach SOP for booking podcast guest appearances. It’s specific.

It tells you exactly what to do: how many connections to send per day, how to vet profiles before reaching out, what message templates to use, when to endorse skills,

when to follow up, what time of day to post comments.

One of our senior guys handed this SOP to two junior team members.

He told them: “Follow this document exactly. If you have any doubts, call me anytime. I’ll clear them.”

That’s it. No fancy training. No three-day workshop. Just a proven doc and an open line for questions.

Both juniors started from zero. Neither had real LinkedIn experience. They began with five connection requests a day.

Only one got accepted at first. Then two. Then three. They used ChatGPT to help craft personalized comments. They ran every outreach message past senior team members before sending.

They showed up daily and did the boring work check profiles, send requests, endorse skills, send messages, post comments, repeat.

Within weeks? Appointments booked.

Real conversations with surgeons, specialists, and practice owners who actually wanted to be on podcasts.

Now here’s the other side.

A third team member had access to the exact same SOP. Same doc. Same senior support available. But he wasn’t booking appointments.

He wasn’t failing loudly either. He was just...stuck. Quiet about it. Not raising his hand. Not sharing what was blocking him.

When I asked him directly on the call What are your pain points? What’s making this hard? the answer was basically silence. And that’s the real problem.

The Process Wasn’t Broken. The Execution Loop Was.

Here’s what most managers get wrong about SOPs and processes: they think creating the process is the hard part. It’s not. The hard part is making sure people are actually running it.

Every day. Without drift.

When I asked the two juniors to walk me through their exact daily workflow, they could tell me step by step.

“I come in, I search for profiles, I pull 8-10 connections, I note them down, I draft comments, I get them reviewed, I post comments in the evening, I send outreach messages, next morning I check replies.”

That’s not talent. That’s discipline and a clear execution loop.

The third person had the same playbook. But somewhere between “having the doc” and “doing the work,” things fell apart.

And here’s what made it worse, nobody caught it early enough.

He wasn’t communicating with his blockers. His manager assumed he was fine because he hadn’t complained. And by the time we got everyone on a call to figure it out, weeks of potential results were already gone.

This is what I call the execution gap: the space between a documented process and daily follow-through.

It’s invisible until you go looking for it. And most companies never go looking.

Why This Keeps Happening in Every Company

This isn’t a “my team is lazy” problem. I’ve seen this pattern play out in 50-person startups and 500-person mid-market companies. The reasons are almost always the same.

People don’t ask for help when they’re stuck.

He had every opportunity to reach out.

He had a senior team member who literally said, “call me anytime.”

But he didn’t. And that’s not unusual, most employees won’t proactively tell you they’re struggling with a process.

They’ll just quietly fall behind and hope nobody notices.

Managers assume silence means everything’s fine.

If someone’s not complaining, they must be executing, right? Wrong. Silence is almost never a sign that things are going well. It usually means someone is stuck and doesn’t know how to say it, or doesn’t feel safe saying it.

There’s no system to catch drift early.

The two juniors who succeeded had something the third didn’t they were actively getting their work reviewed before sending anything. They’d draft a comment, show it to a senior, get feedback, then post. That review loop wasn’t in the SOP.

It emerged because they were in closer contact with the team. The third person was more isolated, and nobody had a system to check whether he was actually running the process daily.

SOPs don’t enforce themselves

A document sitting in a shared folder has zero power. It doesn’t ping you when you skip a step. It doesn’t flag when your connection request numbers drop from ten a day to two.

It doesn’t tell your manager that you haven’t sent an outreach message in a week. The SOP is just instructions. Enforcement is a completely different function and most companies don’t have it.

What Actually Fixes This

I’m not going to pretend this is easy. But after running multiple teams and watching this pattern repeat dozens of times, I’ve learned a few things that actually work.

Make the daily workflow stupidly specific.

Not “do LinkedIn outreach.” Instead:

“Send 8-10 connection requests before 11 am. Draft 3 comments by 1 pm. Get comments reviewed by 2 pm. Post comments by 5 pm. Send outreach messages by 6 pm. Check replies next morning by 9:30 am.”

The two juniors who succeeded could recite their workflow from memory. That level of clarity removes decision fatigue and makes it obvious when someone’s falling behind.

Build in forced checkpoints, not optional ones.

“Call me anytime” is a nice gesture. It’s terrible as a system. Instead, require a daily 5-minute check-in where each person shares what they did and what blocked them.

Make it non-negotiable. The people who were succeeding were already doing informal check-ins by getting their comments reviewed.

The person who was struggling had no such checkpoint. That’s not a coincidence.

Track leading indicators, not just results

By the time you notice someone hasn’t booked any appointments in a month, you’ve lost a month.

Instead, track the daily inputs: 

• How many profiles were reviewed?

• How many connection requests sent?

• How many outreach messages delivered?

If someone’s numbers drop for three consecutive days, that’s your early warning.

Make non-execution visible, fast

The biggest reason the third person fell behind was that his lack of execution was invisible. Nobody saw it until we got on a call weeks later.

If there had been a simple system even a daily Slack message saying “here’s what I did today” someone would have noticed the gap on day two, not day twenty.

Separate the SOP from the enforcement layer.

Your SOP tells people what to do. Your enforcement system tells you whether they’re doing it. These are two different things and they need two different solutions.

Most companies pour all their energy into building the SOP and then wonder why nobody follows it.

That’s like writing a recipe book and being surprised that nobody in your kitchen is actually cooking. 

The Uncomfortable Truth About Team Execution

Here’s what I keep coming back to. 

We had a team member on that call who said something really simple: “I just followed what he told me to do.”

That’s it. 

• No secret sauce. 

• No growth hack. 

• No genius-level talent. 

Just here’s the process, I followed it, I got results.

The gap between teams that execute and teams that don’t isn’t about strategy. It’s not about talent. It’s not even about motivation, really.

It’s about whether your organization has the structure to catch someone who’s falling behind on day two instead of day thirty. It’s about whether your people feel safe enough to say “I’m stuck” before the wheels come off.

It’s about whether you have any system at all to enforce the process you spent weeks building.

Most companies have great playbooks. Very few have execution enforcement.

If you’re a founder or operations leader reading this and thinking “this sounds exactly like my team” you’re not alone.

This is the single most common problem in companies between 200 and 2,000 employees. The SOPs exist. The talent exists. The gap is in the middle.

And that gap?

It’s fixable. But not with another document.