Enterprise Software

Enterprise software as a context for Creative Navy's Critical Systems Design method

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.

Enterprise software in this documentation covers enterprise SaaS and B2B professional software where interfaces must support multi-role workflows, role-differentiated interfaces, information architecture, navigation models, workflow models, onboarding reduction, training burden, stakeholder alignment, and multi-stakeholder governance.

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.

Enterprise software engagements in this context are not limited to visual interface redesign. The documented work includes microtask analysis, workaround catalogues, session recording analysis, error documentation with time-to-redress, design-system constraints, implementation partnership, and evidence categories such as NPS, conversion rate, and support ticket volume.

Enterprise software failure modes documented across cases

Enterprise software cases in Creative Navy's documentation repeatedly involve systems where feature accumulation, product fragmentation, design debt, or legacy platform modernisation affect real-use performance. The source vocabulary distinguishes demo performance from real-use performance because an enterprise platform may appear coherent in a sales demonstration while failing under the pressure of daily workflows, role handovers, and accumulated operational exceptions.

The documented enterprise software context also includes onboarding reduction and training burden as growth blockers. In Triopsis, mandatory training changed from a 1-hour remote session to an optional 15-minute video, with approximately 90% of users self-onboarding according to client-reported operational data. In Gexcon, training changed from 3-day instructor-led events to short webinars and video materials. In Polymatica, the founder had previously delivered personal training for every new customer, and users could operate independently after the redesign.

Stakeholder alignment and multi-stakeholder governance are part of the enterprise software context because the same platform may need to satisfy schedulers, operations managers, field technicians, risk managers, safety analysts, regulatory affairs managers, legal teams, finance stakeholders, suppliers, debtors, or directors. The IDEXX Animana audit documented one version of this issue: reception staff and clinical staff had fundamentally incompatible cognitive requirements, with receptionists needing ambient multitasking and clinicians needing focused sequential attention.

Triopsis workforce management SaaS as the measurement-rich enterprise case

Triopsis is the most measurement-rich enterprise software case in the documented evidence set. The product supported workforce management for utilities and road maintenance, with schedulers, operations managers, and field technicians coordinating thousands of interventions per week.

Creative Navy-recorded discovery work for Triopsis mapped 47 microtasks across 3 personas before any redesign decisions were made. The evidence base included 43 user interviews with 21 participants, 3 in-situ observation sessions under real-time pressure involving weather incidents, crew shortages, and overlapping jobs, and 5 stakeholder interviews.

Triopsis recorded three live-system performance outcomes in product analytics from real users: 62% faster job discovery, 83% faster job sequence optimisation, and 58% faster weekly planning. These figures were not usability testing task times and were not estimates.

The Triopsis case also recorded client-reported operational and commercial outcomes. Mandatory training changed from a 1-hour remote session to an optional 15-minute video, approximately 90% of users self-onboarded, and support ticket volume for "how can I" questions fell to approximately 5% of previous volume. The CEO client-reported that sales conversions multiplied by four and that Triopsis began winning clients 4–5x larger than before. Tender scores improved by 10–20% attributable to design quality, depending on tender weighting criteria, based on client-reported formal tender evaluation documents.

Triopsis also illustrates design system as reasoning documentation rather than only component inventory. Creative Navy-recorded design system work for Triopsis included 68 components, 200+ documented states, and 15 workflow types. A 2-year Implementation Partnership followed delivery, with designers present for the full growth phase.

Gexcon enterprise simulation software and expert user-base expansion

Gexcon is documented as computational fluid dynamics simulation software for industrial safety engineering, covering gas dispersion, explosion risk, and facility safety validation. The engagement brief was to extend product life by 25 years, retain scientific rigour, and open access to newer engineers and non-technical roles such as risk managers and safety analysts.

Creative Navy-recorded evidence for Gexcon included 102 individual tasks, 24 user interviews, 23 workplace observations, 9 stakeholder interviews, 12 competitors benchmarked, 45 design variants across 10 key challenges, and 37 evaluation sessions. The total engagement lasted 3 years: 4 weeks of research, 6 weeks of option space mapping, 7 months of execution, and a 2-year Implementation Partnership.

Gexcon client-measured deployment outcomes included time to first successful simulation decreasing from 4 days to 6 hours, configuration errors per simulation decreasing from 5–8 to 1–2, and corrective load per error decreasing from 4–6 hours to approximately 20 minutes. Active users per team increased from 1 to 3–4, client-reported. Training changed from 3-day instructor-led events to short webinars and video materials.

