Outcomes

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.

The outcomes section is structured in two tiers. Operational outcomes describe what changes for users and teams working with a system: error behaviour, cognitive load, state visibility, recovery, workflow clarity, and team alignment. Strategic and organisational outcomes describe what becomes possible for an organisation once operational performance has been achieved.

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.

Every outcome page requires at least one grounded, specific result. The result may be measured, client-reported, or observed, but the evidential basis must be stated explicitly. A page without grounded evidence is not ready to publish.

Operational outcomes describe direct changes in use

Operational outcomes cover what changes when users and teams interact with the redesigned system under real conditions. These pages address product and UX decision-makers and connect to the failures and situations where the problems are described.

Operational outcomes are direct design outcomes. They describe changes in task performance, error exposure, state interpretation, recovery paths, training burden, and internal alignment around the product. They do not require a claim that the organisation has already converted the operational improvement into a commercial or strategic result.

Reduced error risk covers error likelihood and recovery load

Reduced error risk concerns systems where selection errors, mode errors, omission errors, or misinterpretation errors can create cascading consequences. Creative Navy's Critical Systems Design method addresses this through microtask analysis, error-likely interaction review, and iterative resolution of edge cases and degraded modes.

The clearest before-and-after error evidence is from the Gexcon CFD simulation software case. Configuration errors per simulation scenario fell from 5–8 errors to 1–2 errors after deployment of the redesigned interface. The corrective load associated with each error fell from 4–6 hours to approximately 20 minutes. Both figures were measured by Gexcon across real deployment locations, not in usability testing conditions.

The deSoutter Medical / Zethon surgical device interface provides a regulated medical-device example. Eight orthopaedic and trauma surgeons reported that device state could be verified during brief glances without reading, and that speed and parameter adjustments no longer interrupted workflow. The evidence basis is surgeon reporting from structured review sessions during the design engagement, not post-deployment operational measurement.

Improved operational clarity covers legibility under operating conditions

Improved operational clarity concerns systems where users have the necessary information but cannot act on it efficiently because they must interpret, cross-reference, or reconstruct system state. Creative Navy's Critical Systems Design method addresses this through information architecture redesign, state and status visibility work, cognitive load reduction, multi-perspective synthesis, and tension-driven reasoning.

In the Torqeedo maritime engagement, captains identified key energy states 50% faster with the redesigned interface than with the legacy UI in a controlled experiment with 24 subjects. Glance counts during manoeuvres were reduced in eye-tracking work during real sea trials with 7 subjects.

In the Triopsis engagement, job discovery was 62% faster and weekly planning was 58% faster, based on product analytics from real users in the live system. In the Akrivia Health clinical research platform case, governance reviewers could verify cohort construction logic without escalating to the research team that built the cohort; this was a client-reported operational outcome.

Lower training burden covers reduced dependence on formal instruction

Lower training burden concerns systems that require formal training before users can operate them. Creative Navy's Critical Systems Design method addresses this by designing for discoverability, reducing reliance on memorised states and sequences, and making system logic inferrable from the interface.

The Triopsis case changed onboarding from a mandatory 1-hour remote training session to an optional 15-minute video, with approximately 90% of users beginning to use the system without live instruction. This was client-reported post-rollout data.

The Gexcon case changed the training model from 3-day instructor-led events to short webinars and video materials. The Beissbarth automotive calibration case records training elimination: no-training onboarding became the standard commercial model across the customer base.

The World Customs Organization / IPM case provides a quantified institutional-scale example. WCO reported a 78% reduction in training costs for officers across a context that included 107 member administrations, multilingual environments, varied device fleets, and different connectivity conditions.

The Enhesa legal compliance platform provides a different evidential form. Before the redesign, 45% of users said they had watched training videos, and 81% of those said the videos were not helpful. After the redesign, only 21% of users onboarded post-launch sought training videos at all. The figures were client-measured by Enhesa from its NPS survey, with the pre/post comparison made across cohorts rather than a longitudinal panel.

Better state visibility covers mode, transition, and status recognition

Better state visibility concerns systems where users cannot see what state the system is in, when it has transitioned, or which mode they are operating in. Creative Navy's Critical Systems Design method addresses this through state and transition review, mode clarity design, and information hierarchy restructuring.

The Torqeedo engagement treated state visibility as the central design problem. Propulsion status, battery state, and generator information had been scattered across separate screens; the redesigned interface unified these into 27 screens across 4 operational modes, with a grid structure that kept related values in stable positions. The 50% faster energy state identification result is a direct measure of state visibility improvement.

In the Elsner engagement, sensor fault states such as delayed readings, contradictory values, and calibration faults were surfaced explicitly rather than hidden. The design also introduced a dual-priority alert hierarchy to distinguish primary operational alerts from secondary notifications.

The Swiss petrol station operator case applies state visibility to unattended outdoor terminals and multi-channel transactions. Pump states, card authorisation progress, language selection, and fault conditions needed to be unambiguous on 1024×768 pixel screens under weather conditions, direct sunlight, and temperature extremes. The evidence basis is design decisions documented and validated through prototype testing, with client-reported operational outcomes of improved consistency across sites.

