Pass the Salesforce Designers User-Experience-Designer Questions and answers with ExamsMirror

To optimize Salesforce for the IT help desk team at Cloud Kicks, enabling them to quickly resolve queued cases, adding a List View component to the home page is the most effective approach because:

Customization and Relevance: A List View component can be customized to show a list view that is specifically filtered to display cases that are both assigned to the team members and are currently open. This ensures that team members immediately see the most relevant cases as soon as they log in, without needing to navigate through the Salesforce interface.

Efficiency: Having this component on the home page saves time and clicks, making the process of identifying and accessing pending cases more efficient, which is crucial for quickly resolving issues.

While options A (Case Assignment component) and C (Case inbox component) could also present cases to team members, the List View component's ability to be customized with specific filters offers a more targeted approach to showing the most pertinent cases directly on the home page.

 A storyboard is a visual representation of a user’s journey with a product or service. It shows how the user interacts with the product or service in a specific context, what their goals and pain points are, and how the product or service solves their problems or meets their needs. A storyboard typically consists of a series of sketches or illustrations that depict the user’s actions, thoughts, and emotions at each step of the journey1.

A storyboard is the most suitable technique for CK’s UX Designer to use in this case, because it can help them communicate their innovative solution to the team and show where and why it fits into what the customer does. A storyboard can also help the UX Designer to validate their assumptions, test their ideas, and get feedback from the team and the customers. A storyboard can also inspire the team to generate more ideas and solutions, and align them with the user’s perspective2.

Personas are fictional characters that represent the potential users of a product or service. They are based on user research and data, and they describe the user’s demographics, behaviors, motivations, goals, and frustrations. Personas are useful for understanding the user’s needs and expectations, and for designing products or services that cater to them. However, personas alone are not enough to show how the user interacts with the product or service in a specific context, or how the product or service solves their problems or meets their needs. Personas need to be complemented with other techniques, such as scenarios, user stories, or storyboards, to illustrate the user’s journey3.

A high-fidelity prototype is a realistic and interactive simulation of a product or service. It mimics the look, feel, and functionality of the final product or service, and it can be used for testing and evaluation purposes. A high-fidelity prototype is useful for demonstrating the features and benefits of a product or service, and for getting feedback from the users and stakeholders. However, a high-fidelity prototype is not the best technique for showing where and why a product or service fits into what the customer does, as it focuses more on the details and specifics of the product or service, rather than the context and situation of the user. A high-fidelity prototype is also more time-consuming and resource-intensive to create than a storyboard, and it may not be necessary at the early stages of the design process.

A UX designer who has been asked to improve Salesforce adoption among sales representatives at Cloud Kicks should conduct a workshop with stakeholders to align on the current state and build consensus as the next step after finding out that there is no clear and consistent sales process. This is because:

A clear and consistent sales process is essential for defining the user needs, goals, and pain points, as well as the business requirements, objectives, and metrics. Without a clear and consistent sales process, the UX designer cannot design a user-centric and value-driven solution that meets the expectations and needs of both the users and the stakeholders.

A workshop with stakeholders can help the UX designer to understand the existing sales process, identify the gaps, challenges, and opportunities, and facilitate a collaborative and participatory approach to define the desired future state and agree on the best practices and standards for the sales process. A workshop can also help to establish trust, rapport, and buy-in among the stakeholders, and ensure that they are aligned and committed to the project vision and goals.

A workshop with stakeholders can also help the UX designer to gather feedback, input, and validation from the key decision-makers and influencers, and incorporate them into the design process. A workshop can also help to communicate the value proposition and benefits of Salesforce adoption, and address any concerns, questions, or resistance that the stakeholders may have.

Consequence Scanning is a workshop method that helps teams to identify and mitigate the potential positive and negative impacts of their products or services on users, society, and the environment. When conducting a Consequence Scanning workshop, two important considerations are:

