The strategy designer should conduct an expert interview in consumer device engineering to

determine whether or not to pursue this product idea. An expert interview is a way to gather

information and insights from someone who has specialized knowledge or experience in a relevant

domain. It can help validate assumptions, identify risks, and explore opportunities for innovation.

Performing secondary research may not provide enough depth or specificity for this product idea.

Hiring an engineer may be premature and costly at this stage.

The additional topics that Cloud Kicks should consider before framing the design challenge as a How

Might We question are potential market size and supply chain costs, as these help evaluate the

viability and feasibility of the design opportunity. Shareholder priorities and design team capabilities

or business drivers and signals of success may not be relevant or important for framing the design

challenge.

The best recommendation to help the team efficiently share the right data is to create dashboards in

Tableau, as this allows them to visualize and analyze data from different sources, customize and filter

views, and share insights with different audiences. Developing reports in Sales Cloud or providing

Kanban view in Revenue Cloud may not offer the same level of flexibility and functionality as

Tableau.

The technique that the designer should use to ensure the audience remains engaged is to ask open-

ended questions to the audience to maintain their involvement. Open-ended questions are questions

that require more than a yes or no answer, and invite the audience to share their thoughts, opinions,

or feedback. Asking open-ended questions can help the designer capture the audience’s attention,

interest, and curiosity, as well as encourage interaction and dialogue. Turning the camera off may

reduce the visual connection and rapport with the audience. Dedicating half of the meeting time to

answering questions may not be enough to keep the audience engaged throughout the presentation.

The best approach to increase the desire for research-driven decisions among stakeholders who

misunderstand and undervalue research-driven UX design is to align UX research goals with

stakeholders’ goals, as this helps demonstrate the value and relevance of research for achieving

business outcomes. Creating high-fidelity prototypes or strictly aligning to stakeholders’ business

requirements may not address the root cause of the lack of desire for research.

The best way to collaborate with the UX designer to ensure that new features on the sales platform

are both viable and feasible is to align design implications to business goals, as this helps justify the

value proposition and return on investment of the new features. Co-creating a journey map with

users or identifying user quotes may not address the viability or feasibility aspects of the new

features.

Dot voting is a democratic and quick way to gauge group consensus on the most valued ideas. It

narrows down numerous ideas to those most critical to the group, facilitating focused discussions on

priorities and driving alignment on strategic opportunities.

The question that the team should use to prioritize and turn insights into design opportunities is

“Why is this insight valuable?” This question can help the team evaluate the relevance, significance,

and impact of each insight, and how it relates to the user needs, pain points, goals, and motivations.

The question also helps the team frame the insights in terms of benefits and outcomes, rather than

features or solutions. The other questions may be useful for assessing feasibility or viability, but they

do not prioritize insights based on value.

A Consequence Scanning Workshop is designed to anticipate and address the potential impacts of

technology projects, focusing on ethical considerations. It helps teams identify and mitigate negative

consequences, ensuring decisions contribute to ethical outcomes and avoiding ethical debt.

One way to increase the team’s psychological safety to encourage productive collaboration is to ask

everyone to share a personal experience, as this helps build trust, empathy, and rapport among team

members. Asking everyone their expected level of project involvement or introducing themselves via

title and greatest success may not foster psychological safety, as they may create hierarchy, pressure,

or competition.