Fix problems at the deepest causal link you can reach…

When This Fires

• During root cause analysis when deciding where to intervene
• After mapping a causal chain and choosing the intervention point
• When a surface fix has been applied but the problem keeps recurring
• Any problem-solving context where the symptom is downstream of multiple causes

Common Failure Mode

Fixing the visible symptom because it's the most accessible: "The deploy broke, so we'll add a pre-deploy check." But the deploy broke because the test suite doesn't cover the failing code path (deeper), which happens because the team doesn't write integration tests (deeper still), which happens because there's no testing culture or allocated time (deepest actionable). A pre-deploy check catches one class of failure; building testing culture prevents the entire category.

The Protocol

When a problem surfaces: (1) Trace the causal chain backward: what caused this? What caused that? Keep tracing until you reach the deepest identifiable link. (2) For each link, assess: do I have both ability (can I change this?) and authority (am I permitted to change this?)? (3) Intervene at the deepest link where both criteria are met. (4) If you can only reach a surface link → implement the surface fix, but document the deeper links as future intervention targets. Surface fixes buy time; deep fixes solve the problem.