User-Experience-Designer Salesforce Certified User Experience Designer (SP23) Questions and Answers

The best approach to improve the Sales team’s experience with Contact records in Sales Cloud is to run the Salesforce Optimizer App to identify fields not in use. The Salesforce Optimizer App is a free tool that scans the Salesforce org and provides a diagnostic report on the performance and health of the org1. It analyzes how the org uses various features, such as fields, triggers, layouts, profiles, reports, and more, and suggests customizations and improvements based on best practices1. By running the Salesforce Optimizer App, the Sales team can find out which fields are not being used or are redundant, and remove or hide them from the Contact record page. This way, they can simplify the page layout, reduce the page load time, and focus on the fields that are relevant to their sales activities2.

Moving all unused fields to a separate section at the bottom of the page is not a good option, as it does not solve the problem of having too many fields on the page. It would still affect the page load time and the user experience, as the users would have to scroll down to see the entire page. Moreover, it wouldnot help the users to find the information they need, as the fields would not be organized in a logical or meaningful way3.

Implementing In-App Guidance to help users focus on the most important fields is also not a good option, as it does not address the root cause of the problem, which is having too many fields on the page. In-App Guidance is a feature that allows admins to create custom prompts and walkthroughs to guide users through tasks or processes on Salesforce Lightning pages4. It can be useful for user training, onboarding, or adoption, but it cannot replace the need for a clean and efficient page layout. In fact, having too many prompts or walkthroughs on the page can be distracting and annoying for the users, especially if they are not relevant or helpful4. References:

• Run the Salesforce Optimizer App
• Improve Your Implementation with Salesforce Optimizer
• Page Layouts
• In-App Guidance in Lightning Experience

 The Salesforce Lightning Design System (SLDS) is a collection of resources that help you create user interfaces that are consistent with the Salesforce Lightning principles, design language, and best practices. The SLDS resources that could be used to make custom applications look, act, and sound like Salesforce are:

• Blueprints and tokens: Blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. Tokens are visual design values and attributes that ensure branding and UI consistency at scale. By using blueprints and tokens, you can create custom components that follow the SLDS design standards and patterns.
• Guidelines for voice and tone: Voice and tone guidelines help you write clear, concise, and consistent content that reflects the Salesforce brand personality and values. By using voice and tone guidelines, you can create custom applications that communicate effectively and respectfully with your users.

The SLDS resources that are not relevant to make custom applications look, act, and sound like Salesforce are:

• Full functional components: Full functional components are pre-built Lightning components that provide out-of-the-box functionality and interactivity. They are not part of the SLDS, but rather part of the Lightning Component Library. You can use full functional components to speed up your development process, but they are not necessary to make custom applications look, act, and sound like Salesforce.
• In-App Guidance: In-App Guidance is a feature that allows you to create and deliver contextual help and training to your users within your application. It is not part of the SLDS, but rather part of the Salesforce Platform. You can use In-App Guidance to enhance your user experience and adoption, but it is not essential to make custom applications look, act, and sound like Salesforce.

References: Lightning Design System, Explore SLDS Resources, Getting Started

