I shipped a feature that worked. The metrics proved it. Adoption was moving in the right direction, conversion was up, and technically we nailed the brief. But walking around the office, I could feel it: nobody believed it was working. Some of the stakeholders around the table were new to the company. Some didn’t speak engineering fluently. A few had been burned by promises before - other projects, other teams, other times things looked good on paper and fell apart in production. They needed to feel confident, not just read it in a dashboard.
So I stopped expecting the deck to do the work for me.
I started showing up in standups I didn’t need to be in. I repeated the same three metrics in slightly different ways until people could recite them back to me. I acknowledged the skepticism directly—yeah, we’ve shipped things that looked good early and didn’t stick. Yeah, the last initiative promised adoption and didn’t deliver. I didn’t pretend those doubts were unreasonable. I sat with them.What I realized is that confidence isn’t built on truth alone. It’s built on repetition, on being present, on acknowledging the gap between what happened before and what’s happening now. People needed to hear it from me, in person, over and over, until the perception and the reality finally lined up.
A lot of product management is treated like execution. Ship the thing, measure it, move on. But half of it - maybe more - is managing the belief that you know what you’re doing. You can’t just sit back and trust the data to convince people. Sometimes you have to get out in front of it. You have to help people feel safe, even when the metrics say everything’s fine.
The dashboard is your proof. But you’re the credibility.