Solution-First Problem Escalation
Pause before escalating a problem and bring at least one useful next move
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
In discussing company culture, Professor Green says he dislikes being handed a problem without even the beginning of a solution. He suggests that a person can often use a short interval—he gives half an hour as an example—to think of something that contributes to solving it before reporting upward. The operating mechanism is urgency-sensitive: verify the problem, contain what can be contained, spend a bounded period developing options, then report the facts alongside a proposed move and ownership of follow-through. Green pairs this with accountability that is not primarily punitive; the ideal message is effectively that something went wrong, it has been owned, and a fix is underway. Emergencies remain an explicit exception because immediate escalation matters more than a polished proposal.
Origin
Extracted from The Diary of a CEO
Core principles
- 01Problems should surface without avoidable panic
- 02A short pause can produce useful solution material
- 03Ownership includes contributing to the fix
- 04Accountability should support learning rather than punishment
How to run it
- 1
Triage urgency
Determine whether delay creates safety, security, legal, financial, or operational harm. Escalate immediately when it does.
Pro tip Use existing incident thresholds instead of improvising during a crisis.
Watch out Never delay an emergency report to make it look solved.
- 2
Stabilize the situation
Take any safe, reversible action that limits further damage while preserving useful facts.
Watch out Do not make irreversible changes beyond your authority.
- 3
Form one option
Use a bounded period to identify a plausible cause or next action that can contribute to resolution.
Pro tip Green suggests that even half an hour may be enough for a useful contribution in a non-urgent case.
- 4
Report facts and proposal
Tell the responsible person what happened, what is known, what remains uncertain, and what you propose doing next.
Pro tip Separate confirmed facts from your diagnosis.
- 5
Own the resolution
Follow through, report the outcome, and capture what should change to reduce recurrence.
Pro tip Make accountability a source of pride and learning rather than concealment.
In the wild
Bartlett contrasts a colleague who reports that a problem happened and is already being handled with someone who only shouts that the office is on fire. Green adds a third failure mode: apathy. Their preferred employee neither hides nor dramatizes the problem, but takes ownership and contributes to the fix.
→ Management receives timely situational awareness plus a useful route toward resolution.
Common mistakes
Polishing during an emergency
The bounded thinking period applies only when delay is safe; urgent risks should be escalated immediately.
Reporting panic without facts
Dramatization consumes attention while giving the decision-maker little usable information.
Hiding the problem entirely
Ownership does not mean concealing an issue until it can be presented as fully fixed.
Is it for you?
Best for
Non-emergency operational problems where the person who discovers the issue has enough context to suggest a response.
Not ideal for
Safety, security, legal, or fast-moving incidents where waiting to formulate a solution would increase harm.
From the transcript
“i don't like being presented with problems when there's not even an idea of a solution”
“i want people to take ownership i think ownership's important i think accountability is important”
From the episode
Professor Green - How To Overcome Life’s Hardest Challenges & Find A Purpose