The Problem-First Method

Most product books preach discovery from a keynote stage. Kevin Dias wrote from the wreckage of his own Autopay mistake, spending three months building what a competitor had while real pain sat quietly in support tickets. The Problem-First Method is his honest guide back from that expensive drift.

This isn't a unicorn memoir. Dias builds Ambiki for pediatric therapy practices, where customers hand you solutions, not broken workflows. He confesses to animal avatars nobody wanted, nearly shipping APIs over buzzwords, and watching Autopay flop because therapists simply wanted control. I kept nodding at my own Tuesday rush toward mockups. The book reads more like a postmortem than a pitch deck, though the Juicero chapter right after Safe Oasis restates a lesson Ambiki already proved. Then the wins land: ninja fireworks keeping four-year-olds on teletherapy calls, billing cut from two weeks to two minutes after asking Nicole one better question, and practical tools like Feature Alignment Documents for teams staring down Friday's sprint review.

The writing stays lean and scene-driven, never drowning in consultant-speak. Dias reads like a sharp colleague, not a guru: dry and self-deprecating in failure postmortems, more engaged when the COVID teletherapy chapters pick up. Jamie and Chloe feel lived-in; the kindergarten parking lot is the book's sharpest lesson on stakeholder trade-offs.

If you've ever vowed to stay problem-first, then greenlit the competitor's feature by lunch, you'll recognize yourself here. Dias won't hand you a miracle framework. He'll make you harder to fool when sales is waiting. Whether you pause before the wireframe is another matter entirely.