Customer journey mapping for AI: onboarding that builds trust

The AI journey starts before the first prompt

Classic journey mapping asks: where does the user click, where does it snag? AI features add an emotional layer buttons never had: expectation and distrust. The KPMG study with the University of Melbourne quantifies the starting point – only 46 per cent of people worldwide trust AI systems, 39 per cent in high-income countries. Your user does not arrive neutral. They arrive curious and sceptical at once, and your journey decides which attitude wins.

The most reliable design frame comes from Microsoft's “Guidelines for Human-AI Interaction” (Amershi et al., CHI 2019): 18 guidelines along the interaction cycle – from “make clear what the system can do” through “make clear why it did what it did” to “make correction easy”. They are seven years old and fit GenAI products better than ever, because generative systems fail exactly where the guidelines start: at expectation, explainability and error tolerance.

The four moments that decide adoption

Moment 1: first encounter. Before anyone types, the expectation forms. Say concretely what the feature does (“summarises tickets, answers questions about your projects”) and where the limits are. Overpromising takes double revenge at the first error.

Moment 2: first input. The empty field is an exam many never sit. Example prompts from the real work context, templates and one-click starts lower the bar – the first win must happen in the first session.

Moment 3: first error. It will come, guaranteed. What matters is the handrail: sources to check, visible uncertainty, a correction or discard path without regret. That turns the error into a controlled moment instead of a breach of trust.

Moment 4: habit. From trying to workflow: the feature must appear where the work already happens – in the ticket, the editor, the review – rather than in a separate chat tab one has to visit. Contextual presence beats destination.

Transparency is a feature, not a footnote

In the EU, labelling AI interaction and AI-generated content is a transparency duty under the AI Act – but the duty is the lowest bar. Well-crafted transparency is conversion work: source references make answers checkable, confidence cues calibrate expectations, and a visible “created by AI, approved by you” turns loss of control into a sense of control. In DACH B2B especially, this visibility is a selling point in procurement.

The litmus test for your journey: can a sceptical first-time user experience within five minutes that the feature takes work off their hands without taking control away? If yes, you have built onboarding for the 54 per cent who distrust AI – not just for the early adopters who try everything anyway.

Recommendations

• Design the first error. Write the error scenario as a user story with acceptance criteria: source visible, correction possible, fallback defined. The first error is a feature, not an edge case.
• Kill the empty input field. Three contextual example prompts per entry point, drawn from real use cases. Measure how many first-time users experience a win within one session.
• Show uncertainty actively. Sources, confidence cues, check prompts on sensitive outputs. Calibrated expectation is the cheapest trust protection there is.
• Bring the AI to the work, not the work to the AI. Integrate into the existing workflow environment instead of building another chat tab. Habit grows from proximity to the task.

Scope & caveats

• The KPMG trust figures measure baseline attitudes, not behaviour in your product – use them as a design assumption (“users start sceptical”), not a conversion forecast.
• Too much uncertainty communication can make a good feature look weaker than it is. Calibrate the dose to the use case's risk: brainstorming needs fewer handrails than invoice data.

Matching use cases from the library

From the article straight into practice: these use cases put the concepts to work with Teklens.