Cloud Kicks has identified a Trusted Advisor persona as their primary focus for the next iteration. Which key business process defining their work should be analyzed to make sure the delivered experience fits their needs?
A. Maintaining relationships with existing customers
B. Managing sales pipeline and forecasting
C. Customizing and administering Salesforce
Explanation:
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 spendtime managing tools and processes for sales reps, which includes customizing and administering Salesforce1
References:
Learn About Sales Cloud Personas Unit | Salesforce Trailhead
How to Increase Your Sales with Personas for Salesforce Users | RTS Labs
How to Use Journey Mapping to Improve Employee Engagement
Cloud Kicks (CK) wants to determine whether or not the Experience Cloud site it is launching is intuitive. CK’s UX Designer is going to conduct a usability study. What shouldbe one of the first steps when planning this study?
A. Define the goals of the study.
B. Design changes to the site.
C. Design the information architecture.
D. Analyze the results of the study.
Explanation:
A usability study is a method of evaluating how easy and intuitive a product or service is to use by observing real users performing specific tasks. It can help identify usability issues, user needs, and user satisfaction. One of the first steps when planning a usability study is to define the goals of the study, which are the questions that the UX designer wants to answer or the hypotheses that they want to test. The goals of the study will guide the selection of the participants, the tasks, the metrics, and the methods of the study. For example, if the goal of the study is to find out how users navigate the Experience Cloud site, the UX designer might choose to use a task-based usability test with eye-tracking and think-aloud techniques.
References:
: User Experience Designer Certification Prep: Module 4: Analyze User Research Data
: User Experience Designer Certification Prep: Module 6: Validate User Interfaces
Sales managers want their team members to help each other close Opportunities. The Opportunity and Account organization-wide defaults are private. To grant Opportunity access tosales reps on the same team, owner ship-based sharing rules were created for each team. What is the side effect of this approach?
A. All sales reps will have Read access to Accounts for all Opportunities.
B. Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
C. Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
D. All sales reps will have Read access to all Accounts.
Explanation:
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 access1. 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 accounts2. However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities3. 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 byHigh-Volume Portal Users | Salesforce Security Guide, Sharing Rules | Salesforce Security Guide, Create Owner-Based Sharing Rules | Salesforce Security Guide
A group of sales users needs to be guided step by step through a new process using Floating or Decked Prompts. Their administrative teamwants to the ability to see the adoption of this assistance via Reports and Dashboards.
A. in-App Guidance Prompts using myTrailhead
B. Custom build using Salesforce Flow
C. Basic In-App Guidance Prompts
D. Use the Walkthrough App from AppExchange
Explanation:
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]
A UX Designer wants to inform user stories based on user value and development effort. Which method should be used?
A. Card Sorting
B. Prioritization Matrix
C. Customer Journey Map
Explanation:
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 leastvalue 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 PrioritizeUser Stories (and Build the Right Features), Salesforce User Experience (UX) Designer Certification Guide & Tips
Page 11 out of 42 Pages |
Previous |