An interface built for technical users fails business users
Consultants and power users call a screen powerful, and business users in the same company call it unusable.
A screen may assume knowledge of the system’s internal structure. Check the tasks and knowledge of the intended users before deciding whether to change terminology, layout, training or functionality.
Key facts
- The same screen gets opposite verdicts in one meeting.
- Business users need a consultant present for routine tasks.
- Business users ask for outcomes. Technical users ask for fields.
- Entities, relationships and configuration hierarchies mapped directly onto menus are quick to build and hard for business users to learn.
- Two views over one model add maintenance and may drift without shared behaviour and coordinated releases.
Why it happens
Internal structure became navigation. Entities, relationships and configuration hierarchies map directly onto menus, which makes them quick to build.
Vocabulary and feedback. System labels and feedback that comes mostly from consultants widen the gap, as described in Onboarding needs a consultant.
Permissions are used to reconcile them, and hiding fields leaves the screen organised around the technical model.
How it shows up
- Business users need a consultant present for routine tasks
- Training is repeated and forgotten
- The same screen gets opposite verdicts in one meeting
- Business users keep their own document describing the process in their words
- Business users ask for outcomes, technical users ask for fields
Options and trade-offs
What helps:
- A simplified visual mode with its own structure
- Labels based on business outcomes, with technical terms available on request
- The technical interface kept intact for consultants
- A shared data model and design system under both views
The tension: two views double maintenance and drift apart as features land in one of them. Every new feature needs a defined form in both views before release.
A single view with progressive disclosure is cheaper to maintain. It keeps the technical structure as the frame, and business users still have to learn it.
Common mistakes
- Treating the problem as a training gap
- Hiding fields by permission and keeping the technical layout
- Removing technical depth that consultants rely on
- Letting the two views drift apart after release
Where we’ve worked on this