The Hook
Your product has three major customer segments: SMB, Mid-market, Enterprise. Each segment wants different things. Your CEO thinks Enterprise is most important. Your SMB customers think their needs drive volume.
How do you weight prioritization when stakeholders disagree on importance?
Weighted scoring lets you make the weights explicit. Then everyone can see: This is who we're prioritizing for.
The Mental Model Shift: Weights as Strategic Commitments
Weights aren't neutral. They're product strategy.
| Weighting Scheme | Winner | Loser |
|---|---|---|
| 50% Enterprise, 30% Mid-market, 20% SMB | High ACV customers | High volume, low margin |
| 50% SMB, 30% Mid-market, 20% Enterprise | Viral growth potential | Premium positioning |
| 33% each | Nobody. You're trying to please everyone. | Everyone. You please none well. |
Most teams leave weights implicit and argue about them indirectly ("Feature X is important"). Making them explicit forces the strategic choice.
Actionable Steps
1. Define Your Segment / Stakeholder Weights
For each feature, score:
- Impact on Enterprise customers: 1–10
- Impact on Mid-market: 1–10
- Impact on SMB: 1–10
Then multiply by your decided weights: Final score = (Enterprise score × 50%) + (Mid-market score × 30%) + (SMB score × 20%)
The weights will reveal what you're actually optimizing for.
2. Revisit Weights Annually
Your weights should match your business strategy:
- Scaling upmarket? Increase Enterprise weight.
- Chasing volume? Increase SMB weight.
- Balanced growth? Split weights.
Change weights intentionally, not accidentally.
Key Takeaways
-
Don't hide your prioritization weights. Make them explicit. They reveal your strategic choices.
-
Weights reflect business strategy, not fairness. You're not trying to make everyone equally happy. You're optimizing for your strongest segment.
Real-World Case Studies: Weighted Scoring in Practice
Case Study 1: The Conflict That Killed Alignment
A SaaS company had three customer segments:
- Enterprise (5 customers, $500K each = $2.5M ARR, but super demanding)
- Mid-market (50 customers, $50K each = $2.5M ARR, stable)
- SMB (2,000 customers, $5K each = $10M ARR, high churn)
Their engineering team was small (8 engineers). They needed to pick 3 features to build in Q2.
The features under consideration:
- Custom field types (heavily requested by Enterprise)
- Advanced permissions matrix (needed by Mid-market for security compliance)
- Mobile app (SMB customers asking for it)
What happened (no explicit weights):
- Enterprise stakeholder: "Custom fields are critical. 4 of our 5 customers use this. If we don't ship it, we'll lose $2M ARR."
- Mid-market stakeholder: "Permissions are critical for compliance. Our customers won't renew without it."
- SMB stakeholder: "Mobile is driving our growth. We have 40% churn without it. We need it to hit our 30% growth target."
Everyone made compelling arguments. They spent 2 hours debating without resolving it. Finally, the CEO just picked: "Build custom fields."
Result:
- Enterprise: Happy (got custom fields)
- Mid-market: Upset (permissions aren't getting built)
- SMB: Devastated (mobile isn't coming, churn stays at 40%)
The mid-market and SMB teams lost trust in the prioritization process.
Lesson: Without explicit weights, you're just playing politics. Everyone makes the strongest case for their segment, and stakeholders feel like losers.
Case Study 2: The Same Conflict With Explicit Weights (Resolved)
A different company faced the same situation. They decided to be transparent about weights:
Strategic decision:
- Enterprise weight: 30% (high revenue, stable, but mature)
- Mid-market weight: 30% (growing, strategic, stable)
- SMB weight: 40% (volume-driven, high-growth potential, high churn)
Scoring the same three features:
| Feature | Enterprise Impact | Mid-market Impact | SMB Impact | Final Score |
|---|---|---|---|---|
| Custom fields | 9/10 | 4/10 | 3/10 | (9×.30)+(4×.30)+(3×.40) = 5.1 |
| Permissions | 2/10 | 9/10 | 3/10 | (2×.30)+(9×.30)+(3×.40) = 4.2 |
| Mobile app | 1/10 | 2/10 | 9/10 | (1×.30)+(2×.30)+(9×.40) = 5.3 |
Result: Mobile app (5.3) wins, followed by custom fields (5.1), then permissions (4.2).
Stakeholder reactions:
- Enterprise: "I don't like it, but I see the math. We're prioritizing SMB growth."
- Mid-market: "I understand. Permissions is lower on the list, but we know why."
- SMB: "Great, mobile is coming. But we know the company is balancing SMB+Enterprise."
Key difference: Everyone saw the weights. Everyone saw the math. It was transparent, not arbitrary.
Weighted Scoring in Different Contexts
Context 1: Customer-Segment Weighted Scoring
You have multiple customer segments with different needs.
| Segment | Weight | Why |
|---|---|---|
| Enterprise | 30% | Highest ACV, longest sales cycle, most demanding |
| Mid-market | 30% | Growing, stable, better product-market fit |
| SMB | 40% | Volume driver, viral potential, but high churn |
Context 2: Internal-Stakeholder Weighted Scoring
You have multiple internal stakeholders with different priorities.
| Stakeholder | Weight | Why |
|---|---|---|
| CEO (growth focus) | 40% | Sets overall direction |
| CTO (technical debt) | 30% | Ensures product scalability |
| VP Sales (customer retention) | 30% | Prevents churn |
Context 3: Dimension-Based Weighted Scoring
You score each feature on multiple dimensions, weighted by importance.
| Dimension | Weight | Why |
|---|---|---|
| Revenue impact | 40% | Direct business impact |
| Strategic alignment | 30% | Moves company toward vision |
| Effort required | 20% | Feasibility |
| Customer feedback | 10% | Validates actual demand |
Each feature is scored 1-10 on each dimension, then: Feature score = (Revenue×.40) + (Strategy×.30) + (Effort×.20) + (Feedback×.10)
The Politics: How Weights Become Battlegrounds
Anti-Pattern 1: "Letting the CEO override weights silently"
Weights are set. Then the CEO says, "Actually, let's prioritize the Enterprise feature instead of mobile."
Everyone knows what happened: The weights don't matter. The CEO's opinion does.
Fix: If the CEO wants to override the weights, make it explicit. "I'm overriding the weighted score because [X reason]. New weights should be [Y]."
Anti-Pattern 2: "Weights that don't match reality"
You claim weights are 50% Enterprise, 50% SMB. But your recent releases have been 80% Enterprise features, 20% SMB.
People see through this. Your weights are lies.
Fix: Audit your last 3 releases. What did you actually prioritize? Make weights match reality, or change reality to match weights.
Anti-Pattern 3: "Weights that get debated forever"
You spend 2 hours debating weights in a meeting. Nobody agrees. You table it and never update them.
Result: Weights stay implicit and unmaintained.
Fix: Set weights once per year (or when strategy changes). Don't debate them constantly. Use the weights decisively for 12 months, then revisit.
The Economics: Transparent Weighting Saves Time
Scenario A: Implicit weights, stakeholder debate
- Prioritization meeting lasts 2 hours
- Stakeholders argue about importance
- CEO makes a decision
- 2 segments feel blindsided
- Trust in process erodes
- Cost: 2 hours × 8 people = 16 person-hours
Scenario B: Explicit weights, transparent scoring
- Weights set in advance (10 min conversation)
- Features scored by multiple people (20 min)
- Final scores calculated (5 min)
- Results presented with math (15 min)
- Stakeholders see the logic, even if they don't like the result
- Cost: 50 person-minutes total
Savings: 15+ person-hours of debate, plus improved stakeholder trust.
Setting Weights: A Systematic Approach
Step 1: Define Your Segments or Stakeholders
List the groups you're weighing:
- Customer segments? (Enterprise, Mid-market, SMB)
- Internal stakeholders? (Product, Sales, Engineering, Support)
- Dimensions? (Revenue, strategy, effort, customer sentiment)
Step 2: Set Weights Based on Business Strategy
Don't just average them (33% each). Make strategic choices:
- If you're upmarket: Enterprise 50%, Mid-market 30%, SMB 20%
- If you're chasing volume: SMB 50%, Mid-market 30%, Enterprise 20%
- If you're balanced: Enterprise 40%, Mid-market 40%, SMB 20%
Step 3: Make Weights Visible
Put them in a Notion doc, Slackbot message, or quarterly planning document. Refer to them every time you prioritize.
Step 4: Update Weights Annually
At your annual strategy planning, revisit weights. Did your business strategy change? If so, weights should change.
Step 5: Audit Actual Execution
Every quarter, check: Did we actually follow our weights?
- Planned allocation: Enterprise 30%, Mid-market 30%, SMB 40%
- Actual allocation: Enterprise 35%, Mid-market 25%, SMB 40%
If execution drifts from weights, investigate. Either weights are wrong, or something else is overriding them.
When Weighted Scoring Works (And When It Doesn't)
Weighted Scoring Works For:
- Multi-segment products (B2B SaaS with different customer tiers)
- Organizations with conflicting priorities (Sales vs. Product vs. Engineering)
- Feature scoring across multiple dimensions (revenue + strategy + effort)
Weighted Scoring Fails For:
- Single-segment products (all customers are similar, weights are less useful)
- Crisis situations (you need to move fast, not debate weights)
- Innovation work (future opportunities don't fit neatly into weighted buckets)
Prodinja Connection (Updated)
When you set weighted priorities, execution always diverges from the plan. Halfway through the quarter, an Enterprise customer demands an exception. An urgent bug takes two weeks. Mid-market churn spikes, suddenly requiring immediate action. Every one of those moments quietly erodes trust with whichever faction just got deprioritized, and that erosion is easy to miss because nobody's tracking it. Prodinja's Stakeholders CRM is designed to make it visible: log each stakeholder or faction, and it computes a relationship health score alongside an alignment-debt score that rises whenever a decision runs against what that stakeholder was told to expect. Instead of discovering three quarters later that the SMB team feels ignored, you can watch alignment-debt climb in something closer to real time and decide, deliberately, whether to course-correct or have the harder conversation about why the weights changed.
Key Takeaways (Updated)
-
Weights are strategic commitments. Don't hide them. Make them explicit and visible. They reveal who you're optimizing for.
-
Set weights strategically based on business direction, not fairly. You're not trying to please everyone equally. You're optimizing for specific segments or outcomes.
-
Audit execution against stated weights quarterly. When reality diverges from weights, make a conscious choice: Update weights to match reality, or course-correct execution.
-
Update weights annually or when strategy changes. Don't debate them constantly. Set them, use them decisively, revisit when things change.
-
Use weights to depoliticize prioritization. With transparent weights and math, prioritization becomes about data and strategy, not politics and opinions.