Define the experience to explore

InputCopy Anchor Link

Brief, research, current behavior, marketing context and constraints shared with the team. A ticket can be a source if the team uses one; design work starts from the question to clarify.

ProcedureCopy Anchor Link

1. Write the actor, required capability and value in the story, linking them to evidence.
2. Define the decision the prototype must help make. If outcome or scope remain ambiguous, clarify them with ask-jado before assigning implementation.
3. Distinguish the desired outcome, interaction order and observation conditions: stories, flows and scenarios own different parts of the reasoning.
4. Bound the paths, states and content to explore. Declare what will be simulated and what remains out of scope.
5. Discuss feasibility concerns with development; record their constraints without determining their technical solution.
6. Prepare the UX record and test criteria.

Output and completion criterionCopy Anchor Link

Stories with IDs, sources and status; understandable scope; hypotheses and observable criteria. Every uncertainty that changes the user’s path has a question and a responsible contact.

Breaking work into development issues and tasks follows the team’s chosen process. The designer provides goals, the expected experience and evidence useful to that conversation.

Artifact contract source: UX Planner.