What Creative Navy Learns When an Engagement Falls Short

Creative Navy's failures ledger and evidence basis

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 publishes engagements that did not work to apply the same evidence calibration used elsewhere on the site to unflattering findings. The evidence basis is Creative Navy-recorded engagement evidence except where a third party is named. Client names are used where the client can be named and the engagement is recounted without commercial detail requiring client sign-off. Two engagements are anonymised at client-category level.

The ledger is not presented as a set of universal rules. Some entries contain a settled lesson. Some entries record a boundary condition of Creative Navy's Critical Systems Design method. One entry records a prediction later reported as confirmed by Tecs Software, the third-party developer that inherited the work. One entry, Leo Cancer Care, is published without a settled account of what Creative Navy should have done differently.

Failure pattern: a blank with no source to fill it

Creative Navy's Critical Systems Design method is described in this page as filling upstream gaps in what a client does not know, has not framed, cannot articulate, or will not confront. Creative Navy calls this family of upstream gaps the blanks phenomenon. The first failure pattern appears when there is no source from which to construct the missing content: no users to learn from, no organisational stake to mobilise, or no substance behind the vision.

Big Sky as an empty vision rather than a design brief

Big Sky was a 2017 engagement for a founder who wanted to build a professional social network for excellent working partnerships. The founder spoke in vision terms and asked Creative Navy not to worry about specifics because he would reveal them later.

Sandbox Experiments requires candidate content to be put on a screen so that the content can be tested, corrected, and made more concrete. In the Big Sky engagement, Creative Navy records that there was no view of what the system needed to capture, what people would be connected around, or what artificial intelligence would practically do. The source of specificity needed for Sandbox Experiments was absent.

Creative Navy recommended stopping after two weeks. Creative Navy advised the founder to commission engineers to build a UI-less prototype first, so that the system's buildable capabilities and core entities could be established before design work continued. The lesson recorded by Creative Navy is that a vision with no engineering reality behind it and no source to ground it is a feasibility question, not an early-stage design engagement.

A Big Four professional-services concept as absent organisational stake

The anonymised Big Four professional-services engagement concerned an immersive multi-monitor cybersecurity concept for executives. The six-week purpose was to produce a concept that could be taken to management for a build decision. A project team and roughly ten subject-matter experts were assigned to supply content for the screens.

Creative Navy records that the experts were each available for only about one hour to ninety minutes across the engagement, and that the content offered was too general to visualise. Creative Navy adapted Sandbox Experiments by using provocative visuals and external diagrams to try to make the experts correct, object, and reveal concrete knowledge.

Creative Navy records that the adapted technique did not work because the experts had no stake in the concept. The concept belonged to one sidelined person in the business, and that person did not have the knowledge or organisational cooperation needed to substantiate it. Creative Navy's distinction is that lack of knowledge among engaged experts can be fillable, but lack of stake removes the precondition for filling a blank.

Failure pattern: client conviction overrides evidence

Creative Navy records a second failure pattern where evidence and exploration produce a direction, but the client holds to a contradictory conviction. In these engagements, Creative Navy could have produced work the client asked for. Creative Navy records the engagements as failures because continuing would have produced work that Creative Navy judged harmful, irrelevant, or structurally unable to matter.

Tion and the demand to feature irrelevant dashboard elements

Tion had built an unsatisfactory interface for fume-cupboard design and wanted a better one. The client could fund roughly one-sixth of Creative Navy's quote, with the rest deferred, and accepted an intentionally partial outcome. Creative Navy scoped the work as an improvement to the main dashboard and visual style rather than full UX research and architecture.

At presentation, Tion wanted options that differed at the UX level, with different dashboard elements, because the existing elements were not exciting enough. Creative Navy's position was that an element must be relevant before it is made prominent. The client could not identify useful elements for users, and the three candidate elements proposed were agreed by the client to be distracting and irrelevant.

Creative Navy records that the user research needed to resolve the issue was outside the budget. Creative Navy stopped rather than feature irrelevant elements prominently. The client was disappointed, said so, and did not return.

Pflegewelt and the cinematic experience care workers had no time for

Pflegewelt was an NGO serving care workers in Germany. Pflegewelt wanted an online presence that would attract care workers with features and information and build a database for outreach. Creative Navy engaged care workers, learned their needs, sandboxed features, collected feedback, and prioritised for buildability and reward.

