Salesforce User-Experience-Designer Salesforce Certified User Experience Designer (SP23) Exam Practice Test

Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:

• How many users are using the feature?
• How often are they using it?
• How long does it take them to complete a task with the feature?
• How satisfied are they with the feature?
• How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?

Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.

Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users’ attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:

• Why are users using or not using the feature?
• What are their pain points, needs, and goals with the feature?
• How do they feel about the feature?
• What are their expectations and feedback for the feature?
• How does the feature fit into their context and workflow?

Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.

Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.

References: User Research Methods, Quantitative vs. Qualitative Usability Testing, 8 Essential Usability Testing Methods for UX Insights

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.

 The best way to present Knowledge articles to different audiences is to use page layouts or permissions to display only the fields needed for each audience. This way, the same article can be reused for both internal and external users, but with different levels of detail and visibility. Page layouts can control which fields are shown on the article detail page, and permissions can control which fields are searchable and editable. This is more efficient and consistent than writing separate articles for each audience, which would require more maintenance and duplication. Topics and data categories are different ways of organizing articles, but they do not affect the fields that are displayed. Topics are used for external sites, such as communities or portals, and data categories are used for internal sites, such as the Salesforce app. They can be mapped to each other, but they do not have to be organized the same way. References:

• 5 Best Practices for Salesforce Knowledge
• The Ultimate Guide to Salesforce Knowledge
• How to Write a Good Knowledge Base Article
• Prepare Your Salesforce Knowledge Base

Relationship Design is a creative practice that drives social and business value by building strong relationships. It is based on four mindsets: compassion, intention, courage, and reciprocity. Cloud Kicks can incorporate Relationship Design principles into its business model and customer offerings by adopting these mindsets and applying them to its products, services, and interactions. Some examples of how Cloud Kicks can do this are:

• Prioritizing innovation over copying the competition. This shows that Cloud Kicks is courageous and intentional in creating unique and valuable solutions that meet the needs and expectations of its customers and communities. Cloud Kicks can use design thinking methods, such as empathy mapping, ideation, and prototyping, to generate and test new ideas that solve real problems and create positive impact 1.
• Reframing products in terms of user value over features and functions. This shows that Cloud Kicks is compassionate and reciprocal in understanding and communicating the benefits and outcomes that its products and services can deliver to its customers and stakeholders. Cloud Kicks can use value proposition design tools, such as the value proposition canvas, to identify and articulate the jobs, pains, and gains of its customers, and how its products and services can address them 2.
• Uncovering customer needs over broadcasting product benefits. This shows that Cloud Kicks is intentional and reciprocal in listening and learning from its customers and co-creating solutions with them. Cloud Kicks can use user research methods, such as interviews, surveys, and observations, to discover and validate the needs, preferences, and behaviors of its customers, and to involve them in the design process 3.

References: [Design Thinking] [Value Proposition Design] [User Research]

The best option to simplify working with SLDS in Lightning Components is to install SLDS Validator extension for VS Code. This extension (salesforcedx-vscode-slds) scans the markup of the components, validates it against the SLDS documentation, and provides suggestions onhow to improve the code1. It also offers syntax highlighting, code completion, and context awareness for SLDS tokens and utility classes1. By using this extension, the development team can avoid CSS conflicts, follow SLDS best practices, and create consistent and accessible components2.

Installing SLDS creator from AppExchange is not a valid option, as there is no such app available on the AppExchange. The AppExchange is a marketplace for Salesforce apps, components, and consulting services, not for VS Code extensions3.

Installing Lightning Design System Plugin for Sketch is also not a valid option, as it is not related to VS Code or Lightning Components. Sketch is a design tool that allows users to create wireframes, mockups, and prototypes4. The Lightning Design System Plugin for Sketch is a plugin that provides SLDS components, icons, and styles for Sketch users. It can help designers to create consistent and compatible designs, but it cannot help developers to work with SLDS in VS Code.

References:

• SLDS Validator - Visual Studio Marketplace
• SLDS Validator for VS Code - Lightning Design System
• AppExchange: Salesforce’s Leading Enterprise Cloud Marketplace
• Sketch — The digital design toolkit
• [Lightning Design System Plugin for Sketch]

An interactive prototype is a simulation of the final product that allows users to interact with it and test its functionality and usability. An interactive prototype can be created using tools such as Figma or Invision, and can be shared with stakeholders and users for feedback and validation. An interactive prototype can have several benefits for a UX designer, especially when planning to roll out a refreshed version of a mobile app with some new functionality for customers. Two of these benefits are12:

• To avoid added long-term cost from oversight-driven rework. An interactive prototype can help the UX designer to identify and fix any errors, bugs, or gaps in the design before the development stage. This can save time and money that would otherwise be spent on reworking the product after it is developed. An interactive prototype can also help the UX designer toensure that the new functionality is aligned with the customer needs and expectations, and that it does not compromise the existing functionality or performance of the app.
• To enable iterative feedback from the users. An interactive prototype can provide a realistic and engaging user experience, and allow the users to explore the app and provide their opinions and suggestions. The UX designer can use the user feedback to iterate and improve the design, and to validate the assumptions and hypotheses. An interactive prototype can also help the UX designer to measure the user satisfaction and loyalty, and to test the app’s usability and accessibility.

The following two reasons are not valid for using an interactive prototype in this situation:

• To increase the speed of design compared to paper prototyping. An interactive prototype is not necessarily faster than a paper prototype, as it requires more time and effort to create and refine. A paper prototype is a low-fidelity prototype that uses sketches or drawings to represent the app’s layout and functionality. A paper prototype can be useful for generating and testing ideas quickly and cheaply, and for involving the users in the co-design process3.
• To eliminate the need for journey mapping during discovery. An interactive prototype is not a substitute for journey mapping, but a complement. Journey mapping is a UX research method that visualizes the user’s journey across the app, and identifies the touchpoints, actions, emotions, and pain points. Journey mapping can help the UX designer to understand the user’s context, goals, and needs, and to discover the opportunities for improvement. An interactive prototype can help the UX designer to test and validate the journey map, and to communicate the design vision to the stakeholders and users4. References: Interactive Prototypes Without Coding - Studio by UXPin, What is Interactive Prototypes? — updated 2023 | IxDF, Paper Prototyping as a Usability Testing Technique, Journey Mapping 101 | Nielsen Norman Group

