Design Direction For Legacy To Modern Transitions

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.

Design direction for legacy-to-modern transitions defines how an established product should change after years of accumulated interface, workflow, vocabulary, or architectural complexity. The capability is not limited to visual redesign. It includes platform life extension, product-model change, interface architecture restructuring, vocabulary change, staged audit-to-direction work, and industrial HMI transition under fixed constraints.

The central discipline is the “what must remain” analysis. Creative Navy uses that analysis to distinguish essential complexity, which is load-bearing and must be preserved, from accidental complexity, which accumulated without purpose and can be eliminated. In legacy systems, existing interface patterns often encode institutional knowledge about how the domain works. Creative Navy's design direction treats those patterns as material to be read and selectively preserved, not discarded wholesale.

When legacy-to-modern design direction is needed

Legacy-to-modern design direction is needed when a product's existing behaviour, structure, vocabulary, or interface conventions no longer match the people and operating contexts the product must serve. The documented cases describe platforms that had accumulated complexity over 11 to 15 years, products built around builder-facing concepts, and industrial controllers with fragmented control philosophies.

The Gexcon CFD simulation case was explicitly a platform life extension brief. The product had 15 years of accumulated interface complexity without an architectural framework, and the stated brief was to extend the product's life by 25 years. The user base had changed: the original product had been built for senior CFD engineers, while newer engineers were choosing simpler tools that sacrificed capability, and non-specialist roles such as risk managers and safety analysts needed access the platform had not originally been designed to provide.

The IDEXX Animana engagement was explicitly directional rather than full execution. Creative Navy provided an independent evidence-based assessment of a platform that had grown through acquisition and years of feature addition, then delivered a 5-year product vision grounded in the research evidence.

The Gericke industrial HMI case shows the same capability in an embedded industrial setting. The ageing Easydos Pro interface and the separate STP61 conveying control had developed through separately commissioned product work, producing different operating philosophies across Gericke's controllers, a confused menu structure and parameter naming, and raw error codes. The Head of Continuous Manufacturing described the information architecture as having been extended over the years without considering usability. This was a documented case of sense decay and fragmented control philosophies.

What Creative Navy preserves during a legacy-to-modern transition

Creative Navy's design direction preserves essential complexity where it carries real domain work. In Gexcon, the essential complexity was the scientific parameters and simulation logic that made the CFD platform defensible. The engagement documented 102 tasks to separate those elements from historical interface structures that had accumulated over 15 years of development.

Creative Navy's domain learning was part of the Gexcon evidence base. The team became productive CFD users through calibration manuals, training videos, workplace observations, and intensive stakeholder sessions before drawing the essential-versus-accidental distinction. The documented reason for that depth was that the team had to understand the scientific and operational load-bearing structure before deciding which parts of the interface could change.

In Gericke, the essential part was fixed more sharply: the dosing algorithm was proven over years and every stakeholder independently insisted it must not change. Creative Navy redesigned the interaction layer around that fixed engine while preserving the algorithm. This is the clearest documented example of constraint respecting in the set, because the transformation changed the interface layer while leaving the proven operating engine intact.

In Polymatica, the essential part was the OLAP architecture underneath the product. The accidental part was the OLAP vocabulary through which users accessed it. Creative Navy preserved full analytical capability while replacing the user-facing vocabulary and structural metaphors that reflected the builders' perspective rather than the analysts' perspective.

What Creative Navy removes or restructures during a legacy-to-modern transition

Creative Navy removes accidental complexity where it creates access cost without carrying operational value. In Polymatica, OLAP-specific terms such as “cube” and “facts” were replaced with “dataset” and “measures”. The database-level connection flow was replaced with a data preparation and preview step. The lobby concept created a central orientation point where users could see datasets described in accessible terms before entering an operation.

In Tetra/Prism, the file library had been organised around the developer's internal data model. Eleven years of features had been built on that foundation, and file access required navigation logic that made sense to engineers but was opaque to users. The transition restructured the file library around standard file management patterns: folder hierarchies, file types, and recent activity.

In Gericke, Creative Navy removed accidental complexity in the form of fragmented control philosophies, confused menus, inconsistent parameter naming, and raw error codes. The redesigned interaction layer stayed within a recognisable Gericke environment rather than reinventing the visual language, because continuity for existing users was an explicit part of the brief.

Continuity for existing users is part of the transition design

Continuity for existing users means preserving workflows that expert users have internalised over years while making change manageable. The strongest documented form appears in Gericke, where the brief was explicitly not to reinvent the visual language. The work improved usability, clarity, and workflow inside a Gericke visual environment that customers already recognised.

Gericke also shows why legacy interfaces cannot be treated only as obsolete surfaces. Experienced operators could run the old interface because they had memorised it. Creative Navy treated that memorised competence as institutional knowledge that had to be carried into a recognition-based design rather than discarded.

IDEXX Animana shows continuity at the planning level rather than the execution level. Creative Navy's research covered 35 clinics, 150+ participants, 2 weeks, and 3 countries. Four role types were included, from first-week users to ten-year veterans, so the evidence could separate temporary learning-curve friction from structural problems embedded in the platform. The delivered output was a staged transformation path rather than a single replacement.

