Customer Journey Designer Interview Questions for AI Training Work

I combine direct customer research, like interviews or session recordings, with internal process documentation, rather than mapping purely from the internal perspective, since teams often assume a smoother experience than what customers actually encounter. I validate the map against real behavioral data wherever possible.

I look for moments with high emotional stakes combined with high drop-off or friction data, since those are where a redesign has the most leverage. A low-stakes step with minor friction usually isn't worth the same investment as a high-stakes moment where customers are actually abandoning the journey.

I bring the conversation back to actual customer evidence, like research findings or data, rather than letting it be resolved by whichever stakeholder has more organizational authority. Design thinking works best when the customer's actual experience, not internal opinion, is the deciding factor.

I look at the specific behavioral metrics the redesign targeted, like completion rate or time to complete a step, compared to before the change, rather than relying on qualitative impressions alone. I also check for unintended effects on adjacent steps in the journey that the redesign might have shifted rather than solved.

I design toward the ideal experience first based on genuine customer needs, then work with stakeholders to find the most feasible version that still addresses the core need, rather than starting from constraints and working backward, since starting from constraints tends to produce a design that only marginally improves things.

I'd dig into the discrepancy specifically rather than assuming either source is simply wrong, since interviews can reflect what customers intend or remember doing while analytics shows actual behavior, and the gap itself is often informative about where perception and reality diverge.

I'd bring concrete customer evidence and data showing the actual impact of the friction, framed in terms that connect to that team's own priorities, rather than only advocating from a customer experience perspective in isolation. Making the business case in terms relevant to their goals tends to build buy-in more effectively than appealing to empathy alone.

I'd build separate journey maps for the segments with meaningfully different experiences rather than forcing them into a single generic map, since a map that averages across very different experiences ends up not accurately representing any of them and makes the redesign priorities unclear.

Completion rates for a particular step looked acceptable, but interviews revealed that customers who did complete it felt significant anxiety and confusion along the way, which wasn't showing up as a quantitative problem yet. Redesigning that step for clarity, even though the metrics hadn't flagged it as broken, prevented what was likely to become a bigger issue as volume grew.

I designed a change intended to reduce anxiety at a specific step, but post-launch data showed it actually increased time to completion without improving the underlying satisfaction metric. I went back to the data and interviews to understand the gap, which showed the added reassurance content, while well-intentioned, introduced friction I hadn't anticipated, and I revised the design accordingly.