When the Process Is the Problem
Most managers instinctively look at people when things go wrong. A deadline gets missed, a project stalls, a customer complains—and the first question becomes: who dropped the ball? But more often than you’d expect, the real culprit isn’t a person. It’s the process they were asked to follow.
Broken processes are sneaky. They don’t announce themselves. They show up as vague frustration, repeated mistakes, and team members who seem disengaged or burned out. If your team is working hard but results are still inconsistent, the process deserves at least as much scrutiny as the people running it.
This article will help you identify the signs of a broken process, diagnose what’s actually wrong, and take practical steps to fix it—without derailing your team in the process.
What a Broken Process Actually Looks Like
Not every inefficiency is a broken process. Some friction is normal and even useful. But there are specific patterns that signal something is structurally wrong.
The same mistakes keep happening
If you’re correcting the same types of errors week after week—across different people, different projects, or different time periods—the process is producing those errors. Blaming individuals doesn’t fix that. The system keeps churning out the same outcome because nothing in the system has changed.
No one can explain why a step exists
Ask your team why a particular step is part of the workflow. If the answer is “I don’t know, it’s just how we do it” or “we’ve always done it this way,” that step may no longer serve a purpose. Processes accumulate unnecessary steps over time, especially when they’re never reviewed.
Work-arounds have become standard practice
When people start building unofficial shortcuts around a process, they’re telling you the official process doesn’t work. Pay attention to the workarounds. They often contain the seeds of a better process—or at least point directly at where the current one breaks down.
Handoffs are where things fall apart
The transition points between people, teams, or systems are where broken processes do the most damage. If work consistently gets lost, delayed, or distorted when it moves from one person to another, the process isn’t giving that handoff the structure it needs.
Your team feels exhausted by the work, not energized
A well-designed process reduces cognitive load—it makes the work easier to do well. A broken process does the opposite. If your team members consistently describe their work as frustrating, confusing, or exhausting, it’s worth asking how much of that is structural rather than personal.
Why Managers Often Miss It
There are a few reasons broken processes go unaddressed longer than they should.
The team is managing around it. High-performing employees often compensate for bad processes through sheer effort and improvisation. Things look fine on the surface because people are working harder than they should have to. This masks the problem until someone leaves or burns out.
The process worked before. Many processes were well-designed for an older version of the work—when the team was smaller, the volume was lower, or the tools were different. processes need to evolve as conditions change. What worked two years ago may now be creating drag.
Fixing it feels overwhelming. Managers often sense that something is off but avoid digging in because they’re not sure what to change or they’re worried that changing it will create more problems. So they keep running a system they know isn’t working, hoping it improves on its own. It rarely does.
How to Diagnose the Real Problem
Before you change anything, you need to understand what’s actually broken. Jumping to solutions before you’ve diagnosed the problem is one of the most common process-improvement mistakes.
Map the current process first
Write out every step of the process as it actually happens—not as it’s supposed to happen on paper. Talk to the people doing the work. Walk through a recent example from start to finish. You’re looking for where things slow down, where information gets lost, where people have to make judgment calls that shouldn’t require judgment calls, and where steps seem disconnected from the outcome they’re supposed to produce.
Ask three questions at each step
For every step in the process, ask:
- What is this step supposed to accomplish? If no one can answer clearly, that’s a red flag.
- Is it actually accomplishing that? Compare the intended output to what’s really happening.
- Could this step be simplified, combined with another, or eliminated? Start with a bias toward less, not more.
Look for root causes, not surface symptoms
Use the “five whys” technique: take a specific problem and ask “why” five times in succession. A deliverable was late. Why? Because the reviewer didn’t get it in time. Why? Because the person submitting it didn’t know who the reviewer was. Why? Because responsibility for that step isn’t clearly assigned. Why? Because no one updated the process when roles changed six months ago. That’s the real problem—and it’s fixable.
Talk to your team directly
The people doing the work every day know exactly where the process breaks down. They may not always volunteer it unprompted—especially if they’ve raised concerns before and nothing changed—but they will tell you if you ask sincerely and create a safe environment for honest feedback. Ask what part of the workflow they find most frustrating, what takes longer than it should, and what they would change if they could.
How to Fix It Without Creating Chaos
Once you’ve diagnosed the problem, you can start making changes. The goal is to improve the process without destabilizing the team in the process. Here’s how to do that well.
Fix the most painful point first
You don’t have to overhaul everything at once. Identify the single step or transition that’s causing the most harm and start there. A targeted fix that actually works builds credibility and momentum for further improvements. It also limits the disruption to the rest of the workflow.
Involve the people who do the work
Don’t design the new process in isolation and hand it down. Bring in the team members who are closest to the problem. This serves two purposes: they’ll catch things you’ll miss, and they’ll be far more committed to making the new process work if they had a hand in creating it. People support what they help build.
Define clear ownership at every step
Many broken processes break because it’s unclear who is responsible for what. Someone assumes someone else is handling it. Two people both handle it and create duplication. No one handles it and it falls through. For every step in the revised process, assign a clear owner. That doesn’t mean one person does everything—it means one person is accountable for ensuring the step gets done.
Write it down, but keep it simple
Document the revised process in plain language—enough that a new team member could follow it, but not so detailed that it becomes a burden to maintain. A one-page visual workflow or a brief checklist is often more useful than a ten-page process document that no one reads.
Run a small pilot before rolling out fully
If possible, test the revised process on one project or with one part of the team before changing everything. This lets you catch unintended consequences before they affect the whole operation. Treat it as a learning exercise, not a final verdict. Expect to make adjustments.
Getting Your Team Through the Change
Changing a process—even a broken one—creates uncertainty. People get used to doing things a certain way, and change feels like more work before it feels like less. Your job as the manager is to make the transition as smooth as possible.
Explain the why, not just the what
Tell your team why the process is changing. What problem did the old process create? What should the new one do better? People are far more willing to adapt when they understand the reasoning. Don’t just announce a new procedure—make the case for it.
Give people time to adjust
Even a well-designed process takes time to feel natural. Performance may dip temporarily while people are learning the new approach. Build that expectation in from the start so the team isn’t demoralized if the first few weeks are bumpy. Remind them that the discomfort is temporary and the goal is worth it.
Create a feedback loop
After rolling out the change, build in a deliberate check-in—two weeks or a month out—where the team can flag what’s working and what’s not. This signals that the process is a living system, not a decree. It also catches problems early, before they compound.
How to Prevent Processes from Breaking in the First Place
The best time to fix a broken process is before it breaks. Build these habits into your regular management practice and you’ll spend far less time in crisis mode.
Review processes periodically, not just reactively
Schedule a quarterly or semi-annual review of your team’s key workflows. Ask whether the current process still fits the current reality. Teams grow, tools change, volume shifts, and priorities evolve. A process that hasn’t been reviewed in a year is probably overdue for a tune-up.
Treat friction as a signal, not just an annoyance
When people complain about how something works, resist the urge to dismiss it as resistance or negativity. Take it seriously as data. A recurring complaint about a workflow is often an early warning sign of a process that’s starting to crack under strain.
Build process review into your one-on-ones
Make “what’s getting in your way?” a standing question in your regular check-ins with team members. You’ll surface process problems faster—and the team will feel heard, which matters for engagement and retention.
The Manager’s Role in All of This
Fixing broken processes is one of the highest-leverage things a manager can do. Every hour your team loses to a broken workflow is an hour they’re not spending on the work that actually matters. Every mistake generated by a flawed system erodes confidence, damages trust, and creates rework. Every workaround your team has built is energy that could go somewhere more productive.
When you fix the process, you’re not just improving efficiency. You’re telling your team that you take their time seriously, that you’re paying attention to what makes their work hard, and that you’re willing to do something about it. That sends a powerful message about the kind of leader you are.
The process isn’t the enemy. A well-designed process is one of the most powerful tools you have. But that only holds if you’re willing to look at it honestly—and change it when it stops serving the people and the work it was built to support.
Frequently Asked Questions
How do I know if my team’s process is broken or if it’s a people problem?
Look for patterns that persist across different people and time periods. If the same mistakes keep happening regardless of who’s doing the work, or if your team is working hard but results remain inconsistent, the process is likely the culprit. When multiple team members create unofficial workarounds or can’t explain why certain steps exist, you’re dealing with a structural problem, not a performance issue.
What are the warning signs of a broken workplace process?
The most telling signs include repeated mistakes across different people and projects, team members who can’t explain why certain steps exist, and unofficial workarounds that have become standard practice. Additionally, if work consistently gets lost or delayed during handoffs between people or teams, and your team feels exhausted rather than energized by their work, these are clear indicators of structural problems.
Why do processes break down over time in organizations?
Processes typically break down because they accumulate unnecessary steps over time without regular review. As business needs change, old steps that once served a purpose may become obsolete, but they remain in the workflow simply because “that’s how we’ve always done it.” Additionally, poor handoff structures between people or teams create natural breakdown points where work gets lost or distorted.
How do I fix a process without disrupting my team’s productivity?
Start by examining the unofficial workarounds your team has already created, as these often contain the blueprint for a better process. Focus on fixing the handoff points first, since these cause the most damage when broken. Rather than overhauling everything at once, identify and address the specific breakdown points while preserving the parts of the process that actually work well.
What’s the difference between normal workflow friction and a truly broken process?
Normal friction involves occasional hiccups or minor inefficiencies that don’t follow a consistent pattern. A broken process, however, produces systematic problems: the same errors recurring regardless of who’s involved, widespread confusion about why steps exist, and team members consistently finding ways to work around the official process. Broken processes also create patterns of exhaustion rather than just temporary stress.