Summary:
Viability specifically concerns the financial sustainability of the business model. A key pillar of viability is a revenue stream that exceeds the cost of delivering the value proposition. Therefore, the most critical question to test is whether customers perceive enough value in the offering to part with their money, and at what price point, as this directly validates the core economic engine of the venture.

Correct Option:

C. What are customers willing to pay?
This is the fundamental question for testing viability. The answer directly validates the potential revenue stream of the business model. If customers are not willing to pay a price that makes the venture profitable, the business model is not viable, regardless of how much they like the product. This question probes the crucial link between the value proposition and the customer's wallet.

Incorrect Option:

A. Would customers recommend this to a friend?
This question measures customer satisfaction and loyalty, which are indicators of Desirability and potential for organic growth (like Net Promoter Score). A customer might recommend a free service they enjoy, but that does not validate that the business can generate sustainable revenue.

B. How would customers improve the experience?
This is a valuable question for iterating on the product's design and usability, which falls under Desirability and Feasibility. It helps refine the user experience but does not provide direct evidence about the financial sustainability of the business model.

Reference:
Salesforce Trailhead, "Discover the Three Lenses of Innovation": This module defines Viability as the "business lens," concerned with whether an idea is financially sustainable and profitable. Testing what customers are willing to pay is a direct method of validating this lens and is a core practice in developing a sound business model.

Summary:
In a cross-functional critique, power dynamics and personality types can prevent junior or quieter team members from contributing. The facilitator's goal is to create a structured, equitable process that explicitly gives everyone an equal opportunity to speak, ensuring the feedback is not dominated by the most senior or vocal individuals and that diverse perspectives are captured.

Correct Option:

C. Use a round-robin format, where everyone can share equally:
This is the most effective technique for ensuring all voices are heard. The round-robin format provides a clear structure where each person takes a turn to share their feedback. This prevents interruptions, guarantees everyone has the floor, and psychologically empowers quieter members to contribute because the structure creates an expectation that they will speak. It democratizes the conversation and values each perspective equally.

Incorrect Option:

A. Only collect written feedback from those who are comfortable providing it:
While written feedback can be helpful for introverted participants, using it as the only method prevents the dynamic exchange of ideas that makes a live critique valuable. It siloes feedback and misses the opportunity for the team to build on each other's comments in real-time, which is a key benefit of a collaborative session.

B. Hold separate critiques so everyone feels comfortable speaking:
This is highly inefficient and counterproductive. It fragments the team, creates multiple versions of the truth, and defeats the purpose of a cross-functional session. The goal is to build shared understanding through a single, unified conversation, not to manage multiple parallel conversations.

Reference:
Salesforce Trailhead, "Facilitate an Inclusive and Engaging Virtual Meeting": This module covers facilitation techniques for inclusive collaboration. It recommends structured methods like round-robin to ensure equitable participation and prevent a few voices from dominating, which is essential for gathering comprehensive feedback and building team consensus.

Summary:
At the end of a discovery phase, the team has a deep understanding of user needs and business goals. The next step is to synthesize these insights into a focused, actionable direction for the design team. The framing technique should be open enough to encourage creative exploration but constrained enough to be manageable, turning identified problems into opportunities for solutioning.

Correct Option:

B. Construct "How might we..." questions:
This is the correct and standard technique for framing a design challenge. "How Might We" (HMW) questions are perfectly suited for this transition from discovery to ideation. They reframe identified problems as opportunities, creating a constructive launchpad for brainstorming. For example, a finding that "users feel anxious about delivery times" becomes "How might we reassure customers while they wait for their order?" This frames the right problem without prescribing a solution.

Incorrect Option:

A. Design "For an optimal experience..." questions:
This type of statement describes a desired end state or a design principle. While useful for establishing goals, it is not a framing tool for a challenge. It states an outcome without defining the problem space to be explored, making it less effective for guiding the divergent thinking of ideation.

C. Create "As a user, I should..." questions:
This format is used for writing user stories in agile development, which are specific requirements from a user's perspective. It is a solution-oriented statement that comes after the problem has been framed and explored. Starting with user stories prematurely limits creativity by jumping to a specific solution instead of opening up the problem for broad ideation.

Reference:
Salesforce Trailhead, "Frame Your Design Challenge": This module specifically teaches the "How Might We" technique as a method to transition from research insights to ideation. It emphasizes that a well-crafted HMW question opens up the creative process while keeping it focused on the core user problems uncovered during discovery.

Summary:
Developing a mental health app involves handling highly sensitive personal data related to medical and psychological conditions. This places the app squarely within the scope of stringent health information privacy laws. An external factor like a government regulation is a fixed constraint that can fundamentally shape the product's data strategy, security architecture, and legal requirements, carrying significant financial and reputational risks for non-compliance.

Correct Option:

A. HIPAA regulations:
This is the most impactful external factor. In the United States, the Health Insurance Portability and Accountability Act (HIPAA) sets the national standard for protecting sensitive patient health information. If the app collects, stores, or transmits personally identifiable health data, it must comply with HIPAA's strict rules on security, privacy, and patient rights. This is not a choice but a legal mandate that will heavily influence data architecture, feature set, and third-party service partnerships.

Incorrect Option:

B. Customer adoption:
While critically important, customer adoption is an internal business metric and a goal, not an external regulatory factor that imposes legal constraints on the development process. The strategy must work within external regulations to achieve customer adoption.

C. Push notifications:
This is an internal technical feature and a design decision. While important for user engagement, it is a tool controlled by the company, not an external factor imposing legal or societal constraints on the overall strategy.

Reference:
U.S. Department of Health & Human Services (HHS) Official HIPAA Website: This is the definitive source for HIPAA regulations. It outlines the Privacy and Security Rules that would directly govern the development of a mental health app, making compliance a primary external factor shaping the product strategy.

Summary:
A synchronous journey mapping session for a remote, cross-functional team requires a tool that enables real-time, visual collaboration. The tool must allow all participants to simultaneously contribute ideas, move elements around, and build a shared artifact together. The focus is on collective brainstorming and structuring information, not on creating polished deliverables or presenting finalized information.

Correct Option:

B. Whiteboarding tools:
This is the correct category of tools. Digital whiteboarding tools (such as Miro, Mural, or Jamboard) are specifically designed for this purpose. They provide an infinite canvas where remote team members can simultaneously add digital sticky notes, draw connections, create lanes for a journey map, and comment in real time. This replicates the collaborative energy of an in-person workshop and ensures all voices are heard.

Incorrect Option:

A. Design creation tools:
These are specialized software like Figma or Sketch, used by designers for high-fidelity UI design, prototyping, and creating production-ready assets. They are not ideal for a collaborative brainstorming session with a broad cross-functional team, as they have a steeper learning curve and are optimized for precision over free-form ideation.

C. Presentation tools:
Tools like Google Slides or PowerPoint are designed for linear, one-to-many communication. They are passive for the audience and do not allow for the dynamic, non-linear, and collaborative building process that is essential for a journey mapping workshop. They are for presenting a finished map, not for creating one together.

Reference:
Salesforce Trailhead, "Gain a Shared Understanding": This module emphasizes the use of collaborative workshops to build alignment. For remote teams, it recommends using digital whiteboarding tools to facilitate activities like journey mapping, as they are the most effective way to visually collaborate in real-time and create a shared artifact that everyone contributes to.