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 UserZoom 1 .  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], Trailm ix: User Research

[Card Sorting: A Definitive Guide] 1

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

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 prospects 1

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 retention 2 3

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 team 1

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 spend time managing tools and processes for sales reps, which includes customizing and administering Salesforce 1

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

Visual design refers to the use of colors, shapes, typography, images, icons, and other graphical elements to create a visual hierarchy, contrast, balance, and harmony on the page 1 3 .  Visual design affects the user’s perception, emotion, and attention, and can communicate the brand’s personality, tone, and message 1 3 .  For example, Cloud Kicks can use their logo, color scheme, and font to create a recognizable and distinctive visual identity for their portal landing page 4 .

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

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

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

 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

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

In the context of an existing Customer Experience Cloud portal that is already performing well, the goal is to further increase customer engagement by adding elements that encourage in teraction and participation. Recognizing peers with badges is a highly effective way to achieve this because:

Personalization and Gamification: Badges introduce an element of gamification and personalization, which can significantly increase engagement. Users are motivated to participate and contribute to the community when they see a tangible recognition of their efforts and achievements.

Community Building: Recognizing contributions with badges helps in building a stronger community by highlighting active members and encouraging others to contribute. It fosters a sense of belonging and appreciation among users.

While personalized branding (option A) and customizing page layouts (option B) can enhance the user experience, they do not directly incentivize user interaction and contribution as effectively as recognizing contributions through badges does.

A design thinking approach is a human-centered method for solving complex problems and creating innovative solutions. It involves understanding the needs and desires of the users, generating and testing multiple ideas, and iterating on the feedback and results. A design thinking approach can be divided into two types of thinking: divergent and convergent. Divergent thinking is the process of generating many possible solutions to a problem without judging or filtering them. It encourages creativity, exploration, and experimentation. Convergent thinking is the process of evaluating, selecting, and refining the best solution to a problem. It involves analysis, logic, and criteria. Divergent and convergent thinking are complementary and cyclical. They help the designer to expand the solution space and then narrow it down to the most feasible and desirable option. By using both types of thinking, the designer can encourage more creative problem-solving and avoid premature convergence or fixation on a single idea. Therefore, the best approach combination for the UX Designer at Cloud Kicks is divergent and convergent thinking.  References :  Trailhead: Design Thinking ,  Trailhead: Salesforce User Experience Designer Certification Prep ,  Divergent and Convergent Design Thinking

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

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

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

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

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

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

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

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

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