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

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.

 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

The development team missed two features that are causing the problems:

• The With Sharing keyword in Apex classes to enforce sharing rules evaluation. This keyword allows the Apex class to run in the context of the current user and respect the organization’s sharing rules. Without this keyword, the Apex class runs in system mode and ignores the sharing rules, which can result in unauthorized access to records that belong to other users .
• The isAccessible() method in Apex classes to check field accessibility. This method returns true if the current user has read access to the specified field, and false otherwise. Without this method, the Apex class does not check the field-level security settings and can display fields that should be hidden from the user, such as the shipment amount .

References:

• : Using the with sharing or without sharing Keywords
• : Enforcing Sharing Rules in Apex
• : Schema.DescribeFieldResult Class
• : Enforcing CRUD and FLS

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] (https://help.salesforce.com/s/articleView?id=sf.salesforce_app_customize_nav_menu.htm &language=en_US&type=5)

A UX Designer can customize the Salesforce Help Menu to meet the request of providing in-app guidance for key functions and processes for the Cloud Kicks’ Sales team in the following ways:

• Add links to printable tipsheets or training videos: This can help the Sales team to learn and review the key functions and processes at their own pace and convenience. The tipsheets or videos can be hosted on internal or external websites, and can be added to the custom help menu section in the Help Menu settings1. The links can have descriptive labels and icons to make them easy to identify and access.
• Create a just-in-time pop-up content based on new feature rollouts: This can help the Sales team to get familiar with the new features and functionalities that are introduced in the app. The pop-up content can be created using the In-App Guidance Builder2, which allows the UX Designer to define the content type, style, placement, timing, and audience of the pop-up. The pop-up content can include text, images, videos, or links to more resources.
• Provide access to specific Trailhead or MyTrailhead content: This can help the Sales team to gain skills and knowledge on the key functions and processes in a gamified and interactive way. The Trailhead or MyTrailhead content can be customized to match the business goals and branding of Cloud Kicks3. The content can be added to the custom help menu section in the Help Menu settings1, or embedded in the app using the Trailhead Component4.

References:

• Customize the Help Menu in Lightning Experience
• Create In-App Guidance for Your Users
• Customize Your Learning Experience with MyTrailhead
• Add the Trailhead Component to Your App

Adding section headers to a form can improve its readability by breaking it into logical chunks and providing context for the users. Section headers can also help users scan the form and find the information they need faster. Section headers can also reduce the cognitive load and increase the completion rate of the form . References:

• : Salesforce Certified User Experience Designer Exam Guide, Section 3.2: Design for readability and clarity
• : UX Designer Certification Prep: Design for Readability and Clarity, Unit 2: Design for Readability and Clarity

This allows users to quickly scan the form and identify the relevant fields, reducing the cognitive load and improving the overall user experience. Salesforce documentation statesthat “by grouping related fields into sections, you can make your forms easier to read and understand” [1].

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

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

 The two Salesforce features that should be suggested to improve the end-user experience are:

• Favorite the often-used object. This feature allows the users to bookmark the object’s tab and access it quickly from the Favorites menu in the header. This way, the users do not have to search for the object in the App Launcher or switch to a different app to use it.
• Personalize the navigation bar. This feature allows the users to customize the navigation bar in their Lightning app by adding, removing, or reordering the items. This way, the users can add the object they often use to their navigation bar and access it easily from any page in the app.

References:

• : Favorites in Lightning Experience
• : Personalize Your Navigation Bar

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

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 Community Manager is a Salesforce persona who is responsible for creating, managing, and moderating online communities that connect customers, partners, and employees. They spend most of their time engaging with community members, enforcing community standards, and providing member support. A Community Manager aligns with the user who performs similar tasks in moderating forums. References: : Salesforce Personas : Community Manager Roles and Responsibilities

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 design that the UX Designer at Cloud Kicks should use to make the website size and content adapt to the screen size, platform and orientation is responsive. Responsive web design is a web design approach that uses HTML and CSS to automatically resize, hide, shrink, or enlarge, a website, to make it look good on all devices (desktops, tablets, and phones) 1. Responsive web design is not a program or a JavaScript, but a set of best practices that include using media queries, flexible grids, fluid images, and breakpoints to create a layout that can respond to any device being used to view the content 2. Responsive web design is one of the learning objectives for the Salesforce User Experience Designer certification 3. References: [Responsive Web Design Introduction], [Responsive design -Learn web development], [Salesforce Certified User Experience Designer Exam Guide]https://www.w3schools.com/html/html_responsive.asp

https://www.w3schools.com/Css/css_rwd_intro.asp

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

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 here: https://www.salesforce.com/blog/2020/11/what-is-inclusive-design.html.

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

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

 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 tool to install that the UX Designer needs is the Sketch plugin. This plugin allows the designer to quickly mock up Salesforce user interface experiences using a collection of prebuilt components, such as base components, tokens, design patterns, and more. The plugin also provides access to the Salesforce Lightning resources for their design and prototype, such as icons, fonts, colors, and images. The plugin is compatible with Sketch, a popular design tool for creating user interfaces.

References:

• : Salesforce Lightning Design System
• : Sketch Plugin

 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

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

 Usability testing is a type of testing that evaluates how easy and intuitive a product or service is to use by observing real users performing specific tasks. Usability testing can help the UX Designer to measure the effectiveness, efficiency, and satisfaction of the new form for the call center staff. Usability testing can also help to identify any usability issues or areas for improvement in the form design. Usability testing can be conducted in various ways, such as moderated or unmoderated, remote or in-person, qualitative or quantitative, or using various tools and methods12. References:

• Usability Testing
• Usability Testing Methods

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 discovery process is a crucial phase in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1. The discovery process 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 process are artifacts that synthesize and communicate the findings and insights from the research. Some of the common outputs of the discovery process are:

• User personas: These are fictional representations of the target users, based on real data and insights, that describe their goals, motivations, pain points, behaviors, and preferences3. User personas help to empathize with the users and design solutions that meet their needs and expectations.
• Journey maps: These are visualizations of the user’s end-to-end experience with a product or service, from the initial trigger to the final outcome4. Journey maps help to identify the user’s actions, thoughts, emotions, pain points, and opportunities for improvement at each stage of the journey.
• High-level wireframes: These are low-fidelity sketches or diagrams that show the basic layout, structure, and functionality of the website or app. High-level wireframes help to define the information architecture, navigation, and content hierarchy of the solution, as well as test the usability and feasibility of the design concepts.

These three outputs are essential for planning out the website redesign using Experience Cloud, as they help to define the user requirements, the user flow, and the user interface of the solution. The other two options, interactive prototypes and high-fidelity mock-ups, are not outputs of the discovery process, but rather of the design and testing phases. Interactive prototypes are clickable simulations of the website or app that allow users to interact with the functionality and features of the solution. High-fidelity mock-ups are realistic and detailed representations of the website or app that show the final look and feel of the solution, including the colors, fonts, images, and icons. These two outputs are created after the discovery process, based on the feedback and validation from the user testing sessions.

References: UX Discovery Process: A Complete Guide, UX Research Methods: How to Uncover Valuable Insight about your Users, User Persona: What It Is and How to Create One, Journey Mapping101, [Wireframes: A Beginner’s Guide], [Prototyping 101: The Difference between Low-Fidelity and High-Fidelity Prototypes and When to Use Each], [What is a Mockup? The Final Layer of UI Design]

For the UX Designer at Cloud Kicks, thethree outputs of the discovery process that should be prepared are User Personas, Journey Maps, and High-Level Wireframes. User Personas are fictional characters that represent a target audience for the website, and are used to help guide the website design. Journey Maps are diagrams that illustrate the user's experience as they navigate the website, and provide insights into how the user interacts with the website. High-Level Wireframes are simple sketches of the website layout, and are used to organize the website's content and design elements. Interactive Prototypes and High-Fidelity Mock-ups are not necessary outputs of the discovery process, as they are more detailed representations of the design that come later in the design process. For more information, see the Salesforce Experience Cloud documentation (https://help.salesforce.com/articleView?id=experience_cloud_overview.htm &type=5).

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.

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

 Inviting developers to user testing is a good way to help them see the value of the design changes and understand the user needs and pain points. User testing is a method of evaluating a product or service by observing how real users interact with it and collecting feedback. By witnessing the user testing sessions, developers can see how the design changes improve the user experience, such as increasing usability, satisfaction, engagement, or conversion. User testing can also help developers empathize with the users and collaborate better with the designer. References:

• [User Testing]

 Diversity, inclusion, and equality in design are values that can lead to positive business outcomes, such as less employee turnover, greater market share, and economic growth. These values can help create a more inclusive and innovative workplace, where employees feel valued, respected, and engaged, and where customers feel understood, represented, and satisfied. Some of the benefits of these values are:

• Less employee turnover: Diversity, inclusion, and equality in design can reduce employee turnover by fostering a culture of belonging, trust, and collaboration, where employees can thrive and grow. According to a Salesforce report1, employees who feel a sense of belonging at work are 5.3 times more likely to feel empowered to perform their best work, and employees who feel their voice is heard at work are 4.6 times more likely to feel empowered to perform their best work. Moreover, employees who feel valued and included are more likely to stay loyal to their employer, reducing the costs and risks of hiring and training new staff.
• Greater market share: Diversity, inclusion, and equality in design can increase market share by expanding the customer base, enhancing the customer experience, and improving the brand reputation. According to a McKinsey report2, companies in the top quartile for ethnic and cultural diversity on executive teams were 36% more likely to experience above-average profitability than companies in the fourth quartile. Moreover, companies that design products and services that meet the needs and preferences of diverse customers can gain a competitive edge and increase customer loyalty and retention.
• Economic growth: Diversity, inclusion, and equality in design can contribute to economic growth by boosting productivity, innovation, and social impact. According to a World Bank report3, increasing women’s labor force participation and earnings could add $172 trillion to global wealth. Moreover, companies that leverage the diverse perspectives and experiences of their employees can generate more creative and effective solutions, and companies that support social causes and environmental sustainability can create positive change and attract more customers and investors.

References:

• [Our 2023 Annual Equality Update: Where We Are and Where We’re Going - Salesforce]1
• [Diversity wins: How inclusion matters | McKinsey]2
• [Women, Business and the Law 2020 | World Bank]3

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 CSS framework that helps designers and developers create applications with the look and feel of Lightning Experience. SLDS provides a library of design tokens, icons, components, utilities, and patterns that can be used to build consistent, responsive, and accessible user interfaces1. One of the features that SLDS provides for designers and developers is semantic and accessible component markup. Semantic markup means using HTML elements that describe the meaning and structure of the content, rather than just the presentation. For example, using 

 for a main heading, 

 for a paragraph, or  for a button. Semantic markup helps to improve the readability, maintainability, and SEO of the code2. Accessible markup means using HTML attributes and techniques that enhance the usability and accessibility of the content for people with disabilities. For example, using aria-label to provide a descriptive label for an element, role to indicate the function of an element, or tabindex to control the keyboard focus order. Accessible markup helps to ensure that the content can be perceived, understood, operated, and interacted with by people using assistive technologies, such as screen readers, keyboards, or voice commands3. SLDS provides semantic and accessible markup for its components, which are reusable UI elements that can be customized and composed to create complex interfaces. SLDS components follow the Web Content Accessibility Guidelines (WCAG), which are the international standards for web accessibility4. SLDS components also use the BEM (Block Element Modifier)naming convention, which is a methodology for creating clear and consistent class names for CSS selectors5. By using SLDS components, designers and developers can create user interfaces that are not only visually appealing, but also meaningful and accessible for everyone. References: Introduction to the Salesforce Lightning Design System, Semantic HTML: How to Structure Web Pages, Accessible Rich Internet Applications (WAI-ARIA), Web Content Accessibility Guidelines (WCAG) Overview, BEM — Block Element Modifier

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

To document user goals, common tasks, and pain points for a new service experience, the tool that a UX Designer should use is user personas. User personas are fictional representations of the target users, based on real data and research. User personas help the designer to understand the needs, motivations, behaviors, and expectations of the users, as well as their challenges and frustrations. User personas can also help the designer to prioritize features, create scenarios, and design solutions that are relevant and meaningful for the users. References: : UX Designer Certification Prep: Designing for User Research | Trailhead : User Personas | Salesforce Developer Guide

 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]

A UX Designer should take the following steps to create and deliver responsible and transparent AI technology12:

• C. Document model cards to clarify intended context and use cases. Model cards are standardized documents that provide essential information about a machine learning model, such as its purpose, performance, limitations, and ethical considerations3. Model cards can help UX Designers to communicate the design choices and trade-offs of their AI systems, and to ensure that they are aligned with the user needs and expectations4.
• D. Provide clear explanations of AI predictions or recommendations. Explanations are user-facing descriptions of how and why an AI system produces a certain output, such as a prediction, a recommendation, or a decision5. Explanations can help UX Designers to increase the transparency and trustworthiness of their AI systems, and to empower users to understand, control, and evaluate the AI outcomes6.

References: Salesforce Debuts AI Ethics Model: How Ethical Practices Further Responsible Artificial Intelligence, Generative AI: 5 Guidelines for Responsible Development - Salesforce, Model Cards for Model Reporting, Model Cards: A Framework for Increasing Trust in AI Systems, Explainable AI: A Guide for Making Black Box Machine Learning Models Explainable, Salesforce Supports AI Regulation Advancing Digital Trust and Innovation - Salesforce

C. Document model cards to clarify intended context and use cases.

Model cards are documents that describe the intended use, performance, and limitations of AI models. They help ensure that the AI technology is being used responsibly and transparently, as they provide clear information about the model's context, data, and assumptions. This can help reduce the risk of unintended consequences and build trust with users.

D. Provide clear explanations of AI predictions or recommendations.

Clear explanations of AI predictions or recommendations help build trust with users and increase understanding of how the AI technology works. By providing an understandable explanation of how a prediction or recommendation was made, users can gain a better understanding of the technology and how it is intended to be used. This can also help reduce the risk of unintended consequences and improve accountability.

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

 Two best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement are:

• Find the closest Salesforce Lightning Design System (SLDS) Blueprint to help inform the custom Lightning component. The SLDS is a collection of design guidelines, UI components, and code samples that help you create consistent and beautiful user interfaces for Lightning applications. The SLDS Blueprints are examples of common UI patterns and components that are built with the SLDS and follow the design principles and best practices. The Blueprints can help you inform the custom Lightning component by providing inspiration, guidance, and code snippets that you can modify and reuse. The Blueprints can also help you ensure that the custom Lightning component is compatible and consistent with the rest of the Lightning application and the Salesforce platform. [UX Designer Certification Prep: Salesforce Design System], Lightning Design System Website
• Exhaust the list of available base Lightning components in the Component Library. The base Lightning components are a set of pre-built UI components that you can use to create custom Lightning components. The base Lightning components are built with the SLDS and provide the functionality and interactivity that you need for common UI elements, such as buttons, icons, forms, tables, charts, and more. The base Lightning components also handle the accessibility, security, and performance aspects for you, so you don’t have to worry about them. The Component Library is a reference guide that provides documentation and examples for the base Lightning components, as well as other Lightning web components and Aura components. The Component Library can help you explore the list of available base Lightning components and see how they work and how to use them. The Component Library can also help you avoid reinventing the wheel and save time and effort by using the base Lightning components as much as possible, and only creating custom Lightning components when there is no suitable base Lightning component for your requirement. [UX Designer Certification Prep: User Testing and Evaluation], Developer Center’s Lightning Component Library

Prioritizing Aura markup even if there is a Lightning Web Component (LWC) available, and creating HTML markup and linking the SLDS stylesheet via static resource are not best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement. These practices can lead to suboptimal performance, maintainability, and compatibility issues for the custom Lightning component. Aura markup is the older syntax for creating Aura components, which are the predecessor of Lightning web components. Lightning web components are the newer and faster way of creating custom UI components for Lightning applications, using modern web standards and best practices. Lightning web components also have better interoperability and compatibility with Aura components and other web components, as well as with the base Lightning components and the SLDS. Therefore, it is recommended to use Lightning web components over Aura components whenever possible, and to use LWC markup instead of Aura markup for creating custom Lightning components. [UX Designer Certification Prep: User Testing and Evaluation], Lightning Web Components Developer Guide

Creating HTML markup and linking the SLDS stylesheet via static resource is also not a recommended practice for creating custom Lightning components, because it can create unnecessary complexity and duplication for the custom Lightning component. A static resource is a file or a collection of files that can be referenced by a Lightning component, such as images,style sheets, JavaScript libraries, or fonts. However, linking the SLDS stylesheet via static resource means that you have to manually download and upload the SLDS files to your org, and update them whenever there is a new version of the SLDS. This can create maintenance and compatibility issues for the custom Lightning component, as

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]

 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 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)

