Customer Hierarchy of Needs Workshop

Description

A team workshop that places features on a four-level pyramid (functional, operational, value, efficiency needs) to define a product vision and triage scope.

Dysert and Prabhala adapt Maslow's hierarchy into a product facilitation tool. Level 1 holds functional needs (what the solution must do), level 2 operational needs (routine obligations and efficiency), level 3 value needs (higher benefits such as time or cost savings) and level 4 efficiency needs (peak performance, the team's north star). After preliminary research, a Jobs-to-be-Done workshop produces job statements; a second workshop has the development team fill the template with features at each level. The pyramid sets MVP scope and becomes a checkpoint: incoming requests are first checked against the vision, dropped if they do not move towards it, and otherwise placed at a level and scheduled. After release, the team checks whether expected value is delivered. The authors stress it is a discussion tool, not a specification, and it can be built top-down when the vision already exists.

Attributes

Loss type
Latent
Effort
Days

Steps

  1. Complete preliminary research so the customer's problem and perceived value are understood.
  2. Run a Jobs-to-be-Done workshop with the product team to write job statements from past field research and customer requests.
  3. In a second workshop, fill the four levels with features: functional, operational, value, efficiency.
  4. Design and critique each level to decide how its features will be built.
  5. Triage new requests: drop those that do not move towards the vision; place the rest at a level and schedule them.
  6. After release, measure whether the expected value at each level is delivered.

Sources

  • DUXU 2022: UX Research, Design, and Assessment (Soares et al., 2022)

Also known as

  • Customer hierarchy of needs method

Categories

  • Design
  • Design & Product Practice