Neugo

Neugo as a UK visa case-management platform across three engagements

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.

Neugo is a UK visa application case-management platform. It brings together people seeking a visa and the advisers who help prepare applications, including legal consultants, family offices, and similar roles. Neugo also provides a pipeline of quality data into the Home Office's existing border-force data platforms, where visas are actually issued.

The design problem in the Neugo case was not the visa issuing decision. The issuing decision remained in downstream Home Office systems. The design problem was the human-collaboration layer: the back-and-forth between the actors preparing a visa case to a clean, complete, submittable standard.

Creative Navy's work on Neugo took place across three separate engagements over roughly three years. Engagement 1 was a 7-week opportunity-framing and lobbying prototype. Engagement 2 was a 3-month full platform design and build-support engagement. Engagement 3 was a post-launch audit roughly 1 year after launch.

Naming boundaries for the Neugo case

Neugo and the Home Office may be named in the public case evidence. The consulting company that commissioned engagement 1 must not be named. The development company involved in engagement 2 must not be named.

The public-private consortium structure can be described, but the unnamed consulting and development organisations should remain described by type only. This confidentiality boundary is part of the case evidence and applies to all public use of the Neugo case.

The multi-party visa case-preparation structure

Neugo coordinates different actors around the lifecycle of a single visa case. The documented actors are visa seekers, advisers, case workers, and the Home Office or downstream border-force data platforms.

Visa seekers are the applicants, often acting as part of a travelling party rather than as isolated individuals. Advisers are legal consultants, family offices, and similar parties who prepare the application. Case workers move the case toward a submittable state. The Home Office and downstream border-force data platforms consume the clean data produced by Neugo.

The design challenge was cross-organisational and public-private. Neugo had to fit the existing practice of legal firms, including workflows that often used Excel, while also creating a shared case-management structure that could produce data fit for downstream government systems.

The closest documented portfolio comparison is Dancerace, because both cases involve a multi-party operating model. Neugo differs because the multi-party model sits in a government setting and concerns a net-new build for a single UK jurisdiction.

Engagement 1 used Sandbox Experiments for value elicitation

Creative Navy's engagement 1 on Neugo lasted 7 weeks and was commissioned by an unnamed consulting company that had identified the opportunity for a visa application case-management system. Creative Navy worked with the Home Office and four legal companies to understand what the system would need to be and what would make it appealing.

The purpose of engagement 1 was not to build the production product. The purpose was to create a prototype that could support a process to lobby the government to fund and commission the build, and to give backers something concrete enough to commit to. The output included value/desirability mapping and a clickable Figma prototype.

Creative Navy's Critical Systems Design method uses Sandbox Experiments as one of its phases. In the Neugo case, Sandbox Experiments were used in a value-elicitation mode rather than a conventional requirements-discovery mode. The paired prompt was: what if the system did X, and how would it have to do X for that to actually work for you. The first part stimulated stakeholders' sense of possible value. The second part kept that imagined value tethered to real operating conditions.

The blanks phenomenon appeared in engagement 1 at the value-recognition level. Stakeholders could not initially articulate the value the system would create for them; the sandbox work surfaced that value. This is a problem-recognition register of the blanks phenomenon, related in the documented estate to Puraite but expressed here through a public-sector commissioning prototype.

Engagement 2 designed the full platform and supported implementation

Creative Navy's engagement 2 on Neugo lasted 3 months and followed roughly 1 year of silence after engagement 1. The client returned as a public-private consortium to build the system. Creative Navy worked alongside an unnamed development company.

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 engagement 2, Creative Navy produced the design for the full platform and provided Implementation Partnership for the developers. The system went live approximately 8 months after this engagement.

The engagement began with a 2-week Sandbox Experiments phase based on workshops with legal firms. The workshop themes included handling entire parties travelling together, deciding what to integrate from legal firms' existing tools, deciding what should remain in those tools, and prompting case workers on what to do next. The prompting decision was tied to the value event: a submittable, ready application, rather than an open-ended preparation process.

Concept Convergence in Neugo was prioritisation through desirability and feasibility

Creative Navy's Concept Convergence work in engagement 2 should be read as prioritisation only. It was option space mapping through a desirability × feasibility filter. It did not involve tension-driven reasoning, a local-versus-system tension, or a competitive vector.

