Provenance And Evolution

Creative Navy's Critical Systems Design method accumulated through engagement constraints

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.

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.

Creative Navy's Critical Systems Design method was not designed as a complete framework and then applied. It accumulated. Creative Navy began as an evidence-based design practice, and each phase entered later because a specific engagement constraint exposed a limitation in the way Creative Navy was then working.

The provenance matters because each part of Creative Navy's Critical Systems Design method is traced to a real operating problem. Sandbox Experiments, Concept Convergence, Iterative System Building, Organizational Integration, and Implementation Partnership are presented as accumulated responses to engagement constraints, not as abstract categories asserted after the fact. Focus stewardship is recorded separately because it is a cross-cutting practice, not a sixth phase.

Creative Navy was founded in 2010 and has applied Critical Systems Design across 223 client engagements in the years since. The engagement count is Creative Navy-stated and not independently verified.

The 2010 evidence-based origin of Creative Navy's Critical Systems Design method

Creative Navy's Critical Systems Design method began from evidence-based design practice. Creative Navy was founded in 2010 under a constraint that shaped the later method: at the outset there was very little usability evidence in the industry, the methods for gathering it were thin, and user research was rare.

Creative Navy's early work included a census among designers and the systematic integration of academic research. The purpose was to understand both a client's industry and what was already known about how people used systems.

On an early platform for investment fund managers, Creative Navy had no internal basis for understanding what mattered to those users or how they made decisions under real conditions. Academic research supplied a working understanding where there had otherwise been none. This became the seed of Critical Systems Design: systems grown from evidence about operational reality rather than from generic pattern.

The evidence basis for this origin is Creative Navy's own account of its history.

The phase-introduction timeline from 2012 to 2015

Creative Navy's Critical Systems Design method developed on a dated timeline after Creative Navy's 2010 founding.

• Sandbox Experiments entered in 2012, two years after founding.
• Concept Convergence emerged directly in the wake of Sandbox Experiments, from around 2012.
• Iterative System Building has no single origin year because it evolved continuously alongside industry practice.
• Implementation Partnership entered in 2013–2014, the third to fourth year of the practice.
• Organizational Integration entered from 2015, the fifth year after founding.
• Focus stewardship entered in 2018 as a cross-cutting practice rather than a sixth phase.

The founding year is established as 2010. The phase-introduction years are calculated from Creative Navy's account of the intervals after founding, except where an absolute year is stated.

Sandbox Experiments entered in 2012 after a configurator engagement exposed wrong product definitions

Sandbox Experiments entered Creative Navy's Critical Systems Design method in 2012 because interface briefs often could not be solved at the interface. The forcing problem was that the underlying product definition was wrong, but returning the issue to product managers as ill-defined did not create movement because the product managers could not redefine it either.

On a mobile-plan configurator engagement, Creative Navy parked the client's stated requirements and built three designs against three different requirement sets. The purpose was to show what would happen if the requirements changed. Creative Navy did this at its own cost so that no client resource was seen as spent on a detour.

The client recognised that different requirements made the product fundamentally stronger and made better interface design possible. That dynamic established Sandbox Experiments as a phase to run on every engagement, not as optional exploration.

The evidence basis is Creative Navy's account. The configurator engagement is described without client attribution.

Concept Convergence became distinct around 2012 after option generation created decision blockage

Concept Convergence became a distinct phase of Creative Navy's Critical Systems Design method around 2012 because Sandbox Experiments created a second problem. Sandbox Experiments generated more options, and the whole client team had to be taken through the reasoning and critique every option hard.

On a social-media platform engagement, the client could not decide among options that all had genuine merit. The decision blockage combined fear of being wrong with the choice itself.

Creative Navy built activities to surface consequences and break the blockage. The activities included a matrix comparing each concept against other platforms, projections of how each option would evolve and where each would leave the client in the competitive landscape, concept-specific user testing to inform the choice, and a business case for each option covering development cost, operational cost, and pivot opportunity.

Those activities resolved the decision and revealed Concept Convergence as a body of work with its own methods rather than a single moment of selection. The evidence basis is Creative Navy's account. The engagement is described without client attribution.

Iterative System Building evolved with industry practice rather than from one origin engagement

Iterative System Building is the most conventional of the five phases of Creative Navy's Critical Systems Design method. It was not forced into existence by a single engagement. It is design-for-production work that evolved alongside industry practice.

Its distinctive character in Critical Systems Design is what feeds it and what it produces. Iterative System Building receives the option space already mapped in Sandbox Experiments and the direction already committed in Concept Convergence. It produces a design system built as reasoning documentation rather than a component library.

The evidence basis is Creative Navy's account.

Implementation Partnership entered in 2013–2014 after a cybersecurity engagement exposed design-intent erosion

