Skip to main content

VPM and Design Thinking

Design Thinking and VPM are complementary approaches. Design Thinking focuses on understanding the customer problem deeply before committing to a solution. VPM provides the execution framework once the team is ready to build.

The handoff point is straightforward: Design Thinking reduces problem uncertainty, and VPM reduces delivery uncertainty. Design work clarifies what should be built, for whom, and why it matters; VPM then translates that clarity into a visible, managed execution system with cadence, ownership, and schedule control.

In many organizations, these approaches run in a loop rather than a one-way sequence. Early delivery signals from VPM can trigger focused Design Thinking cycles to refine assumptions, while Design Thinking outputs can be reinserted into the execution plan as scoped changes. Used together, they improve both solution quality and delivery reliability.

Where Traditional VOC Breaks Down​

Many teams treat Voice of the Customer (VOC) as routine: run surveys, hold a few focus groups, summarize findings, then move on. The issue is not usually effort. The issue is structure. Conventional VOC often narrows discovery too early and turns rich customer reality into filtered summaries.

The following gaps are common in practice:

1) Single-Point Filtering​

  • One product lead or analyst becomes the main gate for what gets elevated.
  • Confirmation bias can push familiar narratives over contradictory signals.
  • Emotional and situational detail is often stripped out in translation.
  • Delivery teams hear a summary of the customer, not the customer directly.

2) Over-Reliance on Current Customers​

  • Survivorship bias limits input to people who already tolerate the product.
  • Existing users normalize painful workarounds and under-report them.
  • Non-users, churned users, and competitor users are often excluded.
  • The result is usually sustaining improvement, not breakthrough change.
  • This dynamic aligns with Christensen's warning in The Innovator's Dilemma that incumbent feedback loops can reinforce incrementalism.

3) Solution-Language Instead of Problem-Language​

  • Requests arrive as feature ideas constrained by current assumptions.
  • Teams optimize requested features instead of the underlying job-to-be-done.
  • This is the classic "faster horses" trap.

4) Premature Quantification​

  • Surveys are only as good as the questions already known.
  • Unknown unknowns rarely appear in fixed-choice instruments.
  • Exploration gets cut short before discovery has depth.

5) Averaging That Hides Segments​

  • Aggregation collapses conflicting user needs into an artificial "average."
  • Contradictions, which are often the source of innovation, are treated as noise.

6) Rational-Only Bias​

  • Research focuses on features, functions, and specs.
  • Emotional and social drivers (status, anxiety, identity, confidence) are under-captured.

7) Checkbox Validation​

  • "We talked to customers" can become political cover for decisions already made.
  • Validation is used to justify direction rather than discover it.

8) Builders Separated from Customers​

  • Engineers and designers are kept at distance from direct customer contact.
  • Empathy erodes when it is passed through documents only.

How Design Thinking Changes the Pattern​

Design Thinking addresses these structural gaps by changing who learns, when they learn, and how evidence is interpreted.

  • Cross-functional immersion replaces single-point filtering.
  • Interview pools intentionally include current users, non-users, churned users, and competitor users.
  • Problem framing is separated from solution commitment.
  • Qualitative depth comes first; quantification follows for prioritization.
  • Personas and workflow maps preserve segmentation rather than averaging it away.
  • Emotional and social signals are treated as first-class data.
  • Discovery precedes validation.
  • Builders participate directly so empathy is lived, not summarized.

When paired with VPM, these insights are translated into execution behavior: visible plans, explicit ownership, short feedback cadence, and controlled rollout.

Customer Experience Foundation and Business Case​

Design Thinking is not only a design philosophy; it is an economic lever. Better customer understanding improves retention, spending, and resilience.

Experience Quality Correlates With Revenue​

Harvard Business Review reported that, after controlling for other drivers, customers with top-rated past experiences spent 140% more than those with the worst-rated experiences. In subscription settings, best-experience customers stayed roughly six years longer, while worst-experience customers churned much earlier.

Source: Peter Kriss, The Value of Customer Experience, Quantified, Harvard Business Review, August 2014.

Negative Experiences Destroy Loyalty Quickly​

PwC's multi-country customer experience survey found that 32% of customers would stop doing business with a brand they love after one bad experience. It also found that customers can pay a premium (up to 16%) for strong experience quality.

Source: PwC, Experience Is Everything: Here's How to Get It Right, Future of Customer Experience Survey 2017/18.

Retention Has Multiplying Profit Effects​

Bain/Harvard Business Review reporting on Reichheld's work shows that a 5% increase in retention can raise profits by 25% to 95%, depending on industry economics.

Source: Frederick Reichheld, Bain & Company, as cited in The Value of Keeping the Right Customers, Harvard Business Review, October 2014.

Taken together, these findings reinforce the implementation logic: invest in deep discovery first, prove outcomes in controlled pilots, then scale with VPM discipline.

Figure Placeholders​

Figure placeholder: "Design Thinking" overview visual showing the page's core concepts and flow. Figure path: /img/figures/adoption-design-thinking-fig-01.png Figure placeholder: before/after comparison visual: traditional VOC blind spots (before) versus design-thinking discovery model (after), including coverage of filtering bias, segment blindness, premature quantification, and builder-customer separation. Figure path: /img/figures/adoption-design-thinking-fig-02.png