Decision Framework in AI
From the AI Prompting cheat sheet · Analysis & Problem Solving · verified Jul 2026
Decision Framework
Structured approach to complex decision-making
javascript
NAME: Multi-Criteria Decision Analysis
PURPOSE: Make data-driven decisions using structured evaluation
TEMPLATE:
Help me decide between these options: [OPTIONS].
Decision Context:
- Goal: [PRIMARY OBJECTIVE]
- Constraints: [LIMITATIONS]
- Timeline: [DECISION DEADLINE]
- Stakeholders: [WHO'S AFFECTED]
Evaluation Criteria (with weights):
1. [CRITERION 1] - Weight: [%]
2. [CRITERION 2] - Weight: [%]
3. [CRITERION 3] - Weight: [%]
4. [CRITERION 4] - Weight: [%]
For each option provide:
- Score (1-10) for each criterion
- Weighted total score
- Pros and cons
- Risk assessment
- Implementation complexity
Recommend:
- Best option with justification
- Alternative if constraints change
- Key success factors
EXAMPLE:
Help me decide between these options: Build in-house vs. Buy SaaS vs. Outsource development.
Decision Context:
- Goal: Launch customer portal in 6 months
- Constraints: $500K budget, 3 developers available
- Timeline: Decision needed by month-end
- Stakeholders: 10K customers, 50 support staff
Evaluation Criteria (with weights):
1. Cost - Weight: 25%
2. Time to Market - Weight: 30%
3. Customization - Weight: 20%
4. Long-term Scalability - Weight: 25%
For each option provide:
- Score (1-10) for each criterion
- Weighted total score
- Pros and cons
- Risk assessment
- Implementation complexity
OUTPUT:
## Decision Analysis: Customer Portal Implementation
### Option 1: Build In-House
**Scores:**
- Cost: 4/10 (Weight: 25% = 1.0)
- Time to Market: 3/10 (Weight: 30% = 0.9)
- Customization: 10/10 (Weight: 20% = 2.0)
- Scalability: 9/10 (Weight: 25% = 2.25)
- **Total: 6.15/10**
**Pros:**
✓ Complete control and customization
✓ No vendor lock-in
✓ Intellectual property ownership
**Cons:**
✗ Longest development time (8-10 months)
✗ Highest total cost ($450K + maintenance)
✗ Requires hiring 2 additional developers
**Risk:** HIGH - May miss deadline
**Complexity:** HIGH - Full development lifecycle
### Option 2: Buy SaaS Solution
**Scores:**
- Cost: 7/10 (Weight: 25% = 1.75)
- Time to Market: 9/10 (Weight: 30% = 2.7)
- Customization: 4/10 (Weight: 20% = 0.8)
- Scalability: 7/10 (Weight: 25% = 1.75)
- **Total: 7.0/10**
**Pros:**
✓ Fastest implementation (2-3 months)
✓ Predictable costs ($8K/month)
✓ Built-in best practices
**Cons:**
✗ Limited customization
✗ Ongoing subscription costs
✗ Data privacy concerns
**Risk:** LOW - Proven solutions available
**Complexity:** LOW - Configuration only
### Option 3: Outsource Development
**Scores:**
- Cost: 6/10 (Weight: 25% = 1.5)
- Time to Market: 6/10 (Weight: 30% = 1.8)
- Customization: 8/10 (Weight: 20% = 1.6)
- Scalability: 6/10 (Weight: 25% = 1.5)
- **Total: 6.4/10**
**Pros:**
✓ Good customization flexibility
✓ No need to hire permanently
✓ Access to specialized expertise
**Cons:**
✗ Quality control challenges
✗ Communication overhead
✗ Ongoing dependency for changes
**Risk:** MEDIUM - Vendor reliability crucial
**Complexity:** MEDIUM - Requires strong PM
### 📌 Recommendation
**Primary Choice: Buy SaaS Solution**
- Highest weighted score (7.0/10)
- Meets critical 6-month deadline
- Lowest risk profile
- Recommended vendor: Zendesk or Freshdesk
**Alternative if customization becomes critical:**
- Hybrid approach: SaaS now, custom modules later
- Budget allocation: $200K SaaS, $300K for custom features
**Success Factors:**
1. Negotiate enterprise agreement by month-end
2. Assign dedicated implementation team
3. Plan phased rollout to test with 10% of users
4. Reserve budget for API integrations🎯 Use weighted scoring for objectivity
📊 Provide quantitative and qualitative analysis
💡 Include contingency recommendations