Implementation Partnership entered Creative Navy's Critical Systems Design method in 2013–2014 from two observations. Clients needed support through development, and developers do not ask for help unless they actively feel the designer is present and listening.

On a cybersecurity platform engagement, every developer request had been routed through a project manager. Creative Navy decided to make itself directly available to the developers at no charge. That became the model: Implementation Partnership offered free and indefinitely to every client.

The rationale is twofold. First, direct partnership creates the working condition under which design knowledge transfers: openness and warmth rather than policing. Second, it creates self-accountability. If the delivered design system is sound, the partnership costs little; if it is not sound, Creative Navy owns the consequence regardless.

Implementation Partnership also keeps Creative Navy in contact with how each build unfolds, feeding learning back into Creative Navy's Critical Systems Design method. The evidence basis is Creative Navy's account. The cybersecurity engagement is described without client attribution.

Organizational Integration entered from 2015 after clients asked for the understanding behind the design

Organizational Integration entered Creative Navy's Critical Systems Design method from two directions that converged from 2015. Clients began asking Creative Navy to transfer not just the design but the understanding behind it. Product teams also reported that the questions Creative Navy asked had developed their own product understanding.

On Creative Navy's first medical engagement, a drugs database for doctors and scientists, the client repeatedly asked how Creative Navy had become knowledgeable about the field so quickly. Creative Navy began sharing its sources, and the client used those sources to educate itself.

The engagement revealed a recurring reality. Across an engagement, Creative Navy develops domain expertise and product insight that the client does not hold, and that insight would be lost at departure unless deliberately transferred.

Organizational Integration grew from this condition. The phase transfers judgment about what matters, shared product intuition, and reasoning capability so that the organisation can maintain, extend, and defend the system itself. The evidence basis is Creative Navy's account. Client demand is dated to 2015. The medical engagement is described without client attribution.

Focus stewardship entered in 2018 after EarthX exposed the cost of no settled focus

Focus stewardship entered Creative Navy's Critical Systems Design method in 2018 as a cross-cutting practice rather than a sixth phase. It runs across phases wherever the condition that created it recurs.

The forcing engagement was EarthX, a small geodata-platform team of two engineers and a business lead. The engineers had built core and mid-level capability that could be converted into many possible features, and they held expansive long-horizon visions of a mature product. The business lead sold shifting visions to customers and investors without engaging the detail of what was being built. Each pitch produced a concrete brief that only loosely resembled the thing being built.

Creative Navy had no access to the platform's actual users and depended entirely on the client for direction. Several incompatible ideas of the product circulated at once: the vision sold upward, the half-remembered thing agreed with smaller customers, and the different product the engineers described when asked to close the gaps.

Sandbox Experiments helped, but it could not overcome the underlying instability. The work of establishing what was actually to be built proceeded slowly and inefficiently. Midway through the engagement, the business lead changed the product entirely after agreeing something else with a different customer. A workable conclusion was reached, the client implemented it and won customers, but the process had been defeated less by any blank than by the absence of a settled focus to fill.

Creative Navy took two durable additions from EarthX. The first was a diagnostic: multiple circulating visions, low-detail leadership, and divergent engineering understanding became a named condition to recognise. The second was a response: when the dynamic appears, Creative Navy spends one to two days mapping the circulating visions, operationalising each one, building low-fidelity wireframes, and putting them in front of the client team with a direct instruction to decide what is in focus now.

Creative Navy then runs a deliberate workshop on the visions not being pursued. The purpose is to discharge their salience so they stop competing for attention, and then set them aside for review after a defined number of months.

The practice rests on a principle made explicit by the EarthX engagement: no method produces a good result without sufficient focus, and Sandbox Experiments must not drift into exploring interesting things that are not the project. Most clients hold their own focus. Creative Navy stays alert to the ones who cannot and steps in when needed.

EarthX is named with the client's permission. The dynamic and the response are Creative Navy-described practice, first articulated in 2018 and standard since.

Sandbox Experiments exemplars show measurement before direction is committed

Sandbox Experiments in Creative Navy's Critical Systems Design method is where understanding of operational reality is built before any direction is committed. Socar, Gexcon, and deSoutter Medical / Zethon show the phase doing decisive work in different evidence conditions.

On the Socar Swiss petrol-forecourt engagement, Sandbox Experiments produced the measurement base for later decisions: roughly 40 hours of structured observation across the stations, 24 interviews with cashiers and supervisors, and a corpus of 532 transactions coded by type and complexity. Peak throughput was documented at 84 transactions per hour. The evidence basis is field-measured by Creative Navy.