The care workers pointed toward immediate access to feature and information value. Pflegewelt wanted a cinematic narrative experience with talking characters and entertainment. Creative Navy advised against that direction because it would take control and time away from users who had little spare time.

Creative Navy records that Pflegewelt held to its vision. Creative Navy stated that it was not an entertainment or branding studio, recommended that Pflegewelt find a provider that was, returned the money paid in advance for UI work, and onboarded the replacement provider at no charge by converting the implementation-support allocation into handover support.

Sharpcloud and the client-endorsed result Creative Navy disputes

Sharpcloud's project-management platform used proprietary concepts visualised as screens carrying 100–200 elements of around 14 types. The brief was to reduce screen complexity, improve element recognisability, and add navigation between screens.

Creative Navy's assessment was structural: with that many elements and types on a screen, the load exceeded human capacity by orders of magnitude, and visual treatment alone could not fix it. Creative Navy records that the constraint that would have mattered was showing fewer elements or fewer types, but the client held that the core concepts and requirements could not change.

Creative Navy used Sandbox Experiments on the visual layer alone over four weeks. The client implemented roughly 60% of Creative Navy's suggestions and called the engagement positive. Creative Navy records the engagement as a failure because the interface may have become marginally better but still left users lost in the count of elements.

Predicted failure confirmed after the motorsport-simulation handover

The anonymised motorsport-simulation engagement is the most evidentially complete failure in the ledger because Creative Navy records a prediction made at handover and a later third-party report that the predicted pattern occurred. The client was a race-track mechanics business that had acquired a sophisticated vehicle-simulation product and wanted to develop it further after a prior software-company attempt had already failed.

Creative Navy proposed a full UX and UI plan. The client did not accept the iterative, evidence-led path of Sandbox Experiments and instead wanted Creative Navy to apply the work to isolated components. Creative Navy first applied the work to navigation, producing five versions and explaining the downstream implications of each. The client then asked for visual style applied to navigation, and then for another component in the same isolated way.

Creative Navy advised that continuing component by component would reach the budget the client wanted to avoid while failing to address the big picture that made the components cohere. The client hired two freelancers to continue in the manner it preferred. At handover, Creative Navy described the outcome as "the illusion of control, but it won't work." Creative Navy later ended the engagement after advising against further small isolated deliverables.

Tecs Software, the developer Creative Navy recommended and the development firm that inherited the project, later reported through its development team lead that Creative Navy's prediction had come to pass. According to that third-party report, the freelancers had not used Creative Navy's Critical Systems Design method, components were reworked repeatedly, the architecture made no sense, user needs surfaced unexpectedly, and the work repeatedly reached dead ends.

The cost figures are calibrated as client-reported and relayed through the Tecs Software development lead. Six months in, the client was reported to be where the work should have been after one month. The client was reported to have spent roughly 70% of Creative Navy's original quote without a usable result, before a separately wasted development cost that was binned entirely.

Failure pattern: focus or scope cannot converge under constraint

Creative Navy records a fourth failure pattern where the blank is fillable and the client is willing, but the engagement fails because the client cannot converge under a resource constraint. The problem is not absence of all content. The problem is too many circulating ideas, emotional fixation on surface experience, or insufficient focus to decide what work is actually being done.

Social Match Play and the inability to abstract from emotion to backbone

Social Match Play was a small-team app concept for friends watching a game together and predicting what would happen next for points rather than money. One sprint of Sandbox Experiments surfaced two problems.

Creative Navy records that the team focused on the emotional, cinematic texture of the experience and could not abstract from that surface to the core flows and interactions the app needed first. Creative Navy also records that the intended scope steadily exceeded the initial description. The parties agreed to stop so the team could rethink before spending further.

Creative Navy records Social Match Play as a clean, early, mutually agreed halt. Sandbox Experiments surfaced the disqualifying dynamic in one sprint, even though the engagement ended.

EarthX and the origin of focus stewardship

EarthX was a 2018 engagement with a small team building a geodata platform. The team included two engineers and a business lead. The engineers had expansive visions of a mature product, including the phrase "Wikipedia of geodata." The business lead sold visions to customers and investors but did not engage with the detail of what the engineers were building.