When a lead is converted in Salesforce, three new records are typically created: a contact, an account, and an opportunity. A contact is a person who is associated with an account and has a role in a sales process. An account is a company or organization that is a potential or existing customer. An opportunity is a sales deal that is in progress or has been closed. These records are linked together and use the information from the lead record. The lead record becomes read-only and is marked as converted. References:

• Converting Leads
• Lead Conversion in Salesforce

A usability testing report is a document that summarizes the findings and insights from a usability test, which is a method of evaluating a product or service by observing how real users interact with it. A usability testing report should provide clear and actionable recommendations for improving the user experience and usability of the product or service1. One of the best practices for presenting the findings of a usability testing report is to be specific about the issues testers encountered. This means describing the problems in detail, explaining how they affected the user’s performance and satisfaction, and providing evidence from the data collected, such as quotes, screenshots, videos, or metrics. Being specific about the issues helps to illustrate the severity and impact of the problems, as well as to justify the need for improvement2.

The other two options, reporting only the new issues and omitting already known bugs, and including the names of participants in the report, are not good practices for presenting the findings of a usability testing report. Reporting only the new issues and omitting already known bugs can create a biased and incomplete picture of the usability test results, as it can overlook the recurring and persistent problems that may still affect the user experience and usability of the product or service. Including the names of participants in the report can violate the ethical and legal principles of user research, such as confidentiality, anonymity, and informed consent, which require protecting the privacy and identity of the users who participate in the research3.

References: How to Write a Usability Testing Report (With Templates and Examples) - Xtensio, How to Report Usability Test Results for Maximum Impact | Maze, Ethical Considerations in User Research and Testing | Interaction Design Foundation (IxDF)

A cross-functional flowchart is a type of process map that shows the relationships between process steps and business teams. A cross-functional flowchart uses horizontal or vertical swimlanes to group the process steps by the roles or departments that are responsible for them. A cross-functional flowchart can help Cloud Kicks’ Discovery team to explain how different teams collaborate and communicate in the process, as well as identify any gaps, overlaps, or inefficiencies in the process. A cross-functional flowchart can also show the inputs, outputs, and decisions at each step, and the flow of information and materials across the swimlanes12. References:

• Cross-Functional Flowchart
• Create a Cross-Functional Flowchart

 A responsive user interface is a type of user interface that adapts to different screen sizes, resolutions, orientations, and devices, such as desktops, laptops, tablets, and smartphones. It uses flexible layouts, grids, images, and media queries to optimize the user experience and ensure usability, accessibility, and performance across different devices. A responsive user interface can help Cloud Kicks create a site for its customers to manage events regardless of the device they are using, as it can provide a consistent and seamless experience that meets the user needs and expectations. A responsive user interface can also reduce the development and maintenance costs and efforts, as it can use the same code base and content for different devices, rather than creating separate versions for each device. References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : User Experience Designer Certification Prep: Module 7: Implement User Interfaces
• : What is Responsive Web Design?

To create a site for its customers to manage events regardless of the device they are using, Cloud Kicks should use the best practice of creating a responsive user interface. A responsive user interface is one that adapts to the screen size and orientation of the device, providing an optimal viewing and interaction experience for the user. A responsive user interface can use the same code base and content for different devices, reducing the development and maintenance costs and ensuring consistency and accessibility. A responsive user interface can also leverage the features and capabilities of the device, such as touch, gestures, camera, etc., to enhance the user experience.

References:

• : Responsive User Interface

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].

The approach that is being followed by the UX Designer is the Human-Centered Design. This is a creative design approach that focuses on understanding the end-user’s needs, problems,and context, and then creating solutions that are desirable, feasible, and viable for them. The Human-Centered Design process typically involves four phases: empathize, define, ideate, and prototype.

References:

• : Human-Centered Design
• : Empathize, Define, Ideate, Prototype

When developers are building custom components in Salesforce and need to ensure that these components adapt to user preferences for density settings (Comfy or Compact), they should avoid using REM-based spacing values. This is because REM-based spacing does not automatically adjust based on the density setting chosen by the user, leading to a lack of consistency with the rest of the Salesforce UI, which does adapt to these settings. Instead, developers should:

• A. Use thevarSpacingMediumdesign token in CSS, as Salesforce Lightning Design System (SLDS) design tokens are context-aware and can adjust their values based on the density setting, ensuring a consistent user experience across different user preferences.
• C. Use existing Lightning Components such as the card or page header, which are pre-built to adapt to density settings, ensuring that custom components align with the overall Salesforce UI and respect user settings for density.

References:Salesforce Lightning Design System (SLDS) documentation provides guidelines on using design tokens and building responsive components that respect user settings like density preferences. You can find more information on the official Salesforce Developers website or the SLDS documentation section.

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

To ensure new Salesforce users are given the appropriate onboarding experience, a UX Designer should use the following two on-App Guidance customizations:

• Specify prompt scheduling: This allows the designer to control when and how often the prompts appear to the users, based on criteria such as start and end dates, frequency, and snooze duration. This way, the designer can tailor the onboarding experience to the users’ needs and preferences, and avoid overwhelming or annoying them with too many or irrelevant prompts.
• Set prompt permissions: This allows the designer to target the prompts to specific user groups, based on profiles and permissions. This way, the designer can ensure that the prompts are relevant and useful to the users, and avoid showing them information that they do not need or have access to.

References:

• Salesforce In-App Guidance: Enhance Your User Experience
• Create and Manage In-App Guidance Prompts

  The Salesforce app allows administrators to customize the brand color and the loading page logo to match the company’s branding. The brand color affects the key user interface elements such as the header, buttons, and search bar. The loading page logo is the image that appears after a mobile user logs in. These elements can be customized from Setup by entering Salesforce Branding in the Quick Find box, then selecting Salesforce Branding. The other elements, such as the search bar layout, the background image, and the focus link color, are not customizable in the Salesforce app. References:

