Draw the Symptom-Cause Boundary
Distinguish the user-visible symptom from the candidate cause during system debugging.
Start with what hurts the user, then trace why. What Is Broken The symptom should be expressed in user or service terms: latency above SLO, failed checkout attempts, missing emails, failed jobs, or incorrect data. This keeps urgency tied to impact rather than interesting internals. Why It Might Be Broken The cause path is the chain behind the symptom. Move through layers deliberately: client, edge, API, queue, database, dependency, configuration, data. Each layer needs evidence before it becomes the next focus. Why This Prevents Waste Teams often fix the most visible machine, not the failing mechanism. The symptom-cause boundary keeps…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in