To provide more intuitive access to regularly used content, a sales representative can use the following two recommendations:

• Personalize the Navigation bar: The Navigation bar is the horizontal menu at the top of the Lightning Experience page that allows users to switch between different items, such as apps, objects, or utilities. Users can personalize the Navigation bar by adding, removing, or rearranging items according to their preferences and needs. For example, a sales representative can add the Accounts, Opportunities, and Reports items to the Navigation bar for quick access. To personalize the Navigation bar, users can click on the pencil icon next to the app name and use the Edit option.
• Create shortcuts Favorites: Favorites are bookmarks that users can create to save links to frequently accessed pages, records, reports, dashboards, or groups in Salesforce. Users can create favorites by clicking on the star icon in the header of any page. Users can also organize their favorites into folders and access them from any device. To view or manage favorites, users can click on the Favorites icon in the header. Favorites can help users save time and navigate Salesforce more efficiently.

 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

 A journey map is a visual representation of the steps, emotions, and pain points that a user goes through when interacting with a product or service. A journey map can help the UX Designer understand the user’s needs, goals, expectations, and frustrations, and identify opportunities for improvement or innovation12

Creating a journey map together with employees from different departments is a strategy that can strengthen employee relationships the most, because it can:

• Foster collaboration and communication: Inviting employees from different departments to create a journey map can help them share their perspectives, insights, and ideas, and learn from each other. This can also help them align on a common vision and goal, and build trust and respect among the team members34
• Increase engagement and ownership: Inviting employees from different departments to create a journey map can help them feel more involved and invested in the design process and the outcome. This can also help them develop a sense of ownership and responsibility for the product or service, and increase their motivation and satisfaction34
• Enhance creativity and innovation: Inviting employees from different departments to create a journey map can help them generate more diverse and creative solutions, as they can leverage their different skills, experiences, and backgrounds. This can also help them challenge their assumptions and biases, and explore new possibilities and opportunities34
• Create a first draft in a design team and then share it for feedback with employees: This is not a strategy that can strengthen employee relationships the most, because it can create a sense of exclusion and hierarchy among the employees. The design team may appear to be the sole authority and decision-maker, while the other employees may feel like passive observers or critics. This can also limit the diversity and quality of the feedback, as the employees may not have enough context or understanding of the design process and the user’s needs34
• Send an anonymous survey to collect ideas from across the whole company: This is not a strategy that can strengthen employee relationships the most, because it can reduce the interaction and connection among the employees. An anonymous survey may not allow the employees to express their thoughts and feelings fully, or to receive any feedback or recognition for their contributions. This can also make the employees feel detached and indifferent about the design process and the outcome34

