Noreena Hertz, 2010

“We need to democratize expertise.”

Economist Noreena Hertz made this call in a 2010 TEDSalon talk about using expert advice without surrendering judgment. She urged audiences to listen not only to senior authorities but also to frontline people with relevant experience. Democratizing expertise means widening the evidence considered in a decision. Credentials can indicate deep training, while lived experience, operational proximity, and local knowledge reveal conditions that a distant specialist may overlook. The enduring management question is which decision the idea changes and what evidence would show that the interpretation is wrong. The distinction matters because organizations often preserve the visible result while forgetting the less visible habits and relationships that produced it.

A business can require major proposals to include expert analysis, frontline observations, dissenting views, and customer evidence. Decision makers should explain how conflicts were resolved rather than using one prestigious source as a shield. A useful principle should improve a choice before it becomes a retrospective slogan. Reviewing the mechanism prevents a favorable outcome from being mistaken for proof that every assumption was correct.

The idea does not make every opinion equally reliable. Technical standards, scientific methods, and professional accountability still matter, especially in safety-critical fields. Participation should improve evidence, not erase competence. That requires attention to incentives, affected people, and the conditions under which the idea stops applying. People responsible for execution should help define the measure because they see consequences a dashboard may flatten or miss.

Complex decisions increasingly combine technology, regulation, culture, and operations. Hertz’s warning remains relevant because no single expert is likely to see the entire system or bear all of its consequences. For one upcoming decision, map who has formal expertise and who has direct experience of the outcome. Invite both groups, record disagreements and uncertainties, and state which evidence would cause the decision to change. Recording the decision and its limits gives future teams knowledge they can inspect rather than a success story they are asked to repeat. The next team can reuse the insight while still testing whether its customers, risks, and operating environment are different. A small experiment is useful only when it reveals real behavior. A demonstration arranged for ideal conditions may prove technical possibility while hiding adoption, support, cost, and fairness. The next test should include ordinary users, normal constraints, and a clear comparison so leaders can judge without pretending a pilot is the whole organization. Teams should record exceptions instead of quietly resolving them outside the measure. Those cases often reveal the training, staffing, or policy needed before wider use. A concise public note should show colleagues which observation changed the decision and when the next review will occur.