Customer Journey Mapping

2 posts

figma2 min readCurated summary

Beyond mocks: co-designing journeys, diagrams, and more | Figma Blog

Design is more than producing interface mocks; it also involves shaping customer experiences, processes, culture, and community. Segment’s product design team demonstrates how designers can collaborate with researchers, product managers, engineers, and other colleagues using shared visual artifacts. These co-designing practices create organizational sources of truth, improve decision-making, and strengthen team connections. ## Mapping the Customer Journey with UX Research - A designer and UX researcher mapped Segment’s end-to-end customer experience, from discovery and sign-up through scaled implementation. - The journey was organized around different customer tiers and enriched with analytics. - An interactive prototype included clickable customer stories. - The resulting file became both a reference point for the company and an onboarding resource. ## Diagramming Data Architecture - Designers, researchers, customer success managers, and infrastructure engineers collaborated to visualize how data moves through Segment. - The diagram showed where data is transformed, enriched, and cleaned. - It helped the team identify existing strengths and areas needing improvement. - The artifact became foundational for planning future products and served as another organizational source of truth. ## Retrospecting on the Design System - Segment’s open-source Evergreen design system is used by teams beyond design, making cross-functional feedback especially important. - Designers and engineers held a remote retrospective in Figma using virtual sticky notes. - Participants documented pain points and identified opportunities for improvement. - The exercise informed the following quarter’s OKRs and helped the team co-design a roadmap for Evergreen. ## Building Community Through Collaboration - Co-designing can support social connection as well as product and process work. - For International Women’s Day, remote EPD teammates collaborated in Figma to create personalized appreciation notes for female-identifying colleagues. - The team also adapted the practice for virtual birthday cards and other celebrations. - These activities helped preserve meaningful workplace rituals while working remotely. The article encourages teams to expand co-design beyond product mocks. Shared journeys, diagrams, retrospectives, and collaborative community activities can make complex work visible, align diverse teammates, and create stronger connections.

Read original(opens in new tab)
figma3 min readCurated summary

Customer journey mapping with Figma | Figma Blog

Customer journey maps help teams build a shared understanding of how people experience a process, including emotions, pain points, and opportunities for improvement. The article explains how Lextech uses Figma to research, create, refine, and validate these maps collaboratively. Figma’s component libraries, collaboration tools, version history, and comments make journey mapping more consistent and easier to share with clients and customers. ## When Customer Journey Maps Are Useful - Journey maps visually tell the story of a customer process, such as shopping for a car or purchasing a product online. - They combine process steps with customer emotions and pain points. - A shared map helps people with different perspectives understand research and identify improvement opportunities. - Journey maps are less suitable for highly nonlinear processes with many branches or dependencies; a two-dimensional user-flow diagram may work better. - They may also add limited value when a process is already well documented through other visual methods. ## Building a Journey Map Component Library - Teams can create reusable components and styles specifically for journey maps. - A shared library improves visual consistency and speeds up the creation of new maps. - Global style or component updates can be applied efficiently when the design changes. - Lextech provides a sample Figma file and component library as a starting point. ## Keeping Maps Organized with Tidy Up - Figma’s **Tidy Up** feature helps adjust spacing between journey steps. - It makes it easier to insert or reorder steps without rebuilding large portions of the map. ## Research and Real-Time Collaboration - Multiple designers can work on the same journey map simultaneously. - Lextech also records interview notes directly in Figma, keeping research and map development in one location rather than spreading information across multiple tools. ## Using Version History - Before sending a map to clients, the team manually timestamps a version in the file’s history. - This creates a reliable reference point if the team needs to revisit an earlier state. - Showing how a map evolved can help clients understand how research findings changed the team’s understanding of the customer. ## Gathering Feedback with Comments - Lextech shares rough journey maps with customers to validate research and uncover missing steps. - Comments provide a centralized feedback channel tied to precise locations on the map. - Teams can ask follow-up questions directly in comment threads. - For asynchronous reviews, the team duplicates the file, shares the map as a single-screen prototype, and invites users to comment. - During live reviews, a designer records participant feedback directly in the file. - Separate file copies can prevent earlier comments from biasing new reviewers and make it easier to compare feedback from customers, clients, and other groups. Figma is most effective when journey maps are treated as collaborative, evolving research artifacts rather than static deliverables. Start with reusable components, keep research and feedback in the same file, and validate the map with real users before using it to guide design decisions.

Read original(opens in new tab)