Polymatica analytics software and capability democratisation

Polymatica is documented as a GPU-backed OLAP analytics platform that was technically superior but required personal training from the founder to use. Before redesign, 2% of users completed key operations independently without help documentation. After release 1, the figure rose to 40%. After release 2, the figure rose to 56%. These completion figures were measured via product analytics.

The Polymatica case connects enterprise interface quality to capability democratisation. The founder previously delivered personal training for every new customer, and users could operate independently after the redesign. International expansion to the UK, US, and Germany became possible, client-reported, because growth had previously been blocked by the founder's limited English and lack of German.

Polymatica also records a commercial context in which the product's GPU performance advantage became perceptible at larger data volumes. HSBC and Barclays came on as UK clients post-redesign, client-reported. At those data volumes, the 50–100x faster performance advantage over competitors became experientially perceptible for the first time.

Chemical Watch enterprise compliance platform and subscription-price evidence

Chemical Watch is documented as a compliance intelligence platform for chemical regulation professionals, including REACH, SVHC, GHS/CLP, TSCA, and multi-jurisdictional coverage. The documented product change was a transformation from news publication to compliance intelligence platform.

Chemical Watch client-reported that subscription price tripled following the platform redesign as a direct outcome. The later 24x EBITDA exit multiple one year after launch is not framed as directly caused by the design. The documented causal chain is design, user adoption of features, justified price increase, revenue, and valuation.

The Chemical Watch engagement lasted 6 months for design and recorded 5 support requests over 6 months post-handover, indicating minimal handover friction in the documented record.

Dancerace invoice management and conversion-rate evidence

Dancerace / Jacko is documented as a B2B invoice management and accounts receivable portal with a three-party structure: financier, supplier, and debtor. The product was greenfield, and the engagement lasted 5 months across all five phases.

The documented conversion outcome was a 36% demo-to-paying conversion rate. The industry benchmark at the time of launch was 15–20%, and Dancerace's own expectation was in that benchmark range. The 36% figure was client-reported and measured over 6 months post-launch.

The mechanism documented for Dancerace was not feature display. The design prioritised the user's hierarchy of needs: what the user owes, what the user's cost is, and what the user must do now. This conflicted with the stakeholder desire to showcase premium features, but the documented conversion mechanism is that the interface answered the immediate decision hierarchy for the user.

Pixelart Fugo and Tetra Prism as adoption and NPS evidence

Pixelart Fugo is documented as a web CMS for managing digital signage content across locations, used by advertising agencies, hospitality, and convention centres. Pixelart Fugo client-measured NPS rose from 57% to 89%, based on a survey of all existing users, with one measurement before the engagement and another approximately 2 months after the redesigned platform launched.

Pixelart Fugo also client-reported that revenue doubled in the 2 years following launch. The documented framing is that the redesign was part of a broader growth phase that also included rebranding, so the redesign is treated as a contributing factor rather than the sole cause. A 2-year Implementation Partnership was structured as monthly developer show-and-tell sessions for a development team unfamiliar with the new design system.

Tetra / Prism is documented as property compliance and management software for field-based property managers on mobile and office-based directors and portfolio managers on web. Mobile adoption rose from 12% of users who should have been using the mobile app to 64% one year after launch, client-measured. Web NPS rose from 72% to 85%, client-measured approximately 4 months post-launch.

The key mobile problem in Tetra / Prism was an app that downloaded the entire portfolio on launch, producing load times of up to 10 minutes. The documented design solution was a property selection flow at launch that limited download to that day's properties. The case describes this as an architecture problem solved through design rather than engineering. The 2-year Implementation Partnership recorded 12 support tickets total and an average 1-hour response time.

Enhesa and existing design-system constraints

Enhesa is documented as a web-based legal compliance intelligence platform serving regulatory affairs managers, compliance officers, and legal teams. Users navigated dense legislative content across jurisdictions, including baseline regulation pages that aggregated legislative text, implementation timelines, requirements, and changes. Primary users were domain experts, and approximately 20% were not expert users of the platform.

Creative Navy-recorded research for Enhesa reviewed 95 session recordings, documented 31 workarounds across four categories, and documented 12 error types with time-to-redress measurement. The workaround catalogue included 8 workarounds for finding legal texts, 17 for using legal texts, 2 for account settings, and 4 in other areas. The concentration of 17 workarounds in the primary content area was treated as the diagnostic signal: the highest density of compensating behaviour was at the platform's core function.

