03 — Systems
Fix the system, not the symptom
Reconstructed example · real work
Process designResearchOperationsApprovals kept stalling and work kept coming back. It looked like people were being slow. Mapping every step showed the real problem: the checks came at the end, so every earlier step was guessing.
- TeamRequest
- TeamDraft
- ReviewersReview A
- TeamBack to team!
- ReviewersReview B!
- Final checkQueue!
- Final checkFinal check!
- ↺ back to Draft
My part, in real life
Review problems kept turning up after teams had already written long, complex documents. I traced it to three things missing at the start: early quality checks, reusable templates and clear guidance.
So I designed help that starts before anyone writes: a structured way to draft, a specialist review, and a feedback loop so lessons flow back into prompts and training. The approach was taken into planning across teams while the new workflow was still being designed.
What this shows
I look past the visible problem, fix the cause, and build the lesson back into the system.