20  Experience Design: Human-Centered Design and Journey Mapping

ImportantLearning Objectives

You will be able to:

  1. Apply human-centred design’s core commitments, empathy, co-creation, prototyping, iteration, to employee experience problems.
  2. Run the design-thinking cycle on an HR challenge, from empathize through test, and know where the method earns its cost.
  3. Build employee personas grounded in research rather than stereotype.
  4. Construct a full employee journey map, layered with doing, thinking, feeling, and backstage process, and convert it into a design backlog.

20.1 Introduction

Chapter 19 made experience a design object; this chapter supplies the design method. Human-centred design (HCD) is the discipline of designing from the lived reality of the person who will use the thing, and its management form, design thinking, was articulated for a general audience by Tim Brown (2008): a discovery process that begins in empathy with users, generates many options, and learns through cheap, fast prototypes rather than through complete specification. The reader of this book arrives prepared: design thinking is the same epistemology as agile, hypotheses over plans, evidence over opinion, iteration over big-bang, applied to the understanding of problems as much as to the delivery of solutions, which is why the two movements merged so naturally in EX practice (Kent Beck et al., 2001; Emma Bridger & Belinda Gannaway, 2021).

Applied to employees, HCD corrects the failure mode this book has diagnosed since Chapter 3: processes designed from the administrator’s chair, optimized for the convenience of the function that owns them, encountered as friction by the people who live them. The chapter builds the method in three movements: the design-thinking cycle as the engine; personas as the empathy instrument; and journey mapping, EX’s signature artifact, met in candidate form in Chapter 8 and generalized here to the whole lifecycle of Chapter 19.

flowchart LR
    E["Empathize:<br>research the lived<br>experience"] --> D["Define:<br>the real problem,<br>from the user's side"]
    D --> I["Ideate:<br>many options,<br>co-created"]
    I --> P["Prototype:<br>cheap, fast,<br>testable"]
    P --> T["Test:<br>real employees,<br>real evidence"]
    T -->|"learning"| E
    style E fill:#e3f2fd,stroke:#1976D2
    style I fill:#fff8e1,stroke:#F9A825
    style P fill:#ede7f6,stroke:#7E57C2
    style T fill:#e8f5e9,stroke:#388E3C

20.2 Human-Centred Design for Employees

20.2.1 The Design-Thinking Cycle

The canonical cycle runs in five modes, iterated rather than marched through. Empathize: study the experience as lived, through interviews, shadowing, diary studies, and the listening data of Chapter 12, seeking not opinions about solutions but the texture of the problem. Define: compress the research into a problem statement owned by the user, not the function, “new parents returning from leave lose their footing in the first month” rather than “leave administration needs streamlining”. Ideate: generate options in quantity, deliberately deferring judgment, and co-creating with the employees concerned in the Chapter 12 sense. Prototype: make the leading options tangible at the lowest possible cost, a paper mock-up of the new manager dashboard, a one-team trial of the revised return-to-work fortnight. Test: put prototypes in front of real employees and let the evidence, not the sponsor’s affection, decide what proceeds, the sprint-review discipline of Chapter 5 in design clothing (Tim Brown, 2008).

Where does the method earn its cost? Not everywhere, the contingency judgment of Chapter 4 applies to methods too. Design thinking pays where the problem is human, poorly understood, and expensively easy to solve wrongly: onboarding, returning from leave, performance conversations, workspace change. It is overhead where the requirement is already precise and compliance-bound, the payroll rule of Chapter 4 again (Emma Bridger & Belinda Gannaway, 2021).

WarningCommon Misconception: Design Thinking Is a Workshop

The sticky-note workshop is design thinking’s most visible artifact and least essential part. A two-day ideation event without prior empathy research produces confident solutions to unverified problems; without prototyping and testing afterward, it produces posters. The method’s value concentrates in its least glamorous phases, patient research before, disciplined testing after, and an organization that budgets only for the workshop has bought the middle of a bridge (Tim Brown, 2008).

20.2.2 Personas: Empathy at Scale

A persona is a composite portrait of a distinct employee population, the field-service engineer, the returning parent, the first-time manager, the gig-adjacent contractor of Chapter 24, synthesized from research and carried into every design conversation as the person the team is designing for. Good personas are built from interview and analytics evidence, capture goals, frictions, tools, and context rather than demographics, and are few, three to six covering the workforce’s genuinely distinct experiences. Their function is corrective: HR functions staffed by office-based knowledge workers reliably design for themselves, and the persona wall is what keeps the warehouse night shift, who meet the new self-service portal on a shared terminal in a loud room, present in a design meeting they will never attend (Emma Bridger & Belinda Gannaway, 2021).

