Expectancy Conformity

This post is a conceptual explanation of expectancy conformity – including exam questions, core components, and tags.

In a Nutshell

Expectancy conformity means that system behavior, naming, and placement align with learned patterns and mental models. This reduces cognitive load, speeds up decision-making, and lowers misuse errors.

Compact Technical Description

As a principle of dialog design (ISO 9241-110), expectancy conformity requires:

• internal consistency (same things behave the same way)
• external consistency (platform/industry conventions)

It affects:

• Terms/labels
• Icons and color semantics
• Navigation
• Feedback, undo, confirmations
• Keyboard (Enter confirms, Escape cancels)

Deviations only make sense if they demonstrably provide value and are secured through onboarding/microcopy.

Exam-Relevant Key Points

• Internal vs external consistency
• Alignment with platform guides/industry standards
• Domain terminology consistent (glossary)
• Predictable system feedback + undo
• Keyboard + focus predictable (A11y/WCAG)
• Measurability: first click, tree testing, telemetry

Core Components

1. Target audience mental models
2. External conventions
3. Internal design system (tokens/components)
4. Information architecture
5. Labels/microcopy
6. Iconography
7. Interaction patterns
8. Status/feedback
9. Keyboard/shortcuts/focus
10. Evidence (tests/telemetry)

Practical Example

Problem: "Archive" button deletes permanently -> expectancy breach
Solution:
- Rename: "Archivize"
- Icon: Box instead of trash can
- Snackbar: "archived" + action "Undo"
- Measurement: First-click success increases (e.g., 60% -> 92%)

Advantages and Disadvantages

Advantages

• Less onboarding required
• Fewer misuse errors/support cases
• Faster decision-making

Disadvantages

• Less differentiation/innovation room
• Effort to maintain standards/conventions

Typical Exam Questions (with Short Answer)

1. Internal vs external consistency? Internal = same across the app; external = like the platform/industry.
2. How do you measure expectancy conformity? First click, time to selection, misclick rate, user testing.
3. When are you allowed to deviate? When it creates measurable value + is explained/tested.

Most Important Sources

1. https://www.nngroup.com/articles/ten-usability-heuristics/
2. https://de.wikipedia.org/wiki/ISO_9241