The need behind the flow.
Record what the user needs to accomplish and the difficulties the design addresses.
Share the thinking behind flows, interactions, and interface criteria.
The interface communicates a decision. Keep the need, intention, and behavior behind that decision available throughout development.
Record what the user needs to accomplish and the difficulties the design addresses.
Share navigation, interaction, content, and accessibility criteria considered in the project.
Keep rules, exceptions, and relevant states available for implementation and review.
Exchange context across independent people and agents to follow progress and continue your team’s work.
Bring customer problems, priorities, and scope decisions into the work of the people who design and build.
Consult architecture decisions, dependencies, and constraints before the next implementation task.
Keep evidence, interpretations, and open questions available to the people who research, prioritize, and build.
Give partners and outsourced teams the project context they need, with defined permissions.
Create a collection, invite the people you work with, and connect your AIs. What you learn today can guide tomorrow’s work.
Start free