Government And Public Sector

Government and public-sector systems as coordination problems

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.

In government and public-sector systems, the design problem is rarely confined to a single user at a single screen. The documented pattern is coordination among different actors across jurisdictions, institutional boundaries, organisational tiers, or public-private lines. These actors cannot be standardised into one user model, and the governance structures around the systems often do not follow ordinary product release cycles.

This context contains three structurally different design problems. WCO/IPM illustrates adoption under variable operating conditions in a network-effect enforcement platform. UNICEF illustrates cross-tier comprehension and compliance in an internal governance and reporting system. Neugo illustrates multi-party public-private coordination in a net-new platform without a clear product owner.

Operating vocabulary for government and public-sector systems

Government and public-sector systems in this documentation use vocabulary that separates deployment structure, governance structure, field use, and compliance behaviour.

A member administration or member state is a national administration that forms part of an intergovernmental body's member organisations, as in WCO. A country office and headquarters tier describes the two-tier structure of an international organisation operating through local offices reporting to a central body, as in UNICEF. A public-private consortium is a delivery vehicle in which government, private capital, and commercial beneficiaries jointly commission and build a public system, as in Neugo.

Adoption density is the degree to which all stakeholder groups across all jurisdictions are actively using the platform. In a network-effect system, low adoption by any stakeholder group degrades the value of the whole network. Field conditions are the physical operating conditions of frontline officers at ports, airports, and land border posts, including variable connectivity, mixed device fleets, and limited time per inspection.

Multi-jurisdictional deployment means operating across different legal frameworks, institutional cultures, device fleets, languages, and operational practices. Role-based access and data separation are governance constraints where sensitive data classes cannot be mixed. Bandwidth optimisation means designing for variable and unreliable connectivity as a baseline condition rather than as an edge case.

Workaround indicators include parallel spreadsheets, email chains, shadow processes, and high rates of corrected or resubmitted work. In the documented intergovernmental engagements, these indicators signalled that a deployed platform was not meeting users' needs.

WCO/IPM: adoption under variable field conditions

WCO/IPM shows how adoption density becomes a primary design constraint in a network-effect enforcement platform. The World Customs Organization is an intergovernmental organisation based in Brussels, covering most international trade. IPM is a customs intelligence platform coordinating intellectual property rights enforcement between customs officers and rights holders across member administrations.

The WCO/IPM platform had three user groups: frontline inspection officers at ports, airports, and land borders; intelligence analysts working with patterns and historical cases; and rights holder brand protection and legal teams filing information and monitoring enforcement. The platform was already in production when Creative Navy engaged, but adoption was low across many administrations. Parallel spreadsheets and email chains had emerged as workaround indicators.

The network effect was structurally significant. Officer adoption determined the quality of seizure records entering the network. Rights holder adoption determined the quality of intelligence available to officers. Low adoption on either side degraded the platform's value for both groups.

Creative Navy's Critical Systems Design method was applied across all five phases during the 7-month WCO/IPM engagement. Domain learning covered WCO instruments including the SAFE Framework of Standards, the Revised Kyoto Convention, and the Harmonised System, as well as alert and seizure record logic and the operational relationships of all three user groups with the platform.

Creative Navy's research for WCO/IPM included interviews, workflow mapping, and remote observation with WCO teams and selected member administrations. The three user groups were clarified through research rather than assumed from the initial brief. Cognitive design principles were applied systematically, including recognition over recall, reduced choices per screen, progressive disclosure, and contextual micro-hints on first use of complex actions.

The WCO/IPM design treated bandwidth optimisation, role-based access, and data separation as design constraints. Variable connectivity across member states was a baseline condition. Operational data and rights holder information required separation as a non-negotiable governance requirement.

Usability testing involved 47 participants across Italy, Romania, Uzbekistan, Algeria, and Spain. The geographic spread was deliberate: the test was intended to confirm that the multi-jurisdictional design held under different operational contexts rather than only under controlled conditions.

WCO/IPM outcomes were client-reported unless otherwise stated. The client reported a 78% reduction in officer training costs based on reduced training hours, a 200% increase in rights holder user sign-ups, a 67% increase in platform use among rights holders, a 20% increase among officers, 107 governments signed up to the system, and more than 2000 officers using the system in field operations. The client confirmed a decrease in support tickets and associated costs, but no quantified magnitude is available. INTERPOL Secretary General Jürgen Stock provided an external endorsement, which is third-party endorsement rather than client self-report.

UNICEF: cross-tier comprehension and compliance in institutional reporting

UNICEF illustrates a cross-tier comprehension gap in an internal governance and reporting system. The system was an internal tool for project planning, approval, and reporting, used across headquarters and local-office tiers.

The UNICEF tool involved seven distinct role types across two tiers plus a conditional external user class. At headquarters, the roles were Global Programme Director, Planning & Reporting Manager, Finance Manager, and Admin. At local level, the roles were Country Programme Manager, Project Director/Officer, and Finance Officer in some offices. Monitoring & Evaluation Specialists had conditional external access.

The initial organisational framing was that local offices were uncooperative and put off by a cumbersome interface they otherwise understood. Creative Navy's research revealed a different mechanism: local offices did not understand how their input was used or why it was structured as it was. The interface communicated institutional indifference because reporting requirements appeared as arbitrary bureaucracy rather than as requirements connected to governance, cross-country comparability, planning, and financial oversight.

