Advisory · redesign
Workflow design that removes the waiting
We redesign how work moves through your organisation: fewer stalls, clearer ownership, decisions made at the right level, and less time spent chasing status.
Why workflows stall
Work rarely stalls because people are slow. It stalls at boundaries: a handoff with no owner, an approval that adds days for little benefit, a brief that leaves the next team guessing, a status question that interrupts real work to answer. Fix the boundaries and the same people produce more, without working longer.
Our redesign method
- Map the current state. We draw the workflow as it really runs, including the workarounds, and mark where time waits.
- Name the decision rights. For each branch we agree who decides, who is consulted and who merely needs to know — written down, not assumed.
- Prototype the new flow. We test a simpler version with real cases on real work, with a small group, before any wide rollout.
- Set the service expectations. We define sensible response times at each handoff so waiting becomes visible and manageable.
- Hand over the routine. Managers get a short operating guide and a cadence for reviewing whether the new flow is holding.
What good looks like
- One clear owner for every step, and no orphan handoffs.
- Approvals only where they genuinely change the risk.
- Briefs complete enough that the next team does not have to guess.
- Status visible without meetings, so progress checks stop interrupting work.
- Escalation reserved for real exceptions, not routine decisions.
Making it stick
A new workflow fails if it exists only on a diagram. We build in the small habits that keep it alive: a weekly fifteen-minute review, a simple owner roster, and a rule that any exception is logged briefly so patterns surface. Over a quarter, teams usually stop needing the scaffolding because the simpler flow has become normal.
A worked example
One employer had a approvals chain that added nine days to a routine request. When we mapped it, we found three of the four signatures existed to catch a problem that had been fixed by a system change five years earlier. Removing two steps and setting a service expectation on the remaining two cut the wait to under two days without adding any risk that anyone could identify. The lesson generalises: most slow workflows are not slow because people are slow, but because nobody has looked at the steps in a long time.
Working with IT and compliance
Redesign rarely happens alone. We bring your technology and compliance colleagues in early, so that a simpler flow is testable in the systems that will carry it and defensible where rules genuinely apply. That partnership is what stops a good diagram from becoming a process nobody can run in practice.