• Customize Salesforce Mobile App Branding
• How Salesforce App Branding Works

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.

Demographic data is data that describes the characteristics of a population or a group of people, such as age, gender, race, ethnicity, income, education, or occupation. Demographic data can lead to bias if it is used to discriminate or treat people differently based on their identity or attributes. Demographic data can also reflect existing biases or stereotypes in society or culture, which can affect the fairness and ethics of AI systems. Societal bias is the bias that results from the social norms, values, and expectations of a society or a culture. Societal bias can influence how people perceive, judge, and behave toward others, especially those who are different from them. Societal bias can also be embedded in the data that is used to train or validate AI models, which can then propagate or amplify the bias in the AI outputs or decisions. Therefore, it is recommended to carefully consider which demographic data and for what purpose is fed into an AI model, to avoid societal bias and its negative consequences. References: Salesforce AI Associate: How to Avoid Bias from Demographic Data in AI Models, Recognize Bias in Artificial Intelligence Unit | Salesforce Trailhead, Designing Personalized User Experiences with Data AI | Salesforce

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].

 The two design considerations that should be made when creating a customer support site in Experience Builder that will be internationalized across 12 different countries are:

• Countries may read text in a different direction (right to left vs. left to right) and layouts will need to be adjusted. This is because some languages, such as Arabic and Hebrew, are written from right to left, while others, such as English and French, are written from left to right. This affects not only the text alignment, but also the placement of UI elements, such as buttons, menus, icons, and images. To accommodate different reading directions, the site should use a flexible layout that can be mirrored or flipped based on the language setting. This also follows the principle of designing for accessibility and inclusion, which is one of the learning objectives for the Salesforce User Experience Designer certification12
• Colors may have different cultural meanings in different countries, changing the intent of UI elements. This is because colors can convey different emotions, associations, and messages depending on the cultural context. For example, red can mean danger, passion, or luck, depending on the country. Therefore, the site should use colors that are appropriate andrespectful for the target audience, and avoid colors that may be offensive or misleading. This also follows the principle of designing for the user’s context and environment, which is another learning objective for the Salesforce User Experience Designer certification34

References: [Design for Accessibility and Inclusion], [Add Languages to Your Aura Sites], [Design for the User’s Context and Environment], [Color Meanings by Culture]

:  1 : :  2 : :  3 : :  4

The Salesforce Navigation Setup mode allows the administrator to customize the navigation menu and navigation bar of the Salesforce mobile app using the Mobile Only app. The administrator can select the Lightning pages, Visualforce pages, Lightning components, and other productivity items that they want to appear in the navigation menu and navigation bar. The administrator can also reorder the navigation items and create tabs for them. To customize navigation items, in the Quick Find box, enter Navigation, and select Salesforce Navigation 1. Visualforce pages and Lightning pages can be included in the navigation menu and navigation bar of the Salesforce mobile app, as long as they have tabs created for them. To create a tab, from Setup, enter Tabs in the Quick Find box, and select Tabs 1. References: [Customize the Mobile Only Navigation Menu in the Salesforce Mobile App] &language=en_US&type=5)

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

A docked prompt is a type of In-App Guidance that can be used to provide contextual help and guidance to the users in the Salesforce app. A docked prompt is a small pop-up window that appears at the bottom of the screen, and can contain text, images, links, or videos. A docked prompt can be triggered by various events, such as opening a page, clicking a button, or completing an action. A docked prompt can also be dismissed by the user, or set to expire after a certain time or date12

A UX Designer can customize the Salesforce Help Menu to meet the request of Cloud Kicks’ Sales team by creating a docked prompt based on new feature rollouts. This way, the UX Designer can:

• Inform the users about the new features and how they can benefit from them. For example, the UX Designer can create a docked prompt that introduces the new Einstein Opportunity Scoring feature, and explains how it can help the users prioritize their opportunities and close more deals3
• Guide the users through the steps and best practices to use the new features. For example, the UX Designer can create a docked prompt that shows the users how to access and configure the new Einstein Opportunity Scoring feature, and how to interpret and act on the scores3
• Engage the users and encourage them to explore and adopt the new features. For example, the UX Designer can create a docked prompt that includes a link to a video tutorial, a Trailhead module, or a feedback survey about the new Einstein Opportunity Scoring feature3
• Show a site map of all the content: This is not a way to customize the Salesforce Help Menu to meet the request of Cloud Kicks’ Sales team, because a site map of all the content is not a typeof In-App Guidance, and it does not provide specific and timely help and guidance for the users. A site map of all the content is a visual representation of the structure and hierarchy of a website or app, and it can be useful for planning and designing the user interface, but not for providing In-App Guidance4
• Provide links to external resources, such as training videos or a company dictionary: This is not a way to customize the Salesforce Help Menu to meet the request of Cloud Kicks’ Sales team, because providing links to external resources is not a type of In-App Guidance, and it does not provide contextual and interactive help and guidance for the users. Providing links to external resources is a way to supplement the Salesforce Help Menu with additional information and resources, but not to create In-App Guidance5

References:

• Create In-App Guidance Unit | Salesforce Trailhead
• In-App Guidance - Salesforce Help
• Create a Docked Prompt for New Feature Rollouts Unit | Salesforce Trailhead
• What is a Sitemap? - Interaction Design Foundation
• Customize the Help Menu in Lightning Experience - Salesforce Help

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] [Set Up Automated Chat Invitations]

To create visual consistency with regard to alignments, grids, spacing, and typography, the part of the Salesforce Lightning Design System (SLDS) that should be used is utility classes. Utility classes are CSS classes that provide common styling properties, such as margins, paddings, borders, colors, fonts, and text alignments. Utility classes can be applied to any HTML element to quickly and easily adjust its appearance and layout. Utility classes follow the BEM (Block Element Modifier) naming convention, which makes them easy to read and understand. Utility classes can help the designer to create visual consistency across the Lightning components and pages, without writing custom CSS or overriding the component blueprints. References: : Utility Classes | Lightning Design System : UX Designer Certification Prep: Designing with Lightning Design System | Trailhead

