Take Nobody’s Word for It. Seek the Truth.
How the scientific method shows up in the best product organisations.
Given that failure and bewilderment are to be expected in product work, approaching ideas with humility is essential. You can and should hire for humility across product, engineering, and design. But you cannot assume that individual humility will always shine through. The better product organisations make humility structural: they design processes that guide teams to test, fail, learn, and change their minds openly.
Truth-seeking is humility made operational. It is the discipline of treating your assumptions as bets about reality, not facts you already know. It means trying to see the world as it is, not as you hope it is, once believed it was, or need it to be for your preferred solution to work. In product management, truth-seeking means asking: what do we believe, how confident are we, what evidence supports that confidence, and what would cause us to change our mind?
At the individual level, the scientific method is familiar: observe, form a hypothesis, test it, measure what happens, update what you believe, and repeat. Product teams use versions of this loop all the time. Build, measure, learn. Make a bet. Run an experiment. Test a prototype. Interview customers. Analyse usage. Launch small. Iterate.
But the deeper lesson of science is bigger than the mechanics of an experiment.
The Royal Society captured that spirit in its motto, Nullius in verba: take nobody’s word for it. The point was not to reject expertise, but to refuse final authority. Claims should be tested against reality, rather than accepted as fact just because someone stated them with confidence.
The scientific method changed the world because it created a better relationship with belief. Claims could be challenged. Authority could be questioned. Evidence could be shared. Errors could be corrected. Knowledge could accumulate. It did not depend on scientists being perfectly objective. It built a system where arrogance had fewer places to hide.
Product teams benefit from the same principles.
In a truth-seeking product team, ideas are treated as hypotheses, not commitments. Evidence matters more than status. The customer’s reality has more authority than the most senior person’s opinion. Bad news travels quickly. Teams are rewarded for changing their minds when the evidence changes. Decisions are revisited when new information appears. The goal is not to defend what you hope is true, but to discover what is true enough to act on. A truth-seeking team wants the outcome more than it wants to be right.
This matters because many product mistakes are not failures of effort. They are failures of understanding.
A team believes a customer problem is painful, but customers do not care enough to act. A company believes a market is ready, but the timing is wrong. A roadmap assumes a feature will change behaviour, but usage barely moves. A strategy depends on organisational capabilities that do not really exist. A business case assumes customers, sales teams, support teams and technology will all behave in ways they never actually behave.
The costliest product failures often begin as untested beliefs.
Truth-seeking does not remove uncertainty. It makes uncertainty visible. It turns vague confidence into explicit assumptions. It gives the team a way to ask: what would need to be true for this idea to work? What do we know? What are we guessing? What evidence would change our mind? What is the cheapest way to learn the next important thing?
Product management is not the art of having better opinions. It is the discipline of organising a team’s search for understanding.
In product work, you’re always looking to grow your understanding of…
Your customers: What are customers really trying to achieve? What problems are painful enough to change behaviour? What do they value enough to choose, use, recommend, or pay for?
Your product: How is the product actually performing in real use? Are people adopting it, returning to it, and completing the jobs they came to do? Is it creating meaningful value, or merely generating activity?
Your market: What alternatives do customers already have? What is changing in competition, technology, regulation, culture, pricing, or distribution? Where is demand real, growing, and winnable?
Your organisation: What can this company credibly build, sell, support, and sustain? What capabilities, constraints, economics, incentives, or habits shape what is possible? Where do we have an advantage, and where are we fooling ourselves?
Truth can be uncomfortable because products often perform differently from how teams imagine. Customers may ignore the feature everyone was proud of. They may use the product for a different job than the one it was designed for. They may tolerate a painful workflow because switching is hard, not because the product is loved. They may praise the idea in customer interviews but shun it the next day.
A truth-seeking team studies these signals without defensiveness. It asks not only “Did we ship?” but “Did anything meaningful change?” Did customers become more successful? Did behaviour move in the direction we hoped? Did the product become easier, faster, more valuable or more habit-forming? Did the business model strengthen? Did quality improve? Did the product create fewer downstream costs for support, sales or operations?
The best product methods are not rituals; they are mechanisms for keeping teams in contact with reality.
Beliefs are provisional → Ideas become hypotheses. Science works by treating explanations as temporary until evidence strengthens or weakens them. Product management captures this through hypothesis-driven development, assumption mapping, and language like “what would need to be true?” Ideas are not commitments; they are claims to investigate.
Reality outranks authority → Evidence beats opinion. The scientific method reduced dependence on status, seniority, and persuasion. Product teams mirror this when customer evidence, product data, experiments, and market signals carry more weight than the loudest voice in the room.
Claims must be testable → Bets need success criteria. A scientific claim has to be exposed to the possibility of being wrong. In product, this means defining what success would look like before building: target behaviours, leading indicators, adoption, retention, conversion, revenue, satisfaction, or other outcome measures.
Error correction is progress → Learn cheaply and quickly. Science advances by finding and correcting wrong ideas. Product management captures this through prototypes, MVPs, small releases, A/B tests, discovery interviews, and short feedback loops. The goal is not to avoid being wrong; it is to discover where you are wrong before the cost becomes large.
Anomalies are valuable → Failed experiments deserve attention. In science, surprising results often open the door to better theories. In product, a feature that does not work, a metric that moves the wrong way, or a customer who behaves unexpectedly should not be brushed aside. These moments reveal where the team’s model of the customer, product, market, or company is incomplete.
Knowledge should accumulate → Learning becomes organisational memory. Science compounds because findings are recorded, challenged, shared, and built upon. Product teams capture this through research repositories, experiment logs, decision records, opportunity trees, post-launch reviews, and shared customer insights. The team should not merely have experiences; it should get smarter.
Truth-seeking is a system → Discovery becomes continuous infrastructure. The deeper lesson of science is not that one person runs one experiment. It is that a society builds institutions that keep inquiry alive. Product management captures this through continuous discovery, cross-functional product trios, regular customer contact, product analytics, experimentation, and evidence-guided decision-making. The organisation gets better at learning, not just better at shipping.
That does not mean every decision can be reduced to data. Product work also involves judgement, taste, ethics, strategy and vision. Evidence can tell us what customers do. It cannot, by itself, tell us what kind of company we should become or which trade-offs we should be proud to make.
So the aim is not to replace judgement with evidence. The aim is to make judgement sharper, humbler, and better informed.
Modern product practice is full of methods: discovery, experimentation, metrics, research. Beneath all of them is the same principle. We are trying to get closer to the truth before reality corrects us more expensively.
The best product organisations do not simply make better decisions. They get better at making decisions. Their knowledge compounds. Their errors correct faster. Their beliefs are easier to challenge. Their teams become smarter than any individual within them.