Posts
Cynefin for Technical Support Managers: Match the Response to the Situation
Cynefin helps support managers match their response to the situation: runbooks for clear problems, experts for complicated ones, experiments for complex ones, action for chaos.
A Runbook for When Your Brain Goes Offline
A structured outage runbook removes thinking under stress — five questions, a timecode rhythm, and clear roles to cut response time and keep customers informed.
Bad Agent or Bad System
Hanlon's Razor applied to ticket quality review — how to diagnose whether a low-scoring ticket is a skill gap, a process gap, or a tooling gap before you blame anyone, including in multi-agent tickets.
-
The New Technical Manager Manual Five essential frameworks every new technical manager should internalise — from giving feedback without ego to running incidents without chaos.5 min read
-
The Incident Manager's OS: OODA × RACI × Incident Commander Speed alone isn't enough. OODA gives you rhythm, RACI gives you role clarity, and the Incident Commander gives you decision ownership. Three layers that turn crisis response into something repeatable.7 min read
-
Your Incident Response is Stuck on Observe Most incident response teams are stuck in an endless Observe loop — gathering data without building shared understanding. Here's how John Boyd's OODA framework fixes it.6 min read
-
Occam's Razor: Why Simpler Explanations Usually Win A practical guide to Occam's Razor: why simpler explanations usually win, how to apply it in software and life, and common mistakes to avoid.5 min read
-
The 4D Framework of AI Fluency A breakdown of Anthropic's 4D Framework — Delegation, Description, Discernment, and Diligence — the four core skills for working effectively with AI.4 min read
-
Race Prompting Framework A guide to the RACE prompting framework — Role, Action, Context, and Execute — designed to reduce ambiguity and improve the quality of AI outputs through structured prompt construction.3 min read
-
What is Product Requirement Document (PRD)? A guide identifying the key areas of a well-written PRD for agentic coding, with a ready-to-use prompt to capture all sections including problem statements, goals, features, navigation flow, UI design, and out-of-scope items.4 min read