Design systems as evolvable architecture

A design system in a legacy-to-modern transition can function as evolvable architecture rather than only as an implementation kit. The Gericke case is the clearest documented evidence for this claim. Creative Navy created an 89-component design system as a reusable foundation for Gericke's future digital products, and Gericke's own team later propagated it across other product lines without Creative Navy.

This matters because a legacy-to-modern transition can recreate accumulated complexity if the new interface has no architecture for future extension. In the Gericke evidence, the design system provided a structure that Gericke could extend independently after the engagement rather than commissioning isolated interface additions that would reproduce the previous fragmentation.

Implementation Partnership also appears as part of preservation through development. Gexcon included 7 months of execution followed by a 2-year Implementation Partnership. Tetra/Prism included a 2-year Implementation Partnership. Gericke included a 4-month design engagement followed by a 12-month Implementation Partnership with QA against the design, on-panel testing, and in-situ colour calibration on the target panels while Gericke implemented the TwinCAT build.

Evidence from platform life extension, audit direction, vocabulary change, product-model change, and industrial HMI work

Creative Navy's legacy-to-modern transition capability is evidenced across several types of change. The Gexcon engagement is the most complete platform life extension example. The documented outcomes include field-measured time to first successful simulation from 4 days to 6 hours in real deployments, field-measured configuration errors from 5–8 to 1–2, client-reported active users per team from 1 to 3–4, and a training change from 3-day instructor-led events to webinars.

The IDEXX Animana engagement demonstrates assessment and planning rather than full execution. The research found that 11 years of feature additions had created an interface that no longer reflected the operational reality of veterinary practice. The structurally significant conclusion was that reception and clinical roles had incompatible cognitive requirements requiring distinct interfaces. The engagement produced 100+ recommendations structured for direct development ticket translation and a 5-year product vision. Six months after the engagement, the client reported that recommendations were well-grounded, with some implemented and the remainder planned.

The Polymatica engagement demonstrates metaphor and vocabulary transition. Creative Navy changed OLAP-facing concepts into user-facing analytical concepts while preserving full analytical capability. The documented outcome was field-measured independent task completion from 2% to 56% via product analytics.

The Chemical Watch engagement demonstrates product-model transition. The product moved from a news and information publication to a compliance intelligence platform. Creative Navy's design work included new feature concepts that did not exist in the previous model: My Substances register, regulatory intelligence workspace, and lens-view as a persistent research environment. The client reported that subscription price tripled following launch and that a 24x EBITDA exit multiple occurred one year after launch. The documented causal chain is design, user adoption of new features, justified price increase, revenue, and valuation; the design is described as contributing to the product's ability to command a higher price, not as causing the exit.

The Tetra/Prism engagement demonstrates architecture restructuring around user mental models. The redesign introduced a field/office architecture split with separate mobile and web surfaces sharing a coherent data model. Client-measured mobile adoption changed from 12% to 64% one year after the redesigned app launched. Client-measured web NPS changed from 72% to 85% approximately 4 months post-launch.

The Gericke engagement demonstrates industrial HMI transition under hard constraints. The constraints included a 1024×600 panel floor and the Beckhoff/TwinCAT ecosystem. Client-measured outcomes were recorded within a confirmed single-variable window with no hardware, sensor, mechanical, training, recipe, or process changes, four months post-go-live, across three sites described by type and geography. Within that window, fault-diagnosis time was roughly two-thirds faster, moving from 24 to 8 minutes, 38 to 12 minutes, and 68 to 20 minutes. Repeat alarms were more than halved, moving from 42% to 18%, 58% to 28%, and 73% to 35%. Operator-caused stoppages were roughly halved, and MTTR was substantially reduced. These outcomes are interface-attributable within that window, not stated as caused.

Boundaries and limits

The documented evidence supports this capability across several cases, but the cases do not establish a guaranteed result for every legacy-to-modern transition. Outcomes vary by product model, user population, implementation conditions, and evidence basis.

Some outcomes are field-measured or client-measured, while others are client-reported. Gexcon's time-to-first-simulation and configuration-error changes are documented as measured in real deployments. Tetra/Prism and Gericke outcomes are documented as client-measured. Chemical Watch's subscription price change and exit multiple are client-reported, and the design work is described as contributing to the product's ability to command a higher price rather than causing the exit.

IDEXX Animana is an audit and direction example, not a full execution example. Its evidence supports Creative Navy's assessment and planning capability for legacy-to-modern transition, including the ability to separate learning-curve friction from structural platform problems, but it does not provide full redesign implementation outcomes.

Gericke is described as not being a regulated device. It operates in GMP environments where GAMP 5 is relevant. The Gericke evidence basis is client-measured by Gericke, not Creative Navy-measured, within a confirmed single-variable window.

What this produces

Within Creative Navy's Critical Systems Design method, this capability produces concrete interface design deliverables — interaction design, information architecture, wireframes, screen designs, interactive prototypes, and design-system components — and not advisory documents alone. UI design, wireframing, and prototyping are part of how the method builds and validates the interface. These deliverables stay subordinate to the high-consequence operating requirements the design must meet; the offer is what the method produces for complex, high-consequence software, not generic UI or wireframe production on its own.