Stage 2: Information architecture (1 week)
IA is how you organize features, navigation, and content so users find what they need without thinking about where it is.
Why IA matters more in enterprise
Consumer apps have 10-20 screens. Enterprise applications can have 50-200+. Without deliberate IA, navigation becomes a maze and users bookmark three screens and never discover the rest.
Common IA mistakes
Organizing by department instead of by task. Users think in workflows, not org charts. "I need to approve this purchase order" doesn't map to "Finance > Procurement > Approvals > Pending."
Too many top-level items. If main navigation has 12+ items, users stop reading after four. Group related functions. Use progressive disclosure.
Inconsistent naming. If one section says "Clients," another says "Customers," and the API says "Accounts," users lose trust.
Stage 3: Wireframing and prototyping (1-2 weeks)
Low-fidelity wireframes
Grayscale layouts showing content hierarchy, navigation, and interaction flows. Every screen, every user role, every key scenario. This catches cheap-to-fix problems: "Where does the user go after submitting this form?" or "This workflow requires three tabs — can we consolidate?"
Interactive prototypes
Clickable prototypes that look like the real product but contain no code. Users click through complete workflows, revealing usability issues static wireframes miss.
For AIG Israel's first fully digital claims system, weeks of research with agents and claims handlers shaped one key decision. Five insurance types (car, property, health, travel and general) each need different information. So the forms adapt to the claim: a car accident shows different fields from a travel delay. We went from brief to build-ready specifications in three months, and most claims moved from the call center to self-service.
For IBI Smart's trading platform, prototyping revealed that users needed to execute trades directly from the portfolio view. Nobody had requested it, because they'd never seen it as an option. That single insight reduced trade execution from 7 steps to 3.
Stage 4: Visual design (1-2 weeks)
Design system, not just screens
For enterprise products, you need a design system: a library of reusable components with defined behavior and styling. It keeps 50+ screens consistent and speeds up iteration as the product grows. We built the Israeli Government Design System: hundreds of accessible, RTL-native components in React, Angular, vanilla JavaScript and HTML/CSS, with a Figma kit that mirrors the code. 5,000+ government developers use it.
Four interaction rules to check every screen against
- Top tasks in three steps. Map the five tasks users perform most. Each should take three taps or clicks at most.
- Value on the first screen. An empty screen or a long onboarding sends users away. Pre-populate relevant content and ask only for the information you need to show something useful.
- Feedback within 100ms. Jakob Nielsen's response-time limits put 0.1 second as the limit for a response to feel instantaneous. Every action needs a visible response: a button that changes state, a progress indicator while data loads.
- Complexity that grows with the user. New users need guidance. Power users need shortcuts. Track feature usage and reveal advanced options progressively.
Accessibility is not optional
WCAG 2.1 AA compliance is the minimum. That means a 4.5:1 contrast ratio for normal text, keyboard navigation for all interactions, screen reader compatibility and clear error messaging. Accessible design is also better design for everyone.
Stage 5: Usability testing (1 week)
Recruit 5-7 representative users. Give them specific tasks. Watch them attempt each task without helping. Record hesitations, wrong clicks, and immediate successes.
In Jakob Nielsen's classic analysis (2000), a study with five participants finds about 85% of usability problems. You don't need 50 participants. You need 5 real users and the discipline to watch them struggle.
| Metric | What it tells you |
|---|
| Task completion rate | Can users accomplish their goals? |
| Time on task | How efficient is the design? |
| Error rate | Where do users make mistakes? |
| System Usability Scale (SUS) | Overall perceived usability (the average score is 68) |
| First-click accuracy | Does the user's first instinct lead right? |
Common mistakes in enterprise UX
Designing for the demo, not for daily use. The CEO sees a 20-minute demo. Users live in it 8 hours a day. Optimize for the 8-hour experience: keyboard shortcuts, saved preferences, minimal clicks for frequent tasks.
Treating mobile as an afterthought. Even enterprise tools get used on phones, and retrofitting mobile layouts costs far more than designing them from the start. When we redesigned WeShoes, 70% of its traffic was mobile, so we designed for thumbs first and scaled up to desktop.
Skipping the handoff. Design is only as good as its implementation. Specifications, assets, component documentation, animation details — these determine whether developers build what was designed.
Frequently asked questions
How much does enterprise UX design cost?
For mid-complexity (20-40 unique screens): $30K-$80K for the full process. That's typically 15-25% of total development budget and the part most correlated with product success. See our cost guide for complete project pricing.
Can we skip research if we already know our users?
You think you know your users. You know what they tell you in meetings. Research reveals what they actually do — which is different. At minimum, observe 3-5 users performing real tasks. The "we know our users" assumption is the most expensive one in enterprise software.
How do we maintain design quality post-launch?
A design system maintained as a shared resource between design and development. When new features are built, they use existing components. When new patterns are needed, they're added with documentation. The system prevents the slow degradation where each developer interprets the design differently. Need UX help for your product? Let's talk.
