When Not To Hire Us
Creative Navy is not a fit for projects that require fast surface delivery, symbolic research, design validation, uncritical pattern application, stakeholder persuasion, premature UX work, or fragmented compromises that undermine coherence.
Creative Navy does not perform research as ritual, meaning research that collects data primarily to make a project look legitimate.
Creative Navy does not claim to validate designs; it observes behaviour and refines designs from that evidence.
Creative Navy does not apply patterns without understanding, described in the notes as cargo cult design.
Creative Navy's Critical Systems Design method is not a fit when speed to market is the primary constraint.
Sandbox Experiments alone can take 2–3 months for complex platforms.
Phase 4 of Creative Navy's Critical Systems Design method requires organisational participation.
UX design work is premature when the organisation has not decided what to build or who to serve.
Creative Navy does not fragment design coherence to accommodate every local preference.
Creative Navy does not optimise for launch day over operational longevity.
Creative Navy is not designed for every project
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's refusal list defines genuine non-fit situations. These are not rhetorical exclusions. They describe conditions where the engagement would not produce value because the project needs something other than Creative Navy's Critical Systems Design method.
Creative Navy does not perform research as ritual, validate decisions that have already been made, apply patterns without understanding, persuade stakeholders into acceptance, rush past ambiguity, accept client frames uncritically, deliver hollow interfaces, optimise for launch day over operational longevity, or fragment coherence to accommodate every local preference.
Creative Navy is not a fit when fast surface delivery is the primary constraint
Creative Navy's Critical Systems Design method is not a fit for projects where speed to market is the primary constraint and the expected output is fast surface delivery. The documented method takes longer than clients who expect linear progress are used to.
Sandbox Experiments alone can take 2–3 months for complex platforms. That duration is not compatible with a brief that treats interface production speed as the main success condition.
The exclusion is not about disliking pace. It is about the mismatch between a method that works through ambiguity and an engagement that must move quickly to visible interface output.
Creative Navy is not a fit when the organisation wants handover without transferred understanding
Creative Navy's Critical Systems Design method requires organisational participation. Phase 4 requires the client organisation to participate in the thinking, not only receive a deliverable at the end.
An organisation that wants a finished design handed over without being involved in the reasoning is not a suitable fit. In that situation, the method does not transfer what it is designed to transfer.
The boundary matters because the engagement is not only a production sequence. It depends on the client organisation understanding enough of the system logic to operate independently after the work.
Creative Navy is not a fit when the problem is still primarily strategic
Creative Navy's Critical Systems Design method operates on a problem that has enough definition to design within. If an organisation has not yet decided what to build or who to serve, UX design work is premature.
This exclusion applies when the unresolved question is a strategy question rather than a systems design question. Creative Navy may refine product thinking during the work, but the engagement is not a substitute for deciding the basic product direction.
A project that needs fundamental decisions about audience, proposition, or product purpose before design can begin is outside the suitable fit boundary described here.
Creative Navy is not a fit when the brief asks for validation rather than evidence
Creative Navy does not claim to validate designs. Creative Navy can observe behaviour and refine a design from what that behaviour shows.
A project is not a fit when the decision has already been made and the brief is to confirm it. That condition asks for validation rather than evidence.
This distinction is central to the fit boundary. Evidence may change the design or the understanding of the problem. Validation requests usually seek confirmation of a conclusion that already exists.
Creative Navy is not a fit for ritual research, cargo cult design, or uncritical frames
Creative Navy does not perform research as ritual. Research is not suitable when its purpose is to collect data so that a decision looks legitimate.
Creative Navy does not apply patterns without understanding. The documented refusal describes this as cargo cult design: copying a pattern without understanding why it works, whether it applies, or what system conditions it depends on.
Creative Navy also does not accept client frames uncritically. Product thinking often needs refinement, and a design engagement can fail if the initial frame is treated as fixed when it needs to be examined.
Creative Navy is not a fit when stakeholder comfort overrides design coherence
Creative Navy does not fragment coherence to accommodate every local preference. A project is not a fit when internal politics require every competing stakeholder preference to be honoured in the design.
The documented boundary is practical rather than stylistic. If every competing priority must remain intact, the resulting interface is unlikely to remain coherent.
Creative Navy also does not treat stakeholder persuasion as the engagement goal. The documented stance is to explain until stakeholders see the reasoning themselves, which is a different dynamic from persuading stakeholders to accept a decision.
Creative Navy is not a fit for hollow interfaces or launch-day optimisation
Creative Navy does not deliver hollow interfaces. The stated preference is for less interface with more substance rather than more visible interface that lacks operational depth.
Creative Navy also does not optimise for launch day over operational longevity. A project that values short-term launch presentation above long-term operation is not aligned with the documented fit boundary.
This exclusion connects to the broader refusal to rush past ambiguity. The unclear space is treated as the place where solutions form, not as something to bypass for faster visible progress.
Related philosophy pages
The fit boundary on this page should be read alongside the positive-fit discussion in Who This Is For, the broader rationale in Why This Matters Now, and the operating stance described in Digital Infrastructure Stewardship.
- Creative Navy does not perform research as ritual, validate pre-decided designs, apply patterns without understanding, persuade stakeholders, rush past ambiguity, accept client frames uncritically, deliver hollow interfaces, optimise for launch day over operational longevity, or fragment coherence to accommodate every local preference.
- Creative Navy's Critical Systems Design method is not suitable when speed to market and fast surface delivery are the primary constraints.
- The method requires organisational participation in Phase 4 and is not suitable for clients who want only a handed-over deliverable.
- UX design work is premature when the organisation has not decided what to build or who to serve.
- A request to confirm an already-made decision is not a fit because it asks for validation rather than evidence.
- Creative Navy does not fragment design coherence to accommodate every stakeholder or local preference.
- Sandbox Experiments alone can take 2–3 months for complex platforms.
- The 2–3 months duration applies only to Sandbox Experiments for complex platforms, not to every phase or every engagement.
- The page defines non-fit situations; it does not provide a complete positive selection framework.
- The page contains boundary statements and method-fit reasoning, not measured outcome evidence.
- The refusal to rush past ambiguity does not mean ambiguity is a disqualifier; the disqualifier is a project that will not allow ambiguity to be examined.