| name | shipping-to-learn-diagnostic |
| description | A framework to determine when to invest in deep user research versus when to "ship to learn." Use this when resources are tight, when designing standard features, or when faced with high uncertainty that can only be resolved by real-world usage. |
The "Zero Interest Rate Phenomenon" (ZIRP) PM mindset defaults to heavy research, infinite frameworks, and process-following to avoid risk. In contrast, high-impact PMs recognize that user research is a scarce resource. This skill helps you identify when to bypass lengthy discovery cycles in favor of shipping, copying established patterns, or using creative intuition to gain signal.
The Resource Allocation Logic
Apply this logic to decide whether to stop discovery and start building:
1. The "Standard Pattern" Rule
If you are building a feature that already exists in common products (e.g., a login page, a checkout flow, or a basic profile):
- Action: Skip user research.
- Process: Conduct a competitive analysis of FAANG and top unicorns. Identify the 2-3 most common approaches.
- Logic: Your customers already use these products and are familiar with their UI patterns. Copying them reduces cognitive load for the user and saves your research budget for unique problems.
2. The "Extreme Uncertainty" Threshold
Reserve dedicated user research teams and long discovery cycles only for areas that meet both criteria:
- High Leverage: Success in this area significantly moves a North Star metric or solves a core business risk.
- High Uncertainty: The problem is poorly defined (e.g., entering a totally new B2B segment) or you have zero existing benchmarks.
3. The Analysis-over-Observation Method
When evaluating competitor solutions, don't just list what they do. Perform a "Why" analysis:
- Identify the trade-offs the competitor made.