Consider design ramifications to prevent misuse and protect communities: This means that teams should think beyond the intended use cases and benefits of their products or services, and also consider the possible unintended or harmful consequences that may arise from their design choices. For example, teams should ask themselves how their products or services could be misused, abused, or exploited by malicious actors, or how they could affect vulnerable or marginalized groups, or how they could contribute to environmental or social issues. By considering these design ramifications, teams can proactively address and mitigate the ethical risks and challenges that may emerge from their products or services, and protect the well-being and interests of their users and communities.

Bring together a cross-function group with varied experiences: This means that teams should involve diverse and relevant stakeholders in the Consequence Scanning workshop, such as product managers, designers, developers, researchers, testers, marketers, legal experts, ethicists, users, or representatives from affected communities. By bringing together a cross-function group with varied experiences, perspectives, and backgrounds, teams can gain a more holistic and comprehensive understanding of the potential impacts of their products or services, and avoid blind spots, biases, or assumptions that may limit their vision or judgment. A cross-function group can also foster more creative and collaborative problem-solving, and generate more inclusive and responsible solutions.

 Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the --slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, --slds-c-button-brand-color-background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function. References:

Styling Hooks - Lightning Design System

SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers

–dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1].

[1] https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styling_hooks

 A service-blueprinting workshop is a process that involves mapping out the flow of a service, identifying the touchpoints, actors, processes, and systems that are involved, and highlighting the pain points and opportunities for improvement. A service-blueprinting workshop is a collaborative and creative way to redesign services with stakeholders, as it allows them to see the big picture, empathize with the users, and co-create solutions. A service-blueprinting workshop is suitable for Cloud Kicks (CK) after they have finished conducting research and synthesizing the findings, as it will help them address the issues uncovered in the study and design better service experiences for their customers. References: Service Design Service Blueprints, How to create a service blueprinting facilitation guide, Workshop exercise: Service Blueprint

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

According to the Web Content Accessibility Guidelines (WCAG) 2.1, the minimum color contrast ratio for normal text is 4.5:11. This means that the difference in brightness (luminance) between the text color and the background color should be at least 4.5 times. This ensures that the text is readable by people with moderately low vision, color deficiencies, or contrast sensitivity1. The contrast ratio can be calculated using the formula:

L2​+0.05L1​+0.05​

where L1​ is the relative luminance of the lighter color and L2​ is the relative luminance of the darker color2. The relative luminance is a value between 0 and 1, where 0 is black and 1 is white2. The contrast ratio can range from 1:1 (white on white) to 21:1 (black on white)2.

The contrast ratio requirement for normal text is lower for larger text or bold text, as they are easier to read at lower contrast. For large text (18 point or 14 point bold), the minimum contrast ratio is 3:11. For graphics and user interface components, such as form input borders, the minimum contrast ratio is also 3:13. For level AAA conformance, the minimum contrast ratio for normal text is 7:1 and for large text is 4.5:11.

To evaluate the color contrast ratio of a site, there are various tools available, such as the Contrast Checker or the Contrast Ratio tool. These tools allow users to enter the text color and the background color and see the contrast ratio and whether it meets the WCAG guidelines. They also provide suggestions for improving the contrast ratio if needed.

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce. An architect should consider the following points in this situation:

Changing complex role hierarchy can cause a high level of sharing recalculation. Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources. Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.

Replacing account records ownerships massively can cause data skew. Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities. Therefore, replacing account records ownerships massively should be avoided or minimized23.

A field-level error message is a message that appears next to a specific field when the user enters invalid data or omits required data. It helps the user to correct the error and proceed with the action. A field-level error message is more user-friendly than a validation rule, which displays a generic message at the top of the page and prevents the user from saving the record. A field-level error message can also provide guidance on the correct format and number of digits for the phone number field. Marking the field as required would not ensure that the user enters the phone number in the correct format and with the correct number of digits. Setting a prompt to display on the page using In-App Guidance would not prevent the user from entering invalid data or omitting required data. References: [Field-Level Error Messages], [Validation Rules], [In-App Guidance]