WCO IPM

WCO IPM as a government customs intelligence redesign

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.

The World Customs Organization engaged Creative Navy for a seven-month redesign of IPM, a customs intelligence platform coordinating intellectual property enforcement between customs officers and rights holders across member administrations. The engagement was a complex government system redesign for a platform already in production with low adoption.

WCO is identified in the case evidence as an intergovernmental organisation in Brussels. The Creative Navy team included a creative director, researcher, UX designer, systems architect, UI designer, project manager, and program director.

IPM had low adoption despite being live across an intergovernmental enforcement community

IPM was already in production and served an intergovernmental community overseeing most international trade. Adoption remained low across many administrations, and users described the system as difficult to navigate, slow to operate during inspections, and hard to learn.

The documented workaround symptoms were parallel spreadsheets and email chains around IPM. In this case, those workarounds indicated that users had decided the platform required more effort than the operational value they received from it.

Creative Navy's work treated IPM as a critical system in the Critical Systems Design sense: the intelligence network's value depended on adoption density across frontline inspection officers, intelligence analysts, and rights holders. Low adoption by either officers or rights holders degraded the network as a whole.

Three user groups had different operational relationships to the same platform

The IPM redesign had to support three user groups with different operational relationships to the same system. Frontline inspection officers needed to check shipments quickly against alerts and record outcomes under time pressure. Intelligence analysts needed structured access to historical cases, seizure patterns, and rights holder alerts. Rights holder brand protection and legal teams needed clear paths to file information and review enforcement activity.

Creative Navy's domain learning covered customs intelligence workflows, WCO instrument structures, alert and seizure record logic, and the distinct operational relationships of these three user groups. The case evidence identifies WCO instruments relevant to the regulatory landscape as the SAFE Framework, the Revised Kyoto Convention, and the Harmonised System.

The blanks phenomenon was present because WCO had been operating IPM without a clear empirical picture of why adoption was low or what each user group needed. Creative Navy's research phase made the barriers explicit enough to prioritise core inspection workflows and rights holder alert flows before secondary features.

Legal, data, role, language, and connectivity constraints shaped the interface

Creative Navy's design work on IPM had to respect WCO legal obligations, data protection requirements, member administration expectations, role-based access, and separation between operational data and rights holder information. These were treated as design constraints rather than issues to bypass.

Field conditions varied across member states. Frontline inspection officers worked in ports, airports, and land border posts with unreliable connectivity, mixed device fleets, and limited time per inspection. The platform had to work under these conditions rather than only in controlled environments.

Tension-driven reasoning was used to address the main design tensions in the case: operational simplicity versus system completeness, a single unified interface versus diverse jurisdictional and linguistic contexts, and field speed versus data governance and role-separation requirements.

Creative Navy's Critical Systems Design method covered all five phases in WCO IPM

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.

In the WCO IPM engagement, all five phases were present. Sandbox Experiments included interviews, workflow mapping, and remote observation with WCO teams and selected member administrations. This work clarified the three user groups and documented concrete barriers to use.

Concept Convergence rebuilt the information architecture around real inspection and case management flows rather than internal system structures. Creative Navy applied recognition over recall, reduced choices per screen, progressive disclosure, and contextual micro-hints for first use of complex actions. Option space mapping applied to the information architecture restructuring and intelligence feature design.

Iterative System Building covered detailed design work across officers, analysts, and rights holders. Creative Navy designed context-aware data presentation for officers, pattern analysis for analysts without leaving the primary workspace, and filing and monitoring access for rights holders. The design also addressed role-based views, data separation, bandwidth optimisation for inconsistent connectivity, and accessibility compliance for public sector digital services.

Organizational Integration included design system construction, documentation, and training materials for global distribution. Terminology was normalised for translation and reuse across administrations, and the documented product model was structured for future WCO procurement, technical governance, and training work.

Implementation Partnership followed WCO governance structures, with active oversight during deployment across member administrations.

Microtask-level workflow changes reduced attention demands in routine inspection work

Creative Navy's design response focused on reducing cognitive load in routine inspection and case management flows. The documented changes included fewer choices per screen, less section switching, progressive disclosure, contextual micro-hints, and information architecture aligned to real operational flows.

