Naming the Cause¶

The umbrella for KCG's diagnostic-discipline work. The diagnostic move is distinguishing surface symptoms from structural causes before designing any intervention.

The problem it solves¶

Most leaders operate in reactive mode. Something breaks, they fix it. Something breaks again, they fix it harder. The cycle feels productive but is the most expensive way to run an organization — every recurrence consumes new resources to address the same underlying cause. The reference cost of unaddressed communication failure alone is approximately $12,506 per employee per year (Grossman / SHRM). This umbrella replaces the reactive cycle with a diagnostic approach: pause and investigate, name the structural cause, design a fix at the source, free up the capacity that recurrence was consuming.

The framing shift¶

The question changes from "Who dropped the ball?" to "What made dropping the ball almost inevitable?" From blame to curiosity. From individual fault to structural condition.

Where this applies¶

The diagnostic move — distinguishing surface symptom from structural cause — applies across three practice domains:

Individual development. What pattern does this client keep encountering, and what structure is producing it?
Organizational strategy. Which problem on the leadership team's plate is a symptom, and which is the cause? Where would intervention actually move the system rather than the noise?
Business growth. Where is the real bottleneck in the growth path? When the same problem recurs at higher scale, what structural condition is producing it — and what intervention would address the cause rather than absorb the cost again?

Courses in this umbrella¶

Root Cause Analysis — Course 03. The first and currently only course in this umbrella. 24 lessons across 7 modules.

Glossary terms anchored here¶

What this umbrella hands off to¶

Naming the Objective takes the named cause and converts it into a finishable objective with constraints, criteria, and a roadmap.