Philip’s Project-to-Product Manifesto

• Outcomes over Outputs
• Hypotheses over Requirements
• Problems over Solutions
• Options over Backlogs
• Experiments over Features
• Customer-validated data over PO assumptions
• Measure value over measure cost
• Optionality over Linearity
• Product vision, strategy, personas and principles over product roadmaps
• Small-batch delivery over big-batch delivery
• Optimizing for assumptions being wrong over optimizing for assumptions being right
• Engineers solving problems over POs spoonfeeding them requirements
• Teams of missionaries over teams of mercenaries*

_{* Credit: Marty Cagan}