The designer should consider the traits similar to customer personas when selecting users for testing. Customer personas are fictional representations of the target users of a product or service, based on user research and data. Customer personas help the designer to understand the needs, goals, behaviors, and preferences of the users, as well as their pain points and challenges. Customer personas also help the designer to empathize with the users and design solutions that meet their expectations and requirements. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas]

When selecting users for testing, the designer should aim to recruit users who match the traits of the customer personas as closely as possible. This ensures that the users who participate in the testing are representative of the actual or potential users of the product or service, and that the feedback and insights gathered from the testing are valid and reliable. Selecting users who have traits similar to customer personas also helps the designer to evaluate the usability and user experience of the product or service from the user’s perspective, and to identify and prioritize the areas for improvement. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation]

Traits dissimilar to customer personas, traits similar to friends and family, and traits of the most common demographic and ability are not criteria that the designer should consider when selecting users for testing. These criteria can lead to biased or inaccurate results, as they do not reflect the diversity and complexity of the user population. Users who have traits dissimilar to customer personas may not have the same needs, goals, or expectations as the target users, and may provide feedback that is irrelevant or misleading. Users who have traits similar to friends and family may not be objective or honest in their feedback, and may have a different level of familiarity or expertise with the product or service than the target users. Users who have traits of the most common demographic and ability may not account for the variations and differences among the target users, and may exclude or marginalize the users who have special needs or preferences. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation] References: [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas], [UX Designer Certification Prep: User Testing and Evaluation]

A formula field is a custom field that calculates a value based on a formula expression. A formula field can display text, numbers, dates, or images. A formula field can use the IMAGE function to display an image from a URL. A formula field can be added to an object page layout to show the image on the record detail page1.

A static resource is a file or a collection of files that can be uploaded to Salesforce and referenced in a formula field, a Visualforce page, a Lightning component, or a web tab. A static resource can store images, style sheets, JavaScript, or other files. A static resource can be used to store the custom image that Cloud Kicks wants to display on the record detail page2.

An object page layout is a configuration of fields, buttons, related lists, and other components on a record detail page. An object page layout can be customized to show different information for different users, based on their profiles or record types. An object page layout can be used to add the formula field that displays the custom image to the record detail page3.

These platform tools can be used to achieve the requirement of adding a custom image to a record detail page, making it easier for Cloud Kicks to visually identify its current membership level. For example, the formula field can use the IMAGE function to display the custom image from the static resource, based on the value of another field that indicates the membership level. The object page layout can then include the formula field on the record detail page for the relevant users.

Image field is a custom field that allows users to upload and display images on a record. Image field can be used to show images on a record detail page, but it is not suitable for Cloud Kicks’ requirement, because it does not allow the image to be determined by a formula expression. Image field requires the user to manually upload the image for each record, which is not efficient or consistent4.

Dynamic form is a feature that allows admins to add, group, and reorder fields and sections on a Lightning record page using the Lightning App Builder. Dynamic form can be used to create flexible and dynamic page layouts that can adapt to different contexts and scenarios. Dynamic form also supports visibility rules, which can be used to show or hide fields or sections based on filters or conditions. However, dynamic form is not a platform tool that can be used to display a custom image on a record detail page, as it does not affect the content or functionality of the fields. Dynamic form can only be used to configure the layout of the fields, not the values or images of the fields5.

Lightning components are reusable units of user interface that can be used to build Lightning pages and applications. Lightning components can be built using HTML, CSS, JavaScript, and Apex. Lightning components can display data, images, icons, charts, buttons, or other elements on a Lightning page. SLDS icons are icons from the Salesforce Lightning Design System that can be used in Lightning components to represent actions, objects, or concepts. Compact layouts are page layouts that show a record’s key fields at a glance in the highlights panel, the list view, the Related tab, and other places. Compact layouts can be used to customize which fields are displayed in these places6.

Lightning components, SLDS icons, and compact layouts are platform tools that can be used to display images on a Lightning page, but they are not the best option for Cloud Kicks’ requirement, because they are more complex and require more development skills than a formula field, a static resource, and an object page layout. Lightning components also require more maintenance and testing than formula fields. SLDS icons are predefined icons that may not match the custom image that Cloud Kicks wants to display. Compact layouts are not relevant for displaying images on a record detail page, as they only affect the highlights panel and other places6.

References: 1: Use Images in ‘Formula’ Fields - Salesforce 2: Static Resources | Salesforce Developer Guide 3: Page Layouts | Salesforce Help 4: Image Field | Salesforce Platform - YouTube 5: Dynamic Forms Tips and Considerations - Salesforce 6: Lightning Components Basics Unit | Salesforce Trailhead

 A UX designer’s role is not only to design solutions, but also to facilitate collaboration and communication among stakeholders and users. A clear, consistent sales process is essential for Salesforce adoption, as it defines the steps and actions that sales representatives need to take to close deals. Without a common understanding of the sales process, the UX designer cannot design a Salesforce solution that meets the needs and expectations of the users and the business. Therefore, the designer should conduct a workshop with stakeholders to align on the current state and build consensus on the desired future state. A workshop is an interactive session where the designer can use various techniques, such as journey mapping, persona creation, user stories, and prioritization, to elicit the pain points, goals, and requirements of the stakeholders and users. A workshop can also help the designer to establish trust and rapport with the participants, and to gain their buy-in andfeedback for the proposed solution12. References: Salesforce Adoption Strategies | Salesforce Trailhead, 6 Guiding Principles to Maximize Your Salesforce Adoption | Salesforce Admins

According to the Salesforce Trailhead, the Trusted Advisor persona spends 3+ hours a day maintaining relationships with existing customers. They upsell products, grow deals, and manage renewals. This persona also spends time prospecting for new opportunities in existing accounts and gathering requirements from prospects1