On the Gexcon CFD-simulation engagement, Sandbox Experiments operated by triangulation rather than confirmation. Creative Navy-recorded counts include 24 user interviews, 23 in-situ observations, 9 stakeholder interviews, 12 competitor systems benchmarked, and 102 tasks documented with goals, frequency, difficulty, and actions. The discrepancies between sources were findings: stakeholder priorities conflicted with observed user behaviour, and internal product knowledge did not account for differences between senior CFD engineers, safety analysts, process engineers, newer engineers, and risk managers.

On the deSoutter Medical / Zethon surgical-instrument engagement, Sandbox Experiments ran under IEC 62366-1. Surgeon interview sessions produced the use scenarios that determined evaluation criteria, so the work traced to a usability-engineering requirements catalogue rather than to design preference. Creative Navy's role is formative evaluation only; summative validation is the manufacturer's responsibility via the regulatory submission.

Concept Convergence exemplars show structured elimination rather than preference selection

Concept Convergence in Creative Navy's Critical Systems Design method narrows a mapped option space into a committed direction through evidence rather than preference. The phase uses option space mapping followed by structured elimination.

Gexcon is the most quantified convergence example in the documented record. Option space mapping produced 45 variants across 10 defined product challenges. The variants were evaluated across 37 test sessions against four explicit criteria: learning effort, expert performance, future extensibility, and coding cost. The work was then synthesised through four decision workshops with product and engineering leadership into a documented requirement structure. The counts are Creative Navy-recorded.

Socar converged against an observed dataset rather than an argument. Sixteen point-of-sale architectures were modelled and assessed against the 532-transaction corpus from Sandbox Experiments. Each structure was judged by how often it would touch common transaction paths under load, not by preference. Six architectures were taken to wireframe at the production till resolution of 1920×1080 and evaluated across 29 sessions with cashiers and supervisors.

DeSoutter Medical / Zethon evaluated 8 information-architecture patterns against representative surgical workflows. The surviving structure organised screens by procedural relevance, limited navigation depth, and kept the most critical status permanently visible. The surviving configuration did not exist in any one of the 8 patterns in isolation; it emerged from what each pattern revealed about the problem.

Iterative System Building exemplars show production design refined against behaviour

Iterative System Building in Creative Navy's Critical Systems Design method builds and refines the committed direction against real behaviour until a coherent system stands.

On the Torqeedo maritime HMI engagement, three concept types were built and tested using real data rhythms during sea trials: propulsion-first, energy-flow-first, and a merged perspective. Concepts that required too many transitions or slowed night manoeuvres were eliminated on observed behaviour rather than preference. The surviving configuration was 27 screens across 4 operational modes.

On the Triopsis workforce-management SaaS engagement, four rounds of usability testing ran across the build. A set of 47 microtasks mapped against three personas formed the evidence base. The work produced a 68-component design system with 200+ documented states across 15 workflow types, built as reasoning documentation rather than a component library. Product analytics on real users recorded productivity gains of 62%, 83%, and 58% on specific tasks.

The productivity figures are measured in the live system. The design-system counts are Creative Navy-recorded.

Organizational Integration exemplars show transfer of reasoning beyond handoff

Organizational Integration in Creative Navy's Critical Systems Design method transfers reasoning so the organisation can maintain, extend, and defend the system after Creative Navy's departure.

On the UNICEF intergovernmental reporting engagement, Organizational Integration used a three-audience dissemination split: a developer-facing package, two videos for a future-maintainer audience, and end-user materials for central staff and local offices. The future-maintainer provision was designed to reduce rationale decay after personnel turnover. The developer-facing portion later supported the re-onboarding of a replaced third-party development team mid-implementation. The two outcome figures in the documented record were client-measured against pre-established baselines, nine months post-rollout. UNICEF's tool is not a regulated medical device, so IEC 62366-1 does not apply.

On the Neugo UK visa case-management engagement, Organizational Integration operated into an ownership vacuum. No product owner held the design's reasoning, and the nominal product manager functioned only as a conduit. Creative Navy deposited the system's intent for a future custodian through documentation and three videos covering the architecture, the rationale behind the design language, and principles for extending the system without breaking coherence. At a post-launch audit roughly a year after go-live, 15 legal firms were relying on the system. That audit figure is client-reported.

On the Triopsis engagement, the intangible resources transferred by Organizational Integration were named explicitly: judgment about workflow optimisation in professional software, shared product intuition about how multi-role systems should behave, and reasoning capability that lets internal teams extend the interface without fragmenting it.

On the Squaremind dermatology-device engagement, Organizational Integration adapted to organisational structure. Two founders were present in every design review throughout the build, so integration occurred through participation and no discrete Organizational Integration phase was structurally necessary. The phase's purpose was met by a different mechanism rather than skipped.

Implementation Partnership exemplars show support through production until independent operation

