The Core Question CX Rarely Asks Clearly Enough

At its heart, customer experience design is supposed to answer one thing:

What does the customer actually want—right now, in this moment, from this interaction?

Yet many organizations behave like Dylan’s narrator—surrounded by requests, signals, complaints, and expectations, but still unsure what the ask really is.

The result?

• Products that technically work but emotionally miss
  
  

• Processes optimized for the company, not the customer
  
  

• Experiences that feel busy rather than helpful
  
  

Dylan’s refrain—“What was it you wanted?”—lands like a post-mortem question. CX is most effective when that question is asked before frustration sets in.

Expectations vs. Intent: Where Experience Breaks

One of the song’s quiet tensions is misalignment. Someone wants something. The narrator senses pressure. But clarity never arrives.

That’s a familiar CX failure mode.

Customers don’t experience your org chart.

They experience intent—or the absence of it.

Common disconnects:

• Customers want reassurance; companies deliver information
  
  

• Customers want resolution; systems deliver process
  
  

• Customers want confidence; brands deliver features
  
  

Dylan’s song lives in that gap—the space where expectations are projected but never translated. In CX terms, this is what happens when assumptions replace discovery.

The Burden of Being “Everything”

Another reading of the song frames it as a response to fame, audience demands, and constant reinterpretation. Dylan sounds tired of being cast as a symbol rather than a person.

Customers do this to brands too.

Organizations are expected to be:

• Fast and personal
  
  

• Scalable and human
  
  

• Automated and empathetic
  
  

When CX strategy tries to satisfy every expectation without prioritization, the experience collapses into ambiguity. The customer feels unseen, and the organization feels misunderstood.

That’s when the internal question becomes reactive:

Why aren’t they satisfied? We gave them everything.

But Dylan’s question cuts deeper:

Did we ever agree on what “everything” meant?

Listening Is Not the Same as Hearing

CX teams often pride themselves on “listening to the customer.” Surveys, NPS, feedback loops, analytics dashboards.

But Dylan’s song reminds us:

Listening without interpretation is just noise.

True experience design requires:

• Translating emotion into intent

• Separating stated wants from underlying needs

• Understanding context, timing, and constraint

The repeated question in the song isn’t ignorance—it’s an indictment of shallow listening. The words were spoken. The meaning never landed.

Designing for the Question, Not the Answer

Great customer experience isn’t built by prematurely solving problems. It’s built by staying with the question long enough to understand it.

Before solutions, ask:

• What problem is the customer actually trying to solve?
  
  

• What anxiety are they trying to reduce?
  
  

• What outcome would make this interaction feel “worth it”?
  
  

Dylan never resolves the song because unresolved questions are the point. CX practitioners should take note: clarity precedes satisfaction.

A Quiet CX Mantra

“What was it you wanted?” isn’t cynical.

It’s humane.

It’s the question behind:

• Empathy mapping
  
  

• Journey design
  
  

• Service recovery
  
  

• Change management
  
  

In a world obsessed with optimization, Dylan offers a reminder:

Experience begins not with systems or scripts—but with understanding.

If your customers seem frustrated, disengaged, or indifferent, the most powerful move may not be a new feature or faster workflow.

It may be to pause—and ask the question honestly, early, and often:

What is it you want?

And then, really listen.