cross-channel-journey

name	cross-channel-journey
description	Design a coherent journey across product, email, support, human service, documentation, billing, and other channels while preserving state and expectations.

Cross Channel Journey

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using user research, touchpoint inventory, systems/state, channel owners, policies, and common failure cases. Do not fill material gaps with assumptions when they can change the result.
3. Map user goal and entry points, identify channel transitions, define information/state that must carry across, eliminate contradictory instructions, and design recovery from interrupted handoffs.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Users do not have to restart or reconcile conflicting truths when moving between service channels.