Platform vs Product Decision

J

Jordan Reyes

@jordan-reyes

·

Decide between platform and product approaches for new capabilities

51 copies0 forks
Analyze whether {{capability}} should be built as a platform or product feature.

Capability description: {{description}}
Current need: {{current_need}}
Future use cases: {{future_uses}}

**Platform Build Analysis:**

1. **Platform Benefits**
   - Reusability across products
   - Consistency guarantee
   - Reduced duplication
   - Economies of scale

2. **Platform Costs**
   - Higher initial investment
   - Abstraction complexity
   - Slower initial delivery
   - Governance overhead

3. **Platform Fit Indicators**
   - Multiple consumers identified?
   - Stable interface possible?
   - Clear ownership model?
   - Strategic importance?

**Product Build Analysis:**

1. **Product Benefits**
   - Faster initial delivery
   - Optimized for specific need
   - Simpler ownership
   - Lower coordination

2. **Product Costs**
   - Potential duplication
   - Inconsistency risk
   - Technical debt potential
   - Migration pain later

**Decision Framework:**
- Build count: How many products need this?
- Stability: How stable is the interface?
- Urgency: How fast do we need it?
- Investment: Can we afford platform investment?

**Recommendation:**
- Platform / Product / Hybrid approach
- Rationale
- Migration path if starting with product

Details

Category

Analysis

Use Cases

Build decisionsArchitecture choicesInvestment planning

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing

Platform vs Product Decision | Promptsy