The strategy designer should work through the conflict in the workshop to reach a shared perspective, rather than avoiding or suppressing it. This helps surface different opinions and perspectives, foster constructive dialogue, and align on common goals and criteria. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-strategy-designer-certification-prep/navigate-conflict-in-a-workshop

Interviewing 8-10 customers about how banking fits into their lives and their ideal relationship with their bank is the best way to learn about the unique expectations of the company's customers. This method provides qualitative and contextual insights into the customers' needs, goals, pain points, and emotions. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-strategy-designer-certification-prep/conduct-customer-interviews

The designer should produce a business case and a roadmap to get buy-in from the business stakeholders. A business case is a document that outlines the rationale, benefits, costs, risks, and alternatives of a proposed project or solution. A roadmap is a visual representation of the plan, timeline, milestones, and dependencies of a project or solution. Together, they can help communicate the value proposition, feasibility, viability, and desirability of the cross-cloud 360 prototype to the business stakeholders. A business user flow and journey map may show how the prototype works and what pain points it solves, but they do not provide enough information on the strategic aspects of the project. Business metrics and ROI map may quantify some aspects of the project, but they do not explain how or why the prototype was created.