Service 02 / 04 · Practice

Workflow Design

Between every two steps in a process there is a handoff, and between every two roles there is an assumption. Workflow design is the discipline of making those handoffs explicit: who receives what, in which state, by when, and what happens when it is late. It is the difference between a process that exists on a wall and one that survives a Tuesday.

Typical engagement: 9–11 weeks · Fixed fee
Signals

You are probably here because one of these is true.

  • ×Work that stalls in someone's inbox with no owner
  • ×Three people who can approve and nobody who must
  • ×New hires productive after ninety days instead of nine
  • ×The same request handled four different ways by four teams
Deliverables

What leaves the building.

Every artefact below is written for the person who has to run the process on Monday morning, not for the appendix of a deck.

  • 01Role-based workflow architecture, not department-based
  • 02RACI and decision-rights matrix per workflow
  • 03Handoff contracts: input state, output state, SLA
  • 04Queue, form and escalation design
  • 05Automation candidates with build-ready specifications
  • 06Role playbooks — one page per role, not a 90-page manual
Engagement shape

How the weeks are spent.

Fixed phases, fixed durations, one named owner on our side and one on yours. No open-ended discovery.

Observe

1 week

Sit with the people doing the work. Record every handoff, wait state and informal workaround.

Map roles

1 week

Translate the process into roles and decision rights. Most bottlenecks are authority problems, not effort problems.

Design

2 weeks

Future-state workflow with handoff contracts, escalation rules and exception paths that hold under load.

Instrument

2 weeks

Queues, SLAs and a weekly flow review so the workflow is visible while it is running.

Outcomes

What we are measured on.

Averages across comparable engagements. We agree the target range before kick-off and report against it at week six and week twelve.

27%
capacity recovered without new headcount
6.1 → 1.8 days
approval lead time after redesign
100%
of handoffs with a named owner and an SLA
Questions

Before you commit.

If your question is not here, send it — we answer scope questions in writing before any engagement letter.

Ask a question
Is this a systems project?
No, though it usually produces one. We design the workflow first so that any system you buy is configured against a decision, not a guess.
How do you handle exceptions?
Exceptions are where workflows fail. We map the top twenty by volume and design an explicit path for each, rather than a general rule that nobody follows.
Will this require new headcount?
Rarely. The capacity we recover usually comes from removing wait states and duplicate review, which is where 60–70% of lost hours sit.
Can you design for a hybrid or remote team?
Yes. Distributed teams need more explicit handoff contracts, not less — this is where the work pays back fastest.
Next practice Operational Efficiency
NEXT STEP

Start with a two-week diagnostic.

Fixed fee, fixed scope, and a written answer to where the waste sits in one process of your choosing.