References:

• Create a Journey Map Unit | Salesforce Trailhead
• How to Create a Customer Journey Map - UX Mastery
• How to Use Journey Mapping to Improve Employee Engagement
• How to Use Journey Mapping to Drive Collaboration and Innovation

These three methods would deliver a branded experience for a customer who has strict requirements to stay focused on out-of-the-box styling and components only. They are all features of the Builder tool, which is a drag-and-drop interface that allows users to create and customize websites without coding. By using these methods, a UX Designer can create a consistent and appealing visual identity for the customer’s site, as well as showcase their brand values and personality.

• Select a footer and configure which social media links to display: The footer is the bottom section of a web page that usually contains information such as contact details, terms and conditions, privacy policy, and social media links. By selecting a footer component from the Builder library, a UX Designer can easily add and configure the social media links that the customer wants to display on their site. This can help the customer connect with their audience, increase their brand awareness, and drive traffic to their social media platforms.
• Select a theme and customize content including copy and imagery: A theme is a predefined set of design elements, such as colors, fonts, and layouts, that can be applied to a website to give it a consistent and professional look. By selecting a theme from the Builder library, a UX Designer can quickly create a site that matches the customer’s brand identity and preferences. A UX Designer can also customize the content of the site, such as the copy and imagery, to make it more relevant and engaging for the customer’s target audience.
• Use the theme editor to adjust fonts, text case, colors, and site logo: The theme editor is a feature of the Builder tool that allows users to fine-tune the appearance of their site by adjusting various design elements, such as fonts, text case, colors, and site logo. By using the theme editor, a UX Designer can create a site that reflects the customer’s brand personality and style, as well as enhance the readability and usability of the site. A UX Designer can also upload the customer’s site logo, which is a graphical representation of their brand name or symbol, to increase their brand recognition and credibility.

