Anna Hofmann·
Couldn't pick a CRM so it scored four of them weighted and showed which factor would flip the winner
Build analytically rigorous weighted decision matrices for complex multi-criteria decisions with sensitivity analysis.
Weighted Decision Matrix Architect
You are a decision analysis expert trained at the Decision Quality framework (Keeney, Raiffa). Help me make a high-stakes decision using a rigorous weighted decision matrix.\n\nDECISION TO MAKE: {{decision_question}}\nDECISION CONTEXT: {{context_and_constraints}}\nDECISION MAKER(S): {{who_is_deciding}}\nTIMELINE: {{decision_deadline}}\nOPTIONS UNDER CONSIDERATION: {{list_of_alternatives}}\n\nOUTPUT — Complete Decision Analysis Package:\n\n## 1. DECISION FRAMEWORK CLARITY\nBefore scoring, validate the decision:\n- Problem statement refinement (are we solving the right problem?)\n- Decision type classification: [Strategic / Tactical / Operational / Irreversible / Reversible]\n- What would 'great' look like? Define the ideal outcome.\n- Pre-mortem: 'It's 1 year later and this decision failed. Why?' (list 3 reasons)\n\n## 2. CRITERIA HIERARCHY\nIdentify decision criteria organized as:\n\n**Must-Have Criteria** (threshold/go-no-go — options failing these are eliminated):\n- Criterion 1: [Name] — Threshold: [minimum acceptable]\n\n**Should-Have Criteria** (weighted scoring factors):\n| Criterion | Definition | Weight | Measurement Scale | Data Source |\n|-----------|-----------|--------|-------------------|-------------|\n\nGenerate 6-10 should-have criteria. For weights: use a 100-point budget allocation. Ensure weights sum to 100.\n\nJustification for each criterion: Why does this matter to {{who_is_deciding}}?\n\n## 3. OPTION SCORING MATRIX\nRate each option ({{list_of_alternatives}}) on each criterion using a 1-5 or 1-10 scale:\n\n| Option / Criterion | C1 [w] | C2 [w] | C3 [w] | ... | Weighted Total | Rank |\n|-------------------|--------|--------|--------|-----|---------------|------|\n\nScoring guidelines:\n- 1 = Poor / Does not meet needs\n- 3 = Acceptable / Meets basic needs\n- 5 = Excellent / Exceeds needs (adjust for 1-10 scale accordingly)\n\n## 4. SENSITIVITY ANALYSIS\n- What if criterion weights change ±20%? Does the winner change?\n- Identify 'swing criteria' — which single criterion, if changed, would flip the ranking?\n- Scenario testing: Optimistic vs. pessimistic scoring for top 2 options\n- Break-even analysis: How much would the second-place option need to improve to win?\n\n## 5. QUALITATIVE FACTORS\nList factors NOT captured in the matrix:\n- Strategic optionality (does this option create future opportunities?)\n- Reversibility (can we undo this?)\n- Alignment with values/culture/mission\n- Stakeholder sentiment and change management effort\n- Timing and competitive dynamics\n\n## 6. DECISION RECOMMENDATION\n- Recommended option with clear rationale\n- Confidence level: [High / Medium / Low]\n- Key assumptions that must hold for this to be the right choice\n- Conditions that should trigger a re-evaluation\n- Immediate next steps (3-5 action items)\n\n## 7. DECISION LOG\n- Date, decision makers, method used, key assumptions\n- Template for future review: 'Revisit this decision on [date] or if [trigger event] occurs'
Ergebnisse
# Weighted Decision Matrix — Choosing a New CRM
**Decision:** which CRM to standardize on across sales + support. **Deciding:** VP Sales + VP Ops. **Options:** Salesforce, HubSpot, Pipedrive, stay on current (Zoho).
## 1. Framing
Reversible-but-costly (2yr contracts, migration effort). Pre-mortem: "a year later it failed because adoption stalled — reps kept using spreadsheets."
## 2. Criteria (weights sum to 100)
| Criterion | Weight | Why it matters to VP Sales/Ops |
|-----------|--------|-------------------------------|
| Rep adoption / UX | 25 | A CRM nobody uses is worthless |
| Total cost (3yr) | 20 | Budget is fixed |
| Integration with our stack | 18 | Must sync with billing + support |
| Reporting / pipeline analytics | 15 | Board wants forecasting |
| Customization | 12 | Non-standard sales motion |
| Vendor support / SLA | 10 | Lean ops team |
## 3. Scoring (1–5, weighted)
| Option | Adopt 25 | Cost 20 | Integ 18 | Report 15 | Custom 12 | Support 10 | Total |
|--------|------|------|------|------|------|------|-------|
| HubSpot | 5 | 3 | 4 | 4 | 3 | 5 | **400** |
| Salesforce | 3 | 2 | 5 | 5 | 5 | 4 | 375 |
| Pipedrive | 4 | 5 | 3 | 3 | 2 | 3 | 350 |
| Stay (Zoho) | 2 | 5 | 3 | 2 | 3 | 2 | 290 |
## 4. Sensitivity
If "cost" weight rises +20%, Pipedrive nears HubSpot but doesn't overtake. Swing criterion = adoption: drop HubSpot's adoption to 4 and Salesforce wins on analytics.
## 5. Recommendation
**HubSpot**, confidence: Medium-High. Wins on the highest-weighted factor (adoption) without losing badly anywhere. Re-evaluate if a Salesforce admin is hired (flips customization economics).
Modell: Claude Sonnet 4
45 Likes12 SavesScore: 22
4 Kommentare
Leon Wirth·
The way it batches similar tasks cut my context-switching hard.
Noah Steiner·
Clear, structured, no fluff. Exactly what planning should feel like.
Julia Moser·
Okay this research, analysis output just fixed my week.
Felix Bauer·
This turned a vague goal into a checklist I actually finished.