01 / Change
Change a Live Workflow Without Losing the Cases Inside It
Safe workflow change needs a version boundary, a plan for open cases, observable checks, and a tested way back.
Read 3 min brief →Independent operations field guide
Make the work
visible.
Practical briefs for mapping handoffs, finding exception paths, and choosing where automation can help without hiding responsibility.
Open the briefing bookA workflow is a promise about what happens next.
- 01RequestWho can start it?
- 02QualifyWhat must be true?
- 03DecideWho owns the call?
- 04DeliverWhat closes the case?
- 05LearnWhat changes next time?
Current briefing book
Seven notes for better operating systems
02 / Technology
Choose a Workflow Tool From the Work, Not the Feature List
Tool selection becomes clearer when the team tests its real decisions, exceptions, evidence, and audit needs against a small working scenario.
Read 3 min brief →03 / Service
Write Service Levels for Internal Work
Internal service levels work best when they define a complete request, a meaningful outcome, and the conditions that can change the clock.
Read 4 min brief →04 / Measurement
Measure Waiting Time Before You Measure Productivity
Most workflow delay occurs between activities, so elapsed time and queue age reveal more than counts of completed tasks.
Read 3 min brief →05 / Control
Remove Approval Layers Without Removing Control
A useful approval changes the risk of a decision. A repeated approval often changes only the waiting time.
Read 4 min brief →06 / Exceptions
Design an Exception Queue That Can Actually Empty
An exception queue needs ownership, context, priority, and a return path or it becomes permanent storage for unresolved work.
Read 3 min brief →07 / Design
Map the Decision Before You Automate the Task
A workflow map becomes useful when it shows decisions, evidence, owners, and exception paths instead of only boxes and arrows.
Read 3 min brief →