Process & Workflow
Fix the Work Before You Add More Technology
Automating a bad process can simply give you a faster bad process.
By Sam Vazquez — Operational Intelligence & Transformation Advisor
What causes workflow bottlenecks?
Bottlenecks rarely come from people working slowly. They come from structure: a single approver, a shared queue with no ownership, a step that requires information produced later, or a handoff where context has to be rebuilt from scratch.
The common shapes I look for:
- Handoffs where context is lost and re-created
- Approval chains that protect nobody in particular
- Ownership that is implied rather than assigned
- Duplicate effort across two teams doing the same check
- Manual steps that bridge two systems
- Wait states nobody measures because nobody is blocked visibly
- Process debt — rules added for a situation that no longer exists
- Permanent workarounds that now carry real volume
Redesign the work before you decide what to automate
Mapping a workflow honestly is uncomfortable, because the documented process and the real one are usually different. The real one includes the shortcut, the spreadsheet, the person everyone messages and the step that only works because someone remembers to do it.
Once the real process is visible, the sequence is simple: remove what does not change the outcome, make ownership explicit at each transition, then automate what remains genuinely repeatable.
“How do we know a process is inefficient?”
Compare the total elapsed time to the actual working time. When work takes four days but contains ninety minutes of effort, the problem is not capacity — it is waiting, routing and handoffs.
The second signal is explanation cost: if people routinely have to explain where something is, the process is not carrying its own state.
“Where should we start if everything needs work?”
Pick the workflow with the highest volume, not the loudest complaint. Volume makes improvement measurable and gives the change enough repetition to stick.
One workflow, end to end, done properly also builds the internal credibility needed for the harder cross-team work that follows.
Questions leaders ask
What is process debt?
Process debt is the accumulation of steps, rules and checks that made sense when they were added but are no longer justified by current conditions. Like technical debt, it is invisible in any single decision and expensive in aggregate.
Should we document the current process first?
Document the real process, not the intended one — including workarounds and informal steps. The gap between the two is usually where the opportunity is.
How do you reduce handoffs without reorganizing teams?
Often by moving the decision rather than the people: give the earlier step the information and authority it needs so the work does not have to travel to find a decision.
Related reading
Find the friction. Fix the work.
Want another set of eyes on it?
You don’t have to know what’s broken before you call me. Finding it is part of what you hire me to do.