Tim Harford, 2011

“We need to be a little more systematic about trial and error.”

Tim Harford argued for this discipline in his 2011 TEDGlobal talk about complex problems and the “God complex.” Using examples from engineering, medicine, and economics, he contrasted confident top-down answers with variation, selection, and repeated experiments that allow workable solutions to emerge. Trial and error is not random thrashing. Systematic experimentation specifies alternatives, protects feedback from hierarchy, and creates a way to retain what works while removing what does not. It is especially useful when causes interact and no expert can reliably predict the full system. Behind the concise wording is a claim about how organizations create results. It encourages leaders to look beyond individual effort and examine design, incentives, information, relationships, and the customer context that determine whether a good intention becomes reliable performance.

Leaders can fund several bounded approaches, agree on comparable outcome measures, and decide in advance how results will affect resources. Independent evaluation and a written baseline reduce the temptation to reinterpret every result as support for the most politically favored idea. Managers can translate the claim into a small experiment with a baseline, an owner, a defined customer or employee outcome, and a review date. Specificity protects the work from drifting into broad language that nobody can challenge or verify.

Some experiments expose people to unacceptable risk or distribute costs unfairly. Ethical limits, informed participation, reversibility, and monitoring belong in the design. Trial and error should never become permission to use customers or employees as unwitting test subjects or to repeat preventable harm. Responsible use also requires naming the tradeoff. Speed, cost, autonomy, safety, equity, and learning may not all improve at once. People closest to the consequences should have a meaningful voice, and uncertainty should be reported instead of hidden behind confidence.

Organizations can now run thousands of software and marketing tests, but optimization can narrow around the wrong metric. A system may improve clicks while degrading trust, accessibility, or long-term value. Better experimentation pairs local measures with guardrails and periodic review of the objective itself. Select a complex decision where debate has stalled. Define two genuinely different approaches, one shared outcome, two safety constraints, and a review date. Document what would count as failure so the organization can learn without asking every experiment to justify itself after the fact. Evidence from the experiment can guide scaling, revision, or stopping. The durable lesson is to join purpose with measurement and human judgment, so the organization becomes better at seeing reality and responding before a local success or failure hardens into mythology. Recording the decision and its limits gives colleagues a foundation they can inspect, challenge, and improve instead of asking them to rely on memory, authority, or an unexplained result.