Expectation Conformity

This post is a glossary entry on expectation conformity – including exam questions, core components, and related concepts.

In a Nutshell

Expectation conformity means that system behavior, naming, and placement align with established patterns and mental models. This reduces cognitive load, speeds up decision-making, and minimizes user errors.

Technical Definition

As a dialogue design principle (ISO 9241-110), expectation conformity requires:

• internal consistency (identical elements behave identically)
• external consistency (platform and industry conventions)

It covers:

• Terminology and labels
• Icons and color semantics
• Navigation structure
• Feedback, undo, and confirmations
• Keyboard interactions (Enter confirms, Escape cancels)

Deviations make sense only when they deliver measurable benefits and are supported by onboarding or microcopy.

Exam Checklist

• Internal vs external consistency
• Alignment with platform guides and industry standards
• Domain terminology consistency (glossary)
• Expected system feedback and undo actions
• Keyboard and focus behavior (A11y/WCAG)
• Measurable validation: First Click, Tree Testing, telemetry

Core Components

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

Real-World Example

Problem: "Archive" button deletes permanently → expectation violated
Solution:
- Rename to: "Archive"
- Icon: box instead of trash can
- Snackbar: "archived" + "Undo" action
- Measurement: First-click success improves (e.g. 60% → 92%)

Pros and Cons

Pros

• Faster onboarding
• Fewer errors and support requests
• Quicker user decisions

Cons

• Limited room for differentiation and innovation
• Overhead in maintaining standards and conventions

Common Exam Questions (Quick Answers)

1. Internal vs external consistency? Internal = consistent within the app; external = consistent with platform or industry norms.
2. How do you measure expectation conformity? First Click, time to selection, error rate, user testing.
3. When can you deviate? When it delivers measurable benefit and is explained and validated through testing.

Key Sources

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