A human-centered design process is a creative approach to solving people’s problems that begins with identifying their needs and ends with creating solutions that meet those needs1. A human-centered design process typically involves the following steps in this order23:

Observation: This step involves researching and understanding the users, their context, their goals, their pain points, and their behaviors. Observation methods include interviews, surveys, ethnography, contextual inquiry, and data analysis.

Ideation: This step involves generating and exploring a wide range of possible solutions that address the users’ needs and problems. Ideation methods include brainstorming, sketching, mind mapping, affinity diagramming, and storyboarding.

Prototyping: This step involves creating and testing low-fidelity or high-fidelity representations of the proposed solutions, such as mockups, wireframes, or interactive models. Prototyping methods include paper prototyping, digital prototyping, and rapid prototyping.

User Feedback: This step involves collecting and analyzing feedback from the users on the prototypes, such as their opinions, preferences, satisfaction, and suggestions. User feedback methods include usability testing, user testing, focus groups, and surveys.

Iteration: This step involves refining and improving the prototypes based on the user feedback, and repeating the prototyping and user feedback steps until the optimal solution is achieved. Iteration methods include agile development, design sprints, and A/B testing.

Implementation: This step involves deploying and launching the final solution to the users, and monitoring and evaluating its performance and impact. Implementation methods include release management, change management, and analytics.

References: Relationship Design - Trailhead, Human-Centered Design: Definition and Stages - Interaction Design Foundation, Human-Centered Design Process - Salesforce UX

The order in which CK's UX Designer should undertake the steps of the human-centered design process to achieve maximum impact is Observation > Ideation > Prototyping > User Feedback > Iteration > Implementation. This allows the designer to take into account the user’s preferences and needs from the very beginning, as well as provide the user with feedback throughout the entire process. The order of steps for a human-centered design process is as follows:

Observation: Observing user behaviour and interactions to gain insights into their needs and preferences.

Ideation: Coming up with ideas for potential solutions based on the insights from the observation phase.

Prototyping: Creating a prototype of the potential solution to test out with users.

User Feedback: Gathering feedback from users on the prototype and making changes based on their feedback.

Iteration: Iterating on the prototype based on the feedback from users.

Implementation: Implementing the final solution.

For more information on the human-centered design process, please see the following Salesforce documentation: https://trailhead.salesforce.com/en/content/learn/modules/ux_design_process

 A sales rep who owns an opportunity record will have read-only access to the related account record, if the organization-wide default for the Account object is private. This is because the opportunity owner is automatically granted read-only access to the account that the opportunity is associated with, regardless of who owns the account. This is called implicit sharing, and it is a built-in feature of Salesforce to ensure that users can access the data they need to do their work. However, the opportunity owner will not be able to create, edit, or delete the account record, unless they have other sharing mechanisms that grant them higher access, such as role hierarchy, sharing rules, manual sharing, or View All or Modify All permissions. References:

[Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs

[Control Access to Records Unit | Salesforce Trailhead]1, Unit 2: Implicit Sharing

[Work with Related Lists on Records in Lightning Experience - Salesforce]2, Related List Cards

Dynamic Forms is a feature that allows users to customize the form fields and sections displayed to users on a page layout. Dynamic Forms can be used to create user-centric, intuitive, and dynamic record creation screens for custom objects, such as Appointment. When creating a record using Dynamic Forms, the UX designer should consider the following two aspects12:

The use of tabs when creating the record is not allowed. Dynamic Forms does not support the use of tabs within the form, as tabs are not compatible with the record creation process. Tabs are only available for viewing or editing existing records, not for creating new ones. Therefore, the UX designer cannot use tabs to separate the fields for different record types or software options on the record creation screen.

Fields can be organized into sections. Dynamic Forms allows the UX designer to group fields into sections, and place them anywhere on the page layout. Sections can have labels, collapsible headers, and visibility rules. The UX designer can use sections to create a logical and clear structure for the form, and to show or hide fields based on user input, data, or profile. For example, the UX designer can create a section for each software option, and use visibility rules to display only the relevant section based on the user’s selection.

The following two aspects are not true when creating a record using Dynamic Forms, and should be disregarded:

The form will not be available on mobile devices. Dynamic Forms is compatible with mobile devices, and the UX designer can preview and test the form on different device sizes and orientations. The form will automatically adjust to the screen size and layout of the mobile device, and provide a responsive and consistent user experience3.

All software option sections of the form will always be visible. Dynamic Forms allows the UX designer to use visibility rules to control the visibility of fields and sections on the form. Visibility rules can be based on user input, data, or profile. The UX designer can use visibility rules to show or hide software option sections based on the user’s selection of the record type or the software option. This can reduce the clutter and complexity of the form, and provide a personalized and flexible user experience4. References: Get Started with Dynamic Forms Unit | Salesforce Trailhead, Salesforce Dynamic Forms: Overview & Deep Dive Tutorial, Dynamic Forms and Actions FAQ | Salesforce Help, Create Dynamic Forms with Visibility Rules | Salesforce Trailhead

 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 downloaded again. 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

 A standard person account object is the best option for representing the bank’s customers within its Salesforce instance. A person account is a type of account that represents an individual rather than a company. Person accounts are a hybrid of the account and contact objects, combining their characteristics into one. They allow the bank to store information that applies to humans, such as first and last names, email, phone, address, etc. When a person account is created, a contact is automatically created and associated with the account. Person accounts are the Salesforce official model for representing an individual and can be used alongside business accounts for B2B and B2C activities. In Financial Services Cloud, person accounts can be used for a simplified, customizable user experience1. A person account can also have related opportunities, which are potential sales or revenue-generating events. This way, the financial advisor can access a customer’s record and see all potential business opportunities related to each individual customer2.

The other options are not suitable for the bank’s scenario. A standard lead object is a prospect or potential customer who has expressed interest in the bank’s products or services, but has not yet qualified as a sales opportunity. A lead can be converted into an account, a contact, and an opportunity when it is ready to be pursued3. However, the bank does not need to use leads to track its customers, as they are already existing customers who have accounts with the bank. A standard opportunity object is a sales or revenue-generating event that is related to an account. An opportunity can have multiple stages, products, amounts, and probabilities of closing. An opportunity can also be linked to a campaign, which is a marketing initiative to generate leads or contacts4. However, the bank cannot use opportunities alone to represent its customers, as they are not standalone objects, but rather depend on accounts. A standard account object is a company or organization that the bank does business with. An account can have multiple contacts, which are the people who work at the account and interact with the bank. An account can also have related opportunities, cases, activities, and other records5. However, the bank does not have any corporate or business customers at this time, so using standard accounts would not reflect the nature of its individual customers.

References:

Convert Salesforce Business Accounts to Person Accounts, In Financial Services Cloud, Person Accounts can be used for a simplified, customizable user experience.

Person Accounts - Salesforce, Person Accounts Sales Cloud Basics Content Close Select Filters Product Area Feature Impact Edition Developer Edition Enterprise Edition Essentials Edition Professional Edition Unlimited Edition Experience Salesforce Classic Mobile Lightning Experience Done 632 Results Configure Access to Thanks Badges Set Up WDC Configure Thanks in the Chatter Publisher and Salesforce Mobile App… Build a Culture of Recognition with WDC Manage WDC Enable or Disable WDC Settings WDC Editions and Permissions Skills Limitations Skills Customization Recommended WDC Profiles Recommended WDC Permission Sets Enable WDC Features Configure WDC Assign WDC Only User Licenses Assign WDC Licenses Configure WDC Features Assign a WDC Administrator Create a Support Case Considerations for Setting Up WDC Thanks and Skills Features Assign Publisher Layout to Profiles Assign WDC User Feature Licenses Assign WDC Profiles Assign WDC Permission Sets Endorse a Skill Via Record Detail Pages Add a Skill Via Record Detail Pages Remove a Skill Via Record Detail Pages Schedule Reminders to Update Opportunities View a List of the Accounts or Opportunities in Your Territories Things to Know About Enterprise Territory Management Territory Type Priority Optimizing Your Territory Model Continuously Designing Territory Models Territory Model Managing Territories Enterprise Territory Management Concepts Planning and Managing Territories Territory Model State Territory Type Territory Hierarchy Bird’s-Eye View of Planning and Managing Territories Report on Territories with Assigned Users Report on Territories Without Assigned Accounts Run Assignment Rules for a Territory Reporting on Territories Report on Users Not Assigned to Territories Report on Summarizable Account Fields by Territory Enterprise Territory Management Identify Territory Users by Territory Role Territory Run the Opportunity Territory Assignment Filter Preview Territory Assignments for Accounts Report on Accounts Assigned to Territories Manage Territories with Enterprise Territory Management View and Manage Assignment Rules at the Territory Model Level Enterprise Territory Management: What’s Different or Not Available… Show Your Reps Other Users Assigned to Their Leads’ Territories Enable Features for Enterprise Territory Management Maintain Enterprise Territory Management Find Out Which Territories an Assignment Rule Applies To Enable Enterprise Territory Management Report on the Accounts and Opportunities in Your Territories Explore Your Company’s Territory Model Identify Users in Territories Assigned to Accounts Enable Filter-Based Opportunity Territory Assignment Identify an Account’s Sales Territories Disable Enterprise Territory Management How Account Assignment Rules Work How Do Permissions for Territories Affect Feature and Data Access? Requirements for Assigning Opportunities to Territories Manually Assigning Opportunities to Territories Manually Delete a Territory Model Create a Territory Model Record Preparing Sales Management for Territory Reporting Setting Up and Managing Territory Assignments Define Default User Access for Territory Records

Account | Object Reference for the Salesforce Platform | Salesforce …, Account | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version 36.0) Winter '16 (API version 35.0) Summer '15 (API version 34.0) Spring '15 (API version 33.0) Winter '15 (API version 32.0) Summer '14 (API version 31.0) Spring '14 (API version 30.0) j Overview of Salesforce Objects and Fields Reference Associated Objects (Feed, History, OwnerSharingRule, Share, and ChangeEvent Objects) Custom Objects Object Interfaces Standard Objects AcceptedEventRelation Account AccountBrand AccountContactRelation AccountCleanInfo AccountContactRole AccountInsight AccountOwnerSharingRule AccountPartner AccountRelationship AccountRelationshipShareRule AccountShare AccountTag AccountTeamMember AccountTerritoryAssignmentRule AccountTerritoryAssignmentRuleItem AccountTerritorySharingRule AccountUserTerritory2View ActionCadence ActionCadenceRule ActionCadenceRuleCondition ActionCadenceStep ActionCadenceStepTracker ActionCadenceStepVariant ActionCadenceTracker ActionCdncStpMonthlyMetric ActionLinkGroupTemplate ActionLinkTemplate ActionPlan ActionPlanItem ActionPlanTemplate ActionPlanTemplateItem ActionPlanTemplateItemValue ActionPlanTemplateVersion ActiveFeatureLicenseMetric ActivePermSetLicenseMetric ActiveProfileMetric ActiveScratchOrg ActivityHistory ActivityMetric ActivityUsrConnectionStatus AdAvailabilityDimensions AdAvailabilityJob AdAvailabilityViewConfig AdBuyServerAccount AdCreativeSizeType AdDigitalAvailability AdditionalNumber Address AdLinearAvailability AdOpportunity AdOrderItem AdOrderItemCreativeSizeType AdOrderLineAdTarget AdPageLayoutType AdProductTargetCategory AdQuote AdQuoteLine AdQuoteLineCreativeSizeType AdQuoteLineAdTarget AdServer AdServerAccount AdServerUser AdSpaceCreativeSizeType AdSpaceGroupMember AdSpaceSpecification AdSpecMediaPrintIssue AdTargetCategory AdTargetCategorySegment AgentWork AgentWorkSkill AIApplication AIApplicationConfig AIInsightAction AIInsightFeedback AIInsightReason AIInsightValue AiModelLanguage AIRecordInsight AllowedEmailDomain AlternativePaymentMethod AnalyticsLicensedAsset Announcement ApexClass ApexComponent ApexLog ApexPage ApexPageInfo ApexTestQueueItem ApexTestResult ApexTestResultLimits ApexTestRunResult ApexTestSuite ApexTrigger ApexTypeImplementor AppAnalyticsQueryRequest AppDefinition AppExtension ApplicationFormTemplate AppMenuItem AppointmentAssignmentPolicy AppointmentScheduleAggr

