Most businesses don’t wake up one day and decide their processes are broken. It happens gradually. A workaround here, a “just ask Sarah” there, until one day the team has doubled in size and nobody can quite explain how work actually gets done anymore.
If any of the following sound familiar, it’s worth a closer look.
If a specific task only gets done correctly when a specific person is available, that’s not a process. It’s a dependency. It works fine at 8 people. At 25, it means projects stall every time that person takes a day off, and onboarding anyone else into that role starts from zero.
Ask someone why a task is done a certain way and the honest answer is often “that’s just how we’ve always done it.” That’s a sign the process was never designed. It accumulated. And accumulated processes tend to carry a lot of dead weight: steps that made sense for a five-person team but just add friction for a twenty-five-person one.
Individual teams can be excellent at their piece of the work and things still fall apart, because the failure isn’t within a team. It’s between them. Sales hands off to operations. Operations hands off to delivery. If nobody owns what happens at that handoff point, work sits untouched until someone notices it’s late.
If onboarding means “shadow someone for a few weeks and pick it up,” that’s a real cost, not a minor inconvenience. It slows down every hire, it’s inconsistent (each new person learns a slightly different version of the process), and it doesn’t scale past a certain team size.
If the same bottleneck keeps coming up in different conversations (a report that’s always late, a handoff that always drops something, a task everyone avoids), that’s usually not a people problem. It’s a process gap that keeps resurfacing because nobody has mapped and fixed the actual cause.
None of these signs mean something is fundamentally wrong with the business. They mean the processes that got you here won’t get you to the next stage without some redesign. The fastest way to find out what’s actually costing you time is a structured process audit: map how work actually happens, not how it’s supposed to happen, and get a prioritized list of what to fix first. Read more about how a Process Audit works.