Stronger recovery support covers designed paths back from degraded states

Stronger recovery support concerns systems where the interface gives users no clear path back when something goes wrong. Creative Navy's Critical Systems Design method treats recovery paths, edge cases, and degraded modes as part of the same design work as the primary workflow.

In the Triopsis engagement, weather incidents, job delays, and partial completions were treated as normal workflow states rather than exceptional conditions requiring workarounds. In the Elsner engagement, delayed sensor readings, calibration failures, and fault states were named and designed for, with interface behaviour under fault conditions validated in prototype testing with engineers.

The available stronger-recovery-support evidence still needs an additional specific before-and-after description of what recovery looked like before a redesign, including operational cost or safety exposure.

Better alignment across teams covers shared product reasoning

Better alignment across teams concerns situations where product, engineering, design, domain experts, and stakeholders hold incompatible mental models of what a system should do and why. Creative Navy's Critical Systems Design method addresses this through Concept Convergence, tension-driven reasoning, documented trade-off logic, and Organizational Integration.

The Triopsis engagement addressed multi-stakeholder governance without a central UX framework. The design system included 68 components and more than 200 documented states, giving a 5-person engineering team a coherent mental model rather than disconnected screens.

The Bofin fintech startup case involved an engineering team exceeding 50 developers working across multiple parallel modules. The design system provided shared naming, variant logic, interaction principles, and component boundaries. The product manager reported that mid-sprint clarifications from engineering decreased.

The Tetra / Prism case addressed developer resistance to design-led change. Creative Navy ran approximately 10 sessions attended by the CTO and broader product team, plus 5 dedicated one-hour sessions with developers only. The evidence basis for the session counts is Creative Navy-recorded; the outcome that resistance was resolved and the design proceeded is observed.

Strategic and organisational outcomes are downstream consequences

Strategic and organisational outcomes are not framed as direct products of design alone. The evidential framing is narrower: Creative Navy produced an operational result; that result removed a constraint or created a capability; the organisation was then able to act on it.

These pages address commercial, product leadership, and executive readers. They cover maintenance, capability access, verifiable performance claims, investment evidence, scaling without training dependency, and positioning through interface quality.

Reduced maintenance and downtime covers maintainability after delivery

Reduced maintenance and downtime concerns the ongoing cost of changing, extending, and maintaining a system after delivery. Creative Navy's Critical Systems Design method supports this by documenting design decisions with reasoning, not only specifications, so teams can modify a system without reconstructing intent each time.

The Triopsis design system included 68 components, more than 200 documented states, and 15 workflow types. It was built to give the engineering team a coherent mental model and reduce rework and QA effort. The Callsign fraud detection platform provides time-anchored post-engagement evidence: Callsign continued to use and extend the design system for at least two years after the engagement closed, without Creative Navy involvement, according to client-reported evidence.

The Bofin case addresses maintenance in a parallel-development context. A 50+ developer team was building multiple modules at the same time, creating a risk of design drift. The product manager reported reduced rework due to clearer component definitions and fewer mid-sprint clarifications from engineering.

The available reduced-maintenance-and-downtime evidence still needs a specific before-and-after description of maintenance cost or rework reduction with operational specifics.

Capability democratisation covers broader access to expert capability

Capability democratisation concerns systems that originally required expert users but are redesigned so that other roles can access the capability directly. The expert knowledge is not removed; it is encoded into the interface so it no longer has to be carried entirely by the user.

The Gexcon case is the clearest example. Before the redesign, the system was operable in practice by one active user per team: CFD specialists with years of experience. After the redesign, teams moved from one active user to three or four, according to client-reported operational data. Risk managers and safety analysts gained viable working access without reducing the scientific capability of the software.

The Owkin / K case treats capability democratisation as an explicit design goal in an AI biomedical research platform. The client wanted K's capabilities to become accessible to clinicians with low to medium scientific background. The outcome evidence is directional, based on internal product launch feedback and client characterisation, with no measured user metrics available.

The Hudex AI-powered intelligence analysis platform case applies capability democratisation across a wide expertise range, from ministerial-level government officials needing a fast overview to expert intelligence analysts conducting deep exploration. Client-reported user reception data included 45 existing users rating the redesign as significantly better, and 68% of new users rating usability as good with 23% rating it as very good.

Verifiable performance claims cover measurable product evidence

Verifiable performance claims are outcomes where design produces specific productivity or performance gains that can be used as evidence-grounded sales or marketing claims. The claim is not that every design engagement produces such claims; it is that when performance in reality is measured, the result can become a credible external claim.

The Triopsis case provides live-product analytics from real users: 62% faster job discovery, 83% faster job sequence optimisation, and 58% faster weekly planning. Sales conversions multiplied by four, according to the CEO. Tender scores improved by 10–20% attributable to design quality, based on client-reported tender evaluation documents.

The Gexcon case provides four deployment-measured figures: time to first successful simulation changed from 4 days to 6 hours, configuration errors per simulation changed from 5–8 to 1–2, corrective load per error changed from 4–6 hours to approximately 20 minutes, and active users per team changed from 1 to 3–4. These figures were measured by Gexcon across real deployment locations.

