interaction-flow
/layers:interaction-flow
Assumes /layers:intro has been loaded for framework context.
The interaction structure and flow layer defines how a person interacts with the product: the places they navigate, the affordances available, the content presented, and the flow between states. It sits above the conceptual model (which defines what exists) and below the surface (which defines how it looks).
Decisions this layer needs to make:
- What are the distinct places this flow moves through?
- What can the user do in each place, and where does each action take them?
- What content does each place need to show?
- What happens on failure paths, empty states, and edge cases?
- Is the flow as simple as it can be while still serving the job?
Methods:
| Method | When |
|---|---|
| Breadboarding (Ryan Singer / Shape Up) | Default for most flows. Text-based notation that forces interaction logic to be evaluated before visual design makes changes feel expensive. |
| User story mapping (Jeff Patton) | Complex product, many user types, planning incrementally. Maps activities → tasks → stories across a timeline. |
More from jamiemill/layers-skills
layers-conceptual-model
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
160layers-domain
Maps domain concepts, terminology conflicts, and bounded contexts — produces a noun harvest for the conceptual model layer
158layers-orient
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
157layers-intro
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
157layers-product-strategy
Connects user opportunities to business outcomes and solution bets — produces a strategy tree and prioritised experiments
157layers-interaction-flow
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions
157