Creative Navy's Critical Systems Design method treated the UNICEF problem as cross-tier comprehension and compliance rather than usability in isolation. Headquarters held the rationale for reporting requirements. Local offices executed the process without access to that rationale. When the interface presented requirements without communicating their purpose, it reinforced disengagement and low-quality submissions.

The UNICEF Sandbox Experiments phase lasted 3 months. During that phase, 26 prototypes were reviewed by 56 stakeholders and 4 local offices were engaged intensively. The design phase lasted 13 months, with weekly sprints and two 6-week breaks. Implementation Partnership then ran for 4 years with a third-party developer team. The developer team changed once, approximately a year after designs were completed, and Creative Navy conducted a structured re-onboarding.

The prototypes functioned as an organisational diagnostic instrument. Presenting 26 alternative workflows forced stakeholders to justify why each requirement existed. Several long-standing mandatory requirements could not be justified and were removed, consolidated, or simplified. This reduced complexity at source rather than only making complexity easier to navigate.

Once standards were agreed across tiers, they were embedded in the system through workflows, validation rules, information architecture, and interaction design. Many ambiguities that had previously generated compliance failures were eliminated before users began entering data.

UNICEF outcomes were client-measured against pre-established operational baselines nine months post-rollout. UNICEF measured a 45% reduction in compliance issues, where compliance issues meant submissions failing UNICEF's established reporting standards and requiring headquarters follow-up before acceptance. UNICEF also measured a 42% reduction in report preparation time at headquarters against the same baseline. UNICEF reported 128 countries using the system post-rollout.

The UNICEF compliance reduction and headquarters time saving are analytically connected rather than independent outcomes. Both follow from reducing the volume of defective submissions requiring correction. Both are consequences of workflow and standards redesign at role interactions and handoff points, not of screen usability improvement alone.

Neugo: multi-party public-private case coordination without a clear product owner

Neugo illustrates multi-party public-private coordination in a single-jurisdiction platform. Neugo is a UK visa application case-management platform connecting visa seekers with advisers who prepare applications, including legal consultants and family offices. Neugo produces clean, submittable data that the Home Office's downstream border-force platforms ingest. The visa decision is made in those downstream systems, not in Neugo.

The design problem in Neugo was the human-collaboration layer. The platform had to coordinate applicants, often travelling as a party rather than individually; advisers working in established tooling, frequently Excel; case workers who needed active prompting; and the Home Office as the downstream consumer of the data.

Creative Navy's Critical Systems Design method was applied across three separate Neugo engagements over roughly three years. The first engagement lasted 7 weeks and framed the opportunity for commissioning. Creative Navy worked with the Home Office and four legal firms to produce a visionary conceptual design, a value and desirability mapping, and a clickable Figma prototype. Sandbox Experiments were used in a value-elicitation mode, provoking stakeholders to imagine value while tethering it to real operating conditions.

The second Neugo engagement lasted 3 months and covered the full platform design plus Implementation Partnership for a development company that is not named. Requirements flowed directly from the beneficiary legal firms to design and development. Designs were exposed to the firms at three checkpoints: the first two changed the design, and the third gave the green light. There was no real product owner; the nominal product manager functioned only as a conduit.

Because Neugo had no clear product owner during delivery, Creative Navy prepared Organizational Integration for a future owner. The handover included documentation and three videos covering the architecture, the design-language decisions, and the principles to apply if the system were to grow. The system went live roughly eight months later.

The Neugo design respected the existing tooling of the legal firms. The platform integrated everything from the legal firms' existing tooling except a small number of fields unique to one single firm, preserving what worked without turning one office's idiosyncrasy into the shared system. The workflow actively prompted case workers on what to do next because the value event was a submittable, complete case rather than the open-ended activity of preparing one.

Neugo Concept Convergence was prioritisation only. It involved option space mapping plus a desirability × feasibility filter. It did not involve tension-driven reasoning or a competitive vector, and those canonical Concept Convergence mechanisms should not be attributed to this engagement.

The first Neugo prototype contributed to the system being commissioned, but the design should not be described as securing the commission. Stakeholders told Creative Navy that the design accounted for roughly 30% of the decision factors and that dedicated demo sessions were scheduled around the prototype as part of the lobbying process. This is client-reported evidence for a substantial component of a multi-factor commissioning decision.

At the post-launch audit roughly one year after launch, Creative Navy observed that 15 legal firms were relying on Neugo in production and had begun replacing some of their internal processes with platform features. The four legal firms from the first engagement carried through as second-engagement beneficiaries and were among the fifteen. This is Creative Navy-observed audit evidence rather than a measured operational outcome.

Evidence boundaries across the three engagements

The evidence in this context uses different evidence categories. WCO/IPM outcomes are client-reported unless otherwise stated. UNICEF outcome figures are client-measured against pre-established operational baselines, with UNICEF producing the measurements and Creative Navy helping identify relevant metrics. Neugo production reliance by 15 legal firms was Creative Navy-observed during a post-launch audit.

The figures should not be generalised into a claim that all government or public-sector design work produces the same effects. The cases support narrower claims about three coordination problems: adoption under variable field conditions, cross-tier comprehension and compliance, and multi-party public-private case coordination without a clear product owner.

The Neugo commissioning evidence is explicitly multi-factor. The client-reported statement that the prototype accounted for roughly 30% of decision factors should be treated as evidence that the prototype was a substantial component of the decision process, not as evidence that the design alone secured commissioning.