Every possibility from the experiments was assessed on two dimensions: how strongly users wanted it, and how technically feasible it was within roughly a 2-year horizon. The case evidence records the shape of the convergence rather than measured proportions: a large majority where want and feasibility were both high, a small set dropped because feasibility was near zero regardless of want, and a weighed middle resolved through product-manager input, Creative Navy's input on user salience, and developer input on the designs.

The exact recalled proportions for the large majority, dropped set, and weighed middle are not measured figures. The public claim should remain the shape of the convergence, not a quantified split.

Iterative System Building used beneficiary checkpoints before development handoff

Creative Navy's Iterative System Building work on Neugo moved requirements from beneficiaries to design to development without product-management intermediation of the requirements themselves. The beneficiaries were the legal firms that would use the system.

Before designs reached developers, Creative Navy exposed them to the legal firms at three checkpoints. The first two checkpoints materially changed the design. The third checkpoint gave the design the green light.

This is a documented instance of progressive specification. Requirements were not frozen at the start. They became more specific through beneficiary workshops, design work, legal-firm checkpoints, and then development handoff.

The Neugo tooling decisions also show constraint respecting. The platform integrated everything from the legal firms' existing tooling except a small number of fields that were unique to one single legal office. The design preserved what worked across existing practice without over-generalising one office's idiosyncratic fields into the shared system.

Organizational Integration prepared for a future product owner

Creative Navy's Organizational Integration work in engagement 2 had an unusual recipient problem. The case evidence records that there was, in practice, no genuine product owner: nobody took ownership of decisions or of understanding the system, and the product-management function did not absorb the system as a decision-making owner.

Creative Navy therefore treated Organizational Integration as preparation for a future recipient. The deliverables were documentation plus three videos explaining the architecture, the decisions behind the design language, and the principles to apply if the system grew.

This is an instance of deliverable format following purpose. The integration artefacts were not only a handover to an active owner. They were a bequest to whoever might later take on a genuine product-owner role.

Implementation Partnership supported the unnamed development company

Creative Navy provided Implementation Partnership across the course of Neugo development. The development company cannot be named publicly.

The case evidence records that Creative Navy answered 17 developer questions during Implementation Partnership. This is a Creative Navy-recorded engagement fact, not a measured outcome.

Engagement 3 recorded post-launch reliance and process absorption

Creative Navy returned to Neugo roughly 1 year after launch for a post-launch audit. The purpose was to take stock of new feature needs and assess whether the platform should evolve, take a new shape, or change more radically.

The audit produced the strongest outcome evidence in the Neugo case. Creative Navy observed that 15 legal firms were relying on Neugo in production. Creative Navy also observed that the legal firms had replaced some of their internal processes with Neugo's features, reproducing their own setup inside the platform in an improved form.

The four legal firms involved in engagement 1 carried through as engagement-2 beneficiaries and were among the 15 legal firms relying on Neugo at audit. This makes the audit a longitudinal return point rather than a delivery-time self-report.

Commissioning outcome is client-reported and not causal

The engagement-1 prototype contributed to Neugo being commissioned to be built, but the case evidence does not support a causal claim that the design secured the commission.

The calibrated claim is client-reported: 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. The accurate statement is that the design was a substantial, client-reported component of a multi-factor commissioning decision built partly around demo sessions of the prototype.

This makes Neugo a public-sector register of design-as-investment evidence. The artefact supported a public commissioning decision rather than a private-capital investment decision.

Evidence boundaries for Neugo

The Neugo case contains no field-measured performance metric. The adoption and process-absorption finding is Creative Navy-observed during the post-launch audit, and it is stronger than delivery-time client self-report, but it is not a quantified performance study.

The commission contribution is client-reported. The roughly 30% figure and the dedicated demo-session arrangement are recorded as stakeholders described them to Creative Navy. The case evidence does not establish that the prototype caused the commission.

The convergence split in engagement 2 should not be reported as percentages. The proportions are recollection, not measured figures. The supported public claim is the pattern of prioritisation: a large easy-converge majority, a small infeasible set, and a weighed middle resolved through product-manager, user-salience, and developer input.

Neugo is not a regulated medical device. The IEC 62366-1 caveat used for regulated medical-device work does not apply to this case.