Inspired

The spec must describe the full user experience—not just the product requirements but also the user interaction and visual design. By now, hopefully everyone

For virtually all product decisions, the key is to properly frame the decision to be made, and to first get everyone on the same page in terms of: What problem exactly are you trying to solve? Who exactly are you trying to solve this problem for—which persona? What are the goals you are trying to satisfy with this product? What is the relative prio

sequential is important. The requirements and design happen together, and then implementation and test can happen together.

In my mind, there’s only one form of spec that can deliver on these requirements, and that is the high-fidelity prototype.

For each product effort, there are four major milestones for product council review and decision making: Milestone 1: Review proposed product strategies and product roadmaps, and initiate opportunity assessments for specific product releases. That is, select the product opportunities to be investigated. Milestone 2: Review opportunity assessments a

competitors as clueless, but in my experience every product has at least some things that the product does well, and it’s your job to find these things. Learn from their successes and their mistakes.

product decision makers are all available with the express purpose of making those decisions the product organization needs to get products to market.