CUSTOMER-EXPERIENCE

NPS driver tree

This driver tree links NPS to the experiences that shape whether customers recommend a product. Product value covers whether the core workflow works reliably and whether users reach value through onboarding and adoption. Service experience covers the ability to get help, the speed of response, and the quality of resolution. The score itself is an outcome, not a lever, so the tree focuses the team on measurable experiences that can change it. Combine survey comments with product and support data before prioritising work. Add pricing or value-for-money as a separate branch if it emerges consistently in detractor feedback. It gives readers a concise reference they can reuse when discussing the result with colleagues.

UPDATED 2026-09-24
EXAMPLENPS driver tree
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Customer experience planning

Key decisions

  • Product value: Test whether customers complete their core job.
  • Service: Test ease, speed, and resolution of support.
  • Voice of customer: Link branches to feedback and behavioural data.

When to reuse this

Use to organize an NPS improvement programme without relying on the score alone.

FAQ

Frequently asked questions

Is NPS itself a driver?01
No. It is an outcome measure of customer sentiment.
Why use feedback with the tree?02
Comments help identify which experience branches matter most to customers.
Can pricing be a driver?03
Yes, when perceived value for money materially affects recommendation.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.