Two projects taught me the same lesson from opposite ends of the market: a wellness marketplace for consumers, and a data-discovery platform for enterprise analysts. Different users, different stakes, identical failure mode — the product had the right answer, and people still wouldn't act on it.
The pattern: correctness isn't enough
On the enterprise search redesign, analysts weren't short on results — they were drowning in results they couldn't vouch for. Relevance ranking buried the things that actually decided whether data was usable: where it came from, who owned it, how fresh it was. On HerbaLink, the marketplace had qualified herbalists — but a first-time client couldn't distinguish a licensed practitioner from a confident hobbyist, so the cautious ones simply left.
Users don't act on information. They act on information they can defend — to their boss, or to themselves.
Designing with trust, not adding it
The fix in both cases wasn't a trust badge bolted on at the end. It was rebuilding the core interaction around trust signals. In search, provenance became a first-class column instead of a tooltip, and the ranking model was reframed around lineage, ownership, and recency — analysts went from 40 candidate results to the 4 they could defensibly act on. In HerbaLink, verification became layered, inspectable proof — license, education, peer endorsements — surfaced at every decision point in booking, right where doubt creeps in.
Why this matters to your bottom line
Trust is where products quietly hemorrhage value. The analyst who can't vouch for data re-does the analysis. The client who can't verify a practitioner closes the tab. None of that shows up in an error log — the product 'works.' It just doesn't get believed. Treating trust as a material you design with — not a feeling you hope users develop — is one of the highest-ROI moves available, because it converts existing correctness into actual usage.