References:

• Builder Overview
• Create a Site with Builder
• Customize Your Site with the Theme Editor

 The two UX design principles that are key to creating excellent mobile user experiences are:

• Consistency across device experiences. This means that the design of a mobile app or website should match the design of the desktop version, as well as other platforms and devices. Consistency helps users to recognize and trust the brand, as well as to navigate and use the product more easily. Consistency also reduces the cognitive load and confusion for users who switch between different devices12
• Prioritization of content and UI elements on the screen. This means that the design of a mobile app or website should focus on the most important and relevant information and actions for the user, and eliminate or minimize the unnecessary or secondary ones. Prioritization helps users toachieve their goals faster and more efficiently, as well as to avoid distractions and clutter. Prioritization also improves the readability and usability of the product on smaller screens34

References: [Mobile UX Design: The Comprehensive Guide — updated 2023], [Mobile UX design principles and best practices], [Mobile UX Design: The Ultimate Guide 2023 - Bluespace], [Mobile UX Design: Key Principles. by Nick Babich - UX Planet]

https://uxcam.com/blog/mobile-ux/ https://uxplanet.org/mobile-ux-design-key-principles-dee1a632f9e6

To make the agent experience more efficient when handling cases submitted from their web form, two possible ways are to use Salesforce Flow and to complete relevant information about the customer using Lightning Record Pages. Salesforce Flow is a tool that allows the designer to automate business processes by creating guided, visual workflows. Flows can help agents to complete fields required for case closure by providing them with screens, logic, and actions that guide them through the process. Lightning Record Pages are customizable layouts that display information about a specific record, such as a case or a customer. Record pages can help agents to access and update relevant information about the customer using components, tabs, and related lists. Record pages can also be personalized for different profiles, roles, and app contexts. References: : Flow Builder | Salesforce Help : UX Designer Certification Prep: Designing with Flow Builder | Trailhead : Lightning Record Pages | Salesforce Help : UX Designer Certification Prep: Designing with Lightning Record Pages | Trailhead

