A strategy designer is hired to help service agents pool their shared knowledge, see the bigger picture, and understand what may be causing poor and disjointed support experiences, and where other pain points and opportunities may lie. Which method of co-design workshop should be used?
Journey mapping is the method built to surface end-to-end pain points and disjointed experiences across a service, giving participants the 'bigger picture' the scenario describes. 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. Journey mapping combines stages, actions, touchpoints, emotions, needs, and pain points into an end-to-end representation of an experience. It is especially useful when knowledge is fragmented across people or teams because the shared artifact exposes patterns and breakdowns that are difficult to see in isolation. Here, Journey mapping 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. Ideation focuses attention elsewhere, while Prototyping 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: Journey Mapping - Start Your Journey Map
================================================================
Currently there are no comments in this discussion, be the first to comment!