How to prepare for a customer journey audit

Pick a journey with a recognizable beginning and end. Examples include a trade inquiry becoming an approved order, a referral becoming an initial consultation, or a proposal becoming a delivery kickoff.

List which customer groups and channels are included. Trade and direct customers may need different paths. A showroom conversation can continue by email, so an audit limited to one channel may miss the handoff that causes confusion.

Agree who can explain the process and who can approve changes. Include the people doing the work, not only the people who designed the original process.

• Process: existing stage definitions, checklists, and informal steps.
• Channels: where inquiries arrive and how they are routed.
• Records: examples showing ownership, next actions, and handoffs.
• Customer questions: recurring requests for clarification or updates.
• Measures: available response-time or stage-duration data, with definitions.
• Systems: tools used and the information each one owns.

Choose representative examples, including an ordinary case and an exception. Redact personal or confidential details that are unnecessary for the review. Agree how evidence will be shared before sending exports.

For each step, record what the customer needs, which channel they use, what evidence is available, who is responsible, and what happens next.

This simple structure exposes missing responsibility without assuming the customer needs a new channel or the business needs new software.

Define the start and end of a measure. “Response time” could mean time until an automated acknowledgment or time until a useful answer. Those tell different stories.

Record the period, sample size, and any missing records. Note seasonal demand, staffing changes, unusual projects, or changes in how stages are used. Compare similar cases where possible.

If reliable data is missing, make that a finding. You can begin with qualitative evidence and establish a baseline as part of the improvement work.

The review should lead to a prioritized set of changes. For each proposed change, identify an owner, dependency, intended customer benefit, and way to check whether it worked.

Start with a limited pilot. A clear follow-up rule for one inquiry type can be easier to adopt and assess than a simultaneous redesign of every interaction.

Do we need a complete journey map already?

No. Bring the way the work happens today, including informal workarounds. Creating a shared understanding is part of the review.

What if the evidence is inconsistent?

Keep the inconsistencies visible. They can reveal differences between teams or channels and help define what needs investigation rather than being “cleaned” into a misleading picture.

Tight Ship CX reviews customer workflows and helps translate findings into practical process, CRM, and communication improvements.