Intellectually Honest Problem Memo
Name organizational problems and document how you personally contributed to each one.
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
The Intellectually Honest Problem Memo is a structured diagnosis written when an organization begins losing focus, accountability, or decisiveness. The author reduces a sprawling situation to a small set of core problems, then records under each one how their own choices, omissions, or lost focus contributed. That second move changes the memo from an accusation into a leadership instrument: admitting personal responsibility makes the diagnosis more credible and enables a more candid conversation with others. The draft should be tested with trusted colleagues, refined against evidence, and then used to call plays rather than merely describe dysfunction. The method depends on intellectual honesty—the willingness to acknowledge weaknesses early instead of making excuses, sugarcoating performance, or waiting for the next initiative to solve structural problems.
Origin
Brad Garlinghouse wrote Yahoo’s leaked Peanut Butter Manifesto after a critical New York Times article. The hosts use it as an example of a non-CEO leader naming systemic problems and taking action. Extracted from Marketing Against The Grain.
Core principles
- 01Name problems before proposing solutions.
- 02Reduce complexity to a small number of core issues.
- 03Treat personal contribution as part of every diagnosis.
- 04Seek feedback before presenting the memo as definitive.
- 05Use honesty to surface problems while they are still repairable.
How to run it
- 1
Observe the System
Collect examples of recurring dysfunction, weak outcomes, delayed decisions, and wasted effort. Separate systemic patterns from isolated mistakes.
Pro tip Look for problems that appear across several teams or persist through multiple planning cycles.
Watch out Do not build the diagnosis around a single frustrating incident.
- 2
Distill the Core Problems
Group the evidence into a short list of causal themes. State each problem plainly enough that leaders cannot hide behind jargon.
Pro tip Aim for roughly three to five core problems rather than a catalogue of symptoms.
Watch out A long list can become an excuse to avoid prioritizing the real causes.
- 3
Document Your Contribution
Under every problem, write what you decided, overlooked, tolerated, or failed to clarify. Be specific about the causal link between your behavior and the current situation.
Pro tip Use first-person statements that identify decisions and omissions.
Watch out Do not add a token admission followed by a longer explanation blaming others.
- 4
Test the Diagnosis
Ask trusted colleagues to challenge the problem statements, evidence, and account of your contribution. Revise the memo where their feedback reveals gaps.
Pro tip Invite disagreement explicitly so feedback does not become ceremonial approval.
Watch out Do not circulate an untested diagnosis as established fact.
- 5
Call the Plays
Use the final memo to align leaders on what must change, who owns the response, and how progress will be measured. Move from diagnosis to decisions.
Pro tip Distinguish reversible corrective actions from rare bet-the-company decisions.
Watch out A memo that produces no ownership or action becomes another artifact of indecision.
In the wild
Yahoo SVP Brad Garlinghouse distilled the company’s problems into a small number of themes, including poor focus, unclear ownership, duplicated work, and indecision. Rather than waiting for the CEO, he wrote a memo that named the dysfunction and proposed action.
→ The leaked memo became a durable case study in diagnosing organizational failure, even though Yahoo ultimately failed to restore the required culture.
A founder notices missed launches and inter-team conflict. She groups the symptoms into unclear priorities, weak product ownership, and delayed hiring decisions. Under each heading, she records how her own changing directives or avoidance contributed, asks two executives to challenge the draft, and then assigns corrective owners and metrics.
→ The leadership discussion begins with shared evidence and founder accountability rather than defensive blame.
Common mistakes
Writing a Blame Memo
A document focused only on other people’s failures makes recipients defensive and avoids the author’s leadership responsibility.
Cataloguing Every Symptom
A sprawling list obscures root causes and weakens the organization’s ability to prioritize corrective action.
Stopping at Diagnosis
Naming problems without assigning decisions, owners, and measures reproduces the indecisiveness the memo identifies.
Is it for you?
Best for
It is best for leaders who see systemic problems emerging and need an honest basis for corrective action.
Not ideal for
It is not ideal as a blame document, a substitute for evidence, or a public attack on individuals.
From the transcript
“Are they able to admit where their weaknesses are?”
“Really what we're saying is if you are in a situation in an organization where you're seeing these things happen, name the problems.”
“But no, but it's a very powerful exercise because it forces you to be really honest with yourself.”
From the episode
This Leaked Memo From Yahoo Explains Why Big Businesses Fail