Use patterns to preserve learned behavior.
Design recurring structures to reduce reinterpretation.
Contents 6. Consistency & Coherence 3. Patterns
How to scale behavior without fragmentation.
First, ask yourself
“Does the growth of your system preserve user-learned patterns rather than replace them?”
Mission statement
Ensure users scale understanding by reusing interaction solutions.
Key heuristics Patterns
- Recurring structures must preserve learned behavior.
- Reused visuals must preserve their associated interaction logic.
- Existing patterns must be reused unless they cannot serve the need.
- Patterns must remain consistent across contexts.
- Patterns must function reliably in varied situations.
- New capability must extend established patterns without breaking logic.
- Departures from established patterns must be intentional and clearly signaled.
- Meaningful changes to patterns must be clearly communicated.
- Patterns must be formalized as shared system contracts.
Executive brief
The system must scale by reusing patterns, not by teaching new ones.
Core questions Patterns
“Does the system reuse proven solutions so new features feel familiar?”
“Can the system grow without breaking what users already know?”
Focus areas
Learning-transfer
“Where can users apply what they have already learned?”
“Do new features reuse existing interaction logic?”
Structure-aware
“Is complexity added through repetition or invention?”
“Are new surfaces composed of familiar parts?”
Consistency-aware
“When patterns evolve, is the change made explicit?”
“Are old patterns deprecated responsibly?”
AI-aware
“Does generative UI respect established patterns?”
“Is variation constrained by pattern rules?”
UX directives Patterns
Ensure behavioral consistency within patterns.
Do not reuse visuals without preserving interaction logic.
Prefer reuse over unnecessary invention.
Introduce new patterns only when existing ones cannot serve the need.
Apply patterns comprehensively across contexts.
Prevent fragmenting pattern logic within the system.
Design patterns for cross-context scalability.
Ensure recurring structures function reliably in varied situations.
Extend patterns incrementally during growth.
Add capability without breaking established logic.
Limit and signal deviations from established patterns.
Ensure exceptions are intentional and explicit.
Evolve patterns transparently.
Communicate meaningful pattern changes to prevent forced relearning.
Formalize patterns as shared system contracts.
Maintain documentation to preserve coherence across teams.
Executive summary
- Patterns are reusable interaction contracts, not recurring visual motifs.
- They preserve learned behavior by stabilizing structure and logic across contexts.
- The system must reuse and extend patterns before inventing new ones.
- Pattern behavior must remain consistent, scalable, and comprehensively applied.
- Deviations and evolutions must be intentional, explicit, and governed at system scale.
- Patterns succeed when growth adds capability without forcing users to relearn how the system works.
Success indicators
- Recurring interactions follow the same structure and behavior.
- Similar tasks use the same patterns across the system.
- Visual patterns match consistent interaction behavior.
- New features reuse existing patterns whenever possible.
- Changes to established patterns are clear and intentional.
One-line summary
Before a system can scale, interaction solutions must be reusable and recognizable.