Processes rarely fail dramatically. They tend to degrade gradually, accumulating workarounds and informal fixes until the gap between how work is supposed to move and how it actually moves becomes large enough to cause real problems. By that point, the degradation has usually been visible for some time to the people closest to the work. This article covers five specific indicators that your operational processes have fallen behind your organisation's current needs.
The same problems keep surfacing in different meetings ¶
If a particular type of issue, a delayed handoff, a miscommunication between departments, a recurring error in a specific output, keeps appearing in your team meetings despite having been 'resolved' multiple times, that is a process problem, not a people problem. Recurring issues that survive repeated attempts to fix them are almost always structural. The fix that was applied addressed a symptom rather than the underlying design flaw.
New starters take significantly longer to become effective than they used to ¶
When an organisation is small, new starters can learn how things work by proximity. As the organisation grows, that informal transfer of knowledge becomes unreliable. If your ramp time for new hires has increased without a corresponding increase in role complexity, the most likely explanation is that the tacit knowledge required to do the job well has never been made explicit. That is a process documentation problem.
Senior people are regularly involved in decisions they should not need to make ¶
When a director or founder is consistently pulled into operational decisions that should be resolvable at a lower level, it usually means that the decision-making framework is unclear or absent. People escalate not because they are incapable of deciding, but because they are uncertain about their authority to do so. Redesigning the process means making that authority explicit, not just telling people to use their judgment.
Your tools are creating work rather than reducing it ¶
A technology stack that made sense at thirty people often creates significant friction at one hundred. Systems that were not designed to integrate with each other require manual reconciliation. Data that lives in multiple places has to be consolidated by hand. If your team is spending meaningful time on tasks that exist solely because your systems do not talk to each other, that is a process and systems problem with a tractable solution.
You cannot describe your core processes in writing ¶
This is the most direct test. If you asked three people in your organisation to write down how a specific core process works, and the three descriptions were significantly different, your process is not documented; it is distributed across people's heads. That is manageable when those people are present and stable. It becomes a serious risk when someone leaves, is absent, or when the organisation needs to scale the process beyond its current capacity.
If two or more of these apply to your organisation, an Operational Diagnostic is likely the most useful starting point. It gives you an evidence-based picture of where the problems actually originate before any changes are made. You can read more about how the diagnostic works in our article on what an operational diagnostic involves, or book a discovery call to discuss your specific situation.