What Slywotzky Got Right About Demand — and CX Still Misses

What Adrian Slywotzky Got Right About Demand — and What CX Designers Still Miss

Most organisations treat demand as something to capture. Slywotzky argued it is something to create. That distinction, quiet as it sounds, separates the companies that chase market share from the ones that redefine the market entirely.

Published in October 2011 by Crown Business, Demand: Creating What People Love Before They Know They Want It — written by Adrian Slywotzky with Karl Weber — arrived at a moment when the business world was still explaining the iPhone's success by pointing at Apple's marketing budget. Slywotzky pointed somewhere else: at the architecture of the experience itself. More than a decade on, his framework remains one of the most practically useful lenses for anyone working in customer experience design. Not because it is theoretical, but because it is ruthlessly diagnostic.

This article unpacks Slywotzky's core ideas, applies them to the mechanics of modern CX design, and makes the case that the gap between "very good" and "magnetic" is not a product gap — it is an experience gap.

Why "Very Good" Is the Most Dangerous Place to Be

Slywotzky's central provocation is that very good products fail all the time. They fail not because of poor quality, but because quality without magnetism generates no pull. A product can be technically superior, competitively priced, and well-distributed — and still sit on the shelf while something less polished but more emotionally coherent walks out the door.

He calls the alternative a magnetic product: one that combines high functional performance with an emotional connection strong enough to make the customer feel that switching would be a genuine loss. This is not branding language. It is a structural claim about how demand is generated and sustained.

From a behavioral economics standpoint, Slywotzky is describing the endowment effect — the well-documented tendency, identified by Richard Thaler, for people to value things more once they own or regularly use them. A magnetic product accelerates endowment. It makes the customer feel ownership of the experience, not just the object. The emotional attachment is the moat, not the specification sheet.

For CX practitioners, this reframes the design brief. The question is not "does this work?" but "does this create the kind of relationship where the customer would feel the loss of it?" Those are very different design targets, and most customer journey work is still optimising for the former while ignoring the latter.

The Hassle Map: The Most Underused Tool in CX Design

Of all Slywotzky's concepts, the Hassle Map is the one that deserves the widest adoption in CX practice — and receives the least.

A Hassle Map is a structured inventory of every friction, inconvenience, and obstacle a customer encounters during a transaction or experience. Not the dramatic failures — those get logged in complaints and NPS verbatims. The Hassle Map is interested in the mundane irritants: the extra click, the unexplained wait, the form that asks for information you already provided, the confirmation email that arrives three days late. These are the frictions that customers rarely articulate but always feel.

"The Hassle Map is not a journey map. It is a grievance audit — and the distinction matters enormously for what you do next."

A journey map shows you the steps. A Hassle Map shows you the cost of each step — in time, cognitive effort, emotional energy, and the quiet erosion of trust that accumulates when a company repeatedly asks more of its customers than it needs to. The two tools answer different questions. Journey maps answer "what happens?" Hassle Maps answer "what does it cost the customer to make it happen?"

Richard Thaler's concept of sludge — the friction deliberately or carelessly left in a process that imposes unjustified costs on the user — is the behavioral economics counterpart to Slywotzky's Hassle Map. Both frameworks make the same argument: friction is not neutral. Every unnecessary step is a small act of disrespect that the customer registers, even when they cannot name it.

Effective service design begins with a rigorous Hassle Map, not a wishlist of features. You cannot build demand by adding value on top of unresolved friction. The friction wins.

The Incomplete Product: Why Great Technology Fails at the Last Mile

Slywotzky identifies a recurring pattern he calls the curse of the incomplete product. A company builds something genuinely innovative — a strong core technology, a novel service model, a compelling proposition — and then leaves the surrounding experience unfinished. The product works. The experience of using it does not.

This is not a niche failure mode. It is arguably the dominant failure mode in digital transformation. The application is fast and the interface is clean, but the customer support is unreachable. The onboarding is automated, but nobody explains what happens when something goes wrong. The core product is excellent; the ecosystem around it is an afterthought.

The incomplete product fails not because customers cannot see its value, but because they cannot reliably access that value. And when access is uncertain, demand does not build — it stalls. Customers who want the product but cannot trust the experience become what Slywotzky calls fence sitters: people who are already persuaded in principle but blocked in practice by cost, complexity, or the fear that the experience will let them down.

Converting fence sitters is one of the highest-return activities in demand creation. They require no awareness campaign — they already know you exist. They require no persuasion on the core proposition — they already want it. What they need is the removal of the specific obstacle that is keeping them on the fence. That is a design problem, not a marketing problem.

For organisations working on digital transformation, this framing is particularly useful. The transformation is rarely incomplete at the technology layer. It is almost always incomplete at the experience layer — the human moments, the edge cases, the recovery protocols, the explanations that make the technology feel trustworthy rather than merely functional.

The 45-Degree Angle: Why Incremental Improvement Destroys Demand

One of Slywotzky's sharpest observations is about the geometry of improvement. He argues that most organisations make five-degree improvements — small, incremental refinements that are visible to no one except the internal team that built them. The customer does not feel a five-degree improvement. It does not change their experience in any way that registers.

Demand is created by 45-degree improvements: changes steep enough to fundamentally redefine what the customer expects from the category. A 45-degree improvement does not make the existing experience slightly better. It makes the previous version of the experience feel obviously inadequate in retrospect.