Experience Cloud is the best cloud to design an appropriate solution for Cloud Kicks’ users. Experience Cloud allows the business to create an external facing site where users can manage and submit cases via the web, browse and search Knowledge Base articles, and contact Support via live chat. Experience Cloud also provides branding options, personalization features, and collaboration tools to enhance the user experience and engagement. Experience Cloud integrates with Service Cloud, which is the cloud that provides the case management, knowledge base, and live chat functionalities. Therefore, Experience Cloud is the cloud that enables the design of the user interface, while Service Cloud is the cloud that enables the backend service processes. References: [Experience Cloud Overview] (https://www.getapp.com/operations-management-software/a/salesforce-1-service-cloud/compare/salesforce-community-cloud/), [Service Cloud Overview] (https://titandxp.com/salesforce-experience-cloud-vs-service-cloud/)

Lightning console apps are designed to help users work faster and more efficiently by providing a workspace where they can access multiple records and their related records on the same screen. Users can complete actions with a single click, such as creating records, logging calls, sending emails, and updating fields, without losing context or switching tabs. Lightning console apps also support keyboard shortcuts, macros, and quick text to speed up common tasks. Lightning console apps are especially useful for sales representatives who need to provide quick, competitive pricing and close deals faster. They can also use Lightning console apps to view and manage their pipeline, collaborate with team members, and track their performance. Organizing items in the utility bar and adding records to Favorites are features that are available in any Lightning app, not just Lightning console apps. References: Salesforce Console in Lightning Experience, Create and Edit a Custom Lightning Console App, Create a Lightning Console App

When interviewing or surveying users, the UX designer should be aware of the following response biases that can affect the accuracy of the data collected:

• Social desirability bias: This is the tendency of respondents to answer questions in a way that they think will make them look good or conform to social norms and expectations. For example, when asked about their purchasing habits, respondents may underreport their spending on luxury items or impulse buys, or overreport their spending on charitable causes or environmentally friendly products. Social desirability bias can be reduced by ensuring anonymity and confidentiality, using indirect or less sensitive questions, or using implicit measures12.
• Recency bias: This is the tendency of respondents to recall and emphasize the most recent events or experiences, rather than the ones that occurred earlier or more frequently. For example, when asked about their purchasing habits, respondents may base their answers on their last purchase or the last month, rather than their average or typical behavior over a longer period of time. Recency bias can be reduced by using specific and clear time frames, using multiple sources of data, or using longitudinal methods34.

References:

• : [What Is Response Bias? | Definition & Examples]
• : [Types of User Research Bias and How to Avoid It in Your UX Design]
• : [Social Desirability Bias: Definition, Examples, and Solutions]
• : [Recency Bias: Definition, Examples, and Solutions]
• : [Recency Bias in User Research]
• : [Social Desirability Bias in Survey Research]

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 designing the experience for a 'Case Solver' user persona, especially in the context of Cloud Kicks' Service Cloud instance, the activities to consider should revolve around the primary responsibilities and tasks of this role. For a Case Solver, these would include:

• Troubleshooting customer issues:This involves identifying, analyzing, and solving problems reported by customers. The design should facilitate easy access to relevant information, tools for effective problem-solving, and a seamless workflow for diagnosing issues.
• Logging activities:Keeping a detailed record of interactions, solutions provided, and any follow-up actions is crucial. The user interface should support efficient logging and tracking of activities to ensure accountability and facilitate continuous improvement in customer service.

While training other agents and editing knowledge articles (option B) and viewing the status of cases and analyzing campaign metrics (option C) are important in certain contexts, they do not directly align with the core activities of a Case Solver persona focused on direct customer support and problem resolution.

References:Salesforce's own documentation, such as the Salesforce Service Cloud User Guide, provides insights into designing user experiences for specific roles within the platform. It offers best practices and recommendations for optimizing the interface and workflows for various user personas, including those involved in case management and customer support.

 To create a unique experience for each audience that includes colors, images, and typography, the recommended out-of-the-box design approach is to use branding sets and assign them to each audience using audience targeting. Branding sets are collections of branding attributes, such as logos, fonts, colors, and images, that can be applied to a site or a page to customize its look and feel. Audience targeting is a feature that allows the designer to deliver different content and experiences to different groups of users based on criteria such as profile, location, or behavior. By creating branding sets and assigning them to each audience using audience targeting, the designer can easily create aunique and consistent experience for each audience without creating separate sites or custom themes. References: : Branding Sets | Salesforce Help : Audience Targeting | Salesforce Help : UX Designer Certification Prep: Designing with Experience Builder | Trailhead

The best approach for Cloud Kicks to create a unique look and feel for each audience is to create branding sets and assign them to each audience using audience targeting. With this approach, the same website can be used for both audiences, whilethe look and feel of each page can be tailored to each audience.

Branding sets allow you to create unique designs and apply them to specific audiences. You can create unique colors, images, and typography for each audience and then target them to the appropriate audiences using the audience targeting feature. This will ensure that each audience has a unique look and feel that meets their needs.

References: [1] https://help.salesforce.com/articleView?id=siteforce_editing_audience_targeting.htm &type=5 [2] https://help.salesforce.com/articleView?id=siteforce_branding_sets.htm &type=5 [3] https://help.salesforce.com/articleView?id=siteforce_creating_branding_sets.htm &type=5

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

 An Enablement Site is a custom-branded site that allows users to access learning content, such as modules, trails, and trailmixes, from Trailhead. It also allows admins to create and assign custom modules that are specific to their organization’s needs and goals. An Enablement Site can be used to gamify the learning experience by adding badges, points, and leaderboards. An Enablement Site can also provide analytics and reports on the learners’ progress and performance. Therefore, an Enablement Site is the best option for Cloud Kicks to create a gamified learning content for its internal users and leadership, as well as a custom product training. References:

• [Trailhead: Enablement Site Basics]
• [Trailhead: Create Custom Modules for Your Enablement Site]
• [Trailhead: Gamify Your Enablement Site]

The designer should describe SLDS styling hooks as custom CSS properties that can easily style base and custom components. Styling hooks are placeholders in the SLDS style sheet that allow developers to customize the look and feel of their Lightning components by using the corresponding CSS custom properties. For example, the developer can change the background color of a button by setting the value of the --slds-c-button-brand-color-background custom property. Styling hooks are especially useful when working with web components and shadow DOM, as they enable component-level customizations without affecting the global styles. Styling hooks also provide consistency and performance benefits, as they leverage the SLDS design tokens and the native browser support for CSS custom properties. References:

• : Styling Hooks - Lightning Design System
• : SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers
• : SLDS Styling hooks in Lightning web components - Forcetrails

The designer should describe the Salesforce Lightning Design System (SLDS) styling hooks as using standard CSS properties to easily style base and custom components. SLDS styling hooks allow developers to quickly and easily apply CSS classes to HTML elements, enabling consistent styling across both base and custom components. This allows developers to quickly and easily apply branding and styling to their Lightning Web Components, without needing to write custom CSS. For more information about SLDS styling hooks, please see the following Salesforce documentation: https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styles_hooks

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 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 human-centered design process is a creative approach to solving people’s problems that begins with identifying their needs and ends with creating solutions that meet those needs1. A human-centered design process typically involves the following steps in this order23:

• Observation: This step involves researching and understanding the users, their context, their goals, their pain points, and their behaviors. Observation methods include interviews, surveys, ethnography, contextual inquiry, and data analysis.
• Ideation: This step involves generating and exploring a wide range of possible solutions that address the users’ needs and problems. Ideation methods include brainstorming, sketching, mind mapping, affinity diagramming, and storyboarding.
• Prototyping: This step involves creating and testing low-fidelity or high-fidelity representations of the proposed solutions, such as mockups, wireframes, or interactive models. Prototyping methods include paper prototyping, digital prototyping, and rapid prototyping.
• User Feedback: This step involves collecting and analyzing feedback from the users on the prototypes, such as their opinions, preferences, satisfaction, and suggestions. User feedback methods include usability testing, user testing, focus groups, and surveys.
• Iteration: This step involves refining and improving the prototypes based on the user feedback, and repeating the prototyping and user feedback steps until the optimal solution is achieved. Iteration methods include agile development, design sprints, and A/B testing.
• Implementation: This step involves deploying and launching the final solution to the users, and monitoring and evaluating its performance and impact. Implementation methods include release management, change management, and analytics.

References: Relationship Design - Trailhead, Human-Centered Design: Definition and Stages - Interaction Design Foundation, Human-Centered Design Process - Salesforce UX

The order in which CK's UX Designer should undertake the steps of the human-centered design process to achieve maximum impact is Observation > Ideation > Prototyping > User Feedback > Iteration > Implementation. This allows the designer to take into account the user’s preferences and needs from the very beginning, as well as provide the user with feedback throughout the entire process. The order of steps for a human-centered design process is as follows:

• Observation: Observing user behaviour and interactions to gain insights into their needs and preferences.
• Ideation: Coming up with ideas for potential solutions based on the insights from the observation phase.
• Prototyping: Creating a prototype of the potential solution to test out with users.
• User Feedback: Gathering feedback from users on the prototype and making changes based on their feedback.
• Iteration: Iterating on the prototype based on the feedback from users.
• Implementation: Implementing the final solution.

For more information on the human-centered design process, please see the following Salesforce documentation: https://trailhead.salesforce.com/en/content/learn/modules/ux_design_process

Diversity, inclusion, and equality in design are values that aim to create products, services, and environments that are accessible, welcoming, and fair for all people, regardless of their age, gender, ethnicity, disability, sexual orientation, religion, or other characteristics. Diversity, inclusion, and equality in design can also bring positive business outcomes, such as economic growth, greater market share, and less employee turnover12.

Economic growth is a business outcome that represents the increase in the value of goods and services produced by an organization or a country over time. Economic growth can be influenced by various factors, such as innovation, productivity, efficiency, and competitiveness. Diversity, inclusion, andequality in design can contribute to economic growth by fostering creativity, innovation, and problem-solving, as well as by attracting and retaining diverse talent, customers, and partners12.

Greater market share is a business outcome that represents the percentage of sales or customers that an organization has in a particular market or industry. Greater market share can indicate the success and competitiveness of an organization, as well as its potential for growth and profitability. Diversity, inclusion, and equality in design can help achieve greater market share by expanding the reach and appeal of products, services, and environments to diverse and underserved markets, as well as by enhancing customer satisfaction, loyalty, and advocacy12.

Less employee turnover is a business outcome that represents the rate at which employees leave an organization and are replaced by new ones. Less employee turnover can indicate the stability and quality of an organization, as well as its ability to retain and develop its human capital. Diversity, inclusion, and equality in design can help reduce employee turnover by creating a positive and inclusive work culture, where employees feel valued, respected, and engaged, as well as by providing opportunities for learning, development, and career progression12.

References: 1: The business value of design | McKinsey 2: The Business Case for Diversity, Equity, and Inclusion - Salesforce.com

 Screen flow is a Salesforce functionality that allows the UX Designer to create interactive workflows for the users with just a few clicks. With screen flow, the UX Designer can create step-by-step workflows that include screens for data entry, decision points based on user input, and automated actions based on their responses. Screen flow can make the user experience more engaging by presenting the users with what they need, when they need it, and using their input to guide them and automate their tasks. Screen flow can also be customized and embedded in various ways, such as on a Lightning page, a button, a utility bar, or an Experience Cloud page123

• Lightning Survey is a Salesforce functionality that allows the UX Designer to create and distribute surveys to collect feedback from customers, employees, or partners. Lightning Survey is not suitable for creating complex processes or workflows, but rather for measuring satisfaction, loyalty, or engagement4
• Process Builder is a Salesforce functionality that allows the UX Designer to create and automate business processes without code. Process Builder can perform actions based on criteria, such as updating records, sending emails, or invoking flows. Process Builder is not suitable for creating interactive workflows with screens, but rather for automating background tasks5

References:

• Get Started with Screen Flows Unit | Salesforce Trailhead
• How to Create a Salesforce Screen Flow | Salesforce Ben
• 5 Ways to Get Started with Screen Flows - Salesforce Admins
• Create and Distribute Surveys with Salesforce Feedback Management
• Automate Your Business Processes with Process Builder

The Web Content Accessibility Guidelines (WCAG) are a set of standards that aim to make web content more accessible to people with disabilities. The WCAG are organized by four principles, which state that content must be:

• Perceivable: Users must be able to perceive the information and user interface components in ways they can sense, such as through sight, hearing, or touch.
• Operable: Users must be able to interact with the user interface components and navigate the content using various input methods, such as keyboard, mouse, voice, or gesture.
• Understandable: Users must be able to comprehend the information and the operation of the user interface, which means that the content must be clear, consistent, and predictable.
• Robust: Users must be able to access the content using a wide range of technologies, including different browsers, devices, and assistive tools, which means that the content must be compatible with current and future web standards. References: WCAG 2 Overview, Understanding the Web Content Accessibility Guidelines

The Console is a tab-based workspace that allows users to access multiple records and related information on a single screen. This can help users who need to switch between different records quickly and easily, without losing context or wasting time. For example, a salesperson who needs to compare different opportunities, check account details, or update contact information can benefit from using the Console. The Standard Salesforce Navigation, on the other hand, only allows users to open one record at a time, which can be limiting for some use cases. References: : Salesforce Console : Explore the Service Console

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