Summary:
A loyalty program is a complex initiative that involves various internal and external entities beyond just the customer. The goal is to identify all key people, organizations, and systems that influence or are impacted by the program. This requires a high-level, holistic view of the entire network of actors and their relationships, not just the customer's experience or the internal process flow.

Correct Option:

C. Ecosystem Mapping:
This is the correct mapping process. An ecosystem map visualizes the entire network of players involved in a service or product. For a loyalty program, this would include customers, Cloud Kicks' marketing/sales/finance teams, store employees, technology partners (e.g., point-of-sale systems, app developers), payment processors, and even competitors. It helps identify all influencers and impacted parties, revealing dependencies and opportunities.

Incorrect Option:

A. Journey Mapping:
A journey map focuses exclusively on the customer's experience, detailing their step-by-step interactions and emotional touchpoints with the loyalty program. While crucial for designing the user experience, it does not capture the broader network of internal teams, partners, and external influencers that the strategy designer needs to identify.

B. Service Mapping (or Service Blueprinting):
A service blueprint maps the customer journey and the corresponding internal processes, people, and technology that deliver the service behind the scenes. While it includes internal actors, it is still centered on the linear flow of a single service delivery. An ecosystem map is more strategic, showing the entire interconnected web of entities before diving into the specific service delivery mechanics.

Reference:
Salesforce Trailhead, "Explore Ecosystem Mapping": This module introduces ecosystem mapping as a tool to visualize the relationships between people, organizations, and things that influence a system. It is used to understand the broader context and identify all key stakeholders, which is precisely the goal when mapping influences and impacts for a new loyalty program.

Summary:
The prototype demonstrates the experience, but business stakeholders responsible for funding and resources need to understand the strategic justification and the execution plan. To get buy-in, the strategy designer must connect the conceptual prototype to tangible business outcomes and a clear, actionable plan for implementation that outlines the investment, benefits, and timeline.

Correct Option:

B. Business case and roadmap:
This is the correct combination for securing buy-in.

The Business Case articulates the strategic "why," quantifying the value by linking the improved customer experience to key business drivers like increased revenue, cost savings, or customer retention. It outlines the costs, risks, and expected return on investment (ROI).

The Roadmap provides the strategic "how" and "when," showing a phased plan for turning the prototype into a live solution. It gives stakeholders confidence that the initiative is well-planned and manageable.

Incorrect Option:

A. Business user flow and journey map:
These are excellent tools for designing and communicating the customer experience, but they are tactical design artifacts. They show what the experience will be but do not effectively communicate the financial justification or high-level implementation plan needed for executive buy-in.

C. Business metrics and ROI map:
While critically important, these are typically components within a comprehensive business case. Presenting metrics and ROI alone is insufficient without the broader strategic narrative, resource requirements, and phased execution plan provided by a full business case and roadmap.

Reference:
Salesforce Trailhead, "Create a Roadmap" and "Create a Strategy to Deliver Value": These modules cover the process of building a business case to justify an initiative and creating a roadmap to visualize the execution plan. Together, they are the standard deliverables used to communicate value and secure stakeholder approval for a strategic project.

Summary:
A design challenge statement is a strategic tool used to frame a problem in an open, inspirational, and human-centered way. It is not a solution, a user story, or a business objective. Its purpose is to guide ideation by focusing on the user's need and the desired outcome without presupposing the method to achieve it. The standard format begins with "How might we..." to encourage creative exploration.

Correct Option:

C. How might we save our existing customers time by preemptively serving the info they need to deflect the customer support calls.
This option correctly uses the "How Might We" (HMW) format, which is the industry standard for a design challenge statement. It is broad enough to allow for a wide range of creative solutions yet specific enough to provide a clear direction.

It focuses on the core user need ("save time") and the business goal ("deflect support calls") without specifying a solution like "unify platforms" or a specific feature like "see trending resources." This open-ended nature is the hallmark of a well-formed design challenge.

Incorrect Options:

