mh-cto-sdlc-journey-map

To map the current-state user journey, you analyze the as-is workflow by identifying stages, actions, tools, handoffs, and pain points. This process requires persona sketches and a domain model as inputs to define journey boundaries and generate a comprehensive map document.

As-is workflow analysis documents how users achieve their goals today, capturing every stage, action, tool, handoff, and pain point. You need it during product definition to establish a baseline before designing improvements or future-state workflows.

Yes, you need persona sketches and a domain model to start user journey mapping. The skill retrieves these inputs from persistent facts to define journey boundaries and accurately describe stages from the user's perspective.

The best way to identify pain points and handoffs is mapping the current-state workflow from the user's perspective. Documenting each action and tool used highlights where users experience friction or transfer responsibility across stages.

Current-state journey mapping requires persona sketches and a domain model from persistent facts to function. Without this structured input, you cannot accurately define journey boundaries or describe stages in the user's language.