This is not an argument for radical innovation for its own sake. It is an argument about the threshold of perceptibility. Below a certain magnitude of change, improvement is invisible to the customer — and invisible improvement generates no new demand. It simply maintains the status quo at a higher cost.

The behavioral mechanism here is adaptation level theory: customers calibrate their expectations to the baseline they have experienced, and small improvements are absorbed into that baseline without generating any positive signal. A 45-degree improvement, by contrast, resets the baseline. It creates a new reference point — and with it, a new reason to choose.

For CX leaders, this has direct implications for how improvement programmes are scoped and prioritised. A portfolio of twenty small initiatives, each delivering a marginal gain, is likely to produce less demand than two or three genuinely steep improvements that customers can actually feel. The question to ask of every CX initiative is not "is this better?" but "is this better enough to matter to the customer?"

Designing for Specific Humans, Not the Average Customer

Slywotzky is explicit on a point that many organisations still resist: there is no average customer. Designing for an average produces a product that is mediocre for everyone and excellent for no one. Demand is created by designing for specific, real human beings with particular circumstances, constraints, and desires — and then finding that the solution resonates far more broadly than the narrow profile suggested.

This is the logic behind what is now called CX archetypes — not statistical personas built from demographic averages, but richly observed portraits of real human behaviour, motivation, and context. The archetype is useful not because it represents the majority, but because it is specific enough to generate real design decisions. An average cannot tell you where the friction is. A specific human can.

The practical implication is that demand creation requires ethnographic curiosity — the willingness to observe, in detail, how real people actually behave in the moments that matter, rather than how they report they behave in a survey. Slywotzky's framework is built on this kind of observation. The Hassle Map is not a theoretical construct; it is the output of watching real people navigate real experiences and noting, without judgment, where they stumble.

This connects directly to the Jobs-to-be-Done framework developed by Clayton Christensen: customers do not buy products, they hire them to do a job in a specific circumstance. The circumstance is everything. Two customers with identical demographics may be hiring the same product for entirely different jobs — and the experience design that serves one may actively frustrate the other. Specificity is not a constraint on scale; it is the precondition for it.

From Demand Theory to CX Design Practice

Slywotzky's framework is not a CX methodology in the conventional sense. He does not prescribe a process. But his concepts map directly onto the decisions that CX design teams make every day. Here is how the translation works in practice:

• Start with the Hassle Map, not the feature list. Before any design work begins, conduct a rigorous audit of every friction point in the current experience. Prioritise elimination over addition. Removing a hassle creates more demand than adding a feature, because friction is felt more acutely than equivalent benefit — loss aversion, as Kahneman and Tversky documented, is a more powerful motivator than equivalent gain.
• Test for magnetism, not just satisfaction. CSAT and NPS measure whether customers are content. They do not measure whether customers are attached. Add a simple diagnostic: "Would you feel the loss of this experience if it were taken away?" Answers to that question reveal whether you have built something magnetic or merely adequate.
• Identify your fence sitters by segment. Map the specific obstacles — cost, complexity, trust, access — that are keeping interested non-customers from converting. Design targeted interventions for each obstacle. This is more efficient than broad acquisition spend and more durable than promotional discounting.
• Set a 45-degree threshold for every major initiative. Before committing resources to an improvement programme, ask whether the proposed change is steep enough to be perceptible to the customer. If it is not, either combine it with other changes until it crosses the threshold, or deprioritise it in favour of initiatives that will.
• Complete the product before you scale it. Audit the ecosystem around your core offering — support, onboarding, recovery, communication — and resolve the incomplete elements before investing in growth. Scaling an incomplete product amplifies the incompleteness.
• Design from specific archetypes, not demographic averages. Anchor every design decision in the observed behaviour of real, named human profiles. Specificity generates better decisions and broader appeal than averaged assumptions.

If you want a structured way to assess where your organisation currently sits on this spectrum, the CX Maturity Assessment provides an AI-scored evaluation across twelve building blocks — including the experience design dimensions that Slywotzky's framework most directly implicates.

The Demand Gap Is an Experience Gap

Here is the claim worth taking seriously: most organisations that believe they have a demand problem actually have an experience problem. The market exists. The awareness exists. The intent exists. What is missing is an experience coherent enough, complete enough, and frictionless enough to convert that intent into sustained behaviour.

Slywotzky's contribution is to make this argument with precision. He does not say "improve the experience." He says: map the hassles systematically, build magnetism deliberately, complete what you have started, and make improvements steep enough to matter. These are design instructions, not aspirations.

"Demand is not captured. It is designed — through the deliberate removal of friction, the deliberate construction of emotional connection, and the deliberate completion of every element of the experience the customer actually encounters."

The organisations that understand this do not wait for demand to appear and then compete for it. They build the conditions under which demand becomes inevitable. That is a different kind of ambition, and it requires a different kind of discipline — one that begins not with the product, but with the person using it, and works outward from there.

For teams ready to move from aspiration to architecture, customer experience strategy work at Renascence is built precisely on this logic: diagnosing the experience gap, identifying the friction that is suppressing demand, and designing the interventions steep enough to shift the curve. The methodology is different from conventional CX consulting. So are the results.

Slywotzky wrote about demand. What he was really writing about was design — the kind that creates desire before the customer can articulate what they want. That remains the hardest and most valuable thing a CX team can do.