Therefore, the key business process that defines their work and should be analyzed to make sure the delivered experience fits their needs is maintaining relationships with existing customers. This process involves understanding the customer’s needs, goals, expectations, and satisfaction, as well as providing them with relevant solutions, support, and value. The UX Designer should focus on creating a user interface that enables the Trusted Advisor to easily access and update customer information, communicate and collaborate with customers, and track and measure customer loyalty and retention23

• Managing sales pipeline and forecasting: This is not the key business process that defines the work of the Trusted Advisor persona, but rather the Data Expert persona. The Data Expert persona spends 3+ hours a day on reporting and sales forecasting. They also spend 1–3 hours managing the sales pipeline and tools for the sales team1
• Customizing and administering Salesforce: This is not the key business process that defines the work of the Trusted Advisor persona, but rather the Sales Leader persona. The Sales Leader persona spends most of their day managing, coaching, and training sales reps. They also spendtime managing tools and processes for sales reps, which includes customizing and administering Salesforce1

References:

• Learn About Sales Cloud Personas Unit | Salesforce Trailhead
• How to Increase Your Sales with Personas for Salesforce Users | RTS Labs
• How to Use Journey Mapping to Improve Employee Engagement

Inclusive design is a design approach that aims to create products and services that are accessible and usable by as many people as possible, regardless of their abilities, preferences, or circumstances. Some of the benefits of inclusive design are :

• Extending access to more users: By considering the diverse needs and situations of users, inclusive design can expand the reach and impact of the product or service. For example, designing a website that is compatible with screen readers can benefit not only users who are blind or visually impaired, but also users who are in low-light environments or have low bandwidth.
• Reducing friction for users in achieving their goals: By removing unnecessary barriers and providing multiple ways of interaction, inclusive design can enhance the user experience and satisfaction. For example, designing a mobile app that supports voice input and output can benefit not only users who have difficulty typing or reading, but also users who are multitasking or have their hands busy. References: : [UX Designer Certification Prep: Designing for Accessibility and Inclusion | Trailhead] : [Inclusive Design | Salesforce Developer Guide]

Inclusive design is a practice of designing products, services, and experiences that are accessible and usable for as many people as possible, regardless of ability, age, gender, race, language, or culture. By incorporating inclusive design practices, you can extend access to more users and reduce friction for users in achieving their goals. Salesforce provides more information on the benefits of inclusive design

Visibility of system status is the usability heuristic that is being used in this case. Visibility of system status means that the system should always keep users informed about what is going on, through appropriate feedback within reasonable time1. One way to apply this heuristic is to use visual indicators to let users know which form fields are required, such as asterisks, labels, or colors. This helps users to understand the expectations and requirements of the system, and to avoid errors or confusion. By providing clear and timely feedback, the system enhances the user experience and satisfaction. References: Learn About User Experience Design Unit | Salesforce Trailhead, [10 Usability Heuristics for User Interface Design], Salesforce User Experience (UX) Designer Certification Guide & Tips

A wireframe prototype is a low-fidelity representation of the content and structure of a new feature, without any visual design or branding elements. It is used to test the usability and functionality of the feature with the user, and to gather feedback and iterate on the design. A wireframe prototype can be created using tools like Sketch, Figma, or Adobe XD, and can be interactive or static. References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 2.2: Design and test prototypes
• [UX Designer Certification Prep: Prototyping], Unit 2: Wireframes and Prototypes
• [Prepare for Your UX Designer Credential], Trailmix: Prototyping

The utility bar is a fixed footer that gives users quick access to productivity tools, such as notes, history, and recent items. It can be customized for each Lightning app to enhance the user experience and efficiency. Some of the standard use cases for using the utility bar are:

• Perform common tasks without navigating away from the page: Users can use the utility bar to perform tasks such as creating notes, logging calls, or sending emails without leaving their current context. This reduces the need for switching tabs or opening new windows, and saves time and clicks.
• Access to view a list of records favorited for quick access: Users can use the utility bar to access their favorites, which are records, lists, groups, or other items that they have marked with a star icon for easy access. This allows users to quickly navigate to the items they use most frequently, and organize them in a personalized way.
• Access at any time to a customized set of items specific to an app: Users can use the utility bar to access items that are relevant and useful for the app they are using. For example, in the Sales app, users can access the Lightning Dialer, the Assistant, or the Today’s Events utility. In the Service app, users can access the Omni-Channel, the Macros, or the Case Timer utility. The utility bar can be configured to show different items for different apps, depending on the user’s needs and preferences.

References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : Lightning App Builder: Utility Bar

 The best Salesforce solutions for Cloud Kicks to deliver consistently branded content at every touchpoint are Distributed Marketing and Journey Builder. Distributed Marketing allows individual agents to send personalized and compliant messages to their customers, using pre-approved templates and content created by the corporate marketing team1. Journey Builder enables the marketing team to design and automate customer journeys across channels and devices, using data and analytics to optimize the customer experience2. Email Builder and Customer 360 (B) are not sufficient to ensure consistent branding and communication, as they only cover email marketing and customer data integration, respectively. Service Cloud and Letterhead © are also not the best solutions, as they only focus on customer service and email formatting, respectively. References:

• Distributed Marketing | Salesforce
• Journey Builder | Salesforce

 Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the --slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, --slds-c-button-brand-color-background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function. References:

• Styling Hooks - Lightning Design System
• SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers
• –dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1].

 A page header is a component that appears at the top of every page on a Digital Experience site, and usually contains the site logo, the site name, the navigation menu, and other elements that provide a consistent and recognizable look and feel for the site. A UX Designer can code the page header to update the logo for Cloud Kicks by using the Experience Builder or the Developer Console1. The Experience Builder is a point-and-click tool that allows creating and customizing the page header using predefined templates, themes, and components. The Developer Console is a code editor that allows creating and editing the page header using HTML, CSS, JavaScript, and Lightning components2. Both tools provide the option to upload and insert the new logo image file into the page header, and to adjust its size, position, and alignment.

