Demand Creation Is CX Design at Its Highest Ambition

Most organisations design for the customer they have. The best ones design for the demand they intend to create. That distinction — subtle on paper, transformative in practice — is what separates a competent customer experience function from one that actually moves markets.

Adrian Slywotzky and Karl Weber's 2011 book Demand: Creating What People Love Before They Know They Want It (Crown Business) is not a CX manual. It is something more useful: a theory of why some products and services become indispensable while functionally equivalent alternatives languish. The argument, built across dozens of case studies, is that demand is not discovered — it is engineered. And the engineering discipline it most resembles is customer experience design.

This article unpacks Slywotzky's framework through a CX practitioner's lens, draws in the behavioral-economics mechanisms that explain why his principles work, and translates both into actionable design choices. The central claim is this: demand creation is CX design operating at its highest level of ambition — not just reducing friction in an existing journey, but constructing the conditions under which a customer cannot imagine going back.

What Does "Creating Demand" Actually Mean in CX Terms?

Demand, in Slywotzky's framing, is not the same as awareness or even preference. It is the state in which a customer actively reorganises their behaviour, budget, and habits around your product or service. They do not merely choose you — they miss you when you are absent.

That is a much higher bar than satisfaction. A customer can be satisfied with a service they would drop tomorrow if a cheaper alternative appeared. A customer in a state of genuine demand would not switch even if the alternative were cheaper, because the switching cost — emotional, cognitive, habitual — feels too high. This is the endowment effect in action: once people have integrated a product into their lives, they value it more than its objective utility warrants, simply because it is theirs.

CX design typically concerns itself with the journey a customer already takes. Demand creation asks a prior question: what would make a customer want to take that journey at all? The two disciplines are not in competition — they are sequential. You cannot sustain demand you have created if the experience is poor. But you will not create demand through experience alone if the product is merely adequate.

The demand-creation lens reframes CX design's purpose: not to manage an existing relationship more smoothly, but to make the relationship feel irreplaceable.

Why "Very Good" Is Not Enough: The Magnetic Product Principle

Slywotzky argues that products and services must be "magnetic" — combining high functional utility with a strong emotional connection — to generate real demand. "Very good" does not achieve this. Very good is forgettable. Magnetic is the thing people describe to someone who did not ask.

The behavioral mechanism here is the affect heuristic: when a product generates genuine positive emotion, customers use that emotional response as a proxy for quality across every dimension, including ones they have never tested. The emotional charge does cognitive work that no amount of feature specification can replicate.

In CX design terms, magnetism is not an accident of product development. It is the result of deliberate choices about which emotional states to engineer at which moments. A bank that makes a customer feel genuinely respected during a mortgage application — not just processed — has created an emotional anchor that competitors will struggle to dislodge. A retailer that makes the unboxing of a product feel like an event has turned a logistics touchpoint into a memory.

The practical implication: when mapping customer journeys, the question is not only "where does friction occur?" but "where does emotion peak, and are we designing that peak deliberately?" Most organisations leave their emotional high points to chance. Demand creators do not.

The Hassle Map: Where Demand Dies Before It Starts

One of the most operationally useful frameworks in Demand is the Hassle Map — a structured inventory of the daily frictions, inefficiencies, and frustrations customers encounter across a service journey. Slywotzky's observation is that demand is often blocked not by a bad product but by the accumulated weight of small irritants surrounding it: the form that requires information you already gave, the callback that never comes, the instruction manual that assumes expertise you do not have.

This maps precisely onto what Richard Thaler distinguishes as "sludge" — friction that serves the organisation's interests at the customer's expense — versus friction that is merely accidental but equally corrosive. Both kill demand. Neither is inevitable.

The Hassle Map is, in effect, a practitioner's tool for service design: a systematic method for surfacing the gap between what the organisation believes the experience to be and what the customer actually encounters. That gap is almost always larger than leadership expects. The reason is structural: the people who design processes are not the people who use them, and the people who use them rarely have a channel to report what they find.

Organisations that take the Hassle Map seriously typically discover three categories of friction:

• Procedural friction — steps that exist because of internal policy or legacy systems, not because they add customer value (duplicate data entry, mandatory in-branch visits for digital transactions, multi-step verification for low-risk actions).
• Informational friction — moments where the customer lacks the knowledge to proceed confidently, and the organisation has not anticipated or resolved that gap (unclear pricing, ambiguous next steps, jargon-heavy communications).
• Emotional friction — interactions that leave the customer feeling diminished, ignored, or mistrusted, even when the transaction technically completes (scripted apologies, deflection to self-service when human contact was sought, wait times with no acknowledgement).

