chapter five

5 Product intent: Reverse-engineer the PRD

 

This chapter covers

  • The Curse of Knowledge and why expertise blinds
  • Extracting pain scenes from code
  • The reproduce-it test for one-sentence clarity
  • Competitive positioning through doing less
  • Reading strategic bets the README never mentions

In 2007, a Hacker News commenter dismissed Dropbox as something any Linux user could build in a weekend with FTP and SVN. He was technically correct about every detail and catastrophically wrong about the product, because Dropbox went on to IPO at $12 billion. Drew Houston didn't see an FTP wrapper; he saw millions of people panicking because they couldn't remember whether the latest version of their essay was on their laptop or their desktop. Every engineer who opens a codebase and thinks "it's just CRUD" is making the same mistake: reading the implementation and missing the product entirely.

5.1 "It's just a wrapper": The pain engineers can't see

5.2 Product in one sentence: The reproduce-it test

5.3 Competitive positioning: Why the product that does less often wins

5.4 What the code reveals that nobody advertises

5.5 Summary