Product Discovery: Why Listening First Is the Fastest Way to Ship

I walked into Ford as one of 90 people selected from 3,300 applicants for a leadership development program. You’d think that would come with confidence. Instead, I spent my first weeks asking questions that probably made people wonder if they’d picked the right person.

How does this process work? Why does it work this way? What happened the last time someone tried to change it?

Four promotions in five years. Those early questions were the reason.

The Instinct to Propose: Why New Leaders Get It Wrong

The pressure in every new engagement is to prove you belong. Show you’re smart. Have a point of view. Propose something. This instinct is wrong, and I’ve watched it kill projects.

At Blue Cross, I was brought in to build a healthcare decision engine for 16 million members — find the right care, at the right time, for the right cost. Three variables, life-affecting decisions. I could have imported a framework from a previous company. Instead, I spent time understanding why this three-variable optimization was uniquely hard for the people inside this specific system. What I found was different from anything I would have assumed.

What You Find When You Actually Listen

At every company I’ve worked at, the real problem turned out to be something nobody was talking about. At Ford, the friction wasn’t in the technology — it was in how teams had been organized around the technology. At Blue Cross, the care-finding problem wasn’t about search — it was about trust in the recommendations.

These discoveries only surface when you resist the urge to propose and just pay attention. Not structured research — messy, unfiltered observation. Sitting with people while they work. Watching where they hesitate. Noticing what they’ve normalized.

When Listening Becomes a Shield Against Committing

I’ve also listened too long. On one early engagement, three weeks became five. Stakeholders started asking when I’d have something to show. I’d fallen into the trap of using listening as a shield against the discomfort of committing to a direction.

The signal I watch for now — I call it the pattern saturation point: when I start hearing the same patterns in different conversations, it’s time to stop listening and start building. The prototype always wins the argument — but only after you’ve earned the right to build the right one. That usually happens in week two or three. If you’re still in pure discovery at week six and haven’t synthesized anything, you’re hiding — not listening.

The ROI of Listening: Weeks Saved, Trust Earned

Two weeks of deep listening at the beginning saves months of building the wrong thing. This cadence is now baked into my first 30 days playbook. The founder at Blue Cross didn’t need my framework from my last company. The team at Ford didn’t need an outsider’s opinion on day one. They needed someone who would understand their world before trying to change it.

Years later, I ran into someone from that first Ford team. She told me she’d been skeptical when I started — “all those questions, I thought you didn’t know anything.” Then she laughed. “Turns out you were the only one who bothered to find out what was actually happening before trying to fix it.” That’s the ROI of listening. Not a metric — a reputation that opens doors before you walk through them.