B0336: Customer Value Design Decision Framework

Quality / Updated / COI

Quality

Reviewed

Updated

02/14/2026

Source

Citations & Trust

COI

none

TL;DR

Customer Value Design Decision Framework (Business 0336) aligns decisions around retention rate and NPS so teams can act consistently even under time-to-market pressure. It makes the standardization vs local adaptation trade-off explicit and keeps approval logic auditable.

Applicability

Use this framework when cross-functional decisions slow down because assumptions are inconsistent. It is effective when time-to-market pressure limits execution flexibility and teams must balance near-term outcomes with capability building. Start by fixing scope, time horizon, decision owners, and acceptance criteria. Align the definition of retention rate and NPS and the cadence of data refresh before option comparison begins.

Steps

1. Define objective and success criteria, then agree on formulas and checkpoints for retention rate and NPS. Document in-scope and out-of-scope boundaries.
2. Prepare at least three alternatives at the same level of detail. Map expected impact, required resources, and implementation complexity for each option.
3. Compare options through the lens of standardization vs local adaptation and connect every claim to evidence. Explicitly list assumption-break conditions.
4. Assess risks and define fallback scenarios if time-to-market pressure tightens. Set stop conditions and escalation triggers in advance.
5. Record the final decision, owner, and review schedule. Capture learning outcomes and feed them back into the next cycle template.

Template

Template: 1) Background and objective 2) Success metrics (retention rate and NPS) 3) Constraints (time-to-market pressure) 4) Current issues 5) Options A/B/C 6) Expected impact and side effects 7) Cost and execution effort 8) Risks and mitigations 9) Decision criteria 10) Recommended option 11) Execution and review plan. For each section, include source, assumptions, and owner. Keep option comparison at a comparable granularity and include at least one quantitative indicator per option.

Pitfalls

• If teams use different definitions for retention rate and NPS, the same output leads to conflicting interpretations and delayed approvals.
• If standardization vs local adaptation priorities are not agreed upfront, execution often reverses direction and re-approval costs rise.
• If data sources and assumptions are not documented, decision rationale becomes hard to defend during audit or leadership review.

Case

Case: Repeated re-openings in monthly review meetings were delaying execution. With Customer Value Design Decision Framework (Business 0336), teams compared scenarios using common retention rate and NPS definitions and documented the standardization vs local adaptation trade-off at each gate. Meeting time moved toward exceptions and blockers instead of baseline re-explanations, improving decision speed. Follow-up reviews captured assumption gaps and updated playbooks for the next cycle.

Citations & Trust

• Principles of Management (OpenStax)
• Introduction to Business (OpenStax)