Removing procedural friction is an engineering problem. Removing informational friction is a communication design problem. Removing emotional friction is a culture and training problem. All three require different interventions, but all three sit within the scope of serious CX design work.

The Curse of the Incomplete Product: When CX Design Fails at the Edges

Slywotzky identifies a recurring failure mode he calls the "curse of the incomplete product": a strong core offering surrounded by a weak or neglected ecosystem. The product works; the experience of owning and using it does not. The surrounding support, onboarding, maintenance, and renewal processes are left unfinished — and it is those edges that determine whether demand sustains or collapses.

This is one of the most common and least acknowledged failure patterns in CX. Organisations invest heavily in the acquisition moment — the marketing, the sales process, the launch — and underinvest in everything that follows. Yet the behavioral economics of loyalty runs in the opposite direction. The goal-gradient effect tells us that customers become more motivated as they feel closer to a meaningful outcome; if the post-purchase experience fails to deliver on the promise made at acquisition, the emotional debt is disproportionately large. Disappointment after high expectation is not neutral — it is actively destructive.

The incomplete product problem also manifests in digital transformation programmes. A new app or portal is launched; the core transaction flows beautifully. But the edge cases — the error states, the escalation paths, the moments when the digital channel cannot resolve the issue — are handled poorly or not at all. Customers who hit those edges do not conclude "the app has a bug." They conclude "this organisation does not care about me." The emotional attribution is to the brand, not the technology.

Completing the product, in CX design terms, means extending design rigour from the happy path to the full journey — including failure states, recovery moments, and the long tail of post-purchase interactions that most journey maps do not reach. The service design discipline exists precisely to address this: blueprinting not just what the customer experiences but the backstage processes, systems, and people that either support or undermine it.

The 45-Degree Angle: Why Incremental Improvement Does Not Create Demand

Slywotzky's "45-degree angle of improvement" is a challenge to the incremental mindset that dominates most CX programmes. The argument is that small, iterative improvements — a slightly faster checkout, a marginally clearer invoice — do not shift customer behaviour in any meaningful way. They reduce dissatisfaction at the margin. They do not create demand.

Demand requires a step-change: an improvement so steep and so visible that it reframes the customer's expectations of what the category can deliver. When that happens, the reference point shifts permanently. Customers no longer compare you to what you were; they compare everyone else to what you now are.

This is anchoring at the category level. Once a customer has experienced a dramatically better version of something — a checkout that takes seconds rather than minutes, a claims process that resolves in hours rather than weeks — the previous standard becomes intolerable. Competitors who were previously "fine" are now inadequate. The anchor has moved.

The implication for CX design is uncomfortable: the standard roadmap of incremental optimisation, however well-executed, may be the wrong strategy if the goal is demand creation rather than churn reduction. These are related but distinct objectives. Churn reduction requires removing the reasons to leave. Demand creation requires manufacturing reasons to stay that competitors cannot easily replicate.

The practical test is whether a proposed CX improvement would be noticed and described by a customer unprompted. If the answer is no — if it is the kind of improvement that only registers as an absence of complaint — it is a 5-degree improvement. Valuable, but insufficient for demand creation.

No Average Customer: The Design Trap of the Mean

Slywotzky's observation that there is "no average customer" is a direct challenge to the persona-based design orthodoxy that still dominates many CX programmes. Designing for an average — a composite that represents no one precisely — produces experiences that satisfy no one particularly. The mean obscures the variation that matters.

This is not an argument against segmentation. It is an argument for more honest segmentation: one that identifies the distinct customer variations that drive meaningfully different behaviours, needs, and emotional responses, rather than collapsing them into a single representative archetype.

In behavioral terms, the danger of the average customer is that it masks the loss-aversion asymmetry across segments. A customer who is highly anxious about a transaction — a first-time property buyer, a patient navigating a new diagnosis, a small business owner applying for credit — experiences friction as a threat, not an inconvenience. The emotional stakes are higher, the cognitive load is greater, and the memory of a poor experience is more durable. Designing for the average customer means designing for someone whose emotional stakes are moderate — and therefore systematically under-serving the customers for whom the experience matters most.

