How to use metaphor, story “shards,” and tabletop exercises as a kaleidoscope for re‑examining incidents and uncovering deeper engineering and leadership insights.
How an intentionally analog, “paper path” deployment workflow—backed by premortems, risk analysis, and incident‑readiness practices—can make complex software releases safer, more traceable, and easier to recover from.
How to turn invisible, slow‑burn software risks—like technical debt and security vulnerabilities—into a tangible, desk‑sized “risk clocktower” that drives continuous, proactive risk management.
How to turn past outages into a rotating Ferris wheel of stories, practice, and continuous learning—using analog horror vibes, structured retrospectives, and role‑play to build a more resilient engineering culture.
How a low-tech, rolling paper timeline—an “Analog Incident Story Railcar”—can transform security and reliability incident response, enable blameless postmortems, and bridge the gap between complex data and human understanding.
How to turn complex, messy incidents into compact, visual, reusable lessons—so your organization actually learns from outages instead of repeating them.
How to turn incident postmortems into an ‘analog story orchard’—a visible, shared learning system where teams grow resilience from their hardest‑learned lessons instead of repeating them.
How a simple, physical “incident trolley” can turn scattered postmortems into a shared, rolling story of resilience that moves through your office—and your culture.
How to build a physical, low-noise “incident story lantern” wall that makes system risk visible at a glance, supports DevOps collaboration, and reduces cognitive load without adding more digital alerts.
How to turn real production outages into tangible, shuffleable incident story cards that power better game days, faster responses, and stronger DevOps teams.