Contexts
The classes of design challenge Creative Navy works in — defined by the dominant design problem, not by industry alone.
What this section is
Each context page describes a class of design challenge — medical and clinical systems, expert tools and internal systems, embedded devices and constrained interfaces, high-consequence environments, and others — using the regulatory vocabulary, standards, and operational reality of that domain. A case study's primary context is chosen by the dominant design challenge it exemplifies, not by the client's industry alone, which is why case studies appear under the contexts whose problems they best illustrate.
Creative Navy's documented AI-enabled product work covers systems where AI behaviour must be made usable, governable, auditable, and bounded by human decision-making. The cases show recurring design issues around trust calibration, uncertainty communication, discoverability, progressive disclosure, policy engines, and capability democratisation.
Open article →This context describes design work for consumer products and multi-country platforms where users, markets, brands, and local behaviours vary, but the product still needs a coherent interaction architecture. The available evidence comes from Elsner Elektronik's Cala Touch KNX controller and the OLX automotive marketplace engagement.
Open article →This context covers Creative Navy's documented work on embedded devices and constrained interfaces, including constrained display hardware, microcontroller limits, firmware behaviour, warning architecture, multi-surface systems, and evidence from named engagements.
Open article →This page defines emerging products as a context where product structure, information architecture, interaction logic, or commercial viability is being created for the first time. It documents evidence from Greenlight, Veecle, Puraite, Hudex v2, Squaremind, and Neugo, including project-observed, Creative Navy-observed, Creative Navy-measured, and client-reported outcomes.
Open article →Enterprise software is a Creative Navy context covering complex B2B and SaaS products where multiple roles, accumulated features, training burden, stakeholder governance, and implementation constraints affect performance in reality. The documented cases include Triopsis, Gexcon, Polymatica, Chemical Watch, Dancerace, Pixelart Fugo, IDEXX Animana, Tetra Prism, and Enhesa.
Open article →This context covers software and instrumentation used by domain experts, professional practitioners, analysts, technicians, researchers, and operational teams. The documented evidence spans CFD simulation, OLAP analytics, clinical research, automotive calibration, and AV diagnostic instruments, with outcomes calibrated as client-measured, client-reported, or measured via product analytics where stated.
Open article →This context covers Creative Navy's documented work in financial-services products where interface decisions are constrained by PSD2, SCA, PCI DSS, KYC/AML, MiFID II, SEC anti-fraud rules, FINRA Reg BI, and related financial-promotion constraints. The main evidence examples are Callsign's fraud policy engine, Bofin's open banking marketplace, and eToro's multi-asset social trading surfaces.
Open article →This context covers three documented public-sector design problems: WCO/IPM adoption across member administrations, UNICEF cross-tier governance and reporting, and Neugo multi-party visa case coordination. The common pattern is coordination among actors who cannot be standardised into a single user model.
Open article →High-consequence environments require interfaces to perform under real operating conditions rather than clean test conditions. The documented evidence covers maritime HMI, cardiac support control, operating theatre devices, industrial safety simulation, automotive calibration, enforcement platforms, and industrial process control.
Open article →Medical and clinical systems in Creative Navy's documentation include regulated device interfaces, patient-operated embedded clinical devices, and clinical research platforms shaped by patient safety implications, use-related risk, clinical workflow constraints, and clinical data governance.
Open article →This page defines multi-stakeholder operational environments as design contexts where role-specific requirements, handoff points, shared context, access boundaries, governance structures, and adoption density shape whether a system works in practice.
Open article →This page defines regulated products as a Creative Navy context where interface decisions are constrained by medical-device regulation, financial services regulation, or institutional governance. The documented evidence covers Kardion, deSoutter Medical / Zethon, Callsign, Bofin, and Akrivia Health, with evidence limits stated by case.
Open article →Retail operations systems combine cashier till interfaces, forecourt operations, outdoor payment terminals, multi-language and multi-currency requirements, and peak-load transaction constraints. The documented evidence base comes from a three-year Swiss petrol forecourt programme across seven stations in the Zurich area.
Open article →