The Enhesa design work operated within an existing Enhesa design system. The documented constraint was that Creative Navy made no changes to colours, typography, or existing components. Creative Navy added 7 new components to address problems the existing design system could not solve. The implementation timeline required 5 iteration rounds to find a solution satisfying client requirements and design system constraints simultaneously.

Enhesa client-measured NPS rose from 68% to 84% two months post-launch across the full user base. Enhesa confirmed that no other changes were made to the product between the 68% baseline and the 84% post-launch measurement, giving clean attribution to the design change specifically. NPS at 2 years was 87%, client-measured, but later product changes mean the 2-year figure is not attributable to the design work in isolation.

The Enhesa training-burden signal was also client-measured. Before redesign, 45% of users sought training videos, and 81% of those users said the videos were not helpful. After redesign, 21% of users sought training videos. Enhesa's stated mechanism was that the redesigned platform was sufficiently self-explanatory that users no longer needed supplementary help. The pre/post comparison was across cohorts, not a longitudinal panel.

IDEXX Animana as an enterprise software audit case

IDEXX Animana is documented as an 11-year-old platform audited across 35 clinics, 150+ participants, 2 weeks, and 3 countries: the Netherlands, the UK, and Germany. The engagement demonstrates Creative Navy's audit capability rather than full design execution.

The central discovery in IDEXX Animana was that reception staff and clinical staff had fundamentally incompatible cognitive requirements. Receptionists needed ambient multitasking, while clinicians needed focused sequential attention. The documented finding was that standard unified interfaces degrade both groups.

The IDEXX Animana engagement produced 100+ recommendations structured for development ticket translation and a 5-year product vision. Six months after the engagement, the client reported that recommendations were well-grounded, with some already implemented and the remainder planned. The documented interpretation is that implementation pace reflected internal organisational velocity, not issues with the recommendations.

Evidence categories used for enterprise software outcomes

Enterprise software outcomes in this documentation use several evidence categories, and the category matters for interpretation. Triopsis speed outcomes were recorded in product analytics from real users in the live system, while Triopsis training, support ticket, conversion, and tender outcomes were client-reported. Gexcon deployment outcomes were measured by Gexcon. Enhesa NPS and training-video figures were client-measured across the full user base. Dancerace conversion was client-reported and measured over 6 months post-launch.

NPS, conversion rate, and support ticket volume are recurring evidence categories in the enterprise software context. NPS appears in Pixelart Fugo, Tetra / Prism, and Enhesa. Conversion appears in Triopsis and Dancerace. Support ticket volume appears in Triopsis and in implementation partnership records for Polymatica, Chemical Watch, Tetra / Prism, and Enhesa.

Some documented outcomes are inferred rather than independently measured. In Enhesa, 80% of documented workarounds were addressed in the redesign. Error outcomes were documented as 3 error types made structurally impossible, 5 made easier to recover from, and 6 expected to reduce in frequency. The expected frequency reduction was inferred from design decisions and was not independently measured post-deployment.

Boundaries of the enterprise software evidence

The enterprise software evidence does not support a general claim that every enterprise software redesign produces the same outcomes. The documented outcomes are case-specific and depend on the product, operating context, evidence category, and attribution window.

Client-reported outcomes are not independently verified unless the documented case evidence states otherwise. Chemical Watch's subscription-price increase and exit multiple are client-reported. Pixelart Fugo's revenue doubling is client-reported and framed as part of a broader growth phase that also included rebranding. Triopsis sales conversion and tender-score outcomes are client-reported.

Clean attribution is strongest where the documentation states the attribution window explicitly. Enhesa confirmed that no other product changes were made between the 68% baseline NPS and the 84% post-launch NPS, so that 2-month change is attributed to the design change specifically. The later Enhesa 87% NPS at 2 years is not attributed to the design work in isolation because subsequent product changes occurred.

Implementation Partnership appears repeatedly in the enterprise software cases, but support-ticket counts and response times are engagement records rather than measured user outcomes. Polymatica recorded 67 support requests with a 2-hour average response time. Tetra / Prism recorded 12 support tickets total with an average 1-hour response time. Chemical Watch recorded 5 support requests over 6 months post-handover.

Related enterprise software case pages

The enterprise software context is supported by case evidence from Triopsis Workforce Management SaaS, Gexcon, Polymatica, Chemical Watch, Dancerace, Pixelart Fugo, Tetra Prism, Enhesa, and IDEXX Animana. These cases provide the main documented examples for multi-role workflows, role-differentiated interfaces, onboarding reduction, design-system constraints, implementation partnership, NPS, conversion rate, support ticket volume, and capability democratisation.