Expectation Conformity
This post provides a conceptual overview of expectation conformity – including test questions, core components, and key topics.
In a Nutshell
Expectation conformity means system behavior, naming, and placement align with established patterns and mental models. This lowers cognitive load, speeds up decision-making, and reduces user error.
Core Definition
As a principle of dialogue design (ISO 9241-110), expectation conformity requires:
- internal consistency (same things behave the same way)
- external consistency (platform and industry conventions)
It covers:
- Labels and terminology
- Icons and color semantics
- Navigation
- Feedback, undo, and confirmations
- Keyboard interaction (Enter confirms, Escape cancels)
Deviations only make sense when they deliver measurable benefits and are supported by onboarding or microcopy.
Key Testing Points
- Internal versus external consistency
- Alignment with platform guides and industry standards
- Consistent domain terminology (glossary)
- Predictable system feedback and undo options
- Expected keyboard and focus behavior (A11y/WCAG)
- Measurability: first-click testing, tree testing, telemetry
Core Components
- User mental models
- External conventions
- Internal design system (tokens and components)
- Information architecture
- Labels and microcopy
- Iconography
- Interaction patterns
- Status and feedback
- Keyboard, shortcuts, and focus
- Evidence (tests and telemetry)
Real-World Example
Problem: "Archive" button permanently deletes → breaks expectation
Solution:
- Rename to "Archivize"
- Icon: box instead of trash can
- Snackbar: "archived" + "Undo" action
- Result: first-click success increases (e.g., 60% → 92%)
Strengths and Drawbacks
Strengths
- Shorter onboarding time
- Fewer errors and support requests
- Faster user decision-making
Drawbacks
- Less room for differentiation and innovation
- Effort required to maintain standards and conventions
Common Test Questions (with Quick Answers)
-
What’s the difference between internal and external consistency? Internal = consistent within your app; external = aligned with your platform or industry.
-
How do you measure expectation conformity? First-click testing, decision time, error rate, user testing.
-
When can you break the rule? Only when it delivers measurable value and is explained and tested.