02
State / rule / handoff
Workflow control
Give recurring work clear states, responsibilities, rules, and next steps.
What changes in the operation
Work that can be governed.
- 01
The next step is explicit
People can tell what happens next, who takes it, and what must be true before the work moves on.
- 02
Handoffs survive absence
The flow does not depend on a particular person remembering to chase, explain, or approve the work.
- 03
Recurring work becomes reviewable
A manager can see where work accumulates, waits, or breaks instead of learning about it after a miss.
Operating control
Control that survives the day
A workflow is useful when it keeps work moving through absence, pressure, and changing priorities.
A clear intake instead of informal requests.
Rules that make the handoff repeatable.
Queues that show what is ready and what is blocked.
A traceable path from request to completion.
The problem before the system
Recurring work moves through people and tools without a shared definition of done. Handoffs rely on reminders, and the next step disappears when someone is unavailable or priorities change.
The starting point is the operating constraint—not a feature list or a tool to implement.
Systems involved
Means for work that holds.
The shape is defined around the real work. These are possible means, not products to buy.
- 01
Defined workflows
States and transitions that reflect how the work actually moves, from intake through completion.
- 02
Handoffs and rules
Responsibilities, checks, and decision rules that make the next step clear when work crosses a team boundary.
- 03
Work queues
Prioritized queues that show what is ready, blocked, or waiting—so recurring work does not depend on manual chasing.
A first move
Make the recurring work easier to hold.
A useful first move is narrow: understand one fragile flow, then decide what needs to become clear and reliable.