What podcasting taught me about building products

When I started Hacking Success, I thought of it as a curiosity project. Sit with people who have built something real, ask how they did it, step by step, and publish the conversation. Simple.

I didn't expect the show to become one of the best product schools I've ever attended. But hosting a podcast is secretly training in the exact skill great product people are made of: listening with intent.

Here is what hundreds of hours behind the mic changed about how I build.

1. People explain products better than they explain themselves

Ask a founder to describe their strategy and you'll get the polished version — the one from the pitch deck. Ask them to walk through the day everything almost fell apart and the real system reveals itself: what they actually measured, who they actually called, what they actually cut.

Product interviews work the same way. Users can't narrate their own behaviour, but they can tell you a story — and inside every story sit the requirements your spec was missing. My rule now: never ask for an opinion when you can ask for the last time it happened.

2. Every success story hides a deleted scene

Guests remember the pivot that worked. Nobody remembers the nine pivots that quietly died — and to be fair, they usually weren't documented either. Survivorship bias isn't a flaw in storytelling; it's the default output of it.

The practical fix isn't cynicism, it's sizing. If most experiments fail even for people who eventually win, then no single experiment deserves months of your life. Build small, ship fast, keep the cost of being wrong embarrassingly cheap. The winners I meet aren't right more often — they're wrong more affordably.

3. Questions are UX

On the show, the difference between a flat episode and a great one is rarely the guest. It's whether the host asks the question sitting under the surface: not "how did you grow?" but "what did you stop doing to grow?"

That transfer directly into product work. The prompt on an empty state, the label on a button, the first field of a form — these are interview questions you're asking millions of times. Vague prompts get vague engagement, the same way vague questions get polite answers. Precision in language is precision in data.

4. Consistency compounds in private before it pays in public

Publishing episodes on a rhythm — especially the weeks nobody claps — turned out to be the same muscle as shipping product on a rhythm. The audience grows later; the skill grows immediately. Every episode makes the next one cheaper to make. Every release makes the next release calmer.

Compounding rewards showing up at unremarkable intervals. That's true for shows, products and careers alike.

The meta-lesson

I started the podcast expecting to collect answers. What I actually collected was better questions — about evidence, about bias, about the gap between what people say and what systems reveal.

If any of that resonates, Hacking Success is on every platform. Bring your own product questions; the guests will surprise you.