A. As a user, I want to see trending support resources upon the first login to customer support so I can save my time.
This is a user story, not a design challenge. User stories are used in agile development to define a specific feature or requirement from a user's perspective. It presents a single solution ("trending support resources") rather than an open-ended problem to be explored.

B. Unify platforms and centralize support operations to save customers time and reduce business costs.
This is a solution statement or a business objective. It already prescribes the method ("unify platforms") to achieve the goal. A design challenge should avoid pre-defining the solution to allow the team to discover the best approach through research and ideation.

Reference:
IDEO.org: How Might We

This resource from IDEO, a leader in design thinking, defines the "How Might We" question as a format that "suggests that a solution is possible and offers the chance to answer it in a variety of ways." It is the accepted standard for framing a design challenge.

Summary:
A vision remains abstract unless it is operationalized into measurable goals and integrated into the development lifecycle. To ensure the new mobile app aligns with the strategic vision of a sustainable, efficient digital commerce platform, the strategy designer must translate the vision into concrete metrics and create formal opportunities to evaluate progress against them throughout the project.

Correct Option:

C. Establish KPIs and instill checkpoints in the product development process:
This is the correct and most comprehensive approach.

Establish KPIs: Define Key Performance Indicators (KPIs) that measure both user efficiency (e.g., time to complete a purchase, reduced number of taps) and business logistics efficiency (e.g., reduction in support calls for order tracking, accuracy of delivery estimates).

Instill Checkpoints: Integrate formal reviews at key stages (e.g., after design sprints, during backlog grooming) where the team assesses whether their work is still aligned with the KPIs and the overarching vision. This makes the vision a living guide for decision-making.

Incorrect Option:

A. Design a usability testing recruit plan that leans heavily on environmentalists:
This is a narrow and misguided approach. While sustainability is part of the vision, the core goals are "efficiency for both users and business logistics." Recruiting specifically for environmentalists would bias the feedback toward one aspect and fail to test the broader efficiency goals for a general user base.

B. Research design patterns applicable to digital commerce and business logistics:
This is a valuable tactical activity for the design phase, but it is an input, not a method for ensuring alignment. Researching patterns helps you build the app well, but without KPIs and checkpoints, there is no mechanism to ensure those patterns are effectively serving the strategic vision.

Reference:
Salesforce Trailhead, "Create a Roadmap": This module emphasizes that a vision is realized by setting clear, measurable objectives and integrating strategic checkpoints into the development process. It teaches that alignment is maintained by consistently measuring progress against the goals derived from the vision, which is precisely what establishing KPIs and checkpoints achieves.

Summary:
The goal is to engage developers who are skeptical of the design process. The most effective approach is to involve them in a hands-on, collaborative activity that demonstrates the immediate value of design thinking. Instead of talking about the process theoretically, they need to experience how their direct involvement leads to better, more buildable solutions.

Correct Option:

C. Facilitate a workshop on ideating and sketching with the core team members:
This is the most engaging and effective strategy. A well-facilitated ideation and sketching workshop is active, collaborative, and taps into the developers' innate problem-solving skills. It shows them that design is not about receiving finished specifications but about co-creating solutions. This hands-on experience can break down barriers, build empathy for user goals, and demonstrate how their early input improves feasibility and creates a better product.

Incorrect Option:

A. Conduct interviews with developers to gather insights on process approaches:
While this seems inclusive, it is a passive and analytical approach that keeps developers at a distance. It treats them as subjects to be studied rather than partners to be engaged. It is unlikely to create the buy-in that comes from direct, positive participation.

B. Invite the developers to lead the conversation for synthesis and persona development:
This is a high-risk strategy. Asking skeptics to lead a complex, nuanced process they don't yet believe in can backfire. Without proper context or buy-in, they may feel set up for failure or dismiss the activity as irrelevant, reinforcing their skepticism rather than alleviating it.

Reference:
Salesforce Trailhead, "Collaborate for Better Customer Experiences": This module emphasizes that cross-functional collaboration is key to success. It advocates for involving developers early in the design process through collaborative workshops, which helps break down silos, build shared understanding, and create a sense of joint ownership over the final product.