Chapter 18 · 6 lessons · 670 min
Product Thinking & Guidelines
How to build things people actually want.
Overview
Anyone can build. Few build the right thing. This chapter is about the muscle of product thinking — the ability to find problems worth solving, design solutions people actually want, and ship them without endless polish.
What you'll learn
- How to spot real problems vs. imagined ones (and the Mom Test that filters lies).
- Design fundamentals: hierarchy, spacing, typography, contrast — the 5 rules that fix 90% of ugly UI.
- Why MVPs are about testing hypotheses, not minimizing features.
- Shipping discipline: the 70% rule, the pre-flight checklist, when to ignore feedback.
Who this chapter is for
Founders, product managers, indie hackers, and engineers who want to lead, not just execute. Anyone whose side projects keep getting 'almost ready' but never launch.
Lessons in this chapter
All lessons are free and open — start anywhere, in any order.
- 1What Is Product Thinking?The shift from 'building features' to 'solving problems.'112 min
- 2Design Fundamentals for BuildersHierarchy, spacing, contrast, type — the rules that make non-designers look good.114 min
- 3Shipping Discipline: Ship It, Then PolishWhy perfectionism kills products and how to ship without shipping garbage.111 min
- 4Common Mistakes & How to Avoid ThemThe 5 traps beginners fall into when working on product thinking & guidelines — and the fix for each.111 min
- 5A Real-World WalkthroughA start-to-finish example of applying product thinking & guidelines to a real project you can copy.111 min
- 6Mental Models That Actually HelpThe 3 mental models we keep coming back to when things get hard in product thinking & guidelines.111 min
Glossary
Key terms used throughout this chapter.
- Problem discovery
- The phase where you find a real problem worth solving — usually by talking to users, not building.
- MVP
- Minimum Viable Product — the smallest thing that proves the hypothesis.
- PMF
- Product-Market Fit — when customers pull the product from you faster than you can push.
- Outcome vs output
- Output: 'we shipped X'. Outcome: 'metric Y improved by Z%'. Always chase outcomes.
- North-star metric
- The single number that best represents the value your product delivers.
- Build-measure-learn
- The fastest team wins. Build small, measure honestly, learn ruthlessly, repeat.
Try it yourself
Knowledge sticks when you use it. Do at least one of these before moving on.
- 01.Pick a product you love. Write down the *real* problem it solves in one sentence. Then write down its outputs vs. outcomes.
- 02.Do 3 user interviews using only Mom Test questions. Don't pitch your idea — just listen.
- 03.Take your favorite ugly internal tool at work. Redesign one screen using the 5 rules from Lesson 8.2.
Further reading & sources
Primary, official sources we cross-checked against while writing this chapter.