The other two options, Visualforce pages and email templates, are not the places where the UX Designer needs to code to update the logo for Cloud Kicks. Visualforce pages are web pages that can be used to create custom user interfaces for Digital Experience sites, but they do not affect the page header, which is a separate component that can be added to any page3. Email templates are predefined layouts and content that can be used to send emails to the site users, but they do not have any impact on the site appearance or functionality.

References: Create a Custom Header for Your Site | Salesforce Trailhead and Customize Your Site Header and Footer | Salesforce Trailhead

 A user flow is a UX design method that creates a visual representation of a user’s series of steps to achieve a meaningful goal. A user flow shows the path that a user takes from their entry point to their final action, such as signing up, purchasing, or completing a task. A user flow helps designers understand and optimize the user experience, as well as identify pain points, gaps, and opportunities for improvement. A user flow can take various forms, such as diagrams, wireframes, or prototypes, depending on the level of detail and fidelity required. References:

• What Are User Flows In UX Design? [Full Beginner’s Guide] - CareerFoundry
• What is a User Flow in UX Design? — updated 2023 | IxDF
• User Flows in UX Design: Definition, Benefits, and Best Practices

In visual design, especially within the context of translating style and branding guidelines, certain elements play crucial roles in ensuring that the design effectively communicates the intended brand identity and aesthetic. These elements include:

• Typography:The choice of fonts and how text is styled and arranged can significantly impact the brand's voice and how content is perceived by the audience. Typography can convey feelings, create hierarchy, and guide the user's attention through the design.
• Color:Color schemes are fundamental in visual design as they can evoke emotions, communicate brand values, and improve the user's experience by creating visual interest and guiding focus.
• Imagery:The use of images, icons, illustrations, and other visual media must align with the brand's style and values. Imagery can help tell a brand's story, convey complex information quickly, and connect with users on an emotional level.

Options B and C, such as Wireframes, Personas, Blueprints, Sketching, and Storyboards, are crucial in the early stages of the design process for conceptualization and planning but do not directly translate style and branding guidelines in the same way that typography, color, and imagery do.

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.

 Human-centered design is a practice where designers focus on people and their context, and seek to understand and solve the right problems for them. Human-centered design involves the following elements1:

• Empathy. Designers need to genuinely care about the people they design for, and build empathy by immersing themselves in the community that will use their products or services.
• Creativity. Designers need to find creative ways to solve users’ problems, and generate multiple ideas and prototypes that can be tested and refined.
• Business needs. Designers need to make their products or services commercially successful, and align them with the goals and values of the organization.

To incorporate human-centered design across its organization, Cloud Kicks should adopt the following two practices:

• Observing user behavior. Designers should conduct user research and communicate with their users regularly, to understand their needs, motivations, challenges, and goals. Observing user behavior can help designers to identify the pain points and opportunities for improvement, and to validate their assumptions and hypotheses.
• Putting oneself in the situation of the end user. Designers should empathize with their users, and try to see the world from their perspective. Putting oneself in the situation of the end user can help designers to create products or services that are relevant, useful, and desirable for them.

The following two practices are not aligned with human-centered design, and should be avoided:

• Including innovative ideas to showcase technology. Designers should not prioritize technology over people, and should not include features or functions that are not necessary or beneficial for the users. Including innovative ideas to showcase technology can lead to products or services that are complex, confusing, or frustrating for the users.
• Creating requirements based on business leaders’ priorities. Designers should not ignore the voice of the users, and should not create products or services that only satisfy the business needs. Creating requirements based on business leaders’ priorities can lead to products or services that are irrelevant, useless, or undesirable for the users.

References: Human-Centered Design: An Introduction, Practices, and Principles - Shopify

The users can improve their end-user experience by favoriting the often used object and personalizing the navigation bar. Favoriting the object allows the users to access it quickly fromthe Favorites menu in the header. Personalizing the navigation bar allows the users to add, remove, or reorder the items that they use frequently. These features do not require the administrator to create a new app or modify the existing one, and they can be customized by the users themselves according to their preferences and needs. References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs
• [UX Designer Certification Prep: User-Centered Design], Unit 4: Design for User Needs
• [Prepare for Your UX Designer Credential], Trailmix: User-Centered Design
• [Salesforce Help: Favorites in Lightning Experience]
• [Salesforce Help: Personalize Your Navigation Bar]

Personalized Navigation Tabs are a navigational feature that allows the users to customize the navigation bar of the Salesforce mobile app with the items that they use most frequently. Users can add, remove, and reorder the tabs in the navigation bar, and access them with a single tap. Users can also mark their favorite items with a star icon, and access them from the Favorites tab. Personalized Navigation Tabs can help Cloud Kicks (CK) employees to quickly access the apps, objects, and other items that they need in the Salesforce mobile app12

• Console Navigation is a navigational feature that allows the users to work with multiple records and objects on a single screen in the Salesforce desktop app. Console Navigation is not available in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items3
• Utility Bar is a navigational feature that allows the users to access common productivity tools, such as notes, history, or macros, from a fixed footer at the bottom of the Salesforce desktop app. Utility Bar is not available in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items4

References:

• Personalize Your Navigation Bar in the Salesforce Mobile App - Salesforce Help
• Personalize Your Navigation Bar in the Salesforce Mobile App Unit | Salesforce Trailhead
• Console Navigation - Salesforce Help
• Utility Bar - Salesforce Help

 Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices. Some of the best practices for responsive design are:

• Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences. Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc. For example:

@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }

@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and 900px */ }

@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }

• Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser. It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power. Some of the ways to minimize page weight are:

The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.

References: Responsive Design: Best Practices and Considerations | Toptal®, Responsive design - Learn web development | MDN, The Beginner’s Guide to Responsive Web Design in 2023 - Kinsta, Responsive Design Best Practices. by Nick Babich - UX Planet

