Delivery Prioritization: Scope, Speed, Quality, and Cost Questions

Approach: create a 5-criteria decision matrix, score each option 1–10, normalize to 0–1, apply weights tied to strategic priorities, sum weighted scores, and use sensitivity checks.

Matrix setup:

• Criteria (higher = better): Business Value (BV), Scope Impact (SI: positive = more value; negative scope increases lower score), Timeline Impact (TI: shorter timeline higher score), Resource Cost (RC: lower cost higher score), Quality Risk (QR: lower risk higher score).
• Weights (example, sum=1): BV 0.35, SI 0.20, TI 0.15, RC 0.15, QR 0.15.

Raw scoring (1–10) for three options:
Option A (Incremental feature): BV 6, SI 3, TI 9, RC 8, QR 9
Option B (Big new platform): BV 9, SI 9, TI 2, RC 3, QR 4
Option C (Partnership integration): BV 7, SI 5, TI 6, RC 6, QR 7

Normalize to 0–1: score_norm = (raw - 1)/9
Option A norms: BV 0.56, SI 0.22, TI 0.89, RC 0.78, QR 0.89
Option B norms: BV 0.89, SI 0.89, TI 0.11, RC 0.22, QR 0.33
Option C norms: BV 0.67, SI 0.44, TI 0.56, RC 0.56, QR 0.67

Weighted sum (example):
Option A = 0.560.35 + 0.220.20 + 0.890.15 + 0.780.15 + 0.890.15 = 0.63
Option B = 0.890.35 + 0.890.20 + 0.110.15 + 0.220.15 + 0.330.15 = 0.59
Option C = 0.670.35 + 0.440.20 + 0.560.15 + 0.560.15 + 0.67*0.15 = 0.64

Recommendation: Option C (score 0.64) narrowly leads; Option A close behind. Defensibility: weights reflect strategic focus on business value and low disruption; normalization removes scale bias. To strengthen recommendation run sensitivity analysis (vary BV weight ±10–15%), validate raw scores with data (customer interviews, cost estimates), and present trade-offs: A = low risk fast ROI, B = high upside long-term investment, C = balanced. Include stakeholder review to align weights and assumptions.

Situation: A vendor component is delayed 3 months and blocks launch. Below I evaluate four options across implementation time, cost, legal/regulatory implications, and customer impact, then give a recommendation and next steps.

1. Find alternative vendor

• Implementation time: 6–10 weeks (RFP, evaluation, integration, QA)
• Cost: Moderate–high (procurement, integration, potential license differences, switching costs)
• Legal/regulatory: Need new contracts, SLA review, data/privacy due diligence; possible additional certification timelines
• Customer impact: Low to moderate if integration works; risk of last-minute defects or behavioral differences

2. Build internally

• Implementation time: 3–4 months (design, dev, test) — could align with delay but depends on team capacity
• Cost: High (engineering hours, opportunity cost, maintenance)
• Legal/regulatory: More control over compliance; faster to address regulatory needs in-house but requires QA/certification cycles
• Customer impact: Potentially better long-term product fit; short-term risk if rushed (bugs, missing polish)

3. Delay launch

• Implementation time: 3 months (matches vendor delay)
• Cost: Moderate (marketing/operational costs, lost revenue, stakeholder opportunity cost)
• Legal/regulatory: Minimal incremental risk; gives more time for compliance checks
• Customer impact: Negative (lost market momentum, customer dissatisfaction), but can preserve product integrity

4. Ship with limited functionality (workaround/feature-flag)

• Implementation time: 2–6 weeks (implement fallback, UX adjustments, communication)
• Cost: Low–moderate (engineering for workaround, support ramp)
• Legal/regulatory: Must ensure no regulatory obligations are unmet by reduced functionality; update terms if necessary
• Customer impact: Mixed — retains launch timing and market presence but may disappoint some users; requires clear communication and roadmap commitment

Recommendation:
Ship with limited functionality as the preferred near-term path, combined with parallel tracks: pursue an alternative vendor evaluation (Option 1) and assess internal build feasibility (Option 2) as a longer-term hedge. Rationale: preserves go-to-market timing and revenue momentum while minimizing upfront cost and allowing iterative improvement. Mitigations: clear customer communications, feature flags, prioritized bug fixes, contractual discussions with current vendor for credits/penalties, fast-track integrations with vetted alternatives, and a decision gate in 6–8 weeks to reassess whether to continue workaround, switch vendors, or complete internal build.

Situation: Late in the quarter, Sales committed a custom integration to a key launch customer. Engineering reviewed it and said delivering that integration before launch would delay the release by 6–8 weeks.

Task: As Product Manager I needed to protect the launch date and product roadmap while preserving the customer relationship and Sales’ credibility.

Action:

• Immediately convened a triage meeting with Engineering, Sales, and Customer Success to align on constraints and risks.
• Broke the promised feature into three parts: a) a minimal, low-risk workaround (MVP) that meets the customer’s core need, b) a roadmap plan for the full integration, and c) optional professional services to bridge the gap short-term.
• Negotiated trade-offs with Sales: Sales would present the honest status to the customer, offer the workaround for launch, commit to a concrete timeline for full delivery (with engineering sign-off), and include a concession (e.g., temporary discount, extended support, or a co-marketing commitment).
• Drafted a customer-facing plan: clear scope of the MVP, delivery dates for incremental improvements, success metrics, and a follow-up governance cadence (biweekly check-ins).
• Updated internal roadmap and backlog priorities, reserving a hotfix slot and allocating a small cross-functional task force so the full feature could be delivered within the negotiated timeline.

Result:

• Customer accepted the MVP plus a firm timeline and appreciated transparency; launch proceeded on schedule.
• Relationship preserved; Sales kept credibility because we provided a concrete mitigation and compensation.
• Engineering avoided scope creep; the product roadmap stayed stable and the full integration shipped on the agreed date.
• Lesson learned: Institute a sales enablement checklist and a “promise review” step before commitments—this reduced similar incidents by 80% next quarter.

This approach balances transparency, pragmatic short-term remedies, and a clear, collaboratively agreed path to the long-term solution.

Cost of Delay (CoD) measures the economic impact of delaying a backlog item (usually as $/time). WSJF (Weighted Shortest Job First) ranks work by dividing CoD by job size (duration or effort): WSJF = CoD / Duration. You prioritize highest WSJF.

Worked example (product manager view):
Assume monetary CoD per week (loss in revenue, churn risk, strategic value) and estimated delivery duration in weeks.

Backlog:

• Item A (New checkout optimization): CoD = $18,000/week, Duration = 3 weeks
• Item B (Marketing landing page): CoD = $6,000/week, Duration = 1 week
• Item C (Subscription analytics dashboard): CoD = $9,000/week, Duration = 2 weeks

Compute CoD per week (already given) and WSJF:

• A: WSJF = 18,000 / 3 = 6,000
• B: WSJF = 6,000 / 1 = 6,000
• C: WSJF = 9,000 / 2 = 4,500

Reordering by WSJF (descending): A and B tie at 6,000, then C. If tie-breaker needed, pick lower risk or faster ROI — choose B first (1 week) to capture immediate value, then A, then C.

If you instead rank by raw CoD per week: A (18k), C (9k), B (6k). That would put C ahead of B despite B being quick to deliver. WSJF corrects for delivery duration so you maximize value per unit time.

Notes and best practices:

• CoD components: user value, revenue impact, regulatory cost, strategic value; sum them.
• Duration should include end-to-end lead time, not just development hours.
• Use ranges/Monte Carlo or sensitivity analysis for uncertainty.
• For non-monetary value, use relative scoring (e.g., 1–100) consistently and still divide by size to get WSJF.

Start by framing the decision with goals, constraints, and timelines.

1. Clarify objectives and constraints

• Business goals: revenue, retention, acquisition, margin
• Time horizon: 30/90/365 days
• Constraints: engineering capacity, budget, regulatory risk, brand impact

2. Evaluate impact (quantify where possible)

• Market impact: % of users/addressable market at risk if you do nothing
• Customer value: NPS/usage delta for segments affected
• Financial: short-term revenue at risk, LTV impact
• Strategic: does competitor feature threaten core differentiation or enable commoditization?

3. Assess costs & speed

• Time-to-market estimate for quick fix (weeks), parity (months), superior solution (quarter+)
• Engineering effort (FTE-weeks), UX/QA, ops
• Opportunity cost: what gets de-prioritized and its expected value

4. Go-to-market considerations

• Messaging: defensive (mitigate churn) vs offensive (highlight differentiation)
• Channel readiness: sales enablement, support, paid acquisition
• Data/metrics to validate: activation, churn, conversion lift

5. Decision framework (simple scorecard)

• Score Impact (1–5), Urgency (1–5), Feasibility (1–5), Strategic risk (1–5)
• Compute weighted score; define thresholds:
  • High -> Reprioritize for fast response (build MVP, mitigate churn)
  • Medium -> Timebox to iterate (release parity then roadmap to better)
  • Low -> Double down on differentiation (invest in unique long-term features)

6. Example actions

• Quick response: ship a minimal feature or temporary policy, update help docs, enable targeted offers to at-risk customers
• Parity+improve: roll out basic feature with instrumentation, collect feedback, roadmap superior UX
• Differentiate: accelerate unique capabilities, launch campaigns showing superior outcomes, partner/ecosystem plays

7. Monitoring & follow-up

• Define KPIs and 7/30/90-day reviews, rollback/accelerate triggers, and stakeholder communication plan.

This structured, data-driven approach balances business impact, resource trade-offs, and GTM so you choose the path that maximizes customer and company value.