Building Applications Better the First Time
summary
Claims a 3‑day sales query workflow shrinks to 10 minutes and proves it by building a sales audience‑sizing tool that initially fails because the wrong user is observed, costing days of rework and one two‑week wasted feature. Uses paper prototypes, wireframes and HTML mocks, collects usage data to track every page and search, applies the 80 percent rule, and schedules buffers by double estimated dev time; prototyping saves weeks and a late data corruption reveals the need for extra slack.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:53Highlevel tips
- 2:11Example project
- 3:01Define the problem
- 5:24Observe the user
- 8:16Focus on the majority
- 10:31Prototype with users
- 11:55Low fidelity
- 13:14High functioning
- 14:13High fidelity
- 15:51Overdeliver
- 17:50Feedback loop
- 19:29Summary
- 21:22Questions Tricks
related talks
07mThe Value of Prototypes
27mPower of Prototyping
14mGathering Requirements, and Rapidly Building Proof of Concepts
46mWeeks of coding can save you hours of planning
27mResearch Like You're Wrong
28mHow to create the perfect prototype
23mUsing Data to Bridge Product and Engineering Teams
24mHow To Connect With Stakeholders Through Prototyping