Product Doc

• Start with the customer problem, not the solution — "fall in love with the problem, not the solution" [29: Inspired]
• Set an appetite before exploring solutions — "how much time is this worth?" constrains the design [30: Shape Up]
• Frame opportunities from the customer's perspective, not the company's internal goals [31: Continuous Discovery Habits]
• Define success as outcomes (behavior change, metric movement), not outputs (features shipped) [29: Inspired]
• Every chart or data section needs an action title and a "so what" — data without narrative is noise [26: Storytelling with Data]
• The document must be self-evident to a scanning reader — eliminate anything that makes them stop and think [24: Don't Make Me Think]
• The structure should communicate a coherent conceptual model — terminology and hierarchy match the reader's mental model [23: Design of Everyday Things]

Deep-Dive References

• Product discovery & four risks: book_research/29_inspired_cagan.md
• Appetite, shaping, and pitch format: book_research/30_shape_up.md
• Opportunity solution trees & assumption mapping: book_research/31_continuous_discovery_habits.md
• Signifiers, conceptual models, and error design: book_research/23_design_of_everyday_things.md
• Scanning behavior, visual hierarchy, and trunk test: book_research/24_dont_make_me_think.md
• Data storytelling, Big Idea, and declutter: book_research/26_storytelling_with_data.md
• Pyramid structure, MECE grouping, and SCQ intro: book_research/37_pyramid_principle.md
• PR/FAQ, Working Backwards, and Six-Pager format: book_research/40_working_backwards.md
• Stakeholder navigation & political skills: book_research/35_agenda_mover.md