Core Idea
- Great products result from discovery before engineering, not from customer requests or engineering guesses
- Product management = proving value, usability, and feasibility with real users before committing resources
- User experience design and customer understanding are essential from day one, not add-ons
What Product Managers Actually Do
- Define what customers actually want (not what they say they want)
- Own outcome; avoid delegating discovery to marketing or letting engineering drive decisions
- Work daily with interaction designers and engineers during discovery phase
- Assess opportunities rigorously before proceeding
Discovery Framework: Do This Before Engineering
- Opportunity Assessment: Answer 10 key questions—problem, target market, market size, success metrics, competition, differentiation, timing, go-to-market, critical success factors
- Charter User Program: Recruit 8-10 target customers early; involve them throughout; secure 6+ reference customers before launch
- High-Fidelity Prototypes: Build interactive mockups (not wireframes); test relentlessly with real users; iterate until value is proven
- Product Principles: Define 3-5 core priorities to guide daily decisions; can't optimize everything equally
- Personas: Identify major user types; design each release for one primary persona
- Minimal Product: Cut ruthlessly to essentials only; reduce time-to-market and user complexity
Team Structure
- Separate roles: Product Manager (what to build) ≠ Product Marketing (sell it) ≠ Project Manager (schedule it)
- Hire for passion + empathy: Look for customer obsession, intelligence, work ethic, integrity; skills are teachable
- Designers from day one: Interaction and visual designers drive discovery with PM; not afterthoughts
- Engineer input early: Architects validate feasibility during discovery; prevent late-stage "we can't build this"
Critical Don'ts
- Don't ask customers what to build—they can't envision solutions or know what's possible
- Don't confuse customer requests with requirements
- Don't do custom features for single customers (kills product coherence)
- Don't start engineering until prototype is validated with real users
- Don't skip UX design for speed
- Don't design by committee
Large Company Tactics
- Prove with prototypes first; easier to get forgiven than approved
- Build relationships before needing them; map dependencies early
- Pre-brief one-on-one before big meetings; resolve objections privately
- Pick battles carefully; fight for product outcomes, not against people
Action Plan
- Write opportunity assessment for your next product (answer 10 key questions)
- Recruit 8-10 charter users from your target market willing to participate throughout
- Build interactive prototype of core flows; don't wait for engineering
- Test with 6+ real users; watch them interact; iterate based on their behavior
- Define minimal product by cutting features to essentials only; validate with users
- Organize collaboration: Product Manager + Interaction Designer + Engineer Lead meeting daily during discovery