Evidence Over Opinion: How to Make Product Decisions That Hold Up
Every product organization has had the meeting. A decision needs to be made, the room splits into camps, and the conversation circles until the most senior or most persistent voice wins. The decision gets made, but nobody is quite sure it was the right one, and it gets revisited a month later.
One of the principles Quint Consultation stands for is evidence over opinion. Not because experience and judgment don't matter, but because they work best when they're grounded in what's actually happening with customers, the business and the operation.
Why opinion-driven decisions are so common
Opinion fills the space where evidence is missing. In many industrial technology companies, the information needed to make good product decisions exists, but it's scattered:
- Customer feedback lives in sales notes and support tickets
- Usage data from connected devices or software platforms goes unanalyzed
- Field teams know where products fail in the real world, but rarely get asked
- Financial impact of product choices isn't tied back to the roadmap
When that information isn't pulled together, people default to instinct, anecdote and the most recent conversation they had.
Three sources of evidence that matter most
1. Customer understanding
Go beyond feature requests. Customers will tell you what they want built; the more valuable question is what outcome they're trying to achieve and what's getting in their way. Structured conversations with a range of customers, not just the loudest ones, reveal patterns that a single request never will.
2. Data
For SaaS platforms and connected devices, usage data is one of the most underused assets a company has. Which capabilities do customers rely on daily? Where do they drop off? Which deployments expand and which stall? Even simple, consistent measurement beats a perfect dashboard that never gets built.
3. Operational insight
In manufacturing and field environments, the gap between how a product works in the lab and how it works on site can be enormous. Installation teams, service technicians and operations staff see that gap every day. Their input often explains problems that data alone can't.
Balancing the three forces
Good product decisions rarely optimize for one thing. They balance customer needs, business goals and technical realities. A feature customers love may not be worth building if it can't be supported profitably. A technically elegant solution may miss what the market will actually pay for.
A useful test for any significant decision:
- What evidence tells us customers need this?
- How does it advance a specific business objective?
- What will it realistically take to build, deploy and support?
- What would we expect to see if we're right, and how will we know if we're wrong?
That last question matters. Evidence-based teams don't just use data to make decisions; they define in advance how they'll measure whether a decision worked.
Experience still matters
Evidence doesn't replace leadership. Data is often incomplete, customers can disagree, and some decisions have to be made before all the facts are in. That's where experienced product leadership earns its keep: knowing which evidence to trust, how to weigh it, and when there's enough to act.
The goal isn't to remove judgment from product decisions. It's to give judgment something solid to stand on.
Ready to align strategy, execution, and results?
Contact Quint Consultation to discuss your product and business challenges.


