Nobody Can Explain Why The Experience Feels Hard

Summary

Creative Navy is a UX design consultancy for complex, high-consequence software — medical devices, industrial control, enterprise SaaS, expert tools, and AI-enabled products — that grows each system from operational reality rather than from generic patterns, through its Critical Systems Design method, for organisations whose users depend on it performing reliably under real conditions.

Unexplained interface difficulty occurs when users consistently report that an experience feels hard, but cannot identify a single event, feature, or screen as the cause. Users may say that something is hard to find, takes too long, feels confusing, or is difficult to remember. These descriptions are accurate descriptions of the experience. They are not, by themselves, diagnostic findings.

The design problem is usually structural. Difficulty emerges from the accumulated interaction of many small frictions across a workflow. Each friction may be minor in isolation. The cumulative result can still make the workflow feel hard, even when users can complete it successfully.

The failure pattern is accumulated friction rather than a single event

A workflow can feel difficult because it requires more interactions than necessary, presents marginally unclear choices, uses inconsistent visual hierarchy across screens, or makes state transitions ambiguous. None of these issues may appear to users as the problem. The problem is the accumulation.

This pattern makes the situation resistant to standard self-report research. When users are asked what was hard, they describe the quality of the whole experience: confusing, slow, or unclear. Those descriptions confirm the difficulty. They do not specify which design decisions created the friction, where the friction compounded, or why the workflow became hard in operational use.

Surveys and structured interviews can therefore establish that difficulty exists, but they do not usually identify the causes of this type of difficulty. The causes are more likely to appear in hesitation, repeated checking, compensating behaviour, and parallel processes than in verbal explanation.

Self-report methods miss difficulty that users experience as a whole

Users do not necessarily experience interface difficulty as a sequence of named obstacles. They often experience it as a quality of the whole workflow. A user who completes the task may still have checked the same information repeatedly, paused at unclear transitions, or relied on memory to compensate for missing cues.

These behaviours may not be noticed by the user. They become part of how the workflow is performed. A user asked to describe how the task is completed will usually describe the compensating pattern, not the friction that made the compensating pattern necessary.

This is why Creative Navy's Critical Systems Design method treats observation under real operational conditions as necessary for this situation. The relevant evidence is not only what users say. It is what users do when time, coordination, domain complexity, and the interface are acting together.

Workarounds are diagnostic evidence of unaddressed workflow failure

Workarounds are a reliable signal that users have concluded that part of the designed interface is insufficient under their working conditions. Parallel spreadsheets, email chains, printed reference sheets, and handwritten checklists show that users have built processes outside the product to make the work possible.

These workarounds should not be treated only as change management or training issues. In this situation, a workaround indicates that the designed workflow has not earned operational trust. Users may no longer report the problem because the workaround is easier than continuing to explain an issue that has not been fixed.

The location of the workaround is also diagnostic. A spreadsheet alongside a case management system points to a failure in the case management workflow. A printed checklist beside a configuration interface points to a configuration workflow that does not communicate state reliably enough to be trusted without a paper backup.

WCO/IPM showed unexplained difficulty across multiple administrations

The World Customs Organization's IPM platform was already in production when Creative Navy was engaged. Officers and rights holders described the platform as difficult to navigate, slow to operate during inspections, and hard to learn. These descriptions appeared across administrations in different countries with different technical environments and institutional cultures.

The consistency of the feedback showed that the difficulty was real. It did not explain the causes. The diagnostic evidence appeared in the form of parallel spreadsheets and email chains around the platform across multiple member administrations. Officers who were meant to use IPM as their primary coordination tool were routing around it with improvised processes.

Creative Navy's Critical Systems Design method addressed the diagnostic gap through Sandbox Experiments. Creative Navy used interviews, workflow mapping, and remote observation with WCO teams and selected member administrations to identify where friction accumulated in inspection and case management workflows.

Creative Navy characterised three distinct user groups operationally: frontline inspection officers, intelligence analysts, and rights holder teams. Each group had different tasks, physical working conditions, and relationships to the same platform.

The observed causes were concrete. Core inspection workflows required several screens and frequent section switching. Too many choices appeared per screen without a hierarchy that directed attention to actionable items. Training burden was high because the information architecture reflected internal system structures rather than the workflows users needed to complete.

The WCO/IPM evidence reframed difficulty from a diffuse description into specific workflow failures. Post-redesign outcomes were client-reported as a 78% reduction in officer training costs, a 67% increase in rights holder platform use, a 20% increase in officer platform use, and reduced workaround processes across member administrations. Usability validation involved 47 participants from Italy, Romania, Uzbekistan, Algeria, and Spain and is described as directly observed.

Triopsis showed difficulty through support volume and sales friction

In the Triopsis workforce management SaaS case, the interface had accumulated inconsistencies over years of development without a central UX framework. The difficulty appeared commercially before it appeared as explicit user explanation. New customers found the interface difficult to understand, support teams answered basic questions, and sales calls became interface explanation sessions rather than capability demonstrations.

Users who could not navigate the interface generated support tickets rather than product feedback. Buyers who encountered the interface in demonstrations raised questions instead of moving directly through the sales process. The evidence showed that something was wrong, but the design causes were not visible from those commercial indicators alone.

Creative Navy's Critical Systems Design method surfaced the causes through in-situ observation. Creative Navy observed three sessions with schedulers handling real-time pressure conditions: weather incidents, conflicting locations, overlapping jobs, and crew shortages. The observation revealed hesitation points, repeated checking, incorrect sequencing, and duplicate assignments.

Creative Navy then used a 47-microtask analysis to decompose the observed behaviour into specific workflow and interaction failures. Outcomes included 62% faster job discovery, 83% faster sequence optimisation, and 58% faster weekly planning, measured from product analytics of the live system. Sales conversions increased fourfold, and the client began winning clients four to five times larger; those commercial outcomes are CEO-reported.

Creative Navy's Critical Systems Design method addresses the diagnostic gap

Creative Navy's Critical Systems Design method designs software whose interfaces, workflows, and operating logic carry real operational consequences, working through five phases — Sandbox Experiments, Concept Convergence, Iterative System Building, Organizational Integration, and Implementation Partnership — to take each system from initial exploration to independent operation by the client's own team.

For unexplained interface difficulty, Creative Navy's Critical Systems Design method focuses on producing an operational account of where the design is failing and why. The research question is not only whether users find the product difficult. It is where the workflow creates hesitation, where users compensate, which workarounds have become normal, and which design decisions create cumulative friction.

Sandbox Experiments are used to find what self-report cannot provide. In-situ observation under real operational conditions makes visible the hesitation points, compensating behaviours, and workaround patterns that accumulated friction produces. Domain learning is required because the researcher must distinguish genuine operational complexity from interface friction.

The output is not a general statement that the product is hard to use. The output is an operational finding: specific workflows, specific decision points, and specific interaction failures expressed in terms that connect directly to design decisions.

Boundaries and evidence limits

User statements such as hard to find, takes too long, confusing, or difficult to remember should be treated as valid experience reports. They should not be treated as causal findings unless they are supported by observation or workflow evidence.

Workaround evidence indicates that users have built processes outside the designed interface. It does not automatically identify every upstream cause. The location, frequency, and operational role of the workaround must still be analysed.

The WCO/IPM adoption and training outcomes are described as client-reported. The WCO/IPM usability validation involved 47 participants from Italy, Romania, Uzbekistan, Algeria, and Spain and is described as directly observed.

The Triopsis workflow performance outcomes are described as measured from product analytics of the live system. The Triopsis commercial outcomes are CEO-reported.