Microtask analysis is evident in the reduction of unnecessary steps across inspection and case management tasks. Officers needed immediate access to relevant rights holder information, recent alerts, and historical cases when opening a shipment or product record. Analysts needed pattern analysis without leaving the primary workspace. Rights holders needed filing and monitoring paths that did not depend on informal workarounds.

Progressive specification is visible in the movement from research findings and barrier documentation through to information architecture, interaction design, design system, and rollout documentation for global distribution.

Usability testing involved 47 participants across five countries

The IPM workflows were validated through usability testing with 47 participants from Italy, Romania, Uzbekistan, Algeria, and Spain. The case evidence records that the workflows were validated as faster and less error-prone under realistic conditions.

The usability testing evidence supports the claim that the multilingual, multi-jurisdictional design held across genuinely different operational contexts. The evidence does not provide a numeric speed improvement or quantified error reduction for those usability tests.

Client-reported adoption, use, and training outcomes followed the redesign

WCO reported to Creative Navy that 107 governments signed up to IPM and that IPM remained in active use. WCO also reported a 200% increase in rights holder user sign-ups, a 20% increase in platform use among officers, a 67% increase in platform use among rights holders, and more than 2000 officers using the system in field operations.

WCO reported a 78% reduction in training costs for officers, based on reduced training hours. The case evidence links this result to the outcome category of scaling without training dependency because the system was deployed across many administrations without requiring uniform training infrastructure.

WCO also reported a decrease in support tickets and associated costs. The direction of that decrease is confirmed in the case evidence, but the magnitude is not quantified.

Creative Navy-observed operational changes included reduced workarounds and clearer audit trails

Creative Navy-observed changes included smoother officer onboarding reported by member administrations and reduced reliance on parallel spreadsheets and email chains. Creative Navy also observed that rights holders gained more direct access to filing and monitoring tools.

Member administrations reported clearer audit trails for enforcement actions. This evidence is useful for understanding operational clarity, but the case evidence does not quantify the audit-trail change.

The documented intangible resources transferred during Organizational Integration included judgment about global border management systems, shared product intuition about balancing operational speed with data governance, reasoning capability for extending the system across new enforcement scenarios, and a documented product model usable in future WCO procurement, technical governance, and training work.

Adoption density was the competitive vector described for WCO IPM

The competitive vector described for WCO IPM was adoption density across a fragmented global user base. This competitive vector is constructed from the product context and the design work performed, and the case evidence states that it was not independently verified with WCO.

IPM depended on participation from both officers and rights holders. Officer adoption affected the quality of seizure records and alert responses entering the network. Rights holder adoption affected the quality of intelligence available to officers. Low adoption on either side degraded the whole platform.

The 78% client-reported reduction in training costs and the 200% client-reported increase in rights holder sign-ups confirm this vector from different directions in the case evidence: one indicates reduced friction for officers, and the other indicates increased participation from rights holders.

Third-party endorsement and later return engagement provide longitudinal evidence

The case evidence records a third-party endorsement from Jürgen Stock, Secretary General of INTERPOL, confirming IPM as an effective tool for customs to combat IPR infringements. The exact quotation text is not reproduced here because the case evidence provides only the endorsement summary.

WCO returned to Creative Navy approximately three years after the original assignment to take the educational part of IPM and expand it into a spin-off product with a separate user base and a distinct business case. WCO's own team built the MVP of the educational spin-off before hiring Creative Navy to take it to the next stage.

This sequence is documented as independent evolution followed by a return engagement. The educational feature was a live part of the original IPM platform and formed the basis for the spin-off, so the original platform remained in service at the point of return.

Known evidence limits for WCO IPM

The current adoption figures beyond the 107-government milestone are not known from the case evidence.

Several outcomes are client-reported rather than independently measured in the case evidence, including the 200% increase in rights holder sign-ups, the 20% increase in officer platform use, the 67% increase in rights holder platform use, and the 78% reduction in officer training costs.

The decrease in support tickets and associated costs is directionally confirmed but not quantified. The competitive vector analysis is constructed from the product context and design work performed, and it is explicitly not independently verified with WCO.