Analogous research means looking at organizations outside your own industry that have solved a structurally similar problem, then borrowing insights from how they solved it - exactly what option A describes. In the Platform Strategy Designer context, this question belongs primarily to Value Design. In Value Design, the strategy designer links validated human needs to business outcomes and external context, then defines measurable signals that show whether the intended value is actually being created. Analogous research deliberately looks outside the immediate industry for contexts that contain a structurally similar challenge.
The purpose is not to copy another organization but to transfer useful principles, generate unexpected ideas, and expand empathy beyond familiar solutions. Here, An organization outside of their industry that has solved unique but similar problems is the strongest choice because it most directly matches the outcome, constraint, or decision described in the scenario. The other choices may be useful in a different stage or for a different question, but they do not address the central requirement as directly. A creative setting outside of their office that provides more inspiration and activity focuses attention elsewhere, while A complex system that their customers have experienced navigating successfully addresses a related concern without providing the same fit to the scenario ' s stated objective.
Study Guide Topics: Value Design
Official Salesforce Reference: Research for Design Strategy - Explore Design Strategy Research Methods

Feasibility focuses on operational capacity, technical capabilities, distribution channels, and strategic partners required to execute and deliver the solution. In the Platform Strategy Designer context, this question belongs primarily to Tools and Artifacts. In Tools and Artifacts, the key is to select the method, framework, artifact, or Salesforce capability that directly addresses the uncertainty in the scenario and supports an evidence-based decision. Feasibility is broader than software implementation. It includes the capabilities, channels, operating model, resources, partnerships, and constraints required to deliver the proposition reliably. These factors determine whether a desirable and viable concept can actually work in the real organization. Here, Distribution channels, capabilities, and potential partners is the strongest choice because it most directly matches the outcome, constraint, or decision described in the scenario. The other choices may be useful in a different stage or for a different question, but they do not address the central requirement as directly. Business ROI, data analytics, and customer engagement focuses attention elsewhere, while User desirability, company viability, and deployment stability addresses a related concern without providing the same fit to the scenario ' s stated objective. That distinction is important on the exam: select the method or capability that resolves the specific uncertainty in the scenario rather than the option that is merely plausible in a broader project.
Study Guide Topics: Tools and Artifacts
Official Salesforce Reference: Salesforce Designer Quick Look

Aligning UX research objectives directly with business KPIs demonstrates tangible value to skeptical stakeholders. In the Platform Strategy Designer context, this question belongs primarily to Intangible Deliverables. In Intangible Deliverables, the strategy designer creates alignment, trust, shared understanding, ethical awareness, and persuasive communication so that people can make coordinated decisions around the intended future state. Research is more likely to be valued when its questions are connected to outcomes stakeholders already care about. Aligning UX research goals with business goals shows how evidence can reduce uncertainty around adoption, retention, conversion, support demand, or other strategic measures. Here, Align UX research goals with stakeholders ' goals. is the strongest choice because it most directly matches the outcome, constraint, or decision described in the scenario. The other choices may be useful in a different stage or for a different question, but they do not address the central requirement as directly. Strictly align to stakeholders ' business requirements. focuses attention elsewhere, while Create high-fidelity prototypes to gain design buy-in. addresses a related concern without providing the same fit to the scenario ' s stated objective. That distinction is important on the exam: select the method or capability that resolves the specific uncertainty in the scenario rather than the option that is merely plausible in a broader project.
Study Guide Topics: Intangible Deliverables
Official Salesforce Reference: Alignment as a Strategic Craft - Gain Alignment

Cross-departmental collaboration relies on shared governance models, alignment on taxonomy, decision- making, and communication structures. In the Platform Strategy Designer context, this question belongs primarily to Leveraging Adjacent Roles/Skills. In Leveraging Adjacent Roles/Skills, the strategy designer works effectively with architects, developers, business analysts, organizational designers, accessibility specialists, and other disciplines so that strategy can move into feasible execution. Effort is a practical prioritization input because it represents the cost, complexity, time, and organizational capacity required to deliver an initiative. Comparing effort with expected value or impact helps teams make transparent trade-offs and direct limited resources toward the strongest opportunities. Here, Create a single enterprise-wide digital governance model. is the strongest choice because it most directly matches the outcome, constraint, or decision described in the scenario. The other choices may be useful in a different stage or for a different question, but they do not address the central requirement as directly. Unify all organizational tech stacks under one platform. focuses attention elsewhere, while Have the final say in all intra-departmental decisions.
addresses a related concern without providing the same fit to the scenario ' s stated objective. That distinction is important on the exam: select the method or capability that resolves the specific uncertainty in the scenario rather than the option that is merely plausible in a broader project.
Study Guide Topics: Leveraging Adjacent Roles/Skills
Official Salesforce Reference: Design Strategy Prototyping - Explore Key Prototyping Considerations

Business Process Modelling (BPM) maps operational workflows, operational dependencies, and backend factory interactions to eliminate inefficiencies. In the Platform Strategy Designer context, this question belongs primarily to Leveraging Adjacent Roles/Skills. In Leveraging Adjacent Roles/Skills, the strategy designer works effectively with architects, developers, business analysts, organizational designers, accessibility specialists, and other disciplines so that strategy can move into feasible execution. Business process modeling makes roles, activities, handoffs, decision points, inputs, outputs, and delays visible across an operational workflow. That makes it more suitable for redesigning a multi- party internal process than a customer-facing journey or a Jobs To Be Done statement. Here, Business process modelling is the strongest choice because it most directly matches the outcome, constraint, or decision described in the scenario. The other choices may be useful in a different stage or for a different question, but they do not address the central requirement as directly. Jobs To Be Done framework focuses attention elsewhere, while Customer journey mapping addresses a related concern without providing the same fit to the scenario ' s stated objective. That distinction is important on the exam: select the method or capability that resolves the specific uncertainty in the scenario rather than the option that is merely plausible in a broader project.
Study Guide Topics: Leveraging Adjacent Roles/Skills
Official Salesforce Reference: Process Mapping for Business Analysts - Get Started with Process Mapping