The Diagnostic Hierarchy

Pipeline problems have a hierarchy: the symptom is what the dashboard shows (revenue miss, low win rate), the proximate cause is the conversion rate that dropped, and the root cause is why it dropped. Most organizations stop at the proximate cause — "our Discovery-to-Proposal rate fell from 60% to 42%." That is a diagnosis of where the problem is, not what the problem is. Root cause analysis goes deeper: did lead quality decline? Did the discovery process change? Did a competitor launch a new product? The root cause determines the remediation.

1. Symptom Layer The observable problem: missed quota, declining win rate, growing pipeline age. Symptoms are aggregated outcomes — they tell you something is wrong but not where. Start here, but do not stop here.
2. Proximate Cause Layer The specific conversion rate or metric that changed. Decompose the symptom by stage: which stage-to-stage conversion rate declined? By segment: did it decline across all segments or just one? By time: when did the decline start? The proximate cause narrows the investigation from "something is wrong" to "this specific thing changed."
3. Root Cause Layer The underlying driver of the conversion rate change. Did lead source mix shift (more low-quality leads)? Did rep behavior change (fewer discovery calls per deal)? Did the market shift (new competitor, economic headwind)? Root causes require qualitative investigation informed by quantitative signals. Pull deals from the affected cohort and interview the reps who worked them.