Creative Navy had no access to the platform's actual users and depended on the client for direction. Several product ideas circulated at once: the vision sold upward, a partly remembered agreement with smaller customers, and a different product described by the engineers when asked to fill gaps. Sandbox Experiments helped, but Creative Navy records that the work remained slow and inefficient.

The EarthX engagement succeeded commercially for the client: the client implemented a conclusion, won customers, and was satisfied. Creative Navy records the engagement as inefficient throughout and as the origin of focus stewardship. Since EarthX, Creative Navy's Critical Systems Design method includes a standard response when multiple circulating visions and low-detail leadership appear: map the visions, operationalise each, build low-fidelity wireframes, require the team to decide what is in focus now, and run a workshop to discharge the salience of visions not being pursued.

Failures caused by forces outside Creative Navy's design control

Not every failed engagement in the ledger is treated as a method failure. Creative Navy records some failures as outside the reach of Creative Navy's Critical Systems Design method, either because the client collapsed commercially or because the client decision structure contained a contradiction Creative Navy did not resolve.

Xpress Money and the external shock of bankruptcy

Creative Navy was two months into design-for-production for Xpress Money. The UX had been delivered, the initial UI concept had been delivered and greenlit, and perhaps 17–20 screens remained.

The client announced bankruptcy, later revealed as a major fraud case that made the news. Creative Navy records that no one saw it coming and that people inside the organisation were as shocked as anyone. The company went under entirely and built nothing.

Creative Navy records no design lesson from Xpress Money. The entry is included because it marks the limit of what design controls: the design work can be right and the outcome can still be zero for reasons unrelated to the work.

Leo Cancer Care and the unresolved contradiction in client decision-making

Leo Cancer Care was a high-consequence medical engagement across two engagements. Creative Navy first produced an initial UI establishing the shape of a novel radiotherapy device and demonstrating that its UX was feasible after the client confirmed the device was buildable and found partners. After roughly a year of mechanical development, Creative Navy worked on a more detailed, implementable UX for a first functional prototype.

Requirements were supposed to come from a third-party engineering firm experienced in building radiotherapy devices and contracted by Creative Navy's client. Creative Navy records that the requirements were relevant but generated a need for further research to answer questions to the standard required for compliance, regulatory affairs, and detailed implementation.

The client's project manager greenlit spending every two to three days while also insisting at the macro level that the budget and timeline could not grow. Creative Navy informed the project manager of the consequences each time. The budget was ultimately supplemented and the final stretch curtailed, leaving the work incomplete. The functional prototype covered less of the device's intended functionality than planned, and the client's project manager was unhappy.

Creative Navy does not claim to know the right resolving lesson from Leo Cancer Care. The open question is whether Creative Navy should have forced the contradiction into the open earlier or contracted against such decision structures from the start. The ledger preserves that uncertainty rather than inventing a lesson.

What the failure ledger establishes and does not establish

Creative Navy records the failures as evidence that calibration is applied to unfavourable findings as well as favourable case studies. Sharpcloud is recorded as a failure despite client satisfaction. Leo Cancer Care is recorded without a resolving lesson. The motorsport-simulation engagement is recorded with a forward prediction and later third-party confirmation from Tecs Software rather than Creative Navy's own measurement.

The ledger supports a boundary claim about Creative Navy's Critical Systems Design method. Critical Systems Design can fill blanks when there is a source to work from and sufficient client engagement to construct missing content. Critical Systems Design fails predictably where there is no source to fill a blank, where the client has filled the blank wrongly and will not allow it to be refilled, or where the client cannot hold the focus needed to fill it.

The ledger also records what Creative Navy declined. Tion, Pflegewelt, and the motorsport-simulation engagement each contain a refusal to proceed in the way the client wanted when Creative Navy judged that the work would be irrelevant, damaging, or wasted. This is evidence of a boundary in Creative Navy's practice, not a guarantee that every refusal will later be independently confirmed.

The strongest counterfactual in the ledger is the motorsport-simulation engagement. A successful engagement can show what Creative Navy's Critical Systems Design method produces. That engagement shows what the absence of the recommended method was reported to cost: roughly 70% of the original quote spent without a usable result, six months to reach a position reported as worse than one month of proper work, and the build cost written off. Those figures are client-reported and relayed through Tecs Software, not independently measured by Creative Navy.