Scenario 03

Web Application

A task-oriented digital product — a platform, management tool, patient portal, client dashboard or internal system — where the quality of the user experience is not a marketing consideration but an operational one. When professionals depend on a system to do their work, every friction point costs time, introduces error risk and reduces trust in the organisation that built it.

The situation

The organisation needs to build or redesign a web application. The users are not casual visitors who can be lost and replaced — they are professionals, clients or partners who have to use this system repeatedly, often under time pressure, often with high stakes attached to the decisions the application supports. The organisation knows what the system needs to do functionally but has not yet answered the harder question: how does it need to work for the people who will depend on it every day?

The most common failure mode Esario encounters in web application projects is the conflation of functional specification with UX design. A document that lists what the system must do does not tell you how the interface should present those capabilities, in what sequence, with what information hierarchy, and with what feedback mechanisms for errors and edge cases. These are design problems — and they cannot be solved by developers, however skilled, without design input.

What makes it complex

Web applications are complex because the users are experts. A consumer website can guide an unfamiliar user gently; a professional application cannot afford that patronising slowness. The interface must be dense enough to serve experienced users efficiently but clear enough not to introduce error for new ones. This is one of the most difficult design balancing acts in the discipline.

The backstage is always as important as the frontstage. A clinical management system, a financial reporting platform or a logistics dashboard is the visible surface of a set of operational processes, data flows and system integrations. Esario always begins web application projects with Service Design — mapping the real workflow before designing the interface that represents it.

How Esario approaches it — five phases

Phase 01
Workflow Mapping

Before any interface design begins, Esario maps the full operational reality the application must support. Who are the users — not by role title but by actual task, decision context and information need? What processes does the application need to support, and how do those processes interact with other systems, other people and other organisations? Where does the current workflow break down, and why?

The Service Blueprint produced in this phase is the contract between the design work and the operational reality it must reflect. It identifies the dependencies, the bottlenecks and the edge cases that will determine whether the application works in real conditions — not just in a demo.

Deliverables: Service Blueprint · User role analysis · Task flow maps · Edge case register · System dependency diagram

Phase 02
UX Architecture

The information architecture of a web application is its navigation model, its data organisation logic and its permission structure. Esario designs these with the workflow maps from Phase 1 as the foundation — ensuring that the interface presents information in the sequence and grouping that reflects how users actually make decisions, not the sequence in which data happens to be stored in the database.

Interaction design then addresses every critical workflow: the task flows that users complete most frequently and the error states and edge cases that will determine whether the system is trusted. Accessibility is built in from the first wireframe, not treated as a compliance exercise at the end.

Deliverables: Application IA · Navigation model · Wireframes for all critical flows · Error state design · High-fidelity mockups · Design system documentation

Phase 03
Evaluation & Validation

Professional application interfaces must be tested with the professionals who will use them — not with generic users recruited to approximate the target audience. Esario conducts task-based usability testing with representative users from the actual user population: clinicians, financial professionals, logistics operators, administrators, or whichever expert group the application serves.

The testing methodology for task-oriented applications goes beyond identifying usability problems. It measures task completion rates, time-on-task, error rates and recovery rates — the performance dimensions that matter when the application is used under real working conditions. Expert evaluation (heuristic analysis and WCAG conformance audit) runs in parallel with user testing to catch issues the protocol might miss.

Deliverables: Task-based usability test report · Performance metrics (completion rate, time-on-task) · Expert heuristic review · WCAG conformance audit · Validated design revisions

Phase 04
Technical Integration

Web applications exist at the intersection of multiple systems: back-end databases, third-party APIs, authentication services, data processing pipelines and external platforms. The quality of these integrations determines whether the application delivers on its UX promise in production — a beautifully designed interface backed by unreliable data feeds or slow API responses will fail its users regardless of how well the interaction design was executed.

Esario designs and implements API integrations and custom back-end components with the same rigour applied to the front-end design: clear specification, documented error handling, appropriate security measures and code that can be maintained and extended by the organisation after delivery.

Deliverables: API integration specification · Technical architecture document · Data flow diagrams · Security review · Integration test results

Phase 05
Live Monitoring & Iteration

Professional applications evolve. Regulatory requirements change. Workflows that seemed stable turn out to have edge cases that only appear in production. New user populations join as the organisation grows. The measurement architecture Esario implements post-launch captures usage patterns, error rates and drop-off points — providing the data foundation for a continuous improvement programme rather than a one-time delivery.

Analytics for applications are different from analytics for marketing sites. The metrics that matter are task completion, error frequency, session efficiency and feature adoption — not page views. Esario configures tracking and reporting frameworks that measure what actually determines whether the application is working.

Deliverables: Application analytics implementation · Task completion dashboard · Error monitoring · Quarterly UX review · Prioritised improvement backlog

Engagement flow — Web Application

PHASE 01 Workflow Mapping Service Design User research PHASE 02 UX Architecture UX Design Information Arch. Accessibility PHASE 03 Evaluation & Validation Usability testing UX Evaluation Refine PHASE 04 Technical Integration API & Software Dev AI Integration PHASE 05 Live Monitoring & Iteration Data Analytics Ongoing Evaluation OUTCOME Reliable, usable application trusted by its users Research Design Evaluation Technical Measurement

The five-phase engagement flow for a web application. The refinement loop (Phase 3 → Phase 2) is the core quality mechanism — design is validated with real expert users before development commits to implementation.

What you get

DeliverableRelevant for
Service Blueprint for the application's operational contextCTO, COO, product owner
Application information architecture and navigation modelCTO, development team
Wireframes and interaction flows for all critical tasksCTO, development team, stakeholders
High-fidelity mockups and design system documentationDevelopment team, CMO
Task-based usability test results with performance metricsCTO, product owner, C-suite
WCAG conformance audit and remediation specificationCTO, legal / compliance
API integration specification and documentationCTO, development team
Application analytics dashboard and quarterly UX reviewCTO, C-suite

What this is not

This scenario describes Esario's approach to the design and integration layers of a web application project. It does not imply that Esario replaces the client's development team or takes ownership of the complete software build. Esario works alongside existing development capacity, providing the design specification, integration architecture and UX quality assurance that enables the development team to build the right thing in the right way.

Building something people have to use every day?

The standard for professional applications is higher than for consumer products. We design for that standard.

Talk to Esario →