UX & Journey Mapping for BAs

You have had this experience: a website starts blaring four auto-playing videos at once, and instead of hunting for pause buttons, you leave. Experiences like that leave lasting impressions and directly affect a product's success, which is why companies invest in user experience (UX) design: the practice of examining people's needs and motivations to inform the design of the overall experience with a product or service. Observing behavior, listening to feedback, and reviewing prototypes with real users guides design decisions toward experiences that are clear and enjoyable.

Why is this a BA elective? Three reasons. First, the overlap is enormous: UX design "sits at the intersection of business, technology, and people," which is a sentence you could paste into Module 1's definition of your own job. Second, Salesforce work is experience work: every layout, flow, and portal you write requirements for is someone's daily experience, and adoption (Modules 13 through 15) hinges on how that experience feels. Third, journey mapping specifically has become a standard BA facilitation skill, requested by name on many projects.

Reassurance for the artistically nervous: beauty takes a back seat to clarity. Platform design systems (Salesforce's included) have already made the visual decisions: colors, typography, components. The UX skill you need is combining the pieces meaningfully around real user needs, and that is analysis, not art.

Map-type artifacts are diagrammatic representations of a user's experience. They help designers and stakeholders empathize with the user, spot friction, and identify improvement opportunities: and like land maps, they range from world-map breadth to city-map zoom. The information comes from workshops and user conversations: the maps are research made visible.

• Journey map: a visualization of each step of a persona's experience with a product or service over time, across all touchpoints. The star of this module; full treatment below.
• Service blueprint: extends a journey map by diagramming what happens before and after the product interaction, and establishes the relationships between digital and physical interactions: the complete lifecycle view.
• Ecosystem map: visualizes complex relationships among multiple systems: invaluable (and sprawling) in enterprises with interdependent applications. When your integration conversations from Module 11 need a picture, this is it.
• Empathy map: a quick four-quadrant capture of what a user says, thinks, does, and feels: a lightweight companion to personas.
• Mental model and storyboard: respectively, how users believe a thing works, and a comic-strip narrative of an experience: both cheap, both clarifying.

The second category moves from understanding to designing: screen designs progressing through fidelity levels, from paper sketches to wireframes to interactive prototypes. Prototypes matter because testing a rough draft is radically cheaper than testing built software: they are acceptance criteria you can click. As a BA you will rarely produce high-fidelity screens, but you will constantly review them, test them with users, and translate the feedback into requirements (and your Module 1 toolkit already listed mockups and wireframes among BA contributions).

The practical tool guidance: start with pencil and paper or a whiteboard (still the best brainstorming tools); lean on a design system rather than reinventing components; know that dedicated prototyping tools, virtual-workshop whiteboards, and all-in-one design platforms exist and evolve fast, so stay flexible rather than marrying one tool. Workshops themselves are tools: hold them early for discovery and mid-project for prioritization, and recruit diverse participants so outcomes are inclusive across ages, backgrounds, abilities, and cultures.

One UX habit worth stealing immediately: the feedback discipline. Ask for feedback on everything, make it easy to give (share in formats stakeholders can mark up), and when giving feedback yourself, make it actionable: "the button is hard to find" helps; "I don't like it" does not. This is Module 1's feedback-seeking habit, professionalized.

A journey map is a document that visually illustrates the experience a customer (or user) has with an organization. It identifies:

• The steps or activities the person takes to accomplish a goal
• The challenges they face along the way
• The people they interact with, in one organization or across an ecosystem
• The touchpoints and channels (devices, apps, calls, visits) they encounter
• The feelings, thoughts, and reactions they have throughout

Every journey has highs and lows, and their combination makes or breaks the experience. The crucial discipline: the map captures everything from the customer's point of view, not the organization's.

A simple example: a customer of a subscription service has a support request. Enrollment; a phone call with a question; the representative opens a request and sends confirmation; the rep checks service history (perhaps consulting sales colleagues about prior conversations, or operations for an approval); the service is provided; the record updates and appears in the customer's online portal. The map captures all of it, including the invisible-to-the-customer collaboration, because anything that affects the customer's experience belongs on the map.

Here is the connection to Module 5 that makes this module click for BAs. A process map shows how the organization executes work: swim lanes, handoffs, systems. A journey map shows how the customer experiences that work: waiting, wondering, calling back, feeling relieved. Same underlying reality, opposite camera angle. The most powerful analysis pairs them: the process map explains why the journey map's painful waiting step exists, and the journey map explains why anyone should care about fixing the process. Speak both languages and you can translate customer pain directly into process requirements.

The benefits: it builds shared understanding of everything the customer experiences; it demystifies how each role affects the customer (people who think their work is invisible discover it is a touchpoint); it aligns teams across silos around one story; it surfaces process optimizations and pain points with their emotional stakes attached; it grounds prioritization in customer impact; and it produces an artifact that keeps influencing decisions long after the workshop ends.

A journey map is ultimately a story. Walk your draft end to end as narrative, and answer three questions: What is your one-sentence introduction? What is your summary? What is your point of view on the best first steps to take as a result? A map that cannot be narrated is a spreadsheet in disguise.

Do not skip visual polish, and do not confuse it with aesthetics: this is about readability and effectiveness. Ask: What must people take away? What if they encounter the map without you there to explain it? What if they only have a few minutes? Concrete touches that transform comprehension: a persona header with photo and story ("Meet Jack, 32, who prefers email, values convenience, and browses from his phone") grounds every reader in a human being; emoji or curve visualizations of the Feelings row make the highs and lows legible at a glance. With story elements added, the map stops being a business graph and becomes the foundation for your solution.

One final pass before celebrating: a consequence scan: pausing to consider unintended consequences of your proposed solution and how to mitigate them. Reconvene your workshop participants, share the refined map and opportunities, and ask:

• What could this idea mean to the customer: security, reliability, support, accessibility?
• What could it mean for wellbeing and relationships: who else does the customer's experience affect?
• What if everyone in the world used it: any broad community or societal impact?
• Could it shift or deepen power structures or privilege?

Be genuinely prepared to revise or replace ideas based on the answers. Responsible innovation builds the customer and community relationships that business success rests on: and for a course training analysts to serve real communities, this scan is not a nice-to-have; it is the job done honorably.