The Salesforce Lightning Design System (SLDS) reflects the patterns and components that underpin the Salesforce product. These patterns and components provide a unified language and consistent look and feel when designing apps and products within the Salesforce ecosystem. The Lightning Experience UI, which SLDS represents, was crafted using four core design principles. We encourage you to keep them in mind as you develop your applications. They are1:

• Clarity — Eliminate ambiguity. Enable people to see, understand, and act with confidence.
• Efficiency — Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.
• Consistency — Create familiarity and strengthen intuition by applying the same solution to the same problem.
• Beauty — Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship. References: Introduction to the Salesforce Lightning Design System

 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:

 To restyle a Lightning Experience model to meet brand guidelines, the designer should use design tokens and find the appropriate component blueprint. Design tokens are variables that store visual design attributes, such as colors, fonts, and spacing. They allow the designer to customize the appearance of Lightning components without writing any code. Component blueprints are design specifications for Lightning components that provide guidance on how to use them, what properties they support, and how they behave in different scenarios. They help the designer to choose the right component for the model and apply the brand guidelines consistently. References: : Design Tokens | Salesforce Developer Guide : Component Blueprints | Lightning Design System : UX Designer Certification Prep: Designing with Lightning Components | Trailhead

The Path component is a Salesforce Lightning Design System (SLDS) component that can be used to represent stages for opportunities within the sales process. The Path component displays the stages as a horizontal bar with icons and labels, and highlights the current stage with a blue background. The Path component also allows users to move opportunities to different stages, view and edit key fields for each stage, and access guidance and tips for each stage. The Path component can be added to any object that has a picklist field with values that represent stages, such as the Stage field on the Opportunity object12. References:

• Path Component
• Set Up a Path for Your Sales Team

Designing perceivable content means that the content should be presented in a way that can be convertible between different formats, so that users with different sensory abilities can access it. For example, providing text alternatives for images and videos, captions and transcripts for audio, and audio descriptions for visual content. This way, users who are blind, deaf, or have low vision or hearing can perceive the content using assistive technologies, such as screen readers, braille keyboards, or captions. The content should not only be presented in a visual format (A) or an audio format (B), as that would exclude users who cannot see or hear the content. The content should be adaptable to different formats and devices, and follow the Web Content Accessibility Guidelines (WCAG) principle of perceivability12. References:

• Perceivable - Accessibility | MDN
• What Is Perceivability in Web Accessibility? WCAG Principles Explained

Themes and branding allow Salesforce app developers to customize the look and feel of their apps to match their company’s branding and accessibility standards. One of the features of themes and branding is the ability to select a brand color, which is the primary color used for buttons, links, and highlights. Salesforce automatically generates a color palette based on the brand color, which includes accessible colors that meet the WCAG 2.1 contrast ratio guidelines. This ensures that the app is visually appealing and accessible to users with different color vision abilities. Developers can also customize other aspects of the theme, such as the logo, page background, and default font. References: [Themes and Branding Basics], [Accessibility in Salesforce]

 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

A moderated usability study is a type of user research where the UX Designer interacts with the participants as they perform tasks on the prototype solution. The designer can ask follow-up questions to obtain further information about the issues participants may encounter, such as why they made certain choices, how they felt about the experience, and what they would like to see improved. This can help the designer gain deeper insights into the user needs, preferences, and pain points, as well as validate or invalidate their design assumptions. A moderated study also allows the designer to clarify any confusion or ambiguity that the participants may have during the session, and to adjust the tasks or scenarios as needed. References:

• [User Experience Designer Certification Prep: Conduct User Research]
• [User Experience Designer Certification Prep: Analyze User Research]
• [User Experience Designer Certification Prep: Validate Solutions]

The one token and one utility class that should be suggested to the developers to ensure custom components respect the density settings are:

• varSpacingMedium. This is a design token that defines the medium spacing value for the vertical and horizontal spacing between elements. This token can be used to adjust the spacing according to the density setting of the user. For example, if the user prefers the Comply density setting, the token value will be 16px, and if the user prefers the Compact density setting, the token value will be 8px.
• slds-p-around_medium. This is a utility class that applies the medium padding value to all sides of an element. This class can be used to add padding to the custom component according to the density setting of the user. For example, if the user prefers the Comply density setting, the class will apply 16px of padding, and if the user prefers the Compact density setting, the class will apply 8px of padding.

References:

• : Design Tokens
• : Spacing Tokens
• : Utility Classes
• : Padding Utility Classes

 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]

Card sorting is a UX research method used to discover how people understand and categorize information. In a card sort, participants group ideas or information written on cards into different categories in a way that makes sense to them. The designer can use virtual cards, pieces of paper, or an online card sorting tool. Card sorting can help the designer to:

• Assess the information architecture (IA) of a website or homepage
• Learn how people understand different concepts or ideas, and how they feel about them
• Understand where users expect certain content to be found
• Get inspiration for labeling and grouping content or ideas

In this case, the designer wants to understand the structure and layout of the navigation menu for the Experience Cloud site. The designer can use card sorting to learn how users would group and label the pages or features of the site, and what categories or subcategories they would expect to see in the navigation menu. This can help the designer to create a user-friendly and intuitive IA that matches the users’ mental models and expectations.

To conduct a card sorting activity, the designer should:

• Define the goal and scope of the card sort
• Choose the type of card sort (open, closed, or hybrid)
• Choose the format of the card sort (moderated or unmoderated)
• Select the cards and categories to use
• Recruit and screen the participants
• Run the card sort sessions
• Analyze and interpret the results
• Apply the findings to the design

