Problem Solving is the disciplined sequence of stabilizing perception, naming what matters, framing the issue at the right level, and designing an intervention the organization can learn from rather than merely react through.
This competency resolves the difference between speed as anxious motion and momentum as motion that still points the right way under pressure.
The tension it resolves
Under pressure, leaders often solve the first story that fits the pain, at the wrong level, with a mechanism mismatched to the problem's real nature. The organization then manages a portfolio of reactions instead of resolving the constraint that produced the original miss.
What the competency demands
In practice, this competency requires resisting the urge to jump to solutions before understanding has caught up with urgency, and treating a problem as a signal about fit rather than a personal failure to be hidden. It also requires knowing when stopping is the more competent move than continuing.
Across Levels of Work
1Level 1 — QualityProblems arrive as abnormality: the discipline is noticing variance, containing it, and restoring the standard cleanly.
2Level 2 — ServiceProblems become rhythmic rather than purely technical, showing up as growing queues, dropped handoffs, or inconsistent experience.
3Level 3 — PracticeThe work shifts from restoring the standard to improving the method, or to testing a new approach when the old one is aging out.
4Level 4 — Strategic DevelopmentProblems resist local fixes and require redesigning systems, decision rights, and thresholds across interdependent functions.
5Level 5 — Strategic IntentRecurring problems become signals that underlying direction or viability assumptions are drifting and must be tested.
This competency has its own chapter in the second edition.