Customer Experience Design UniMelb: What It Actually Means

Most organisations treat customer experience design as a communication problem — a matter of tone of voice, visual polish, and the right apology when something goes wrong. The University of Melbourne's graduate subject Customer Experience Design (MKTG90041) takes a different view: that CX design is fundamentally a systems problem, one that requires structured methods, testable hypotheses, and deliberate organisational change. That distinction is worth unpacking, because it points to something the broader profession still gets wrong.

Customer experience design is not the art of making interactions feel pleasant. It is the discipline of intentionally shaping every touchpoint a customer encounters — so that the cumulative effect builds trust, reduces effort, and earns loyalty. The difference between decoration and design is whether the work is grounded in evidence, structured around the customer's actual job, and connected to operational reality.

What UniMelb's CX Design Subject Actually Covers

MKTG90041 is a 12.5-credit-point graduate subject within the University of Melbourne's Master of Digital Marketing, also available to working professionals through the Community Access Program. It is delivered on-campus at Parkville and runs in Semester 2. The curriculum is tighter than most CX training you will encounter in the market: it centres on Human-Centered Design principles, digital touchpoint transformation, and — critically — organisational change management. The last element is where most CX programmes lose their nerve, and UniMelb's inclusion of it is the right instinct.

The methodological spine of the subject combines four frameworks that practitioners will recognise immediately:

• The Double Diamond — the Design Council's diverge-then-converge model that separates problem discovery from solution development. It forces teams to resist the instinct to jump to answers before they have properly defined the question.
• Desirability, Viability, and Feasibility (DVF) — the IDEO-originated lens that tests whether a proposed solution is wanted by customers, sustainable for the business, and achievable with available technology or capability.
• Jobs-to-be-done (JTBD) — the framework, associated with Clayton Christensen's work at Harvard Business School, that reframes customer behaviour around the functional, social, and emotional progress a person is trying to make, rather than around demographic categories or product features.
• The Hook Model — Nir Eyal's four-stage framework (trigger, action, variable reward, investment) for understanding how products and services build habitual engagement.

The practical toolkit is equally grounded: discovery research, empathy mapping, customer personas, journey mapping, service blueprinting, prototyping, and iterative improvement metrics. Students learn to map existing journeys, identify critical physical and digital touchpoints, design digital transformations with intent, and test prototypes against measurable outcomes.

This is, in short, a serious curriculum. It does not teach CX as a soft skill. It teaches it as a design discipline with a methodology, a process, and accountability to evidence.

Why the Double Diamond Is the Right Starting Point for CX Design

The Double Diamond is deceptively simple. Diverge to discover the real problem; converge to define it precisely; diverge again to generate solutions; converge to deliver the one that works. In practice, most organisations skip the first diamond entirely. They already know what the problem is — or think they do — and go straight to building the solution. The result is a product or service that solves the wrong thing very efficiently.

In customer journey design, this manifests as journey maps that document the organisation's intended process rather than the customer's actual experience. The map looks clean. The reality is chaotic. The Double Diamond disciplines teams to go and find out what is actually happening before they design anything.

The diverge-define phase is where the behavioral economics lens becomes indispensable. Customers do not experience a journey rationally, step by step, weighting each touchpoint equally. Daniel Kahneman's peak-end rule — established through his research on experienced utility, published across multiple papers from the late 1980s through the 1990s — tells us that people judge an experience primarily by its most intense moment and its final moment, not by the average across all interactions. A journey map that treats every touchpoint as equally important is not just incomplete; it is actively misleading. The Double Diamond, done properly, surfaces which moments actually shape memory and which are merely transactional noise.

Jobs-to-be-Done: The Framework That Cuts Through Persona Mythology

The JTBD framework deserves particular attention because it corrects one of the most persistent errors in CX design practice: the belief that a detailed customer persona is the same as customer understanding.

A persona tells you that your customer is a 38-year-old professional with two children and a preference for digital channels. JTBD tells you that the same person, in a specific context, is trying to make a financial decision without feeling judged, or trying to resolve a billing dispute without losing an afternoon to it. The job is the unit of analysis, not the demographic profile. And the job changes depending on the moment, the channel, and the emotional state the customer brings to the interaction.

This matters enormously for service design. When you design around the job rather than the persona, you stop building features that customers can describe and start solving problems they cannot always articulate. The classic example from Christensen's research — published in his 2016 book Competing Against Luck (co-authored with Taddy Hall, Karen Dillon, and David Duncan, Harvard Business Review Press) — is the milkshake study: fast-food customers were not buying milkshakes for the taste; they were hiring them for a long, boring commute that needed something to do. The product was right. The job it was serving had never been properly understood.

Applied to CX design, the JTBD lens reframes the entire design brief. The question is not "how do we improve the onboarding flow?" It is "what is the customer trying to accomplish in the first 30 days, and what is getting in the way of that?"

Where the UniMelb Curriculum Points Beyond Itself

The frameworks taught in MKTG90041 are the right ones. But a curriculum, by definition, teaches the method in a controlled environment. The harder challenge — the one that determines whether CX design actually changes anything in an organisation — is implementation under real conditions: competing priorities, legacy systems, organisational silos, and leaders who are enthusiastic about the concept but resistant to the implications.

UniMelb's inclusion of organisational change management in the curriculum signals an awareness of this gap. The subject does not pretend that good design automatically gets adopted. That is an honest and important acknowledgement. But the gap between understanding change management as a concept and executing it inside a large organisation is substantial.

Three practical realities that the classroom cannot fully replicate:

• The governance problem. CX design decisions cut across functions — marketing, operations, technology, legal, HR. Without a clear governance model that gives someone actual authority to make cross-functional calls, even the best journey redesign stalls at the boundary between departments. CX governance strategy is not a bureaucratic nicety; it is the mechanism that determines whether design intent ever reaches the customer.
• The measurement problem. Prototyping and concept testing are taught in the curriculum, and rightly so. But in live organisations, the metrics used to evaluate CX initiatives are often disconnected from the moments that actually drive customer perception. NPS is measured quarterly; the peak moment that shaped it happened six weeks ago and no one recorded it. Building measurement systems that capture the right signals at the right frequency is a design challenge in itself.
• The employee experience problem. Every customer-facing touchpoint is delivered by a person or a system that a person configured. The quality of the customer experience is downstream of the quality of the employee experience. Organisations that design beautiful customer journeys on top of broken internal processes are building on sand. This is not a peripheral concern — it is the central operational challenge of CX design at scale.

The Behavioral Economics Layer That Most CX Curricula Miss

The Hook Model, included in the UniMelb curriculum, is a behavioral framework — it draws on variable reward schedules and commitment mechanisms to explain habitual engagement. But it sits at the product-design end of the behavioral spectrum. There is a broader behavioral economics toolkit that CX designers need, and it operates at the level of the individual interaction rather than the product architecture.

Loss aversion — the well-documented tendency, established by Kahneman and Tversky in their 1979 paper "Prospect Theory: An Analysis of Decision under Risk" (Econometrica, Vol. 47, No. 2) — means that customers respond more strongly to the prospect of losing something they have than to the prospect of gaining something equivalent. A loyalty programme framed around points you risk losing generates more engagement than one framed around points you might earn. This is not a marketing trick; it is a structural design choice about how the programme communicates its value.

Friction versus sludge — a distinction Richard Thaler and Cass Sunstein developed through their work on choice architecture, elaborated in Thaler's 2021 book Nudge: The Final Edition — matters acutely in digital CX design. Friction is effort that serves the customer (a confirmation step before an irreversible action). Sludge is effort imposed on the customer to serve the organisation (a cancellation process that requires a phone call). The DVF framework taught in the curriculum asks whether a design is desirable, viable, and feasible. A behavioral lens adds a fourth question: does this design impose unnecessary effort on the customer to solve a problem that is actually the organisation's problem to solve?

These concepts do not require a separate course in behavioral economics. They require CX designers who have been trained to ask behavioral questions at every stage of the design process — during discovery, during ideation, and during prototype testing. That integration is the next frontier for CX design education.

From Curriculum to Practice: What Structured CX Design Actually Requires

Whether you are a graduate student completing MKTG90041 or a CX leader trying to build design capability inside an organisation, the translation from method to practice follows the same logic. The frameworks are the starting point, not the destination.

A structured CX implementation roadmap typically moves through the following sequence:

1. Discovery before design. Conduct genuine customer research — interviews, observation, complaint analysis, behavioural data — before drawing a single journey map. The Double Diamond begins with divergence for a reason. Assumptions about customer needs are almost always partially wrong and occasionally catastrophically wrong.
2. Define the job, not the persona. For each segment of the journey, articulate the functional, social, and emotional job the customer is trying to complete. This becomes the design brief. Everything that follows is evaluated against whether it helps the customer complete that job with less effort and more confidence.
3. Map the current state with honesty. Document what actually happens, not what the process diagram says should happen. Include the workarounds, the handoff failures, the moments where customers are left without information. The gap between the intended journey and the lived experience is where the design work begins.
4. Identify moments of truth. Apply the peak-end rule: which moments will disproportionately shape the customer's overall perception of the experience? Design those moments with deliberate intensity. Do not spread design effort evenly across all touchpoints — that is the same mistake as treating all touchpoints as equally important in the journey map.
5. Prototype and test before you build. The curriculum's emphasis on prototyping and concept testing is correct. The discipline is to test the assumption, not the execution — to find out whether the design solves the right problem before investing in the infrastructure to deliver it at scale.
6. Connect design to operations. A service blueprint, not just a journey map, is the tool that makes this connection explicit. The blueprint shows what the customer experiences on the front stage and what the organisation must do backstage to deliver it. Without this connection, design intent and operational reality diverge the moment the project ends.
7. Build the governance to sustain it. Assign ownership of each moment of truth. Establish the metrics that will tell you whether the design is working in live conditions. Create the feedback loop that brings customer signals back into the design process continuously, not just at annual review.

Why CX Design Requires Organisational Courage, Not Just Methodology

The frameworks in MKTG90041 — the Double Diamond, DVF, JTBD, the Hook Model — are genuinely useful. They are also, in a sense, the easy part. They give practitioners a shared language, a structured process, and a set of tools that make the work legible to stakeholders. That matters.

What the methodology cannot supply is the organisational will to act on what the research reveals. Discovery research frequently surfaces uncomfortable findings: that a product customers were told they wanted is actually one they find confusing; that a process the operations team is proud of creates significant customer effort; that the channel the organisation has invested in is not the one customers prefer. Customer-centricity efforts fail most often not because the design was wrong, but because the organisation was not prepared to act on what the design process revealed.

This is where the change management component of the UniMelb curriculum connects to something deeper than project management. Embedding customer experience design as an organisational capability — rather than a one-off project — requires leaders who are willing to let customer evidence challenge internal assumptions, and structures that give CX practitioners the authority to act on what they find. That is a cultural question as much as a methodological one.

For organisations serious about building that capability, the question is not whether to learn the frameworks. The question is whether the organisation is ready to be changed by what applying them reveals. The curriculum teaches the method. The harder work — and the more consequential one — is building the culture that makes the method matter.

If you are assessing where your organisation stands on that spectrum, a structured CX maturity assessment is a useful starting point: it surfaces the gaps between design intent and operational reality before you commit to a design programme that the organisation is not yet ready to sustain.