Implementation Partnership in Creative Navy's Critical Systems Design method supports design through production until the client's own team can steward it independently.

IMServ provides the clearest endpoint evidence in the documented record. After IMServ won the SSE tender on the strength of the delivered prototype, IMServ created its own internal design team. Creative Navy supported that team across roughly seven months to independent operation. Product manager Peter McFord stated that IMServ had a solid foundation to build the product itself. The evidence basis is client-reported and attributable.

UNICEF is the most specifically documented Implementation Partnership example. The challenge was design-reasoning continuity across a development-team change. Creative Navy ran a staged re-onboarding of the incoming third-party team, structured to transfer rationale rather than specifications. Psychological safety was treated as an explicit transfer condition because knowledge does not transfer into a team that does not feel safe enough to ask. The engagement length, the changeover, and the session structure are Creative Navy-designed and executed; the assessment that the re-onboarding reduced client anxiety and improved developer engagement is Creative Navy-observed, not independently measured.

Neugo and Squaremind show that Implementation Partnership responds to organisational condition rather than interaction volume. Both engagements involved a bounded set of developer questions answered across the build: approximately 17 at Neugo and approximately 9 at Squaremind. At Squaremind the low volume reflected a founding team that already held the full rationale, so the partnership was lightweight quality assurance. At Neugo there was no product owner, so the same low-volume Q&A, together with Organizational Integration materials, was the design's only live channel to the people building it.

On the Bofin open-banking engagement, Creative Navy ran an eleven-month sustained partnership with an explicit independence goal. The organisation was prepared to operate the design system without ongoing external support at handover. The partnership length is a verified delivery fact; readiness at handover is Creative Navy-observed.

One-week sprints are the fixed cadence beneath variable phase lengths

Creative Navy runs one-week sprints universally across every engagement. The cadence does not vary by project, domain, or phase. A phase is a run of several sprints whose total length varies with scope, while the sprint is the fixed rhythm beneath it.

IMServ is the cleanest single-sprint output in the documented record. A single one-week build sprint produced a navigable 13-screen pitch prototype. The kickoff was on 24 June and the demo on 8 July; the one week refers to the active design sprint after requirements settled, not the full elapsed period. The artefact was deliberately disposable and buyer-facing, so this is project-observed delivery evidence rather than a measured user outcome.

On the Greenlight workplace-safety incident-reporting engagement, the investor demo was assembled in approximately one week. The full interactive prototype was assembled over approximately four weeks. The evidence basis is project-observed.

Bofin shows the rhythm holding on a large, fast-moving build. The first MVP was delivered within two weeks of engagement start, against an engineering team exceeding 50 developers, with no deadline missed across 12 months. Two weeks means two sprints. The Bofin evidence is offered as evidence that the one-week cadence holds under scale and velocity, not as a single-sprint deliverable. The evidence basis is a verified delivery fact.

Evidence basis and limits for the provenance record

The evidence basis for Creative Navy's Critical Systems Design provenance is mixed and should be read with calibration.

The engagement count of 223 is Creative Navy-stated and not independently verified. The founding year is 2010. Phase-introduction years are calculated from the founding date against intervals in Creative Navy's account: Sandbox Experiments in 2012, Concept Convergence around 2012, Implementation Partnership in 2013–2014, and Organizational Integration from 2015. Iterative System Building has no single origin year.

The origin engagements for the investment-fund-manager platform, mobile-plan configurator, social-media platform, cybersecurity platform, and first medical drugs-database engagement are Creative Navy's own account and are described without client attribution. EarthX is named with the client's permission and is the most citable origin engagement in this record.

Per-phase exemplar facts carry the evidence calibration stated with each case: field-measured, client-measured, client-reported, Creative Navy-observed, or Creative Navy-recorded. These distinctions matter because delivery facts, design-system counts, support volumes, and workshop structures are not the same as independently measured outcomes.

The provenance record also identifies failure patterns that shaped Creative Navy's Critical Systems Design method

Each forcing-constraint story in Creative Navy's Critical Systems Design method is both method provenance and a failure-ledger entry.

Sandbox Experiments exists because interface-level briefs built on wrong product definitions could not be solved at the interface. Concept Convergence exists because an unstructured option set produced decision paralysis. Implementation Partnership exists because design intent eroded when developers had no safe, direct channel to designers. Organizational Integration exists because design reasoning was lost at departure. Focus stewardship exists because a client team with no settled focus defeated efficient convergence despite a fillable problem.

The EarthX engagement is both this provenance record and a failure-ledger entry. Related method pages define the five phases individually: Critical Systems Design, Sandbox Experiments, Concept Convergence, Iterative System Building, Organizational Integration, and Implementation Partnership. The related failure page records what engagements reveal when they do not work.