Lead | Object Reference for the Salesforce Platform | Salesforce …, Lead | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version

The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user’s mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text that appear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System] References: [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

 An Enablement Site is a custom-branded site that allows users to access learning content, such as modules, trails, and trailmixes, from Trailhead. It also allows admins to create and assign custom modules that are specific to their organization’s needs and goals. An Enablement Site can be used to gamify the learning experience by adding badges, points, and leaderboards. An Enablement Site can also provide analytics and reports on the learners’ progress and performance. Therefore, an Enablement Site is the best option for Cloud Kicks to create a gamified learning content for its internal users and leadership, as well as a custom product training. References:

[Trailhead: Enablement Site Basics]

[Trailhead: Create Custom Modules for Your Enablement Site]

[Trailhead: Gamify Your Enablement Site]

The best ways to analyze and implement feature enhancements as a result of user acceptance testing are:

A. Determine the change in scope and impact of each enhancement request. This will help to evaluate the feasibility, priority, and effort of each request, and to communicate the expectations and trade-offs to the stakeholders1.

C. Reduce unexpected results by configuring and testing in a sandbox. A sandbox is a copy of the production environment that allows testing and development without affecting the live data and users2. By using a sandbox, the feature enhancements can be tested and validated before deploying them to the production environment3.

E. Create a prioritization list and perform a feasibility analysis. This will help to rank the enhancement requests based on their value, urgency, and complexity, and to determine which ones are feasible to implement within the given time and budget constraints4.

References: Salesforce User Experience Designer Exam Guide, What is a Sandbox?, Test New Features Before a Release, Prioritize User Needs

The Salesforce Lightning Design System (SLDS) is a CSS framework that helps designers and developers create applications with the look and feel of Lightning Experience. SLDS provides a library of design tokens, icons, components, utilities, and patterns that can be used to build consistent, responsive, and accessible user interfaces1. One of the features that SLDS provides for designers and developers is semantic and accessible component markup. Semantic markup means using HTML elements that describe the meaning and structure of the content, rather than just the presentation. For example, using 

 for a main heading, 

 for a paragraph, or  for a button. Semantic markup helps to improve the readability, maintainability, and SEO of the code2. Accessible markup means using HTML attributes and techniques that enhance the usability and accessibility of the content for people with disabilities. For example, using aria-label to provide a descriptive label for an element, role to indicate the function of an element, or tabindex to control the keyboard focus order. Accessible markup helps to ensure that the content can be perceived, understood, operated, and interacted with by people using assistive technologies, such as screen readers, keyboards, or voice commands3. SLDS provides semantic and accessible markup for its components, which are reusable UI elements that can be customized and composed to create complex interfaces. SLDS components follow the Web Content Accessibility Guidelines (WCAG), which are the international standards for web accessibility4. SLDS components also use the BEM (Block Element Modifier) naming convention, which is a methodology for creating clear and consistent class names for CSS selectors5. By using SLDS components, designers and developers can create user interfaces that are not only visually appealing, but also meaningful and accessible for everyone. References: Introduction to the Salesforce Lightning Design System, Semantic HTML: How to Structure Web Pages, Accessible Rich Internet Applications (WAI-ARIA), Web Content Accessibility Guidelines (WCAG) Overview, BEM — Block Element Modifier

 The additional UX elements that should be reviewed to influence the brand experience are visual, content, and interaction design. These elements are essential for creating a consistent, engaging, and memorable user experience that reflects the company’s brand identity and values12.

Visual design refers to the use of colors, shapes, typography, images, icons, and other graphical elements to create a visual hierarchy, contrast, balance, and harmony on the page13. Visual design affects the user’s perception, emotion, and attention, and can communicate the brand’s personality, tone, and message13. For example, Cloud Kicks can use their logo, color scheme, and font to create a recognizable and distinctive visual identity for their portal landing page4.

Content design refers to the creation, organization, and presentation of text, audio, video, and other media to convey the brand’s value proposition, story, and information to the user15. Content design affects the user’s understanding, interest, and trust, and can communicate the brand’s purpose, benefits, and voice15. For example, Cloud Kicks can use clear, concise, and compelling headlines, subheadings, and body text to highlight their products, services, and customer testimonials on their portal landing page.

Interaction design refers to the design of the user interface elements, such as buttons, links, menus, forms, and sliders, that enable the user to interact with the page and perform tasks1 . Interaction design affects the user’s behavior, satisfaction, and feedback, and can communicate the brand’s functionality, usability, and responsiveness1 . For example, Cloud Kicks can use intuitive, consistent, and accessible navigation, search, and filtering options to help the user find what they are looking for on their portal landing page.

By reviewing and improving these UX elements, Cloud Kicks can ensure that their portal landing page delivers a positive and coherent brand experience to their users, and that their brand identity is translated into the user experience.

References:

The 5 Elements of User Experience Design

How to Create a Brand Experience That Works With Your UX

Visual Design Basics

Use Branding Sets in Experience Builder

Content Design: What It Is and Why It Matters

[How to Write Effective Web Content for Your Experience Cloud Site]

[Interaction Design Basics]

[Designing User Interfaces for Experience Cloud Sites]