How to design deliberate handoffs, sustainable on-call rotations, and SRE-style practices so critical incident context doesn’t sink between development and on-call teams.
How a low‑tech, high‑clarity “cardboard carousel” of paper dashboards can transform incident response, post‑incident reviews, and continuous learning for engineering and business teams.
How hand-drawn “subway maps” of alerts, failures, and escalations can reveal hidden reliability risks that dashboards and code never show—and how to build your own using RBDs, FTA, and gemba-style observation.
How a deliberately low‑tech, pencil‑and‑string “incident radar” can reveal hidden production risks, make SLOs tangible, and turn incident reviews into shared, cross‑functional learning sessions.
How to use simple, paper-first chaos drills and tabletop exercises to build real incident response skills—before you touch production or spin up fancy chaos engineering tools.
How a cardboard “railway toybox” with paper trains can help on‑call teams design safer, clearer, and more reliable handover rituals—before incidents happen in production.
How simple pencil sketches and narrative metaphors can transform painful incidents into a living garden of reliability rituals, supported by DevOps practices, observability, and structured learning.
Explore the “Cardboard Incident Rail Labyrinth,” a hands-on tabletop exercise where teams build tangled paper tracks to visualize and practice navigating multi-threaded outages, uncovering gaps in incident plans and mental models.
How to turn tabletop exercises into a traveling, paper‑based reliability arcade that brings SRE and incident‑response practice out of the conference room and into public, playful spaces.
How a cardboard tabletop ‘city’ of your microservices can reveal hidden risk neighborhoods, change coupling, and failure paths that traditional dependency graphs obscure—and how to use it for powerful incident-response tabletop exercises.