The solution is not to design a different journey for every customer. It is to identify the two or three dimensions of variation that most affect the experience — anxiety level, digital confidence, time pressure, stakes of the decision — and design the journey to accommodate the full range, not just the centre. CX archetypes built around behavioral and emotional variation, rather than demographic proxies, are a more reliable foundation for this work.

Converting Fence-Sitters: The Hidden Demand Pool

One of the most commercially significant ideas in Demand is the concept of the "fence-sitter" — a potential customer who is aware of a product, is not hostile to it, but has not yet made the move to purchase or commit. Fence-sitters are not lost customers; they are latent demand waiting for the right trigger.

Slywotzky argues that demand creators systematically identify and address the hidden barriers that keep fence-sitters in place. These barriers are rarely about price or awareness — they are about perceived risk, effort, or uncertainty. The customer does not know if the product will work for their specific situation. They are not sure the process will be straightforward. They have a vague concern they cannot quite articulate.

This is where the behavioral economics of loss aversion is most directly applicable. Fence-sitters are not neutral; they are loss-averse. The perceived risk of a bad outcome outweighs the perceived benefit of a good one. Converting them requires reducing the perceived downside — through trial mechanisms, social proof, transparent process design, or simply making the first step so small and low-commitment that the activation energy drops below the threshold of inaction.

In CX design, this translates to a specific design challenge: what does the pre-purchase or pre-commitment experience look like for someone who is interested but uncertain? Most organisations design their pre-purchase journey for customers who have already decided. The information architecture, the calls to action, the onboarding flow — all assume a level of commitment that fence-sitters do not yet have. Closing that design gap is often where the largest untapped demand lives.

Demand Creation as a CX Design Discipline: What It Requires

Taken together, Slywotzky's framework implies a set of design commitments that go beyond the standard CX programme. They are worth stating plainly:

1. Map the hassles before you map the journey. Understand the full friction landscape — procedural, informational, emotional — before designing solutions. The Hassle Map is the diagnostic; the journey map is the design response.
2. Complete the product before you promote it. Audit the edges of the experience — error states, recovery paths, post-purchase support, renewal — with the same rigour applied to the core transaction. Incomplete products destroy demand regardless of how strong the core is.
3. Design for emotional peaks, not just functional adequacy. Identify the two or three moments in the journey where emotional charge is highest, and design those moments with explicit intent. Leave nothing to chance at the peak.
4. Set a 45-degree ambition before you plan the roadmap. Ask what a step-change improvement would look like — one that would shift customer expectations for the category — before defaulting to incremental optimisation.
5. Segment by behavior and emotion, not demographics. Build archetypes around the dimensions of variation that most affect the experience: anxiety, stakes, digital confidence, time pressure. Design for the full range.
6. Design the pre-commitment experience for the uncommitted. Audit the journey from the perspective of a fence-sitter: someone interested but uncertain. Reduce the perceived risk of the first step.

None of these commitments is technically complex. All of them require organisational will — the willingness to look honestly at the gap between the experience you believe you deliver and the one your customers actually have. That gap, in our experience, is almost always the real barrier to demand creation. Not product quality. Not price. The experience.

If you want to benchmark where your organisation currently sits on this spectrum, the CX Maturity Assessment offers a structured starting point: a diagnostic across the twelve building blocks of CX capability that surfaces where the gaps are largest and where the highest-leverage interventions lie.

The Demand Imperative: CX Design as Competitive Strategy

The organisations that have created the most durable demand in their categories — in hospitality, in financial services, in healthcare, in retail — share a common characteristic. They did not treat customer experience as a service function. They treated it as the primary mechanism through which competitive advantage is built and defended.

That is a strategic choice, not an operational one. It requires the CX function to operate with a different mandate: not "how do we reduce complaints?" but "how do we make ourselves irreplaceable?" Not "what do our customers need today?" but "what would make them unable to imagine going back?"

Slywotzky's contribution is to show that this ambition is not abstract. It has a methodology. It starts with an honest inventory of hassles. It requires completing the product before promoting it. It demands designing for emotional peaks, not just functional adequacy. And it insists on treating customers as the varied, behaviorally complex individuals they are — not as a statistical average that no one actually resembles.

The organisations that take this seriously do not just improve their NPS scores. They change the reference point against which their entire category is judged. That is what demand creation looks like at scale — and it is, at its core, customer experience strategy operating at its full potential.

The gap between where most organisations are and where that ambition sits is large. But it is a design problem. And design problems, unlike structural ones, can be solved.