User-Experience-Designer Reviews Questions

The usability of accordion elements in a mobile environment could be improved by expanding the first section by default. This is because it can provide the user with a clear indication of what kind of content is hidden in the accordion, and encourage them to explore the rest of the sections1. Expanding the first section by default can also reduce the user’s cognitive load, as they do not have to make a decision on which section to open first2. Moreover, expanding the first section by default can improve the accessibility of the accordion, as it can help screen reader users to understand the structure and purpose of the widget3.

Using the Back browser button to collapse content is not a good option, as it can confuse the user and break the expected browser behavior. The Back button is meant to navigate to the previous page, not to collapse an accordion section4. Using the Back button to collapse content can also create navigation issues, as the user might lose their current page or state4.

Moving an expanded section to the top of the screen is also not a good option, as it can disrupt the user’s spatial memory and orientation. Moving an expanded section to the top of the screen can change the order and position of the accordion sections, which can make it harder for the user to find and access the section they want5. It can also create a jarring and inconsistent user experience, as the user might not expect the content to move around the screen5.

References:

• How to design the perfect accordion
• Accordions: Design guidelines
• Accessible Accordion - examples and best practices | Aditus
• Don’t Use The Back Button To Modify Data
• Usability of a mobile navigation consisting mostly of accordions?

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 best option for guiding sales users through a new process using floating or docked prompts is to use the Walkthrough App from AppExchange. This app allows admins to create and manage in-app guidance walkthroughs using clicks, not code. Walkthroughs are interactive tutorials that guide users through a series of steps on a Lightning page. Users can see the prompts, click the action buttons, and follow the instructions to complete the process. Admins can also track the engagement and completion of the walkthroughs using reports and dashboards. The Walkthrough App is compatible with the standard in-app guidance feature, and does not require a subscription to myTrailhead1 .

The other options are not suitable for this scenario because:

• In-App Guidance Prompts using myTrailhead: This option requires a subscription to myTrailhead, which is a customizable learning platform that allows admins to create their own content and branding. In-app guidance prompts are one of the features of myTrailhead, but they are not the same as walkthroughs. Prompts are single-step messages that appear on a Lightning page, while walkthroughs are multi-step tutorials that guide users through a process. Prompts can be used to provide tips, announcements, or links, but they cannot show users how to perform a task234.
• Custom build using Salesforce Flow: This option requires coding and development skills, which may not be available or feasible for the admin team. Salesforce Flow is a tool that allows admins to automate processes and tasks using clicks or code. Flows can be triggered by various events, such as buttons, actions, schedules, or record changes. Flows can also display screens to users, which can contain fields, text, images, or components. However, screens are not the same as prompts or walkthroughs. Screens are part of a flow logic, and they require user input to proceed to the next step. Screens cannot be customized to appear as floating or docked prompts, and they cannot guide users through a Lightning page56.
• Basic In-App Guidance Prompts: This option does not require a subscription to myTrailhead, but it also does not provide the functionality of walkthroughs. Basic in-app guidance prompts are the same as the ones mentioned in the first option, but without the customization and branding of myTrailhead. Basic prompts can be created and managed using clicks, not code, and they can be filtered by profiles and permissions. However, basic promptsare still single-step messages that appear on a Lightning page, and they cannot show users how to perform a task23.

References:

• : [In-App Guidance Walkthroughs: Getting Started for Sales Users]
• : [In-App Guidance Dashboard: Walkthrough Engagement]
• : [In-App Guidance in Lightning Experience]
• : [Salesforce Flow | Salesforce Developer Center]
• : [Salesforce Flow Workflow Automation Tools - Salesforce.com]
• : [The Complete Guide to Salesforce Flow | Salesforce Ben]
• : [Trailhead | The fun way to learn]
• : [Editions & Pricing - myTrailhead- Salesforce]
• : [Salesforce introduces myTrailhead, a personal learning platform …]
• : [Trailhead | The fun way to learn Salesforce]
• : [Getting Started with myTrailhead - Salesforce]

 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