If more than one sounds familiar, that's worth a look.
The same data gets typed into two systems by hand
If a person is re-keying information that already exists somewhere else, that's not a training problem — it's a missing connection between two tools.
Work sits waiting on one person to notice it
A request that only moves forward once someone happens to check an inbox or a queue is a process with no real routing — just hope.
The same handful of questions get answered from scratch every time
If a support or sales conversation keeps hitting the same five questions, that's a sign the answer belongs in a system, not in someone's memory.
Nobody fully trusts the numbers in the weekly report
When a report is assembled by hand from several systems, errors creep in quietly, and eventually nobody trusts it enough to act on it fast.
Growth means hiring more people to do the same repetitive task
If the only way to handle more volume is more headcount doing exactly what the last hire did, the process — not the team — is the bottleneck.
Something breaks whenever the one person who understands it is out
A process that only works because one specific person holds it together in their head is a risk, not a system.