The Psychological Solution Hierarchy
Solve problems with psychology before engineering for 10x cheaper results
The Psychological Solution Hierarchy challenges the default approach of throwing engineering and money at problems by asking: can this be solved psychologically first? Sutherland's key example is the Eurostar, where £6 million was spent reducing journey time by 40 minutes. For 0.01% of that cost, Wi-Fi could have improved enjoyment more. For 10%, supermodels serving free wine would have made passengers request slower trains. The framework proposes evaluating every problem through three lenses—technical, economic, and psychological—and seeking solutions at the intersection. Organizations systematically underweight psychological solutions because they lack the institutional frameworks that engineering and economics enjoy.
- Psychological solutions are typically orders of magnitude cheaper than engineering solutions for the same problem
- Organizations have a structural bias toward mechanistic solutions because they fit existing evaluation frameworks
- The nature of an experience depends not just on its objective qualities but on the uncertainty, meaning, and control surrounding it
- Every problem should be evaluated through technical, economic, AND psychological lenses before choosing an approach
- Define the problem in human termsBefore jumping to solutions, restate the problem from the user's emotional and psychological perspective. The Eurostar problem isn't 'the train is too slow'—it's 'passengers are bored and unproductive during the journey.' The Underground problem isn't 'trains are infrequent'—it's 'passengers feel anxious not knowing when the next train arrives.' Human-centered problem definition opens entirely different solution spaces.
- Generate solutions across all three domainsBrainstorm solutions in three categories: technical/engineering (build something new, optimize something existing), economic (change prices, incentives, or resource allocation), and psychological (change perception, framing, information, or context). Force yourself to generate at least three psychological solutions before evaluating any of them. Most teams skip this step entirely.
- Compare cost-per-unit of satisfactionEvaluate solutions not by their objective impact but by their impact on human satisfaction per dollar spent. The countdown display on the Underground platform cost almost nothing but delivered the highest satisfaction improvement per pound. Wi-Fi on Eurostar would cost 0.01% of the engineering solution while delivering more perceived value. This metric consistently favors psychological solutions.
- Test the psychological solution firstBecause psychological solutions are cheaper and faster to implement, test them before committing to engineering solutions. Run a small pilot: change the signage, add information, reframe the narrative, alter the environment. If the psychological solution captures 80% of the value at 1% of the cost, the engineering solution may be unnecessary. Korea tested countdown timers on both red and green lights—the test revealed which application worked.
- Layer solutions from psychological to technicalDeploy solutions in order of cost-effectiveness: psychological first, then economic, then engineering. Each layer may reduce or eliminate the need for the next. Google combined all three—simple interface (psychological), free service (economic), and excellent algorithm (technical)—but the psychological simplicity was arguably the most valuable differentiator.
Transport for London achieved its highest passenger satisfaction improvement per pound spent not by adding trains or increasing frequency, but by installing simple countdown displays on platforms. The insight: a seven-minute wait with certainty is less painful than a four-minute wait with uncertainty. The psychological solution addressed the real problem (anxiety) rather than the assumed problem (wait time).
Eurostar spent £6 million to reduce the Paris-London journey by 40 minutes—a pure engineering solution. Sutherland argues that 0.01% of that budget on Wi-Fi would have improved enjoyment and usefulness far more, or 10% spent on premium hospitality would have made passengers want the journey to last longer. The company solved the wrong problem at 100x the necessary cost.
Sutherland observed a fundamental asymmetry in organizations: creative, psychological ideas must pass through rational gatekeepers (cost-benefit analysis, feasibility studies, ROI calculations), but engineering solutions never have to pass through creative review. Nobody says 'the numbers add up, but let me show this to some crazy people to see if they can find something better.' This one-way filter systematically eliminates the cheapest, most effective solutions. He traces this to the lack of a unified psychological framework—what Charlie Munger calls 'a latticework on which to hang your ideas'—comparable to what engineers and economists have long enjoyed.