03 — Workflow & Systems
Status: Optional · take this after Core Judgment · do not take it first
Purpose
This pack is for people who need to change how recurring work actually gets done across people and tools. It assumes you have completed Core Judgment. If the decision filters from Core are not yet solid, go back. You will need them here. The goal is practical: redesign work so that AI (or any tool) is placed deliberately, human judgment stays in the right places, and you can tell whether the change actually improved anything.
The modules
- Map the Work That Actually Happens — official process diagrams are fiction; the real map starts with real triggers
- Decide Where a Human Must Stay in the Loop — checkpoints are deliberate, not accidental leftovers
- Design the Smallest Useful Change — grand redesigns die; small, testable changes survive
- Measure Before and After — if you do not measure, you are just rearranging steps and hoping
- Failure Handling at Workflow Level — a workflow that cannot surface and handle its own failures is not ready for production
Who this is for
People who own or operate recurring workflows — team leads, process owners, operators, coordinators — and want the machine carrying what it can carry without losing visibility or accountability.
What you will be able to decide after this
- Where a workflow actually starts, and whether the official description matches reality.
- Which steps a human must own, and why.
- What the smallest useful change is — and how you would roll it back.
- Whether a change improved the numbers that matter, not just the steps on a slide.
- Whether the workflow can survive a realistic failure without losing ownership.
Rules of this pack
- Every module builds on the artifact from the previous module. By Module 5 you hold one redesigned workflow, not five worksheets.
- The maps, briefs, and measurements are about one real workflow you care about. Pick it in Module 1 and keep it.
- Nothing here re-teaches Core Judgment. Net value, verification cost, and evidence standards are assumed.
- 45–90 minutes per module. You have a job; this should not feel like a second one.
The checkpoint
You are getting value from this pack when you can:
- Identify the real triggers that start work
- Map work as it actually happens, not as it is supposed to happen
- Place human checkpoints deliberately
- Design small, measurable changes instead of grand rewrites
- Know whether a change improved the numbers that matter
- Handle failure without losing ownership or visibility — and prove it with a simulation
If you are still starting from tools or from idealized process diagrams, stay here and do the mapping work properly.