The design should be optimized for color contrast-ratio and screen-reading technology, as these are the best practices for designing for visually impaired people12. Color contrast-ratio is the difference in brightness and color between the foreground and the background of a text or an image3. A high color contrast-ratio makes the text or the image more visible and readable for people with low vision or color blindness4. Screen-reading technology is a software that converts text and images on a screen into speech or braille output for people who are blind or have severe vision loss. A design that is compatible with screen-reading technology ensures that the content and functionality of the product are accessible and understandable for these users. References: Accessibility Standards - Salesforce Help, How to Configure Salesforce for your Blind and Low Vision Users - Salesforce Admins, Color Contrast Ratio - WebAIM, Color Contrast Checker - WebAIM, [Screen Readers - WebAIM], [Screen Reader User Survey #8 Results - WebAIM]

The correct answer is B. When designing for a visually impaired audience, it is important to optimize for color contrast-ratio and screen-reading technology. This will ensure that the design is accessible to those with visual impairments. Color contrast-ratio ensures that the text is easily readable, while screen-reading technology allows people with visual impairments to access the content on the website using a screen reader. Additionally, Salesforce has some great resources on designing for accessibility, such as their Accessibility Design Guide [1] and their Accessibility Best Practices [2].

[1] https://www.salesforce.com/content/dam/web/en_us/www/documents/salesforce-accessibility-design-guide.pdf [2]  https://developer.salesforce.com/docs/atlas.en-us.salesforce_accessibility_best_practices.meta/salesforce_accessibility_best_practices/accessibility_best_practices_intro.htm

 A style guide is a document that defines the visual identity and branding of a company, such as the logo, color palette, typography, iconography, imagery, and tone of voice. It helps ensure consistency and coherence across different platforms and channels, and communicates the company’s values and personality. When implementing a company’s brand on Salesforce, the style guide should be the source of truth for consistency, as it provides the guidelines and rules for applying the brand elements to the user interface. A style guide can also include a pattern library, which is a collection of reusable UI components and design patterns that follow the style guide. A design principle is a statement that expresses the core values and goals of a design process, and guides the decision making and evaluation of a design solution. The Salesforce Lightning Design System (SLDS) is a set of design guidelines and resources for creating consistent and beautiful user experiences on the Salesforce platform. It can be used as a reference and a foundation for customizing the UI according to the company’s style guide. References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : User Experience Designer Certification Prep: Module 7: Implement User Interfaces
• : What is a Style Guide and Why Every UX Designer Needs One
• : What is a Pattern Library and Why Should You Use One?

The Salesforce Lightning Design System (SLDS) is a comprehensive library of design patterns, components, and guidelines that enable developers and designers to create consistentuser interfaces on the Salesforce platform. It includes a comprehensive library of user interface components, guidelines for design consistency and accessibility, and detailed usage instructions. Using the Salesforce Lightning Design System ensures that all design elements and interactions on Salesforce use the same set of standards and patterns, resulting in a consistent and unified user experience. For more information, see the Salesforce Lightning Design System page (https://www.lightningdesignsystem.com/).

 The additional UX elements that should be reviewed to influence the brand experience are visual, content, and interaction design. These elements are essential for creating a consistent, engaging, and memorable user experience that reflects the company’s brand identity and values12.

Visual design refers to the use of colors, shapes, typography, images, icons, and other graphical elements to create a visual hierarchy, contrast, balance, and harmony on the page13. Visual design affects the user’s perception, emotion, and attention, and cancommunicate the brand’s personality, tone, and message13. For example, Cloud Kicks can use their logo, colorscheme, and font to create a recognizable and distinctive visual identity for their portal landing page4.

Content design refers to the creation, organization, and presentation of text, audio, video, and other media to convey the brand’s value proposition, story, and information to the user15. Content design affects the user’s understanding, interest, and trust, and can communicate the brand’s purpose, benefits, and voice15. For example, Cloud Kicks can use clear, concise, and compelling headlines, subheadings, and body text to highlight their products, services, and customer testimonials on their portal landing page.

Interaction design refers to the design of the user interface elements, such as buttons, links, menus, forms, and sliders, that enable the user to interact with the page and perform tasks1 . Interaction design affects the user’s behavior, satisfaction, and feedback, and can communicate the brand’s functionality, usability, and responsiveness1 . For example, Cloud Kicks can use intuitive, consistent, and accessible navigation, search, and filtering options to help the user find what they are looking for on their portal landing page.

By reviewing and improving these UX elements, Cloud Kicks can ensure that their portal landing page delivers a positive and coherent brand experience to their users, and that their brand identity is translated into the user experience.

References:

• The 5 Elements of User Experience Design
• How to Create a Brand Experience That Works With Your UX
• Visual Design Basics
• Use Branding Sets in Experience Builder
• Content Design: What It Is and Why It Matters
• [How to Write Effective Web Content for Your Experience Cloud Site]
• [Interaction Design Basics]
• [Designing User Interfaces for Experience Cloud Sites]

CK can assign learning content to employees using In-App Learning functionality in the following two ways:

• Trailmixes: Trailmixes are custom learning paths that can include modules, projects, trails, and even external links. CK can create and assign trailmixes to learners based on their roles, goals, or interests. Learners can access trailmixes from the Learning Home or the Guidance Center in Salesforce.
• Modules/Badges: Modules are units of instruction that cover specific topics and skills. Badges are earned by completing modules or projects. CK can assign modules or badges to learners to help them learn specific features or functionalities in Salesforce. Learners can access modules or badges from the Learning Home or the Guidance Center in Salesforce. References:
• : In-App Guidance in Lightning Experience
• : Learn MOAR in Spring '21 with In-App Learning
• : Enable Users to Learn in the Flow of Work

The best way to achieve the requirement of having a flag field on the case object that marks a case as sensitive and can be viewed by all users who have access to the case but only be edited by the assigned case assessor is to create a custom Lightning component. A custom Lightning component can use the Lightning Data Service to access the case record and its fields, and apply conditional rendering and editing logic based on the user’s role and the case assessor field. This way, the flag field can be displayed to all users who can view the case, but only be editable by the user who is the case assessor. This solution also follows the principle of designing for performance and scalability, which is one of the learning objectives for the Salesforce User Experience Designer certification. References: [Create Custom, Reusable Lightning Components], [Lightning Data Service Basics], [Design for Performance and Scalability]

https://trailhead.salesforce.com/en/content/learn/modules/lex_dev_lc_basics/lex_dev_lc_basics_intro : https://trailhead.salesforce.com/en/content/learn/modules/lightning_data_service/lightning_data_service_intro : https://trailhead.salesforce.com/en/content/learn/modules/ux-designer-certification-prep/design-for-performance-and-scalability

 A sales rep who owns an opportunity record will have read-only access to the related account record, if the organization-wide default for the Account object is private. This is because the opportunity owner is automatically granted read-only access to the account that the opportunity is associated with, regardless of who owns the account. This is called implicit sharing, and it is a built-in feature of Salesforce to ensure that users can access the data they need to do their work. However, the opportunity owner will not be able to create, edit, or delete the account record, unless they have other sharing mechanisms that grant them higher access, such as role hierarchy, sharing rules, manual sharing, or View All or Modify All permissions. References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs
• [Control Access to Records Unit | Salesforce Trailhead]1, Unit 2: Implicit Sharing
• [Work with Related Lists on Records in Lightning Experience - Salesforce]2, Related List Cards

A Salesforce Console application is designed to optimize the user experience for service representatives who work on multiple records and tasks at the same time. The console navigation features allow the user to access multiple records and related information in a single screen, without switching back and forth between tabs or windows. The features that are relevant to the designer recommendation are:

• More than one detail item can be open at a time. This allows the user to work on multiple records simultaneously and switch between them easily.
• Multiple subtabs can be beneath a single parent record. This allows the user to view and access related information, such as activities, emails, notes, and attachments, without leaving the parent record.
• A split list of records and individual record detail can be seen on the same screen. This allows the user to browse through a list of records, such as a queue or a report, and see the details of the selected record on the same screen.

The feature that is not relevant to the designer recommendation is:

• Service representatives with lower resolution monitors will have a better user experience. This is not true, because a Salesforce Console application requires a minimum screen resolution of 1024 x 768 pixels to display properly. Users with lower resolution monitors may experience scrolling issues or truncated information.

References: What Features Are Available in Lightning Console Apps?, Personalize the Navigation Menu for Lightning Console Apps, Navigate Around

Voice and tone are two aspects of writing that affect how the reader perceives and responds to the content. Voice is the consistent expression of the writer’s or the brand’s personality, values, and attitude. Voice reflects who the writer or the brand is, and what they stand for. Tone is the variation of the voice depending on the context, audience, and purpose of the content. Tone is the way in which the writer or the brand speaks to the reader, and how they convey their emotions, intentions, and expectations. Tone can change depending on the situation, the message, and the reader’s needs and feelings12.

For example, at Salesforce, we have a voice that is friendly, helpful, and empowering. We use simple, clear, and conversational language that shows our respect and appreciation for our customers, partners, and community. We also use humor, metaphors, and storytelling to make our content engaging and memorable. However, our tone can vary depending on thetype and goal of the content. For instance, when we write instructional content, such as Trailhead modules or user guides, our tone is more informative, instructive, and supportive. We use active voice, imperative mood, and positive feedback to guide the learner and encourage their progress. When we write promotional content, such as blog posts or social media posts, our tone is more persuasive, enthusiastic, and inspiring. We use rhetorical devices, emotional appeals, and calls to action to attract the reader and motivate them to take action34.

Therefore, a UX Designer would differentiate between voice and tone by understanding that voice reflects personality, and tone is the way in which one speaks. References: Voice and Tone - Lightning Design System, How To Create a Voice and Tone Program For Your Brand | Salesforce, Learn Why We Write the Way We Do Unit | Salesforce Trailhead, Write for Trailhead Unit | Salesforce Trailhead

A lookup relationship is a type of relationship that links two objects together, but the relationship is not required. This means that the child object can exist independently of the parent object. A lookup relationship can be either one-to-many or many-to-one, depending on the cardinality of the objects involved. For example, a contact can have a lookup relationship to an account, which means that a contact can belong to one account, but an account can have many contacts. Alternatively, a custom object can have a lookup relationship to a user, which means that a custom object can belong to many users, but a user can have only one custom object record. References: Trailhead: Data Modeling, Trailhead: Salesforce User Experience Designer Certification Prep, Salesforce Help: Define Lookup Relationships

The conceptual approach of desirable, feasible, and viable describes how to evaluate design solutions based on three criteria:

• Desirable: The solution meets the needs and wants of the users and stakeholders.
• Feasible: The solution can be implemented with the available resources and technology.
• Viable: The solution can generate value and sustain itself in the market and environment. By incorporating human-centered design, CK is aiming to create design solutions that are desirable for its Sales team and customers, feasible with the Salesforce platform and tools, and viable for its business goals and strategy. References:
• [1]: UX Designer Certification Prep: Design Thinking, Unit 3: Ideate
• [2]: UX Designer Certification Prep: Design Thinking, Unit 4: Prototype and Test

 T-shirt sizing is a methodology that can be used to roughly estimate the work required for each item in a sprint backlog. It involves assigning a size category (such as XS, S, M, L, XL) to each item based on its complexity, effort, and uncertainty. T-shirt sizing is a relative estimation technique that allows the team to compare items and prioritize them accordingly. It is also a quick and easy way to get a high-level overview of the scope of work without getting into too much detail. References:

• [UX Designer Certification Prep: Agile UX]
• [Agile Estimation Techniques: A True Estimation in an Agile Project]

 A diary study is a research methodology that involves asking participants to record their thoughts, feelings, behaviors, and activities over a period of time, usually in response to prompts or questions from the researcher1. A diary study is suitable for Cloud Kicks (CK) to conduct discovery phase research to understand more about the customers’ purchasing habits, as it will allow them to remotely observe customers’ buying patterns over the course of a 2-month period. A diary study will also provide rich and contextual data on the customers’ needs, preferences, motivations, and pain points, as well as the factors that influence their purchasing decisions1. References: Salesforce User Experience Designer Exam Guide, Diary Studies: How to Conduct from Start-to-Finish

Voice is the overall personality of the design, while tone is the way that personality is expressed. Voice represents the core characteristics of a design, such as the values, attitude, and emotions it conveys. Tone is how those characteristics are expressed in the design, suchas the language, visuals, and other elements. For example, a design with a friendly voice might be expressed through warm colors, friendly imagery, and casual language. Salesforce has some great resources on voice and tone such as [1] and [2].

[1] https://www.salesforce.com/blog/2017/11/voice-tone-brand-personality.html [2]  https://www.salesforce.com/blog/2018/10/voice-tone-brand-personality-ux.html

These are three of the four core principles of Web Content Accessibility Guidelines (WCAG), which provide a set of standards and best practices for making web content accessible to people with disabilities. The fourth principle is Perceivable, which means that the information and user interface components must be presented in ways that users can perceive. The principles are further divided into 13 guidelines and three levels of conformance (A, AA, and AAA). References:

• [Web Content Accessibility Guidelines (WCAG) Overview]
• [WCAG 2.1 at a Glance]

Salesforce's Learning Paths functionality is designed to personalize the learning experience within the Salesforce environment by guiding users through curated content relevant to their role and learning objectives. For employees, especially as part of an onboarding process, the following feature could be particularly useful:

• Trailhead modules:Trailhead is Salesforce's online learning platform that offers modules covering a wide range of topics related to Salesforce products, best practices, and general business skills. Assigning Trailhead modules through Learning Paths allows for structured and guided learning tailored to the employee's specific needs and roles, making it an ideal choice for onboarding.

While hands-on challenges (option B) and Superbadges (option C) are also part of the Trailhead ecosystem and valuable for learning, they are more suited for testing and validating skills after completing foundational modules, rather than as initial assigned learning content in an onboarding process.

References:Salesforce Trailhead provides extensive resources and guides on how to use Trailhead for learning and development, including setting up Learning Paths for employees. The Trailhead website offers detailed information on modules, hands-on challenges, and Superbadges, which can be leveraged to create a comprehensive onboarding experience.

The SLDS utility that provides the most flexible system to meet the requirements of designing a responsive page is Grid. Grid is a utility that allows you to create a layout using a series of rows and columns that house your content. Grid uses a 12-column structure that can be adjusted based on breakpoints, which are predefined screen sizes that trigger a change in the layout. Grid also supports nesting, alignment, ordering, and offsetting of the columns. By using Grid, you can create a responsive page that can adapt to different screen resolutions and devices12 References: [Grid - Lightning Design System], [Mastering Salesforce Lightning Design System Grids and Lightning Layouts]

https://www.lightningdesignsystem.com/utilities/grid/

https://developer.salesforce.com/blogs/developer-relations/2017/04/mastering-salesforce-lightning-design-system-grids-lightning-layouts

A heuristic evaluation is a usability inspection method that involves having evaluators examine a user interface and assess its compliance with established usability principles (or “heuristics”). These heuristics are guidelines or rules of thumb that help identify common usability problems. During a heuristic evaluation, evaluators inspect the interface and identify potential usability issues based on the heuristics. The evaluators then report their findings to the designers or developers, who can use this feedback to improve the interface. Heuristic evaluation is a cost-effective and efficient way to identify usability problems early in the design process. It can be done quickly and does not require large groups of participants. It is particularly useful for identifying problems that may not be detected through user testing or surveys1.

A heuristic evaluation is the most suitable method for determining the portal’s compliance with recognized standard usability principles, such as Nielsen’s 10 heuristics for user interface design2. These heuristics cover aspects such as visibility of system status, match between system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency of use, aesthetic and minimalist design, help users recognize, diagnose, and recover from errors, and help and documentation. By applying these heuristics to the portal, the UX team can identify and prioritize the usability problems that need to be fixed.

An intuitive review is a less formal and less rigorous method of usability inspection, where an evaluator relies on their own intuition and experience to judge the usability of an interface. An intuitive review does not follow a set of predefined heuristics or criteria, and it is more subjective and prone to bias. An intuitive review can be useful for getting a quick overview of the interface, but it is not as reliable or comprehensive as a heuristic evaluation3.

User testing is a usability evaluation method that involves observing and collecting data from actual or potential users as they perform tasks with the interface. User testing can provide valuable insights into how users interact with the interface, what difficulties they encounter, and what their preferences and expectations are. User testing can also measure the effectiveness, efficiency, and satisfaction of the interface. However, user testing is not the bestmethod for determining the compliance with standard usability principles, as it does not directly assess the interface against the heuristics. User testing is also more time-consuming, resource-intensive, and complex to conduct than heuristic evaluation4.

References: 1: A Comparison of User Testing and Heuristic Evaluation Methods for Identifying Website Usability Problems | SpringerLink 2: 10 Usability Heuristics for User Interface Design 3: Heuristic Evaluation of User Interfaces versus Usability Testing 4: Difference Between Heuristic Evaluation VS Usability Testing - Storyly

The best place on the SLDS website for the designer to find accessible HTML and CSS used to create components along with implementation guidelines is the Component Blueprints1. Component Blueprints are framework-agnostic, accessible HTML and CSS that provide the basic structure and style for Lightning components1. The designer can use the Component Blueprints to create custom Lightning Web Components that are consistent with the Lightning Design System. Design Tokens (B) are not the best place to find HTML and CSS, as they are variables that store design attributes, such as colors, fonts, and spacing2. Development Tools © are not the best place to find implementation guidelines, as they are tools and resources that help developers build and test Lightning components, such as VS Code extensions, LWC recipes, and Playground3. References:

• Component Blueprints | Salesforce Lightning Design System
• Design Tokens | Salesforce Lightning Design System
• Development Tools | Salesforce Lightning Design System

Q Tabs are a type of SLDS component that can be used to organize and consolidate content on a record page. Q Tabs are a variant of the Tabs component that are designed for use in the Lightning App Builder. Q Tabs allow users to switch between different views of related information within the same context. Q Tabs can also be nested to create subtabs within a tab. Q Tabs can help UX designers to create content-rich record pages that are easy to navigate and consume. Q Tabs can also help to reduce clutter and scrolling on a record page by grouping related content into tabs. Q Tabs can be customized with different icons, labels, and badges to indicate the type and status of the content in each tab. Q Tabs can also be configured to load content dynamically or on demand, which can improve the performance and user experience of the record page. References: Q Tabs Component Blueprint | Lightning Design System, Tabs Component Blueprint | Lightning Design System, Tabs | Lightning Web Components Developer Guide | Salesforce Developers

 The best way to apply branding to a Salesforce org using Lightning Experience is to create a custom theme in Themes and Branding. Themes and Branding is a feature that allows the administrator to customize the look and feel of Salesforce to match the branding of the organization. The administrator can add logos, default images, and colors to the theme. The administrator can also choose one of the built-in Salesforce themes, or create their own custom themes with just a few clicks. To create a custom theme, from Setup, enter Themes and Branding in the Quick Find box, then select Themes and Branding. Click New Theme and upload the logo, brand colors, and images that follow the company design guidelines. The administrator can also preview and activate the theme for the entire org 1. References: [Brand Your Org in Lightning Experience] (https://help.salesforce.com/s/articleView?id=sf.brand_your_org_in_lightning_experience.htm &language=en_US&type=5)

 The human-centered design approach is a problem-solving technique that puts real people at the center of the development process, enabling designers to create products and services that resonate and are tailored to the audience’s needs. The human-centered design approach typically involves four stages: clarify, ideate, develop, and implement1. The first stage, clarify, is dedicated to collecting data and observing the users to clarify the problem and how to solve it. Rather than developing products based on assumptions, designers conduct user research and assess user needs to determine what the users want. The clarify stage requires empathy—the capability of understanding another person’s experiences and emotions. Designers need to consider the users’ perspectives and ask questions to determine what products they’re currently using, why and how they’re using them, and the challenges they’re trying to solve2.

Therefore, the activity that should come first in the human-centered design process is observing the medical staff while they use their existing portal. This activity will help the UX designer to understand the context, the goals, the pain points, and the preferences of the medical staff,as well as to identify the opportunities for improvement and innovation. The other activities, such as estimating the cost, writing technical requirements, and designing a mockup, belong to the later stages of the human-centered design process, after the problem and the user needs have been clearly defined.

References: What is Human-Centered Design? — updated 2023 | IxDF and What Is Human-Centered Design? | HBS Online

The first activity inthe process when using a human-centered design approach to redesign a portal that medical staff use to report on patient demographics should be observing the medical staff while they use their existing portal. This is a critical step in the process, as ithelps to identify user needs, preferences, and behaviors so that the design of the new portal can be tailored to meet their specific needs.

Observing the medical staff while they use the portal will help to identify any existing problems and highlightareas where the portal can be improved. This can include issues with usability, functionality, and accessibility. Additionally, observing how the medical staff interact with the portal can help to identify any potential areas of improvement and uncover anyhidden requirements or user needs.

References: [1] https://www.salesforce.com/blog/2019/02/human-centered-design.html [2]  https://uxplanet.org/human-centered-design-process-3d3d3f9a50db [3] https://uxdesign.cc/human-centered-design-for-ux-designers-d4f0e741b9a9

The Path feature that should be used to add onboarding value for the sales representatives is the Key fields component. The Key fields component allows the admin to specify up to five fields that are important or required for each stage of the Path. The sales reps can see and edit these fields directly from the Path, without scrolling through the record page. This helps to guide the reps on what information they need to gather or update at each stage, and ensures data quality and completeness. The Key fields component can also be used to enforce validation rules or required fields, by preventing the reps from moving to the next stage until they fill out the necessary fields. References:

• : Set Up a Path
• : Considerations and Guidelines for Creating Paths
• : Optimize Sales Processes with Path in Salesforce

Einstein Bots and Automated Invitations are two Salesforce features that can boost engagement on Cloud Kicks’ website. Einstein Bots are chatbots that can provide automated and personalized responses to customers’ questions and requests on the website. They can also escalate complex cases to human agents, collect feedback, and provide recommendations. Einstein Bots can help Cloud Kicks to improve customer satisfaction, reduce wait times, and increase conversions 1. Automated Invitations are pop-up messages that invite website visitors to start a chat or video call with a service agent. They can be triggered by various criteria, such as time spent on the website, page visited, or customer profile. Automated Invitations can help Cloud Kicks to proactively engage with potential customers, offer assistance, and generate leads 2. References: [Einstein Bots Basics] (https://ascendix.com/blog/salesforce-sales-engagement/), [Set Up Automated Chat Invitations] (https://bing.com/search?q=Salesforce+features+to+boost+engagement)

The alternative (alt) text is a short block of text that describes the content and function of an image or other non-text element on a web page. The alt text is read aloud by screen readers and other assistive technologies to provide access to people who cannot see the image. The alt text also helps with search engine optimization and displays on the page if the image fails to load1.

When designing a custom component that includes a clickable icon in a Lookup field, the alt text should be concise, descriptive, and meaningful. The alt text should convey the purpose and action of the icon, rather than its appearance or format. Therefore, the best option for the alt text of the icon is “Search button”, as it describes what the icon does and how the user can interact with it. The other options are not suitable for the alt text, as they either include unnecessary words, such as “image of” or “photo of”, or omit important information, such as “button”. For example, the option “Image of a search button” is redundant, as the screen reader will already announce that the element is an image. The option “Search” is incomplete, as it does not indicate that the element is a button that can be clicked. The option “Image of amagnifying glass” is irrelevant, as it describes the appearance of the icon, rather than its function.

References: Everything you need to know to write effective alt text and Write helpful Alt Text to describe images

The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, resources, and tools that help create consistent, beautiful, and accessible user experiences across the Salesforce platform1. Component blueprints are one of the key resources that the SLDS provides. They are framework-agnostic, accessible HTML and CSS code snippets thatcan be used to create UI elements such as buttons, cards, menus, and more2. A UX Designer who is asked to design a new application built on Salesforce should become familiar with the SLDS component blueprints as their first step, because they can help them to3:

• Understand the structure, behavior, and appearance of the standard Salesforce components and how they can be customized or extended.
• Follow the SLDS design principles and best practices, such as clarity, efficiency, consistency, and beauty.
• Ensure that the application is responsive, adaptive, and compatible with different devices and screen sizes.
• Leverage the SLDS design tokens, icons, and utilities to create a coherent and scalable visual language.
• Reduce the development time and effort by reusing the existing code and avoiding duplication.

The other options are not the best first steps for a UX Designer who is asked to design a new application built on Salesforce. Creating branding sets for each audience using Experience Builder is a later step that involves applying the visual identity and style of the application todifferent user segments and channels4. Finding and reviewing relevant AppExchange packages is a research step that can help to identify existing solutions or features that can be integrated or adapted to the application5. Designing a series of custom web components for the app is a development step that can be done after defining the requirements, wireframes, and prototypes of the application.

References:

• Lightning Design System, Lightning Design System Create the World’s Best Enterprise App Experiences Design System Fundamentals Component Blueprints Ready-to-use HTML and CSS UI elements provide the foundation for Salesforce experience development Go to Blueprints Tokens Visual design values and attributes that ensure branding and UI consistency at scale View Tokens Design Guidelines Design principles and best practices that guide beautiful, consistent, user-friendly product experiences Read Guidelines Tools New! Easy-to-use tools help all Trailblazers optimize workflows and bring Salesforce ideas to life Get Tools
• Blueprint Overview - Lightning Design System, Blueprint Overview - Lightning Design System What’s New Getting Started Platforms Design Guidelines Kinetics Accessibility Component Blueprints Overview Accordion Activity Timeline Alert App Launcher Avatar Avatar Group Badges Brand Band Breadcrumbs Builder Header Button Icons Cards Chat Docked Utility Bar Dueling Picklist Dynamic Icons Dynamic Menu Expandable Section Feeds File Selector Files Form Element Global Header Global Navigation Icons Illustration Input List Builder Lookups Map Menus Notifications Page Headers Panels Path Picklist Pills Progress Indicator Prompt Radio Button Group Rich Text Editor Scoped Notifications Scoped Tabs Select Spinners Tabs Textarea Tiles Timepicker Toast Tooltips Tree Grid Trees Trial Bar Vertical Navigation Vertical Tabs Visual Picker Welcome Mat Utilities Design Tokens Icons Tools Resources Blueprint Overview Component blueprints are framework agnostic, accessible HTML and CSS used to create components in conjunction with our implementation guidelines. For more details, check out the glossary on the FAQ page. Show Filters Showing 85 blueprints, 183 variants. Accordion Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nActivity Timeline Responsive Adaptive Styling Hooks Prototype Base \n \n Alert Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nApp Launcher Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nAvatar Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nInitials Checkmark \nCheckmark \nAvatar Group Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nGrouped Checkmark \n \nBadges Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nBrand Band Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nBreadcrumbs Lightning Component Responsive Adaptive Styling Hooks Prototype Base \n Checkmark \nBuilder Header Responsive Adaptive Styling Hooks Prototype Base \n \n Toolbar \n \n Button Groups Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nList Checkmark \n \nRow Checkmark \n \nButton Icons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nBordered Filled Container Checkmark \n \nBordered Inverse Checkmark \n \nBordered Transparent Container Checkmark \n \nBrand Checkmark \n \nInverse Checkmark \n \nStateful Checkmark \n \nTransparent Container Checkmark \n \nButtons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nDual Stateful Checkmark \nCheckmark \nStateful Checkmark \nCheckmark \nWith Icon Checkmark \nCheckmark \nCards Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nEinstein Checkmark \nCheckmark \nWrapper Checkmark \nCheckmark \nCarousel Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nChat Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nPast Checkmark \n \nCheckbox Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nForm Element Checkmark \nCheckmark \nCheckbox Button Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nCheckbox Button Group Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nCheckbox Toggle
• UX Designer Certification Prep: Design System Fundamentals, UX Designer Certification Prep: Design System Fundamentals Learn how to use the Salesforce Lightning Design System (SLDS) to create consistent, beautiful, and accessible user experiences across the Salesforce platform. Add to Favorites Add to Trailmix tags ~1 hr 30 mins +500 points Module Design System Fundamentals Learn about the Salesforce Lightning Design System (SLDS) and how it can help you create consistent, beautiful, and accessible user experiences across the Salesforce platform. 4 hrs 15 mins +800 points Project Build a Bear-Tracking App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build a bear-tracking app. 2 hrs 15 mins +500 points Project Build a Conference Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build a conference management app. 2 hrs 15 mins +500 points Project Build a Discount Calculator with Visualforce Use Visualforce and the Salesforce Lightning Design System to build a discount calculator. 2 hrs 15 mins +500 points Project Build a Survey App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build a survey app. 2 hrs 15 mins +500 points Project Build a Travel Approval App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build a travel approval app. 2 hrs 15 mins +500 points Project Build a Volunteer Management Appwith Lightning App Builder Use Lightning App Builder and the Salesforce Lightning Design System to build a volunteer management app. 2 hrs 15 mins +500 points Project Build an Expense Tracker App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build an expense tracker app. 2 hrs 15 mins +500 points Project Build an Inventory Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build an inventory management app. 2 hrs 15 mins +500 points Project Build an Order Management App with Visualforce Use Visualforce and the Salesforce Lightning Design System to build an order management app. 2 hrs 15 mins +500 points Project Build an RSVP Management App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build an RSVP management app. 2 hrs 15 mins +500 points Project Build an SMS Notification App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build an SMS notification app. 2 hrs 15 mins +500 points Project Build an
• Branding Sets Unit | Salesforce Trailhead, Branding Sets Unit | Salesforce Trailhead Branding Sets Learn how to use branding sets to apply different styles to your digital experiences. Add to Favorites Add to Trailmix tags ~20 mins Incomplete Branding Sets Customize the look and feel of your digital experiences with branding sets. 15 mins +200 points Quiz +200 points Get Started with Branding Sets Learn how to create and apply branding sets to your digital experiences. 5 mins +200 points Quiz +200 points
• AppExchange Basics Unit | Salesforce Trailhead, AppExchange Basics Unit | Salesforce Trailhead AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. Add to Favorites Add to Trailmix tags ~25 mins Incomplete AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. 20 mins +200 points Quiz +200 points Get Started with AppExchange Learn what AppExchange is and how it can help you extend Salesforce functionality. 5 mins +200 points Quiz +200 points

A heuristic evaluation is a method of inspecting the usability of an interface by comparing it to a set of general principles or heuristics. It can help identify potential problems and areas for improvement in the design. A heuristic evaluation is usually done before creating any prototypes, as it can provide insights and guidance for the design process. A low-fidelity prototype is a rough sketch or mockup of an interface that can be used to test and validate design ideas with users. It is usually created after conducting some research and analysis of the user needs and goals. A design template is a pre-made layout or structure that can be used to create an interface. It can help save time and ensure consistency in the design, but it may not suit the specific needs and preferences of the users or the business. A design template is usually applied after defining the content and functionality of the interface. References:

• [Heuristic Evaluation]: This is a Trailhead module that explains what a heuristic evaluation is, how to conduct one, and how to use the results to improve the design of an interface.
• [Low-Fidelity Prototyping]: This is a Trailhead module that covers the benefits and best practices of creating and testing low-fidelity prototypes with users.
• [Design Templates]: This is a Trailhead module that introduces the concept of design templates and how to use them in Experience Cloud.

Customer interviews are a qualitative research method that allows the UX Designer to understand the needs, goals, pain points, and behaviors of the target users. To conduct effective customer interviews, the UX Designer should follow some best practices, such as:

• Engage in a friendly and informal way: The UX Designer should try to establish rapport and trust with the interviewee, and make them feel comfortable and relaxed. This can help elicit honest and candid responses, and encourage the interviewee to share more details and stories. The UX Designer should use a conversational tone, smile, and show interest and empathy12
• Ask open-ended questions: The UX Designer should avoid asking yes/no questions, or questions that lead or suggest a specific answer. Instead, the UX Designer should ask open-ended questions that allow the interviewee to express their thoughts and feelings in their own words. The UX Designer should also probe deeper by asking follow-up questions, such as “why?”, “how?”, or “can you tell me more about that?” 12
• Listen actively and attentively: The UX Designer should focus on listening to the interviewee, and avoid interrupting, judging, or correcting them. The UX Designer should also use verbal and non-verbal cues, such as nodding, eye contact, and paraphrasing, to show that they are paying attention and understanding the interviewee. The UX Designer should also take notes or record the interview, with the interviewee’s permission, for later analysis12
• Ignore vague or general answers: This is not a best practice, because vague or general answers can indicate that the interviewee is not comfortable, engaged, or clear about the question. The UX Designer should try to clarify the question, or ask more specific or concrete questions, to elicit more meaningful and relevant responses12
• Analyze findings in the moment: This is not a best practice, because analyzing findings in the moment can distract the UX Designer from listening to the interviewee, and bias their interpretation of the data. The UX Designer should wait until the interview is over, and review thenotes or recordings, before analyzing the findings and identifying patterns, insights, and opportunities12

References:

• Customer Interviews: The Ultimate Guide - User Interviews
• How to Conduct User Interviews - Interaction Design Foundation

A UX designer who has been asked to improve Salesforce adoption among sales representatives at Cloud Kicks should conduct a workshop with stakeholders to align on the current state and build consensus as the next step after finding out that there is no clear and consistent sales process. This is because:

• A clear and consistent sales process is essential for defining the user needs, goals, and pain points, as well as the business requirements, objectives, and metrics. Without a clear and consistent sales process, the UX designer cannot design a user-centric and value-driven solution that meets the expectations and needs of both the users and the stakeholders.
• A workshop with stakeholders can help the UX designer to understand the existing sales process, identify the gaps, challenges, and opportunities, and facilitate a collaborative and participatory approach to define the desired future state and agree on the best practices and standards for the sales process. A workshop can also help to establish trust, rapport, and buy-in among the stakeholders, and ensure that they are aligned and committed to the project vision and goals.
• A workshop with stakeholders can also help the UX designer to gather feedback, input, and validation from the key decision-makers and influencers, and incorporate them into the design process. A workshop can also help to communicate the value proposition and benefits of Salesforce adoption, and address any concerns, questions, or resistance that the stakeholders may have.

References:

• Salesforce Adoption: Common Issues & 6 Best Practices - Itransition
• What is Salesforce Adoption? 15+ Salesforce Adoption Strategies | Salesforce Ben
• Improving Salesforce User Adoption: Strategies & Best Practices - Cynoteck
• 17 Best Salesforce Adoption Strategies for Success (2023) - Whatfix

 A prioritization matrix is a method that helps UX designers to inform user stories based on user value and development effort. A prioritization matrix is a table that compares different user stories or features based on two criteria: user value and development effort. User value is the benefit or satisfaction that the user will get from using the feature. Development effort is the time, cost, and complexity involved in building the feature. By plotting user stories or features on a prioritization matrix, UX designers can identify which ones are high-value and low-effort, which ones are high-value and high-effort, which ones are low-value and low-effort, and which ones are low-value and high-effort. This helps UX designers to prioritize the user stories or features that will deliver the most value to the user with the least amount of effort, and to deprioritize or eliminate the ones that will deliver the leastvalue to the user with the most amount of effort. A prioritization matrix can also help UX designers to communicate and align with stakeholders and developers on the scope and feasibility of the project. References: Prioritize User Stories and Features Unit | Salesforce Trailhead, How to PrioritizeUser Stories (and Build the Right Features), Salesforce User Experience (UX) Designer Certification Guide & Tips

Updating the homepage with access to commonly used reports is the best way to make sure the user can quickly accessthe reports they need. This could include making the global search bar bigger on every page, adding the daily task component to the homepage, or creating a mind board to communicate the visual style of the UI. Additionally, Salesforce has some great resources on designing for search, such as their Search Design Guide [1] and their Search Best Practices [2].

[1] https://www.salesforce.com/content/dam/web/en_us/www/documents/salesforce-search-design-guide.pdf [2]  https://developer.salesforce.com/docs/atlas.en-us.salesforce_search_best_practices.meta/salesforce_search_best_practices/search_best_practices_intro.htm

The principle that would represent Cloud Kicks’ company strategy is prioritizing engagement over number of impressions. This principle is based on the intention mindset of Relationship Design, which means engaging with clear purpose and focusing on the quality of interactions rather than the quantity1. Reframing products in terms of outputs over outcomes (A) is not a Relationship Design principle, as it does not consider the value or impact of the products for the customers. Highlighting product benefits over uncovering customer needs © is also not aRelationship Design principle, as it does not show empathy or understanding of the customers’ problems or goals. References:

• Embrace the Relationship Design Mindsets Unit | Salesforce Trailhead

The Salesforce Lightning Design System (SLDS) is a set of design guidelines and resources for creating consistent and beautiful user experiences on the Salesforce platform. It provides UI components, icons, fonts, colors, and more that follow the best practices and accessibility standards of Salesforce. One of the features of SLDS is the ability to create custom themes that reflect the brand identity and personality of a company or an app. Custom themes can be implemented using design tokens, which are variables that store the values of the UI elements, such as colors, sizes, spacing, fonts, etc. Design tokens can be overridden or customized to change the appearance of the UI components without modifying the CSS or HTML code. To implement the company colors in all UI components, such as buttons and icons, using a custom theme, the UX designer should use the design tokens prefixed with “brand”, such as $brand-primary, $brand-secondary, $brand-accessible, etc. These design tokens control the color scheme of the UI components and can be assigned the values of the company colors. For example, to change the color of the primary button to the company’s blue color, the UX designer can use the following design token:

$brand-primary: #0070d2;

References:

• : User Experience Designer Certification Prep: Module 7: Implement User Interfaces
• : Salesforce Lightning Design System: Customization
• : Salesforce Lightning Design System: Design Tokens

The Path’s Guidance for Success sections can include the following two elements:

• Images and Links: Images and links can be used to provide visual cues and additional resources for the sales representatives. For example, an image of a checklist or a link to a best practice document can help the reps complete the required tasks at each stage. Images and links can be added using the rich text editor in the Path Settings page.
• Rich Text: Rich text can be used to provide text-based guidance, such as tips, reminders, instructions, or motivational messages. For example, a rich text guidance can tell the reps what information they need to gather from the customer or what actions they need to take to move the opportunity forward. Rich text can be formatted using the rich text editor in the Path Settings page. References:
• : Set Up a Path
• : Considerations and Guidelines for Creating Paths
• : Optimize Sales Processes with Path in Salesforce

The two elements that can be used in the Path's Guidance for Success section are Images and Links and Rich Text. Images and Links can be used to provide visual elements to the Guidance for Success section, while Rich Text can be used to provide text-based explanations and instructions. In addition, a Progress Indicator can be used to show the user's progress through the Path.

Images and Links can be used to provide visual elements to the Guidance for Success section. For example, if the user needs to read an article, a link to the article can be included, as well as an image of the article cover. Similarly, if the user needs to view a video, a link to the video and an image of the video can be included.

Rich Text can be used to provide text-based explanations and instructions. This can include explanations of what the user should be doing at each stage of the Path, as well as any other helpful information.

Finally, a Progress Indicator can be used to show the user's progress through the Path. This can help the user understand where they are in the Path and how far they have left to go.

References: [1] https://help.salesforce.com/articleView?id=path_guidance.htm &type=5 [2] https://help.salesforce.com/articleView?id=path_customize_guidance_success.htm &type=5 [3] https://help.salesforce.com/articleView?id=path_use_guidance_success.htm &type=5

Dynamic Forms is a feature that allows users to customize the form fields and sections displayed to users on a page layout. Dynamic Forms can be used to create user-centric, intuitive,and dynamic record creation screens for custom objects, such as Appointment. When creating a record using Dynamic Forms, the UX designer should consider the following two aspects12:

• The use of tabs when creating the record is not allowed. Dynamic Forms does not support the use of tabs within the form, as tabs are not compatible with the record creation process. Tabs are only available for viewing or editing existing records, not for creating new ones. Therefore, the UX designer cannot use tabs to separate the fields for different record types or software options on the record creation screen.
• Fields can be organized into sections. Dynamic Forms allows the UX designer to group fields into sections, and place them anywhere on the page layout. Sections can have labels, collapsible headers, and visibility rules. The UX designer can use sections to create a logical and clear structure for the form, and to show or hide fields based on user input, data, or profile. For example, the UX designer can create a section for each software option, and use visibility rules to display only the relevant section based on the user’s selection.

The following two aspects are not true when creating a record using Dynamic Forms, and should be disregarded:

• The form will not be available on mobile devices. Dynamic Forms is compatible with mobile devices, and the UX designer can preview and test the form on different device sizes and orientations. The form will automatically adjust to the screen size and layout of the mobile device, and provide a responsive and consistent user experience3.
• All software option sections of the form will always be visible. Dynamic Forms allows the UX designer to use visibility rules to control the visibility of fields and sections on the form. Visibility rules can be based on user input, data, or profile. The UX designer can use visibility rules to show or hide software option sections based on the user’s selection of the record type or the software option. This can reduce the clutter and complexity of the form, and provide a personalized and flexible user experience4. References: Get Started with Dynamic Forms Unit | Salesforce Trailhead, Salesforce Dynamic Forms: Overview & Deep DiveTutorial, Dynamic Forms and Actions FAQ | Salesforce Help, Create Dynamic Forms with Visibility Rules | Salesforce Trailhead

The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user’s mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text thatappear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System] References: [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

 A deal closer is someone who is responsible for closing sales deals with prospects and customers. They need to update existing prospect and customer records to keep track of their interactions and status. They also need to log activities such as calls, emails, and notes to document their communication and follow-ups. They also need to review and work through their list of leads or opportunities to prioritize their tasks and identify the best prospects to focus on. These activities are essential for a deal closer to manage their pipeline and achieve their sales goals. Creating cases from issues and customizing and administering Salesforce are not activities that a deal closer would do each day. These are more likely to be done by a customer service agent or a Salesforce administrator, respectively. References: [Salesforce Certified User Experience Designer Exam Guide], [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas]

Inclusive design is a methodology aimed at creating products that are accessible to as many people as possible, regardless of their abilities or circumstances. The benefit of inclusive design is that it focuses on reducing friction for users in achieving their goals by:

• Considering a wide range of human diversity, including ability, language, culture, gender, age, and other forms of human difference.
• Identifying and eliminating unnecessary barriers that might prevent people from effectively using a product or service.
• Ensuring that products and services can be used by everyone, to the greatest extent possible, without the need for adaptation.

Inclusive design does not mean tailoring a solution to one type of user (B) or creating a lowest-common-denominator design that meets only the most basic needs of all users (C). Instead, it seeks to understand and address the needs of a broad audience to create more usable and accessible experiences for everyone.

References:The Interaction Design Foundation provides extensive resources on inclusive design, its principles, and how to apply them in the design process. These resources offer valuable insights into creating designs that are accessible and beneficial to a wide audience.

 Service design is a practice that aims to design and deliver holistic, human-centered, and value-driven solutions that consider the needs and expectations of not only the individual users, but also the stakeholders, the employees, the partners, and the society involved in the service. Service design focuses on more than just the user interface or the user experience, but also on the processes, systems, interactions, touchpoints, and channels that enable the service to be delivered and consumed. Service design can help create engaging, connected, and social value-driven solutions that improve the quality, efficiency, and sustainability of the service . References:

• : User Experience Designer Certification Prep: Module 1: Understand User Experience Design
• : What is Service Design?

Service Design is a design practice that focuses on providing better experiences to users by understanding the context of their needs and how they interact with systems, services, and products. Service Design goes beyond User Experience Design by focusing on more than just individual people, and instead considers the entire ecosystem, including connected and social value-driven solutions. Salesforce provides more information on Service Design here: https://www.salesforce.com/resources/service-design/.

The best option for guiding sales users through a new process using floating or docked prompts is to use the Walkthrough App from AppExchange. This app allows admins to create and manage in-app guidance walkthroughs using clicks, not code. Walkthroughs are interactive tutorials that guide users through a series of steps on a Lightning page. Users can see the prompts, click the action buttons, and follow the instructions to complete the process. Admins can also track the engagement and completion of the walkthroughs using reports and dashboards. The Walkthrough App is compatible with the standard in-app guidance feature, and does not require a subscription to myTrailhead1 .

The other options are not suitable for this scenario because:

• In-App Guidance Prompts using myTrailhead: This option requires a subscription to myTrailhead, which is a customizable learning platform that allows admins to create their own content and branding. In-app guidance prompts are one of the features of myTrailhead, but they are not the same as walkthroughs. Prompts are single-step messages that appear on a Lightning page, while walkthroughs are multi-step tutorials that guide users through a process. Prompts can be used to provide tips, announcements, or links, but they cannot show users how to perform a task234.
• Custom build using Salesforce Flow: This option requires coding and development skills, which may not be available or feasible for the admin team. Salesforce Flow is a tool that allows admins to automate processes and tasks using clicks or code. Flows can be triggered by various events, such as buttons, actions, schedules, or record changes. Flows can also display screens to users, which can contain fields, text, images, or components. However, screens are not the same as prompts or walkthroughs. Screens are part of a flow logic, and they require user input to proceed to the next step. Screens cannot be customized to appear as floating or docked prompts, and they cannot guide users through a Lightning page56.
• Basic In-App Guidance Prompts: This option does not require a subscription to myTrailhead, but it also does not provide the functionality of walkthroughs. Basic in-app guidance prompts are the same as the ones mentioned in the first option, but without the customization and branding of myTrailhead. Basic prompts can be created and managed using clicks, not code, and they can be filtered by profiles and permissions. However, basic promptsare still single-step messages that appear on a Lightning page, and they cannot show users how to perform a task23.

References:

• : [In-App Guidance Walkthroughs: Getting Started for Sales Users]
• : [In-App Guidance Dashboard: Walkthrough Engagement]
• : [In-App Guidance in Lightning Experience]
• : [Salesforce Flow | Salesforce Developer Center]
• : [Salesforce Flow Workflow Automation Tools - Salesforce.com]
• : [The Complete Guide to Salesforce Flow | Salesforce Ben]
• : [Trailhead | The fun way to learn]
• : [Editions & Pricing - myTrailhead- Salesforce]
• : [Salesforce introduces myTrailhead, a personal learning platform …]
• : [Trailhead | The fun way to learn Salesforce]
• : [Getting Started with myTrailhead - Salesforce]

To optimize the relationship between two objects in Salesforce, such as Container and Container Bids, where there is a need for a tight relationship and cascading delete functionality, a Master-Detail relationship is most suitable. This type of relationship has the following characteristics:

• Cascading Delete:When a record in the master (or parent) object is deleted, all related detail (or child) records are automatically deleted. This ensures data integrity and aligns with the requirement that Container Bids should be deleted when their associated Container is deleted.
• Tight Coupling:A Master-Detail relationship creates a strong linkage between the two objects, where the detail (child) record's existence is dependent on the master (parent) record. This is appropriate for scenarios where the child record should not exist without its parent.

Options B (Hierarchical Lookup) and C (Many-to-one Lookup) do not provide the same level of dependency and cascading delete functionality inherent in a Master-Detail relationship.

References:Salesforce's official documentation provides extensive information on different types of relationships between objects, including Master-Detail relationships. The Salesforce Developer Documentation is a valuable resource for understanding how to set up and use these relationships to ensure data integrity and optimize application design.

Dynamic Actions are a feature that allows the UX Designer to customize the actions that appear on the Highlights panel of a Lightning record page based on criteria such as record status, user profile, or field value. This way, the UX Designer can declutter the Highlights panel and show only the relevant actions for each record. Dynamic Actions can be configured in the Lightning App Builder instead of the page layout editor, which gives more flexibility and control to the UX Designer. References:

• Salesforce Dynamic Actions – Overview & Deep Dive Tutorial
• Create Dynamic Actions in Lightning App Builder - Salesforce
• Add Visibility Rules for Dynamic Pages - Trailhead

The UI configuration that should be used to further individualize each featured topic is to select and upload images that represent each featured topic. This option allows the UX Designer to customize the appearance of the Featured Topic component and make it more visually appealing and engaging for the users. The images can help to convey the meaning and relevance of each topic and attract the users’ attention. The images can also create a consistent and branded look for the Experience Cloud site.

References:

• : Featured Topic Component
• : Customize the Featured Topic Component

This allows users to easily distinguish between different topics and quickly scan for relevant topics. Salesforce documentation on the Featured Topics component states that “You can add a description for each featured topic, which appears in the user interface below the topic label” [1].

[1] https://help.salesforce.com/articleView?id=knowledge_articles_sites_featured_topic.htm &type=5

The SLDS BEM naming convention consists of three parts: block, element, and modifier. A block is a standalone component that can be reused across projects, such as a button, a card, or a modal. An element is a part of a block that has no standalone meaning, such as a label, an icon, or a header. A modifier is a flag that changes the appearance or behavior of a block or an element, such as size, color, or state. The modifier is separated from the block or element by two hyphens (–), and can have a value separated by a single hyphen (-), such as .slds-button–brand or .slds-button–neutral. The class .slds–size-l-of-2 does not follow thisconvention because it has no block or element name before the modifier. It should be something like .slds-grid–size-l-of-2 or .slds-col–size-l-of-2. References:

• [1]: Salesforce Lightning Design System - Introduction
• [2]: Salesforce Lightning Design System - Naming Con

According to the Web Content Accessibility Guidelines (WCAG) 2.1, the minimum color contrast ratio for normal text is4.5:11. This means that the difference in brightness (luminance) between the text color and the background color should be at least 4.5 times.This ensures that the text is readable by people with moderately low vision, color deficiencies, or contrast sensitivity1. The contrast ratio can be calculated using the formula:

L2​+0.05L1​+0.05​

whereL1​is the relative luminance of the lighter color andL2​is the relative luminance of the darker color2.The relative luminance is a value between 0 and 1, where 0 is black and 1 is white2.The contrast ratio can range from 1:1 (white on white) to 21:1 (black on white)2.

The contrast ratio requirement for normal text is lower for larger text or bold text, as they are easier to read at lower contrast.For large text (18 point or 14 point bold), the minimum contrast ratio is3:11.For graphics and user interface components, such as form input borders, the minimum contrast ratio is also3:13.For level AAA conformance, the minimum contrast ratio for normal text is7:1and for large text is4.5:11.

To evaluate the color contrast ratio of a site, there are various tools available, such as theContrast Checkeror theContrast Ratiotool. These tools allow users to enter the text color and the background color and see the contrast ratio and whether it meets the WCAG guidelines. They also provide suggestions for improving the contrast ratio if needed.

References:

• Understanding Success Criterion 1.4.3: Contrast (Minimum)
• Contrast Ratio - WCAG Color Contrast Checker
• WebAIM: Contrast Checker
• WCAG: Accessible colour and contrast ratios
• Contrast ratio - WCAG WG

An App Builder styling property is a feature that allows a Lightning web component to expose CSS properties that can be set by an administrator in the Lightning App Builder. This way, theadministrator can customize the look and feel of the component depending on the context and use case. For example, a component can have a styling property for the background color, the font size, or the border radius. The administrator can then change these values in the App Builder without modifying the code of the component. References:

• [Create App Builder Styling Properties]

The best approach to enable partners to quickly browse and see their opportunities segmented by key attributes is to configure a pre-filtered opportunity list view for each key attribute with the partner group. This way, the partners can easily access the list views that show only the opportunities that match the criteria, such as closing within 2 weeks or valued at more than $100,000. Creating a custom Lightning Web Component using a data table for each key attribute (A) might be too complex and time-consuming, and it might not be compatible with the Experience Builder. Allowing each user to create a filter for each key attribute and link to the opportunities list view (B) might be too tedious and inconsistent, and it might not provide a quick and easy way to browse the opportunities. Configuring a pre-filtered opportunity list view for each key attribute with the partner group © is a simple and effective solution that leverages the existing functionality of the Experience Builder and the list view component12. References:

• List View Component | Salesforce Experience Cloud
• Create and Edit List Views | Salesforce Help

 The Salesforce Lightning Design System (SLDS) is a collection of design resources that help create consistent and beautiful user interfaces across various platforms. The SLDS includes base components, tokens, design patterns, icons, fonts, and more, that follow the design principles and best practices of Lightning Experience. The SLDS can be used on the following three platforms:

• Visualforce: Visualforce is a framework that allows developers to create custom user interfaces for web and mobile applications on the Salesforce platform. Visualforce pages can leverage the SLDS styles to match the look and feel of Lightning Experience, without writing any CSS code. By adding the attribute lightningStylesheets="true" to the  tag, Visualforce pages can automatically transform the standard Visualforce components into their SLDS equivalents12.
• Heroku: Heroku is a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. Heroku applications can leverage the SLDS resources, such as the base components, the tokens, and the design patterns, to create web applications that have a consistent Lightning Experience look and feel. Heroku applications can also use the Lightning Out feature to embed Lightning components into their pages, and use the Lightning Web Components framework to create reusable UI elements34.
• Azure: Azure is a cloud platform that offers various services and tools for building, deploying, and managing applications. Azure applications can leverage the SLDS resources, such as the base components, the tokens, and the design patterns, to create web applications that have a consistent Lightning Experience look and feel. Azure applications can also use the Lightning Out feature to embed Lightning components into their pages, and use the Lightning Web Components framework to create reusable UI elements56.

References:

• [Lightning Stylesheets for Visualforce | Salesforce Trailhead]1
• [Lightning Stylesheets for Visualforce | Salesforce Developers]2
• [Build Apps with Lightning Design System | Salesforce Trailhead]3
• [Lightning Web Components | Salesforce Developers]4
• [Salesforce Lightning Design System for Azure Web Apps | Microsoft Azure]5
• [Lightning Web Components and Azure | Salesforce Developers]6

A field-level error message is a message that appears next to a specific field when the user enters invalid data or omits required data. It helps the user to correct the error and proceed with the action. A field-level error message is more user-friendly than a validation rule, which displays a generic message at the top of the page and prevents the user from saving the record. A field-level error message can also provide guidance on the correct format and number of digits for the phone number field. Marking the field as required would not ensure that the user enters the phone number in the correct format and with the correct number of digits. Setting a prompt to display on the page using In-App Guidance would not prevent the user from entering invalid data or omitting required data. References: [Field-Level Error Messages], [Validation Rules], [In-App Guidance]

 Dynamic Forms is a feature that allows users to customize the layout of a record detail page by placing fields and sections anywhere on the page, and applying visibility rules to show or hide them based on certain criteria. Dynamic Forms can help service agents to create user-centric, intuitive, and dynamic layouts that display only the relevant fields and sections for the reservation process. Dynamic Forms can also improve page load times and reduce the need for multiple page layouts and record types. Dynamic Forms is currently available for custom objects and some standard objects in Lightning Experience12. References:

• Dynamic Forms
• Get Started with Dynamic Forms

 Shadow DOM is a web standard that encapsulates the internal document object model (DOM) structure of a web component. It isolates the component’s markup and styles from the rest of the page, and prevents the component from being affected by or affecting the global DOM. When designing or developing the stylesheets for a parent-child LWC structure, the following impacts of the shadow DOM should be considered:

• The CSS styles defined in the parent list component are not shared with the child items. This is because the shadow DOM creates a boundary between the parent and the child components, and the styles defined in the parent component do not cascade down to the child components. This means that each component needs to define its own styles, or import them from a common source. This also means that the parent component cannot directly style the child components, or vice versa12.
• Any custom styles shared between the list and child items should be imported from a shared CSS file. This is a recommended practice to avoid duplicating the same styles in multiple components, and to maintain consistency and reusability. A shared CSS file can be created as a static resource, and imported into the components using the loadStyle() method from the platformResourceLoader module. Alternatively, a shared CSS file can be created as a LWC component, and imported into the components using the @import directive134.

References:

• : [Shadow DOM | Lightning Web Components Developer Guide | Salesforce Developers]
• : [Light DOM | Lightning Web Components Developer Guide | Salesforce Developers]
• : [Understanding Shadow DOM and Template in LWC – SFDC Lightning]
• : [Shadow DOM, CSS and Styling Hooks in LWC what you need to know]
• : [How to Share CSS Between Lightning Web Components | Salesforce Developers Blog]
• : [How to Use a Shared CSS File in a Lightning Web Component | Salesforce Developers Blog]

 The best way for the designer to help mitigate pushback from developers is to work together on setting up UX Indicators. UX Indicators are a set of metrics that measure the user experience of a product or feature, such as usability, satisfaction, engagement, and adoption1. By working together on setting up UX Indicators, the designer and the developers can align on the goals and expectations of the design changes, and use data and evidence to evaluate their impact. This can help to reduce the subjective opinions and assumptions that might cause pushback, and foster a collaborative and user-centered culture. Sharing research notes from previous projects with them (A) might not be very helpful, as the research might not be relevant or applicable to the current project, and the developers might not trust or understand the research methods or findings. Getting buy-in from the development lead first and let them persuade others (B) might not be very effective, as it might create a top-down or hierarchical approach that does not involve the developers in the design process, and might make them feel excluded or ignored. References:

• UX Designer Certification Prep: UX Indicators

The discovery phase is a crucial stage in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1. The discovery phase typically involves various research methods, such as interviews, surveys, observations, and analytics, to gather data and insights about the users and the context of use2. The outputs of the discovery phase are artifacts that synthesize and communicate the findings and insights from the research. Some of the practices that should be considered for planning out the strategy for an upcoming discovery phase are:

• Gather insight from end users: One of the main objectives of the discovery phase is to empathize with the end users and understand their goals, motivations, pain points, behaviors, and preferences. This can be done by conducting user research, such as interviews, surveys, focus groups, or usability tests, to collect qualitative and quantitative data from the target audience3. Gathering insight from end users helps to validate the assumptions and hypotheses about the problem and the solution, as well as to identify the user requirements and expectations for the design.
• Establish the research plan and timeline: Before conducting any user research, it is important to establish a clear and realistic research plan and timeline. The research plan should define the research objectives, questions, methods, participants, and deliverables. The research timeline should specify the duration, frequency, and sequence of the research activities, as well as the deadlines and milestones for the deliverables4. Establishing the research plan and timeline helps to ensure that the discovery phase is well-organized, efficient, and effective, as well as to communicate the expectations and responsibilities to the stakeholders and the team members.
• Understand the problem before moving to solutions: Another key practice for the discovery phase is to focus on understanding the problem before jumping to solutions. This means defining the problem statement, the scope, and the constraints of the project, as well as identifying the root causes, the symptoms, and the impacts of the problem. Understanding the problem before moving to solutions helps to avoid wasting time and resources on creating solutions that do not address the real needs and pain points of the users, or that are not feasible or viable for the business or the technology.

The other two options, considering platform-based before custom solutions and determining user acceptance criteria, are not practices that should be considered for planning out the strategy for an upcoming discovery phase. Considering platform-based before custom solutions is a practice that belongs to the design phase, not the discovery phase, as it involves choosing the best solution option based on the user research findings and the design principles5. Determining user acceptance criteria is a practice that belongs to the testing phase, not the discovery phase, as it involves defining the criteria that the solution must meet to be accepted by the users and the stakeholders6.

References: UX Discovery Process: A Complete Guide, UX Research Methods: How to Uncover Valuable Insight about your Users, User Research: What It Is and Why You Should Do It, How to Create a UX Research Plan, Platform-Based vs. Custom Solutions: Which One to Choose?, User Acceptance Testing (UAT): A Complete Guide

For Cloud Kicks' upcoming discovery phase, the three practices that should be considered are:

A. Understand the Problem Before Moving to Solutions: Establishing a clear understanding of theproblem and what the desired outcomes are before beginning the discovery phase is essential for successful project planning. This can be done by gathering data and insights from end users, conducting research, and understanding how the problem is currentlybeing addressed.

B. Gather Insight from End Users: Gathering insights from end users is a crucial step in the discovery phase. End users provide valuable feedback and insights into the problem and how a potential solution may work. This feedback can helpshape the overall project plan and help identify potential solutions.

C. Establish the Research Plan and Timeline: The research plan and timeline should be established before beginning the discovery phase. This should include a list of tasks to be completed, the resources needed, and a timeline for completion. This plan should be communicated to all stakeholders so everyone is aware of the project goals and timeline.

Card sorting is a technique that helps UX designers understand the mental model of users and how they organize information into categories. Card sorting involves giving users a set of cards, each with a piece of information or a feature, and asking them to sort them into groups that make sense to them. The designer can then analyze the results and identify patterns, similarities, and differences among the users’ categorizations. Card sorting can help the designer suggest a suitable architecture for the new internal community, based on how the employees think about the site’s content and functionality. Card sorting can be done in person or online, using tools like OptimalSort or UserZoom1. References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 2.1: Conduct user research
• [UX Designer Certification Prep: User Research], Unit 3: User Research Methods
• [Prepare for Your UX Designer Credential], Trailmix: User Research
• [Card Sorting: A Definitive Guide]1

 Voice and tone are two important aspects of UX writing that affect how users perceive and interact with a product. According to the Salesforce User Experience Designer Exam Guide, voice and tone are defined as follows:

• Voice reflects the personality of the brand or product. It is consistent and does not change depending on the context or situation. Voice conveys the values, mission, and identity of the brand or product through the choice of words, phrases, and style of communication.
• Tone reflects the way the voice speaks to the users. It is context-specific and can change depending on the user’s mood, goal, and situation. Tone conveys the attitude, emotion, and empathy of the voice through the use of punctuation, grammar, and formatting.

For example, Mailchimp is a brand that has a distinctive voice and tone. Their voice is friendly, humorous, and quirky. Their tone varies depending on the user’s experience, such as congratulating them for a successful campaign, or apologizing for an error. They use a tone map to guide their writers on how to adjust their tone for different scenarios.

References:

• : [Salesforce User Experience Designer Exam Guide]
• : [Voice and Tone | Salesforce Style Guide for Documentation and UX Writing]
• : [Voice and Tone | Salesforce Trailhead]
• : [UX writing 101: A beginner’s guide to mastering tone of voice]
• : [Tone of Voice and User Experience | UX Magazine]
• : [Things I learned designing the voice and tone for our company]
• : [How to use voice and tone in UX writing]
• : [Voice and Tone | Mailchimp Content Style Guide]

When the Service team at Cloud Kicks faces difficulty due to an overload of list views, the most effective way to improve their experience is by decluttering the list views to make relevant ones easier to find. This can be achieved by:

• Streamlining the List Views:Removing less frequently used or irrelevant list views from the public view helps in reducing clutter and focusing on the most pertinent information. This streamlining process makes navigation more intuitive and efficient for the service team members.

Options B (Updating Sharing Rules) and C (Allowing users to manage public list views) might help in managing access to records and customization, but they do not directly address the issue of having too many list views, which is the primary concern impacting the team's ability to find relevant information quickly.

References:Salesforce's documentation on managing list views provides strategies for organizing and customizing list views to improve usability and efficiency. This includes guidelines on creating, editing, and managing visibility of list views to ensure that users have access to the most relevant and useful information.

Card sorting is a UX research method where participants group ideas or information into different categories, based on what feels natural to them. Card sorting is ideal for the early stages of a website project, when the UX designer needs to understand how users organize and label content. Card sorting can help the UX designer to suggest a suitable architecture for the internal community, based on the employees’ mental model and expectations. Card sorting can also reveal any gaps or overlaps in the content, and provide insights for naming the categories and subcategories. References: Card Sorting / Tree Testing | Bentley University, Tree Testing vs. Card Sorting: Which is Right for You? | Maze

 One of the administrative capabilities that can be used for mobile navigation menu setup is to include Visualforce and Lightning pages as menu tabs. Visualforce and Lightning pages are custom pages that can display data, logic, and interface elements in the Salesforce mobile app. To include Visualforce and Lightning pages as menu tabs, the UX Designer needs to create tabs for those items first, and then add them to the navigation menu of the Mobile Only app or the Lightning app12

• Menu tabs can be based on different user types: This is not an administrative capability that can be used for mobile navigation menu setup, but rather a feature of the Lightning app navigation method. The Lightning app navigation method allows the UX Designer to create different Lightning apps for different user types, and assign them to different user profiles. Each Lightning app can have its own navigation menu and navigation bar, which can be customized with the items that are relevant for each user type34
• Menu tabs visibility is based on user location: This is not an administrative capability that can be used for mobile navigation menu setup, but rather a feature of the geolocation field type. The geolocation field type allows the UX Designer to store the latitude and longitude coordinates of a record, and use them for various purposes, such as displaying maps, calculating distances, or filtering reports. The geolocation field type does not affect the visibility of the menu tabs in the Salesforce mobile app.

References:

• Customize the Mobile Only Navigation Menu in the Salesforce Mobile App
• Customize a Lightning App Navigation Menu in the Salesforce Mobile App
• Create a Lightning App Unit | Salesforce Trailhead
• Assign a Lightning App to a User Profile Unit | Salesforce Trailhead
• [Geolocation Custom Field Type - Salesforce Help]
• [Use Geolocation Fields in Formulas - Salesforce Help]

Keyboard navigation is a way of interacting with a web application using only the keyboard, without a mouse or a touch screen. Keyboard navigation is essential for users who have visual impairments, motor disabilities, or other accessibility needs. Keyboard navigation also benefits users who prefer to use the keyboard for efficiency or convenience. One of the aspects of keyboard navigation that can be tested for accessibility is the tabbing order, which is the order in which elements on a page receive focus when the user presses the Tab key. The tabbing order should be logical, meaning that it follows the natural reading order of the page and the expected user workflow. A logical tabbing order helps users navigate the page easily and intuitively, without skipping or repeating elements. A logical tabbing order also helps screen readers announce the elements in a meaningful sequence. Therefore, testing the tabbing order for logic is a way of verifying keyboard navigation for accessibility. The other options are not related to keyboard navigation. Keyboard actions do not provide audio feedback by default, although some screen readers may have this feature. Actionable items are not highlighted in a specific color, although they may have a visible focus indicator, such as a border or an outline, to show which element has focus. The color of the focus indicator is not a factor for keyboard navigation, as long as it is distinguishable from the background. References: Keyboard Shortcuts, Use Lightning Experience with a Screen Reader, Accessibility in LWR Sites

The best way for the designer to illustrate the existing process, including the pain points and opportunities, is to observe the complaints process and create a journey map. A journey map is a visual representation of the customer’s or user’s experience with a product or service, from their perspective. It shows the steps, interactions, thoughts, feelings, touchpoints, context, and opportunities for improvement along the way. A journey map can help the designer to understand the current state of the complaints process, identify the pain points and gaps, and prioritize the areas for intervention. A journey map can also help to communicate the user’s needs and expectations to the stakeholders and developers, and align them on a common vision for the solution. References:

• : Start Your Journey Map Unit | Salesforce Trailhead
• : Add Journey Mapping to Your Solution Toolbox Unit | Salesforce Trailhead
• : Customer Journey Mapping Resources - Salesforce