Why Your Team Keeps Ignoring the Process You Built
Why Your Team Keeps Ignoring the Process You Built
If your team delivers client facing services and you’ve been experiencing employee turnover, client churn, or a level of unpredictability (and surprises…which you hate) - we see you and we wrote this blog post to bring you relief.
Founders and CEOs exhaust their efforts and reach the conclusion the issue is within the staff.
Execution systems fail most often because they're built around how leadership wishes work happened, not how it actually happens. Your team is likely not ignoring the process out of laziness, but they route around it because it added friction to their day instead of removing it.
The fix lies in reconciling the differences between leadership expectations and reality, redesigning ownership and handoffs, and removing additional oversight. Which can feel counterintuitive to leadership.
These “Surprises” Are Less Random Than You Think
“Things were going well and then my client gave me a call to escalate an issue on their end I had heard nothing about right up until then.”
“We hired a company three years ago to document all of our processes. It’s like a 300 page book and my team never uses it. It’s frustrating when I ask them if they used the SOP and they tell me no.”
“I regularly find out about issues like three weeks after they’re identified. I’m not sure if the team is afraid to tell me or just don’t think to loop me in. But I don’t like it.”
All of these are real anecdotes from companies we’ve helped.
And they aren’t shocking surprises. At least to us. These are symptoms of unclear ownership, unclear decision making rules, and then when the ambiguity finally surfaces, it presents as a surprise.
Why is my team not following process?
Contrary to popular belief, it’s not due to lack of discipline. It’s due to the design of your processes. If people aren’t following processes, it’s likely because they’re over engineered, out-of-date, or too rigid.
Instead of viewing this as defiance from your team, record it as a data point. This is what we do at The 128 Collective, and it’s low hanging fruit for you to implement in your company as soon as today.
You want to collect data points on which processes aren’t being followed and by who. Then you can better understand the why and how to fix it.
“As the founder, you’re a bottleneck”
Look, we’re on social media. We hear this messaging over and over again, we know you’re tired of it. With a company who delivers client-facing services, this shows up as every decision needing to go through leadership.
It creates a layer of ambiguity at all levels of the business. Does the founder actually need to approve this? We better make sure. Better safe than sorry.
And as the founder, you probably have no idea that every petty approval is passing through you.
If one person is the review/approval system, you will naturally lose visibility into the work and your processes. Or, if there is no ownership around decision making, you will also lose visibility into the work and your processes.
Something you can ask yourself to start identifying these gaps is: If I shut my phone off for the next week and did no work, what would I come back to that would be stuck?
A lot of founders will reply with, approvals for Statement of Work, blog approvals, social media post approvals, conference booth design approvals, deliverables for key accounts, milestone calls with clients, etc. Those are all bottleneck points.
Where The Work Is Actually Hitting a Wall
Handoffs Without Owners
Work sits in limbo between teams or individuals because there’s no “definition of done”.
Judgment Calls Without Context
Decisions requiring undocumented context stall when that person is unavailable — this is often where "surprises" originate.
The tool that replaced a decision, not made one
Buying software before defining ownership just gives the same confusion a new interface.
Why The Tool You Want to Buy or Build Won’t Fix This
Human instinct is going to be, “let’s do something about this”. Usually lends to buying a tool. Or in 2026, it might be building a tool with Claude and OpenClaw.
That’s not going to work.
Here’s why.
The system has to exist before the tool can support it, not the other way around.
This is true 101% of the time.
A tool is the easy way out. Do not take it.
What does gaining visibility require?
We encourage you to think less of visibility in terms of well-built dashboards, three page reports, and weekly status calls. Visibility should look like clear ownership, well defined handoffs, and decisions that don’t require leadership.
The goal isn’t more process, it’s the right structure, so your team can easily follow the process. If you’re interested in learning where the gaps in your company might be, book a complimentary call with our Founder, Erica, to start digging in.
-
Because the SOP was built around how leadership wanted work to happen, not how it actually happens on the ground. When following the process is slower or more confusing than just winging it, people will route around it every time — not out of laziness, but because the process is adding friction instead of removing it.
-
Visibility usually disappears because one person — often the founder — is quietly acting as the decision-making system instead of the company having one. As the business grows past what that person can track in their head, information stops reaching them in time, which is exactly when "surprises" start showing up.
-
No — a tool doesn't create a system, it just gives an undefined system a new place to live. If ownership and decision rights weren't clear before the software, they won't be clear after it; you'll just have the same confusion spread across more tabs.
-
It's when every ambiguous decision in the company routes back to one person, usually the founder, because there's no defined system for resolving it otherwise. It feels like hands-on leadership, but it's actually a missing operational structure — and it's the direct cause of both the visibility gaps and the burnout founders describe.
