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

The best onboarding design practice for Cloud Kicks would be to identify the message, audience, and purpose for content. This would help them tailor the content to the different needs and preferences of their employees, and provide them with the most relevant and useful information. Providing written help documentation as the single source of truth for learning about new features (A) might not be engaging or effective for all users, especially those who prefer visual or interactive learning. Creating pop-ups to give users a full visualization of a product © might be intrusive or overwhelming for some users, and might not explain the benefits or features of the product clearly. Identifying the message, audience, and purpose for content (B) is a key step in creating user-centered onboarding design, as it helps to define the goals, scope, and tone of the content, and to align it with the user’s needs, expectations, and motivations.  References :

[UX Designer Certification Prep: Onboarding Design]

[UX Designer Certification Prep: Content Strategy]

[Salesforce Certified User Experience Designer Exam Guide]

 When the organization-wide default for Accounts is private, users can only access the accounts they own or are explicitly shared with them.  However, when the organization-wide default for Opportunities is private, users can access the opportunities they own, are explicitly shared with them, or are associated with accounts they can access 1 . Therefore, when ownership-based sharing rules are created for each team to grant access to opportunities owned by their team members, the sales reps on the same team will also have Read access to the accounts for those opportunities.  This is because the sharing rules for opportunities automatically grant access to the parent accounts 2 .  However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities 3 . The sales reps will also not have access to all accounts or all opportunities, only those that are owned by their team members or themselves.  References :  Sharing Records Owned by High-Volume Portal Users | Salesforce Security Guide ,  Sharing Rules | Salesforce Security Guide ,  Create Owner-Based Sharing Rules | Salesforce Security Guide

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

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

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 .

A sketch plugin is a tool that allows the UX designer to quickly mock up Salesforce user interface experiences using the Lightning Design System (SLDS) resources, such as base components, tokens, and design patterns. The sketch plugin is a free plugin for Sketch, a design toolkit that helps create wireframes, mockups, sample screens, and more. With the sketch plugin, the designer can search and drag the prebuilt components from the plugin into the canvas, and export the mockups as pdf, jpeg, or png files. The sketch plugin also supports synonyms and variants for the components, making it easier to find and use the desired elements.  The sketch plugin can be downloaded from the SLDS website 1  or from the AppExchange 2 .  References :

[Create Quick Salesforce UI Mockups: Lightning Design System Plugin for Sketch] 1

[Lightning Design System Sketch Plugin] 2

The Salesforce Lightning Design System (SLDS) provides component blueprints that will ensure consistency for Cloud Kicks’ functional components. Component blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. They follow the design guidelines, accessibility standards, and best practices of Lightning Experience. They also include variants, states, and modifiers to handle different use cases and scenarios. By using component blueprints, Cloud Kicks can create functional components that are consistent with the look and feel of Lightning Experience without writing custom code or CSS.  References :

Component Blueprints

Introduction to the Salesforce Lightning Design System

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

[Salesforce Certified User Experience Designer Exam Guide], Section 2.2: Design and test prototypes

[UX Designer Certification Prep: Prototyping], Unit 2: Wireframes and Prototypes

[Prepare for Your UX Designer Credential], Trailmix: Prototyping

 To improve the experience of the service team at Cloud Kicks, their UX Designer should do the following 1 2 :

B. Share list views to Public Groups and only add relevant users. This will help to organize and manage the list views based on the roles and responsibilities of the service team members, and to avoid cluttering their list view menu with unnecessary or irrelevant list views.  Public Groups are collections of users, roles, or other groups that can be used to share list views, reports, dashboards, and other records 3 .

C. Remove irrelevant public list views. This will help to reduce the number of list views available, and to make it easier for the service team members to find the relevant ones. Irrelevant public list views are those that are outdated, duplicated, unused, or not applicable to the service team’s needs or goals.

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