3.3 Process Mapping and Touchpoint Identification

3.3 Process Mapping and Touchpoint Identification

Quick Answer: Process maps show how work moves inside the organization; journey maps show how customers experience progress. Touchpoint inventories list the interaction nodes (customer and employee-mediated) across channels. CCXP professionals use all three to find gaps where processes “succeed” but experiences fail.

Personas and journey maps still leave a critical blind spot if you never examine how the work actually runs. Domain 1 expects you to connect insight to operational reality: the systems, handoffs, policies, and human touchpoints that create or destroy experience. Process mapping and touchpoint identification are the tools that make that connection visible.

---

Why This Distinction Matters

Many improvement programs fail because teams “fix the process” (cycle time, accuracy, cost) while customers still feel confused, anxious, or abandoned. Others redesign a glossy front-end journey without changing backstage workflows, so the new promise collapses at the first exception. The CCXP standard is to hold both lenses:

• Experience lens (journey): What did the customer try to do, feel, and need?
• Operational lens (process): What steps, roles, systems, and controls actually executed?

Gaps between those lenses are often where the highest-ROI CX work lives.

---

Process Mapping vs Journey Mapping

Internal Process View

A process map (flowchart, swimlane, SIPOC, value-stream sketch) documents how inputs become outputs. It answers: Who does what, in what order, with which system, under which rule? It is essential for root-cause analysis, automation, staffing, and risk control. Example process step: “Fraud team reviews flag within 24 hours and updates case status code.”

Customer Experience View

A journey map may show the same period as: “I transferred money; the app said pending; nobody told me why; I called twice; I worried my rent would bounce.” Operationally the fraud review may be working as designed. Experientially it may be a severe pain point. Both statements can be true.

How Professionals Use Them Together

1. Map the current-state journey for a persona/scenario.
2. Map the supporting processes behind painful stages.
3. Align timestamps and handoffs (when did the customer feel X vs when did the process do Y?).
4. Identify breakage types: missing touchpoint, broken touchpoint, unnecessary touchpoint, or backstage failure that surfaces as experience pain.
5. Decide whether the fix is communication, policy, process redesign, system change, or employee enablement.

Later domains deepen this with service blueprinting (frontstage, backstage, support processes). In Domain 1, your job is to recognize that insight work includes inventorying and relating these views—not only collecting survey scores.

---

Touchpoints: Definition and Inventory

A touchpoint is any point of interaction between the customer (or prospect) and the organization’s brand, people, products, or systems—direct or mediated. Touchpoints can be:

• Customer-initiated (call, chat, store visit, app login)
• Organization-initiated (bill, alert, outbound collection, proactive status message)
• Passive / environmental (packaging, branch atmosphere, invoice layout)
• Employee touchpoints that shape CX even when the customer is not present (knowledge base used by agents, dispatch tools, exception queues)

Why Inventory Both Customer and Employee Touchpoints

Employee tools and handoffs are often the hidden determinants of customer experience. If agents lack a unified customer history, every call becomes a re-interrogation—an employee touchpoint failure that customers feel as effort and distrust. A mature inventory therefore includes:

Building a Touchpoint Inventory

Practical steps:

1. Scope a journey scenario and persona (do not inventory “everything forever” in one pass).
2. List all interaction nodes by stage and channel from research, analytics, and frontline workshops.
3. Classify ownership, purpose, frequency, and criticality (moment of truth vs low-stakes).
4. Assess quality signals — satisfaction, effort, completion, error, complaint themes.
5. Flag orphans and duplicates — touchpoints with no owner, or multiple messages that conflict.
6. Link to process steps — which workflow produces or depends on this touchpoint?
7. Prioritize gaps for measurement and design.

---

Finding Gaps Between Process and Experience

Process–experience gaps are patterns you should recognize on exam items:

1. Process Complete, Customer Uncertain

Status fields update internally, but no customer-intelligible update is sent. The process KPI is green; CES and inbound volume are red.

2. Handoff Seams

Work moves from sales to onboarding to billing with clean internal tickets, while customers repeat information and receive conflicting answers. The map shows multiple process owners; the journey shows one continuous burden on the customer.

3. Policy Walls at the Edge

A process correctly enforces a rule (ID verification, credit, returns). The experience fails because the rule is unexplained, alternatives are hidden, or employees lack exception guidance. Fixing experience may mean better explanation and choice architecture—not abandoning the control.

4. Channel Breaks

Customers start in digital and finish in contact center, but context does not travel. Process “swims” in separate systems; experience feels like starting over.

5. Invisible Employee Friction

Average handle time targets are met by rushing, which increases recontacts. Process efficiency metrics improve while relationship metrics erode—classic misaligned measurement.

---

Scenario: Inventory Reveals the Real Breakage

A utilities firm maps a “move home” journey and sees high effort at final bill. Leadership assumes billing calculation complexity is the root cause and funds a rating-engine project. A touchpoint inventory plus process map shows something else: five separate confirmation messages (web, email, SMS, letter, agent script) with inconsistent move dates; field scheduling system does not share the confirmed date with billing start; agents have a workaround spreadsheet. Customers experience contradictory touchpoints; the process “succeeds” as separate local completions. The prioritized fix becomes touchpoint rationalization and system handoff, not only engine sophistication. Insight work that stops at journey emotion without process/touchpoint linkage would have funded the wrong program.

---

Connecting Back to Personas and Journeys

Use the three tools as a stack:

1. Personas define whose jobs and contexts you are optimizing.
2. Journey maps show stages, emotions, and moments of truth for those personas.
3. Process maps + touchpoint inventories expose the operational machinery and interaction nodes that create the journey.

Together they turn Domain 1 insights into something the organization can govern: owners, metrics, and design backlog items. Alone, any one artifact can mislead.

---

Exam Focus

Be ready to:

• Differentiate process mapping (internal workflow) from journey mapping (customer experience over time)
• Inventory customer and employee touchpoints across channels and stages
• Detect gaps where process success masks experience failure (handoffs, silence, channel breaks, policy communication)
• Choose methods that combine evidence, frontline knowledge, and operational truth—not a single siloed map
• Translate identified gaps into prioritization inputs for strategy and design work downstream

Master this section and you will not confuse a clean flowchart with a good experience—or a pretty journey poster with an operable system of touchpoints.