A UX Designer is creating a one-to-many or many-to-one relationship between two objects.
Which kind of relationship should the designer use to link the two objects?
: A lookup relationship is a type of relationship that links two objects together, but the relationship is not required. This means that the child object can exist independently of the parent object. A lookup relationship can be either one-to-many or many-to-one, depending on the cardinality of the objects involved. For example, a contact can have a lookup relationship to an account, which means that a contact can belong to one account, but an account can have many contacts. Alternatively, a custom object can have a lookup relationship to a user, which means that a custom object can belong to many users, but a user can have only one custom object record.Reference:Trailhead: Data Modeling,Trailhead: Salesforce User Experience Designer Certification Prep,Salesforce Help: Define Lookup Relationships
Cloud Kicks (CK) wants gamified learning content for its internal users and leadership. CK wants to create a custom product training as a part of the experience.
What should be recommended?
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.Reference:
[Trailhead: Enablement Site Basics]
[Trailhead: Create Custom Modules for Your Enablement Site]
[Trailhead: Gamify Your Enablement Site]
Cloud Kicks wants to plan out the strategy for an upcoming discovery phase.
Which three practices should be considered?
Choose 3 answers
The discovery phase is a crucial stage in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1.The discovery phase typically involves various research methods, such as interviews, surveys, observations, and analytics, to gather data and insights about the users and the context of use2. The outputs of the discovery phase are artifacts that synthesize and communicate the findings and insights from the research. Some of the practices that should be considered for planning out the strategy for an upcoming discovery phase are:
Gather insight from end users: One of the main objectives of the discovery phase is to empathize with the end users and understand their goals, motivations, pain points, behaviors, and preferences.This can be done by conducting user research, such as interviews, surveys, focus groups, or usability tests, to collect qualitative and quantitative data from the target audience3. Gathering insight from end users helps to validate the assumptions and hypotheses about the problem and the solution, as well as to identify the user requirements and expectations for the design.
Establish the research plan and timeline: Before conducting any user research, it is important to establish a clear and realistic research plan and timeline. The research plan should define the research objectives, questions, methods, participants, and deliverables.The research timeline should specify the duration, frequency, and sequence of the research activities, as well as the deadlines and milestones for the deliverables4. Establishing the research plan and timeline helps to ensure that the discovery phase is well-organized, efficient, and effective, as well as to communicate the expectations and responsibilities to the stakeholders and the team members.
Understand the problem before moving to solutions: Another key practice for the discovery phase is to focus on understanding the problem before jumping to solutions. This means defining the problem statement, the scope, and the constraints of the project, as well as identifying the root causes, the symptoms, and the impacts of the problem. Understanding the problem before moving to solutions helps to avoid wasting time and resources on creating solutions that do not address the real needs and pain points of the users, or that are not feasible or viable for the business or the technology.
The other two options, considering platform-based before custom solutions and determining user acceptance criteria, are not practices that should be considered for planning out the strategy for an upcoming discovery phase.Considering platform-based before custom solutions is a practice that belongs to the design phase, not the discovery phase, as it involves choosing the best solution option based on the user research findings and the design principles5.Determining user acceptance criteria is a practice that belongs to the testing phase, not the discovery phase, as it involves defining the criteria that the solution must meet to be accepted by the users and the stakeholders6.
For Cloud Kicks' upcoming discovery phase, the three practices that should be considered are:
A) Understand the Problem Before Moving to Solutions: Establishing a clear understanding of theproblem and what the desired outcomes are before beginning the discovery phase is essential for successful project planning. This can be done by gathering data and insights from end users, conducting research, and understanding how the problem is currentlybeing addressed.
B) Gather Insight from End Users: Gathering insights from end users is a crucial step in the discovery phase. End users provide valuable feedback and insights into the problem and how a potential solution may work. This feedback can helpshape the overall project plan and help identify potential solutions.
C) Establish the Research Plan and Timeline: The research plan and timeline should be established before beginning the discovery phase. This should include a list of tasks to be completed, the resources needed, and a timeline for completion. This plan should be communicated to all stakeholders so everyone is aware of the project goals and timeline.
Which document should be the source of truth for consistency when implementing a company's brand on Salesforce?
A style guide is a document that defines the visual identity and branding of a company, such as the logo, color palette, typography, iconography, imagery, and tone of voice. It helps ensure consistency and coherence across different platforms and channels, and communicates the company's values and personality. When implementing a company's brand on Salesforce, the style guide should be the source of truth for consistency, as it provides the guidelines and rules for applying the brand elements to the user interface. A style guide can also include a pattern library, which is a collection of reusable UI components and design patterns that follow the style guide. A design principle is a statement that expresses the core values and goals of a design process, and guides the decision making and evaluation of a design solution. The Salesforce Lightning Design System (SLDS) is a set of design guidelines and resources for creating consistent and beautiful user experiences on the Salesforce platform. It can be used as a reference and a foundation for customizing the UI according to the company's style guide.Reference:
: User Experience Designer Certification Prep: Module 5: Design User Interfaces
: User Experience Designer Certification Prep: Module 7: Implement User Interfaces
: What is a Style Guide and Why Every UX Designer Needs One
: What is a Pattern Library and Why Should You Use One?
The Salesforce Lightning Design System (SLDS) is a comprehensive library of design patterns, components, and guidelines that enable developers and designers to create consistentuser interfaces on the Salesforce platform. It includes a comprehensive library of user interface components, guidelines for design consistency and accessibility, and detailed usage instructions. Using the Salesforce Lightning Design System ensures that all design elements and interactions on Salesforce use the same set of standards and patterns, resulting in a consistent and unified user experience. For more information, see the Salesforce Lightning Design System page (https://www.lightningdesignsystem.com/).
In which two ways could the usability of accordion elements be improved in a mobile environment?
Choose 2 answers
Accordion elements are UI components that allow users to expand and collapse sections of content. They are useful for organizing information in a limited space, such as on mobile devices. However, they also have some usability challenges, such as discoverability, accessibility, and navigation. To improve the usability of accordion elements in a mobile environment, two possible ways are:
Include persistent headings. Persistent headings are the labels that indicate the content of each section and allow users to tap on them to expand or collapse the content. Persistent headings should be visible at all times, even when the content is expanded, so that users can easily see the context and switch between sections. Persistent headings should also be clear, concise, and descriptive, so that users can understand what each section contains and decide whether to explore it or not. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]
Only allow users to open one selection at a time. This means that when a user taps on a heading to expand a section, any other previously expanded section should automatically collapse. This prevents the content from becoming too long and overwhelming for the user, and also helps to maintain the focus and hierarchy of the information. It also reduces the need for scrolling and the risk of losing the position of the headings. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]
Nesting an accordion inside of another is not a good way to improve the usability of accordion elements in a mobile environment, because it creates a complex and confusing structure that is hard to navigate and understand. It also increases the cognitive load and the number of taps required for the user to access the information. Using the 'back' browser button to collapse content is also not a good way to improve the usability of accordion elements in a mobile environment, because it breaks the user's expectation and the consistency of the UI. The 'back' browser button should be used to go back to the previous page or screen, not to collapse the content within the same page or screen. It also makes it difficult for the user to return to the expanded content if they want to. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]Reference:[UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]
Kenneth Morgan
1 day agoTomoko
18 days agoCharisse
26 days agoChauncey
1 month agoClay
1 month agoWhitney
2 months agoBeata
2 months agoDustin
2 months agoAleshia
2 months agoBrice
3 months agoTamala
3 months agoBen
3 months agoFreeman
3 months agoPeggy
4 months agoJettie
4 months agoYen
4 months agoRoselle
4 months agoRasheeda
5 months agoLaila
5 months agoCarin
5 months agoEllsworth
5 months agoMalcolm
6 months agoLinette
6 months agoKayleigh
6 months agoDudley
6 months agoStefanie
7 months agoMelodie
7 months agoFreeman
7 months agoTamar
7 months agoLelia
8 months agoDevora
8 months agoLina
10 months agoAfton
11 months agoMayra
12 months agoPeggie
1 year agoDeonna
1 year agoVal
1 year agoEdwin
1 year agoLouann
1 year agoIsreal
1 year agoZona
1 year agoFarrah
1 year agoJonell
1 year agoHaley
1 year agoMaryann
2 years agoBenedict
2 years agoTresa
2 years agoKatheryn
2 years agoBelen
2 years agoAyesha
2 years agoLauryn
2 years agoMona
2 years agoOdette
2 years agoNobuko
2 years agoStaci
2 years agoBettina
2 years ago