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

Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices. Some of the best practices for responsive design are:
* Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences.
Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc. For example:
@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }
@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and
900px */ }
@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }
* Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser.
It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power. Some of the ways to minimize page weight are:
* Optimize images: Images are often the largest contributors to page weight, so it is important to optimize them for the web. This means choosing the right format, size, resolution, and compression level for each image, as well as using responsive images techniques, such as the srcset and sizes attributes, to deliver the most appropriate image for each device and screen size.
* Implement caching: Caching is a technique that stores a copy of a web page or its resources on the browser or the server, so that they can be reused without having to be downloadedagain. This reduces the amount of data that needs to be transferred and improves the loading time of a web page. Caching can be implemented using HTTP headers, such as Cache-Control and Expires, or using service workers, which are scripts that run in the background and intercept network requests.
* Minify and concatenate files: Minification is a process that removes unnecessary characters, such as whitespace, comments, and formatting, from the code files, such as HTML, CSS, and JavaScript, to reduce their size. Concatenation is a process that combines multiple code files into one, to reduce the number of HTTP requests that the browser needs to make. Both minification and concatenation can help to reduce the page weight and improve the performance of a web page.
* Use a content delivery network (CDN): A CDN is a network of servers that are distributed across different locations and regions, and that store and deliver copies of a web page or its resources to the users. A CDN can help to reduce the page weight and improve the speed of a web page by serving the content from the nearest server to the user, reducing the latency and bandwidth consumption.
The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.
References: Responsive Design: Best Practices and Considerations | Toptal, Responsive design - Learn web development | MDN, The Beginner's Guide to Responsive Web Design in 2023 - Kinsta, Responsive Design Best Practices. by Nick Babich - UX Planet

The Path's Guidance for Success sections can include the following two elements:
* Images and Links: Images and links can be used to provide visual cues and additional resources for the sales representatives. For example, an image of a checklist or a link to a best practice document can help the reps complete the required tasks at each stage. Images and links can be added using the rich text editor in the Path Settings page.
* Rich Text: Rich text can be used to provide text-based guidance, such as tips, reminders, instructions, or motivational messages. For example, a rich text guidance can tell the reps what information they need to gather from the customer or what actions they need to take to move the opportunity forward. Rich text can be formatted using the rich text editor in the Path Settings page. References:
* : Set Up a Path
* : Considerations and Guidelines for Creating Paths
* : Optimize Sales Processes with Path in Salesforce
The two elements that can be used in the Path's Guidance for Success section are Images and Links and Rich Text. Images and Links can be used to provide visual elements to the Guidance for Success section, while Rich Text can be used to provide text-based explanations and instructions. In addition, a Progress Indicator can be used to show the user's progress through the Path.
Images and Links can be used to provide visual elements to the Guidance for Success section. For example, if the user needs to read an article, a link to the article can be included, as well as an image of the article cover.
Similarly, if the user needs to view a video, a link to the video and an image of the video can be included.
Rich Text can be used to provide text-based explanations and instructions. This can include explanations of what the user should be doing at each stage of the Path, as well as any other helpful information.
Finally, a Progress Indicator can be used to show the user's progress through the Path. This can help the user understand where they are in the Path and how far they have left to go.
References:
[1] https://help.salesforce.com/articleView?id=path_guidance.htm&type=5 [2] https://help.salesforce.com/article

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 Salesforce Lightning Design System (SLDS) reflects the patterns and components that underpin the Salesforce product. These patterns and components provide a unified language and consistent look and feel when designing apps and products within the Salesforce ecosystem. The Lightning Experience UI, which SLDS represents, was crafted using four core design principles. We encourage you to keep them in mind as you develop your applications. They are1:
* Clarity - Eliminate ambiguity. Enable people to see, understand, and act with confidence.
* Efficiency - Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.
* Consistency - Create familiarity and strengthen intuition by applying the same solution to the same problem.
* Beauty - Demonstrate respect for people's time and attention through thoughtful and elegant craftsmanship. References: Introduction to the Salesforce Lightning Design System