The correct answer is B, have users sort the cards based on similar categories or groups. This is the main task of a card sorting activity, where users are asked to group the cards (representing the pages or features of the site) into categories or groups that make sense to them. The designer can then analyze the results to see how users organize and label the information, and use that to inform the design of the navigation menu.

 Tiles are standard components that display records or objects as a collection of boxes that contain a photo and additional information1. Tiles are suitable for Cloud Kicks (CK) to display contact information, including avatar, name, and title, for people who are related to a customer on a Record page, as they provide a compact and visual way to show the relevant data. Tiles also allow users to interact with the records by clicking or tapping on them1. Tiles can be customized to fit the availablespace and layout of the Record page2. References: Components - Salesforce Lightning Component Library, Tiles - Lightning Design System

 Interactive cards are compact components that can displayinformation such as avatars, names, and titles in an organized way. Additionally, Interactive Cards are designed to be responsive and can be used to display information on smaller screens, such as mobile devices, without taking up too much space. This makes them ideal for CK's use case, as they can display all of the required information within the limited title space. For more information, see the Salesforce Lightning Design System documentation

 Confirmation bias is the tendency to seek out and prefer information that supports our preexisting beliefs, while ignoring or rejecting information that contradicts them. Confirmation bias can affect the validity and reliability of user feedback, as it can lead to biased questions, selective interpretation, and skewed results. To avoid confirmation bias in user feedback, Cloud Kicks can follow these two strategies:

• Interview users about the intended use of the product to support the questionnaire creation. This can help Cloud Kicks to understand the user needs, expectations, and goals, and to design questions that are relevant, clear, and unbiased. By interviewing users, Cloud Kicks can also avoid making assumptions about the user behavior, preferences, and pain points, and instead base their questions on real user data and insights 1.
• Diversify feedback by ensuring it features as many unique perspectives as possible. This can help Cloud Kicks to reduce the risk of sampling bias, which occurs when the feedback is collected from a group of users that is not representative of the target population. By diversifying feedback, Cloud Kicks can capture a wider range of user opinions, experiences, and feedback, and avoid overlooking or dismissing important user segments or viewpoints 2.

References: [How to Avoid Confirmation Bias in UX Research] [How to Avoid Sampling Bias in User Research]

The three standard Salesforce objects that should be used in this experience are:

• Lead: A lead is a person who has shown interest in the company’s products or services, but has not yet been qualified as a potential customer. Leads can be captured from various sources, such as web forms, referrals, events, or marketing campaigns. Leads can store information such as name, email, phone, company, and status. Leads can be converted into accounts, contacts, and opportunities when they are ready to buy.
• Contact: A contact is a person who is associated with an account and has a role in a sales process. Contacts can store information such as name, email, phone, title, and address. Contacts can be related to multiple accounts, opportunities, cases, activities, and other objects. Contacts can be used to track the communication and interaction history with the customers.
• Opportunity: An opportunity is a sales deal that is in progress or has been closed. Opportunities can store information such as name, amount, stage, probability, close date, and owner. Opportunities can be linked to accounts, contacts, products, price books, quotes, contracts, and other objects. Opportunities can be used to forecast revenue, manage sales pipeline, and track sales performance.

References:

• Standard Objects
• Leads and Opportunities
• Contacts

An empathy map is a tool that helps to synthesize what CK knows about the users and share this insight with the rest of the organization. An empathy map is a visual representation of the user’s perspective, based on their thoughts, feelings, actions, and needs. It helps to create a shared understanding of the user’s goals, pain points, motivations, and emotions. An empathy map can also help to identify gaps in the user research and generate new ideas for design solutions. References:

• : Creating a Customer Empathy Map Using The 5 Senses
• : Why Empathy Is Crucial to Business Success
• : Use Empathy Maps to build better software

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

Compact display density is a global user interface setting that allows users to view more content on every screen by reducing the amount of space between page elements and aligning the field labels to the left of the fields. Compact display density is suitable for text information-rich Salesforce orgs, such as Cloud Kicks, that want to maximize the use of limited screen space on laptops. Compact display density can be set as the default for the org by the system admins, or chosen by individual users from their profile menu1.

Comfy display density is another global user interface setting that provides a spacious view with labels on the top of fields and more space between page elements. Comfy display density is suitable for orgs that want to emphasize readability and clarity, or that have more complex or interactive fields. Comfy display density is not the best option for Cloud Kicks, as it would reduce the amount of content that can be displayed on each screen1.

Enable collapsible sections is a feature that allows users to collapse or expand sections on a record page layout. Collapsible sections can help users focus on the most relevant information and reduce scrolling. However, collapsible sections are not a global user interface setting, but a page layout option that can be configured by the admins. Collapsible sections can be used in combination with either comfy or compact display density, but they do not affect the alignment of the field labels or the spacing between the page elements2.

References: 1: Personalize Lightning Experience Display 2: Collapsible Sections in Lightning Experience Record Pages

Cloud Kicks (CK) can use the following three solutions to leverage the Salesforce Lightning Design System (SLDS) in its custom applications, without migrating to Lightning Experience:

• Lightning Stylesheets for Visualforce: This solution allows CK to apply the SLDS styles to its existing Visualforce pages, without having to rewrite the markup or use a static resource. By adding the attribute lightningStylesheets="true" to the  tag, CK can automatically transform the standard Visualforce components into their SLDS equivalents, and give the pages a consistent Lightning Experience look and feel12.
• Standard Design Tokens: This solution allows CK to use the SLDS design tokens, which are predefined variables that store the visual design attributes of the SLDS, such as colors, fonts, sizes, and spacing. By using the design tokens, CK can ensure that its custom applications follow the SLDS guidelines and remain consistent with the Lightning Experience theme. CK can access the design tokens through the Lightning Design System Scoping tool, or by downloading them as a static resource3 .
• Heroku: This solution allows CK to build and deploy its custom applications on Heroku, a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. By using Heroku, CK 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. CK can also use the Lightning Out feature to embed Lightning components into its Heroku applications, and use the Lightning Web Components framework to create reusable UI elements .

References:

• [Lightning Stylesheets for Visualforce | Salesforce Trailhead]1
• [Lightning Stylesheets for Visualforce | Salesforce Developers]2
• [Design Tokens | Lightning Design System]3
• [Using Design Tokens | Lightning Aura Components Developer Guide | Salesforce Developers]
• [Build Apps with Lightning Design System | Salesforce Trailhead]
• [Lightning Web Components | Salesforce Developers]

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]

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.