Second public asset · Cinderella by Donna Gilmore
A field guide to the repeatable process failures people keep pretending are normal.
For operators, builders, and anyone tired of confusing recurring workflow pain with complexity. If the same process embarrassment keeps returning in different outfits, this is for you.
“If a workflow keeps creating the same kind of pain, it is no longer an incident. It is a pattern.”
Inside Cinderella
The worldview shift
- • Recurring pain is usually a pattern, not a mystery
- • Invisible cleanup is still operational debt
- • Human memory is not infrastructure
- • Naming the workflow crime is the first fix
What this is
The Workflow Crimes Field Guide is Cinderella’s second practical asset: a short guide to the repeatable process failures teams normalize once they happen often enough.
Who it’s for
Operators, builders, founders, and workflow owners tired of watching recurring process failures get renamed instead of fixed.
This page should feel sharper, darker, and more diagnostic than Review Gates — less elegant safety checklist, more naming-and-seeing tool.
What’s inside
A cleaner language for diagnosing operational dysfunction.
The field guide helps you name the repeatable patterns before they harden into culture.
• Recurring work disguised as novelty
• Invisible cleanup hidden behind polished systems
• Confidence without inspectability
• Edge cases pretending to be rare
• Human memory used as infrastructure
• Review removed for aesthetic reasons
Get the field guide
The worldview-deepening companion asset.
Enter your email and I’ll send you the Workflow Crimes Field Guide. You’ll also get future machine-room notes, workflow lessons, and useful operator artifacts from Cinderella.