Are Your Lights On? How to Figure Out What the Problem Really Is
A short, funny book that is mostly a sequence of anecdotes making a single argument: most problems people try to solve are not the problems they actually have, and the work of defining the problem is usually harder and more important than the work of solving it.
The authors — Weinberg in particular — write with the light touch of experienced consultants, and the book reads as a collection of cautionary tales disguised as riddles.
For product direction it is essential training in the first skill of the job: noticing when a team is about to spend six weeks solving the wrong problem.
Short, re-readable, and one of the few books in this library you can finish in an afternoon and return to for years.
Central argument
Gause and Weinberg argue that the central failure in problem-solving is not incompetence at finding solutions but the systematic misidentification of what the problem actually is. Their core thesis is that problems are never self-presenting: every problem statement is a representation shaped by whoever is reporting it, and that representation almost always obscures the real issue. The book works through a series of riddles and consulting anecdotes to demonstrate that the problem behind the stated problem is where the real work lies — and that solving the stated problem often makes things worse.
Critique
The book's anecdotal structure, while charming, means its prescriptions remain largely heuristic: it teaches the reader to be suspicious of problem statements without providing a rigorous method for interrogating them. A thoughtful reader could fairly object that the book equips you to diagnose the disease — premature problem-solving — without giving you much procedural guidance on the cure, leaving practitioners with heightened anxiety about problem definition but few concrete tools for doing it more reliably. Its age also shows in assuming a consultant-client dyad as the default context, which maps imperfectly onto the messy, multi-stakeholder environments of modern product organizations.
Why it matters for product
For a product director, the book's sharpest application is in discovery and roadmap decisions: the moment a team receives a brief from a stakeholder or reacts to a metric drop, they are already at risk of solving the representation of the problem rather than the problem itself. Weinberg and Gause's insistence that 'whose problem is it?' is always the first question is directly useful when navigating organizational pressure to ship features that address symptoms — a common failure mode where delivery velocity becomes a substitute for problem clarity. The book also reframes the CPO's role not as solution arbiter but as the person responsible for keeping the team honest about what problem is actually on the table.