The Problem-First Method
Stop building solutions in search of a problem. A practical framework to help you recognize when you've drifted from the problem—and find your way back before it's too late.
- Feature Alignment Document (FAD) template
- 10-Question Problem Validation Checklist
- Five Whys Worksheet
- Problem Atlas (Problem-Driven Roadmap)

What you'll learn
Frame the right problem
Stop anchoring on solutions. Use first principles, 5 Whys, and evidence to isolate the real job to be done.
Tools that force honesty
Use the Feature Alignment Document (FAD) and 10-Question Checklist to make “linger on the problem” something you can actually do.
Real stories, real lessons
Study stories—some painful, some amusing—of products that solved the wrong thing, and those that got it right.
Who it's for
→You ship features that get built, launched, and quietly ignored—and you're tired of pretending that's normal.
→You want a way to say "no" to requests that sounds less like gut feeling and more like evidence.
→Your investors asked you to "add AI" and you're pretty sure they don't know what problem that solves either.
→You're looking for a framework that doesn't just sound good in theory but actually changes how your team talks about what to build next.
→You've sat through one too many roadmap meetings where "because competitors have it" was the entire justification.
→You want to stop confusing activity with progress—and you need something more concrete than "just talk to users."
Inside the book
Part I: The Trap
- 01The Autopay Mistake — When "competitor has it" becomes your North Star
- 02Invented Problems — Juicero, Safe Oasis, and the compliance mirage
- 03Solutions in Search of a Problem — Google Glass and the answer nobody asked for
- 04The API Mirage — When discovery gets skipped
- 05Why We Love Solutions — The dopamine trap (ft. Air Canada's chatbot disaster)
- 06The Three Disguises — How solutions sneak past careful teams
- 07The Default Setting — Why solution-first thinking feels like gravity
Part II: The Mindset
- 081,000 Songs in Your Pocket — When Apple got it right
- 09Questioning the Water You're Swimming In — Spotify and first-principles thinking
- 10Ninjas and Fireworks — Teletherapy in a pandemic
- 11The Parking Lot Problem — Multiple stakeholders, competing truths
- 12The Spreadsheet I Didn't Build — Solving the real problem
Part III: The Framework
- 13The Feature Alignment Document — Not another PRD
- 14The 10-Question Problem Validation Checklist — Pre-flight checks before you build
- 15Problem Atlas — The problem-driven roadmap
- 16Five Whys — Or: Why your first answer is usually wrong
- 17Getting to the Problem — Solution or problem? The game
Part IV: Building with Discipline
- 18The SMS Project — Where theory met practice
- 19Different Customers, Different Problems — The local optimum trap
- 20Sometimes You Need to Say No — Complexity is the silent killer
- 21The Discount Code We Didn't Build — Resisting the obvious
- 22Tough Problems — The ledger that wouldn't balance
- 23Reading Between the Lines — Playing detective with support messages
Plus: Your Toolkit
- →Feature Alignment Document (FAD) template
- →10-Question Problem Validation Checklist
- →Five Whys Worksheet
- →Problem Atlas Template
Free Sample
Read the Introduction and Chapter 1 (The Autopay Mistake)
Download Sample (PDF)Listen to the audiobook
Press play to hear a free preview, narrated.
Readers’ verdict
Real words from people who actually read the book.
“I work in IT, not as a builder, and picked this up because the author's a friend. Turns out the method applies anywhere people bring you problems disguised as solutions. "The share is slow" is never about the share. "We need SMS reminders" is never about SMS. Half my job is refusing to act on the first sentence someone says and digging until I find what's actually broken upstream — and this book gives that instinct a name, a structure, and a few tools I'll actually use. Problem-first is something most teams know they should do and somehow never do. This book is a clear, honest guide to actually getting there.”
“Excellent book. Kevin's book really helps you to work through your business problems with various tools and stories and to help prevent you from drifting away from those problems. I highly recommend this book.”
Note: one of the perks of being an indie author with my own site is I get to do what I want — and that means showing my mom’s testimonial. Yes, it’s extremely biased. Yes, I’m still showing it.
eBook
PDF & EPUB (Kindle, Apple, Google, Nook, Kobo).
Plus the audiobook (MP3 + M4B).
Includes 3 free eBook gifts for friends.
Frequently asked questions
Quick answers before you decide.
What is the Problem-First Method?
The Problem-First Method is a practical product-management framework for founders, product managers, and builders. Instead of jumping straight to features and solutions, it gives you tools to confirm you're solving a real, well-understood problem before you commit to building anything. Those tools include the Feature Alignment Document, a 10-Question Problem Validation Checklist, Five Whys, and the Problem Atlas roadmap.
Who is this book for?
It's written for founders and product managers, designers and engineers, pre-product-market-fit startups, and scale-ups fighting feature bloat — anyone tired of shipping features that get built, launched, and quietly ignored, who wants a concrete way to decide what's actually worth building next.
What formats are included?
The $15 eBook bundle includes the book as a PDF and as EPUB files for Kindle, Apple Books, Google Play, Nook, and Kobo, plus the full audiobook in both MP3 and M4B — and three free eBook gift copies for friends. The book is also available in print on Amazon as a paperback ($18) and a hardcover ($24).
How long is the book?
The PDF is 248 pages and 44,768 words. The Problem-First Method runs 23 chapters across four parts — The Trap, The Mindset, The Framework, and Building with Discipline — plus an introduction and a hands-on toolkit of templates and worksheets.
Is there a money-back guarantee?
Yes. Every eBook purchase is covered by a 14-day money-back guarantee — if the book isn't for you, email within 14 days of your purchase for a full refund. See the Refund Policy for the details.
Will I get updates?
Yes. When the eBook is revised, you can re-request your download link at any time and you'll receive the latest version at no extra cost.