TipPractitioner Insight: One Hour of Shadowing Beats Ten Personas

Personas decay into stereotype when the research behind them ages or never existed. The antidote is contact: put every member of the EX squad into regular direct observation, a shift shadowed quarterly, support tickets read weekly, exit interviews attended in person. Direct exposure does what documents cannot, it transfers the tacit texture of the experience, Chapter 17’s socialization applied to design, and it keeps the team honest when the persona and a living counterexample disagree.

20.3 Employee Journey Mapping

20.3.1 Anatomy of a Journey Map

A journey map lays a specific persona’s path through a specific experience along a timeline, and layers beneath each stage what the employee is doing, thinking, and feeling, the emotional curve is the map’s signature line, together with the touchpoints encountered (Chapter 21’s subject), and, in the fullest versions, the backstage: the systems, hand-offs, and process owners invisible to the employee whose failures produce the frontstage pain, the two-maps audit of Chapter 19 drawn as one artifact (Emma Bridger & Belinda Gannaway, 2021). The map is built the way Chapter 8 built its candidate version: from evidence, interviews, listening data, observation, never from the process documentation alone, and validated with the people it depicts before anything is designed from it.

NoteWorked Example: Journey Map Extract, First Ninety Days (Persona: Graduate Engineer, First Job)
Stage Doing Thinking and feeling Touchpoints Backstage finding
Offer to day one Signing, waiting, relocating Excited; anxious at three silent weeks Offer letter, portal, one email No owner of the pre-boarding window
Week one Forms, inductions, waiting for access Deflated: “they did not expect me” IT desk, badge office, buddy (unassigned) Access request starts on day one, takes 6 days
Weeks two to four First tickets, shadowing Overwhelmed; afraid to ask “basic” questions Team stand-up, manager 1:1 (once) Manager check-in cadence unspecified
Days 30 to 90 Real work, first review Growing confidence; unclear on expectations Check-in, learning platform No 90-day goal ritual; Chapter 9 cadence absent

The map’s analytical yield is the emotional curve’s shape: the peaks to protect and amplify, and the troughs, silent pre-boarding, accessless week one, question-fear, that become the design backlog, ordered by the severity-times-frequency logic Chapter 21 formalizes. Note how the example’s troughs are backstage failures and psychological-safety failures (Amy Edmondson, 1999), not perk deficits, the Chapter 19 point made empirical.

20.3.2 From Map to Backlog to Iteration

The map is a diagnosis, not a deliverable. Its findings convert into the machinery Part II built: each trough a backlog item with a hypothesis (“assigning the buddy at offer stage will cut week-one deflation”), each fix piloted as a minimum viable change in the Chapter 18 manner with one cohort, each pilot reviewed against the next cohort’s journey evidence and the listening signals of Chapter 12, then scaled or killed. Journeys also acquire owners: the journey product owner, onboarding, growing, leaving, is EX’s version of Chapter 5’s HR product owner, accountable for the emotional curve of one journey end to end, across every function whose backstage touches it (Emma Bridger & Belinda Gannaway, 2021; Natal Dank & Riina Hellström, 2020).

flowchart TD
    R["Research:<br>interviews, shadowing,<br>listening data"] --> M["Journey map:<br>doing, thinking, feeling,<br>touchpoints, backstage"]
    M --> B["Design backlog:<br>troughs as hypotheses,<br>ordered by impact"]
    B --> PL["Pilot:<br>minimum viable change,<br>one cohort"]
    PL --> V["Evidence:<br>next cohort's journey,<br>pulse signals"]
    V -->|"scale, adapt, or kill"| M
    style R fill:#e3f2fd,stroke:#1976D2
    style M fill:#fff8e1,stroke:#F9A825
    style PL fill:#ede7f6,stroke:#7E57C2
    style V fill:#e8f5e9,stroke:#388E3C

20.4 Case Studies

20.4.1 Case Study 1: IBM, Redesigning Performance Management by Design Thinking

When IBM retired its decades-old annual appraisal in 2015, it refused to let HR design the successor alone. The company ran the replacement as a design-thinking project on its own workforce: soliciting input from tens of thousands of employees, publishing the emerging design in internal social channels for open challenge, testing prototypes of the new approach, and iterating on the feedback before launch. The result, Checkpoint, embodied what employees had actually asked for: shorter goal cycles, more frequent feedback in the Chapter 9 manner, and dimensions of contribution beyond a single rating. The process mattered as much as the product: an appraisal system is exactly the kind of imposed experience employees distrust, and co-creation in the Chapter 12 sense converted the launch from an announcement to be survived into a design many thousands had already touched. IBM subsequently applied the same enterprise design-thinking method, personas, journey maps, iterative prototyping, across its internal HR products.

