Value ShapingHeart-dominant: who is this for, what does it mean?

The governing question of Value Shaping is: who is this for, and what does it mean to them? Value Shaping asks what it should mean and what it should make someone feel, questions that have answers only if the designer has genuine contact with the actual user.

Value Shaping leads with Heart. The primary activity turns relational: understanding the user, and the meaning the work should produce for them.

In practice, the meaning you choose carries a build cost. Say the meaning is “the user should feel that the system noticed them.” Delivering that takes stored state, history, and response timing tuned to the moment. If the team ships on a tight timeline with stock components, that meaning is out of reach, the build constraining what value you can shape. The trade-off is between the meaning you want and the form your team can actually build to carry it. Miss it in Value Shaping and Experience Realisation inherits it. The team strains to realise a value claim the constraints never allowed, and the failure looks like weak craft when the fault was upstream all along.

Four questions structure Value Shaping.

• Audience, Who is this for, in full?
  The primary user is only the starting point. Every design decision affects others too: secondary users who encounter the product, users in contexts the team didn’t imagine, people the product reaches without ever being designed for them. A sharper version: who does this affect that you’ll never hear from? That is the audience the team most often forgets.
• Meaning, What should this experience mean, beyond what it does?
  Utility and meaning are two different claims. A product can satisfy every functional requirement and still feel extractive, or demeaning to the person using it. Norman’s three levels, visceral (first moment), behavioural (in use), reflective (what this says about who you are), locate meaning at the reflective level. A designer who works only at the visceral and behavioural levels has asked what it looks like and how it functions. Meaning is the question they skip.¹
• Feeling, What should this make people feel?
  A different question from Meaning. Meaning is reflective, what the experience makes you think. Feeling is visceral, the immediate response before any interpretation. A product can be meaningful and still feel flat. It can even feel strong in the moment and be quickly forgotten.
• Trade-off, What gets deprioritised, and is that a value judgement or a business constraint?
  Every decision trades something off. Resource trade-offs, what the team can build in the time available. Value trade-offs, whose experience benefits most, whose is given less weight. There is a deeper question teams rarely ask: is this kind of experience worth creating at all? Herbert Simon called design “devising courses of action aimed at changing existing situations into preferred ones.”² The word preferred always implies someone it serves, and someone it costs. Value Shaping is where those questions have to be answered, before delivery can begin.