The Tetra / Prism case provides an adoption measure. Mobile app adoption among the user population that should have been using the app rose from 12% to 64% over the year following the redesign launch. The web platform NPS improved from 72% to 85%, measured by Tetra approximately 4 months after the new web design launched.

The Enhesa case provides a clean attribution window for NPS. NPS moved from 68% to 84% in the two months following the redesigned platform launch, and Enhesa confirmed that no other product changes were made between the baseline and post-launch measurements. The later two-year figure of 87% is directional because subsequent product changes had occurred.

Design as investment evidence covers interface quality in funding contexts

Design as investment evidence concerns cases where interface quality becomes relevant to securing investment or development funding. The claim is not that Creative Navy produces fundraising outcomes. The narrower claim is that design quality can communicate product readiness, product thinking, structural coherence, and market readiness in investment contexts.

In the Veecle embedded systems development studio case, designs across onboarding, telemetry, workspace creation, AI integration, and a UI starter kit were used in investor demonstrations. Veecle reported that the interface comprised approximately 70% of the pitch and that the engagement was instrumental in unlocking £2M in development funding. This is client-reported and not independently verified.

In the Owkin / K case, the prototype served as the lead artefact of the investment pitch and answered whether Owkin had a paradigm for making backend capability accessible to users. Owkin attributed £5M in investment to the design work. The figure is approximate, client-reported, and not independently verified.

In the Hudex case, the redesign was reported by the client as critical and foundational to the commercial growth phase. Three months into that growth phase, Hudex received £3M in investment. The causal link between interface quality and the investment decision cannot be independently verified.

Scaling without training dependency covers reach beyond trained users

Scaling without training dependency concerns products whose reach is limited because operation requires specialist training, local training support, or specialist staff. Creative Navy's Critical Systems Design method addresses this by encoding guidance, orientation, and operating logic into the interface.

The World Customs Organization / IPM case is the primary example. IPM served officers across 107 member administrations with inconsistent connectivity, mixed device fleets, varied technical literacy, and different administrative cultures and languages. WCO reported a 78% reduction in training costs after the redesign.

The same case records a 200% increase in rights holder sign-ups and deployment in field operations involving more than 2000 officers. These figures are client-reported by WCO to Creative Navy.

Positioning through interface quality covers visible differentiation

Positioning through interface quality concerns markets where technical specifications between competing products have converged and the interface becomes the visible differentiator. The page does not claim that Creative Navy produces positioning as a service. It claims that design quality can produce positioning as a consequence when the interface performs differently under evaluation.

The Triopsis case records that the interface became a visible advantage in sales demos. Prospective customers commented on clarity unprompted, the company began winning clients 4–5 times larger than before, and tender scores improved by 10–20% on design criteria.

The Torqeedo case records a CEO-reported strengthening of competitive position in the professional maritime market. Torqeedo was subsequently acquired by Yamaha Motor Co.; the causal link between the interface and the acquisition is inferred from timing and competitive positioning, not independently verified.

The COX Marine case records distributor-reported feedback relayed to Creative Navy: distributors reported to the client that the cluster display interface is the best in the industry. The evidence is not independently verified.

The Elsner Elektronik / Cala Touch KNX case records dealer-channel advocacy. Dealers who saw early prototypes at trade fairs became active advocates, placing promotional materials in their locations and providing more comprehensive recommendations to customers. Early post-launch sales figures were reported by Elsner as better than expected, but precise figures are not available.

Evidence calibration applies across both outcome tiers

Outcome evidence is calibrated by source and strength. Some results are measured in live products or deployment contexts, such as Triopsis product analytics and Gexcon deployment metrics. Some results are client-measured, such as Enhesa NPS and Tetra adoption. Some results are client-reported, such as WCO training cost reduction and Callsign design system longevity. Some results are Creative Navy-recorded or Creative Navy-observed during engagements, such as session counts or observed resolution of design resistance.

The evidential standard is explicit: every outcome page needs at least one grounded result, and the type of evidence must be stated. Strategic and organisational outcomes require particular care because they are downstream consequences rather than direct design outputs.

Boundaries and limits

Outcome pages should not be read as guarantees. The evidence describes what was measured, reported, or observed in specific engagements.

Strategic and organisational outcomes are downstream from operational performance. The correct framing is that Creative Navy produced an operational result that removed a constraint or created a capability, and the client organisation then acted on that change.

Some evidence is not independently verified. Client-reported funding attribution, distributor feedback relayed through a client, and CEO-reported commercial effects are useful evidence, but they are not equivalent to independent measurement.

Some outcome pages identify evidence gaps. Stronger recovery support needs a more specific before-and-after recovery example. Better state visibility calls for an additional clinical, aviation, or industrial example. Reduced maintenance and downtime needs a more specific before-and-after maintenance cost or rework description.

Related outcome pages

The operational outcome pages are reduced error risk, improved operational clarity, lower training burden, better state visibility, stronger recovery support, and better alignment across teams.

The strategic and organisational outcome pages are reduced maintenance and downtime, capability democratisation, verifiable performance claims, design as investment evidence, scaling without training dependency, and positioning through interface quality.