Discussion Questions:

  1. Why is performance management an especially high-stakes candidate for co-created design? Use Chapter 9’s unbundling analysis and this chapter’s empathize-define distinction.
  2. Publishing a half-finished design for open internal challenge is uncomfortable. Which Chapter 3 principle does it operationalize, and what did it buy at launch?
  3. Design a test protocol for a Checkpoint prototype: cohort, duration, and the evidence that would have justified scaling or killing it.

20.4.2 Case Study 2: DBS Bank, Journey Thinking Turned Inward

The Singapore bank DBS, in its celebrated transformation into a technology company that happens to bank, made journey thinking its universal method: customer journeys were mapped, instrumented, and owned, and the bank then pointed the same machinery at its own people. Employee journeys, joining the bank, getting equipped, learning, mobility, were mapped with the same rigour as customer ones, run by joint squads in the Chapter 11 style, measured end to end, and iterated; the bank’s stated ambition was to make banking joyful for customers and employees, and it instrumented both. Signature outcomes included a radically compressed, largely digital onboarding experience and internal platforms treating employees as users of the bank’s own craft. DBS’s lesson generalizes: an organization that already runs customer-experience discipline possesses, in-house, every method this chapter teaches, and the EX question is whether it has the will to aim that discipline at itself.

Discussion Questions:

  1. What advantages does a company gain by using the same journey method and vocabulary for customers and employees? What risks of false equivalence arise?
  2. DBS gave employee journeys owners and end-to-end metrics. Map this onto the journey-product-owner role and specify the metrics you would set for the equipping journey.
  3. “Joyful” is an emotional-curve target. Translate it into measurable journey evidence without reducing it to a satisfaction score.

20.5 Summary

NoteChapter Summary

Human-centred design supplies EX’s method: empathy research before problem definition, options generated and co-created, learning through cheap prototypes tested on real employees, the design-thinking cycle Tim Brown (2008) articulated, sharing agile’s epistemology of evidence over specification (Kent Beck et al., 2001). The method earns its cost on human, ill-understood, expensive-to-guess-wrong problems, not on compliance-bound ones (Emma Bridger & Belinda Gannaway, 2021). Personas carry research-grounded empathy into design conversations and are kept honest by direct contact. The journey map, layering doing, thinking, feeling, touchpoints, and backstage along a persona’s timeline, converts experience into a diagnosable curve whose troughs become a hypothesis backlog, piloted as minimum viable changes, reviewed against next-cohort evidence, and owned end to end by journey product owners (Natal Dank & Riina Hellström, 2020). IBM shows the method rebuilding the most distrusted HR product by co-creation; DBS shows customer-journey discipline aimed inward. Chapter 21 descends from the journey to its atoms, touchpoints, and the strategies that enhance them.

TipKey Terms

Human-centred design · Design thinking · Empathize, define, ideate, prototype, test · Problem statement · Co-creation · Persona · Journey map · Emotional curve · Backstage · Design backlog · Journey product owner

Summary

Concept Description
Human-Centred Design
Human-centred design Designing from the lived reality of the person who will use the thing
Design thinking Brown's management form of HCD: empathy, options, and learning through prototypes
Shared epistemology with agile Hypotheses, evidence, and iteration applied to understanding problems as well as delivering solutions
Empathize Researching the experience as lived, seeking the problem's texture rather than solution opinions
Define Compressing research into a problem statement owned by the user, not the function
Ideate Generating options in quantity with judgment deferred and employees co-creating
Prototype Making leading options tangible at the lowest cost that can generate evidence
Test Letting real-employee evidence, not sponsor affection, decide what proceeds
Method contingency Spending the method where problems are human, ill-understood, and costly to guess wrong
Workshop fallacy Buying the ideation event without the research before it or the testing after it
Personas
Persona A research-grounded composite of a distinct employee population carried into design
Persona decay Personas ageing into stereotype when the research behind them stops
Shadowing discipline Regular direct observation transferring tacit experience texture to the design team
Journey Mapping
Journey map A persona's path through an experience, layered with doing, thinking, feeling, and touchpoints
Emotional curve The feeling line whose peaks are protected and whose troughs become the backlog
Backstage layer The invisible systems and hand-offs whose failures produce frontstage pain
Evidence-built maps Building maps from interviews, listening data, and observation, never process docs alone
Map-to-backlog conversion Troughs restated as hypotheses, piloted as minimum viable changes, reviewed on cohort evidence
Journey product owner A named owner accountable for one journey's emotional curve across all functions
Case Evidence
IBM Checkpoint IBM's co-created replacement of the annual appraisal, designed with tens of thousands
DBS employee journeys DBS aiming its customer-journey machinery at joining, equipping, learning, and mobility