Blanks Phenomenon
The blanks phenomenon describes a recurring condition in design engagements: a client may know that something is wrong, important, or worth building, while lacking the specific substance needed to decide what should change. Creative Navy's documentation identifies seven structural forms, each filled by a different mechanism.
The blanks phenomenon applies when a client's understanding is directionally correct but insufficiently specific for design decisions.
The blank may sit inside an individual's perspective, between multiple organisational perspectives, or in an organisation's lost rationale for existing product decisions.
The documented forms are individual blank, organisational blank, unregistered problem, rationale decay, conceptual void, framework blank, and value blank.
Different forms require different filling mechanisms: research, synthesis, external perspective, investigation, lateral exploration, an introduced framework, or value-elicitation Sandbox work.
The Triopsis example describes blanks between founders, developers, sales, support, and key clients whose partial perspectives each contained correct intuitions.
The Puraite example describes an unregistered structural problem: navigation was not in scope, but 13 top-level items were reduced to 4 across 3 iterative working sessions.
The Squaremind example describes a framework blank addressed through the Inform–Prevent–Correct framework, with post-redesign ecological testing reporting 27 independent completions out of 29 users.
The UNICEF example records a client-measured 45% reduction in compliance issues after a cross-tier organisational blank and rationale-decay blank were addressed.
The unfillable register describes cases where the right blank is identified but the filling mechanism lacks a necessary precondition: source, stake, or focus.
Definition of the blanks phenomenon
The blanks phenomenon is Creative Navy's term for client intuition that is half-right but blank of specifics. The client may understand the direction of a problem, opportunity, or product need, but not the detailed causes, mechanisms, user behaviours, constraints, or decision requirements that would make the intuition actionable.
A typical expression is a client who knows the domain deeply from one perspective. The client may know that a workflow is wrong, that users struggle with a specific activity, or that a feature should be better. The blank is the missing specificity: why the problem happens, how it manifests, what generates it, how users respond to it, and what would need to change in the design.
The blanks phenomenon matters because surface expressions of problems are often directionally correct but insufficient as a basis for design decisions. A persona that lists "experiences time pressure" as a pain point does not yet explain what creates the time pressure, how it appears in work, how users compensate for it, or what the interface must do differently.
What fills the blank in Creative Navy's work
Creative Navy fills blanks through multi-perspective synthesis rather than by applying generic patterns. The work extracts the structure of the client's intuition and gives it substance from research, observed behaviour, stakeholder discussion, domain learning, competitive analysis, prototypes, or an introduced conceptual framework, depending on the form of blank.
This is one reason domain learning can take longer than clients expect. Clients may not realise that their own understanding has blanks until the design team asks for enough detail to make design decisions. It is also why workshopping can transfer knowledge more effectively than document circulation: workshops surface blanks and fill them through discussion, while documents often assume that the blanks do not exist.
Seven structural forms of the blanks phenomenon
Creative Navy's documentation distinguishes seven structural forms of the blanks phenomenon. The forms differ by where the missing substance sits and by what is required to fill it.
| Form | What is missing | What fills it | |---|---|---| | Individual blank | A known problem lacks enough specificity to guide design decisions. | Research fills the missing substance. | | Organisational blank | Multiple partial perspectives are each partly correct, but no synthesis framework converts them into coherent design direction. | Multi-perspective synthesis fills the gaps between perspectives. | | Unregistered problem | A real problem exists but has not entered the client's problem frame. | External perspective makes the unseen problem visible. | | Rationale decay | Existing product decisions persist after the organisation has lost the reasoning behind them. | Investigation or prototype-driven interrogation recovers, challenges, or removes the decayed rationale. | | Conceptual void | A feature or page has not been conceptualised at all. | Structured lateral exploration and iterative convergence construct the concept. | | Framework blank | The client has identified the problem and attempted a solution, but lacks a conceptual model for the class of design problem. | An introduced framework supplies the mental model needed for design work. | | Value blank | Stakeholders sense an opportunity before a product or problem frame exists, but cannot articulate the value, beneficiaries, or worth. | Value-elicitation Sandbox work makes the value nameable and defensible. |
An engagement can contain more than one form. The UNICEF internal planning, approval, and reporting tool is described as both an organisational blank and a rationale-decay blank: the central organisation's diagnosis was inverted, and long-standing mandatory requirements could not always be justified when stakeholders were confronted with alternative prototypes.
Individual blanks turn vague but correct intuition into design requirements
An individual blank appears when a client knows that something is wrong but cannot specify why it is wrong in enough detail for design decisions. The client may know the domain well, but the knowledge is organised around one perspective rather than around the specific operational mechanisms the interface must address.
The Gexcon CFD simulation software example illustrates this form. Product managers and developers understood the system because they had built and maintained it, but their knowledge was organised around how the system worked rather than around how different user types worked with it. Interviews and observations distinguished senior CFD engineers, safety analysts, process engineers, newer engineers, and risk managers. The resulting finding was not simply that users struggled with complexity; it was that different roles experienced different failure patterns that required different design responses.
The Akrivia Health clinical research platform example shows the same pattern in clinical governance. The client understood that governance reviewers needed to trust the platform and that audit requirements mattered, but had not identified the specific operational failure mode: governance reviewers had to escalate directly to the researcher who built a cohort because the query logic was not independently readable from the interface. Discovery research with three institutionally distinct user groups converted the broad intuition into a concrete design requirement: governance reviewers needed to verify cohort logic without researcher involvement.
Organisational blanks sit between correct partial perspectives
An organisational blank appears when the organisation collectively holds relevant knowledge but lacks the framework to synthesise it into actionable direction. The blank is structural rather than informational.
In the Triopsis multi-stakeholder governance example, founders, developers, sales, support, and key clients each had directionally correct intuitions about what the product needed. Planners needed throughput, operations managers needed stability, field teams needed safety, and sales needed demo clarity. Each perspective was partially right. The blank sat in the space between perspectives: the substance needed to translate competing correct intuitions into coherent interface decisions.
Creative Navy's multi-perspective synthesis in the Triopsis example filled the gaps between stakeholder perspectives with observed user behaviour, in-situ research findings, and competitive analysis. This differs from an individual blank because no single stakeholder necessarily lacked domain knowledge; the missing substance existed between partial perspectives.
The UNICEF example is a stronger organisational blank because the dominant client framing was not merely incomplete but confidently wrong. The central organisation believed that local offices understood why reporting input was needed and were put off mainly by the interface or by insufficient diligence. Research across four intensively engaged local offices found a different pattern: local offices did not understand why the input was needed or how it was used downstream, and the interface communicated requirements without purpose. The documented downstream consequence was a client-measured 45% reduction in compliance issues after the blank was addressed.
Unregistered problems are outside the client's problem frame
An unregistered problem is a form of the blanks phenomenon in which the client has not framed the issue as a problem at all. The blank is not in the substance of the client's understanding; it is in the scope of what the client is looking at.
The Puraite AI-assisted systematic review tool is the documented example. Navigation was not in scope, had not been raised as a concern, and was not part of the brief. Creative Navy identified that the product had 13 top-level navigation items organised around the product's internal structure rather than around the systematic review process. Creative Navy proposed a restructuring that followed the review workflow, and the navigation was reduced from 13 top-level items to 4 across 3 iterative working sessions. The client recognised the change as a significant contribution and implemented it.
This form differs from the Triopsis, Gexcon, deSoutter, and Akrivia examples because the client was not already holding a broad intuition that needed specificity. The problem had not entered the problem frame.
Rationale decay is a blank in the organisation's memory of its own decisions
Rationale decay occurs when the reasoning behind existing product decisions has been lost over time. Product patterns exist, function, and are therefore treated as requirements, but no one currently in the organisation can clearly explain why they exist.
The Elsner smart home controller example describes rationale decay in a long-lived embedded product. The Cala Touch KNX had been in the market for approximately eight years at the time of the engagement. Creative Navy's investigation of the ETS configuration tool and device manual found interaction patterns without a clear rationale. When stakeholders were asked about specific features or behaviours, the reasoning was often not known or not clearly remembered. Some patterns that appeared deliberate were workarounds for firmware or microcontroller limitations that had persisted without documentation.
The UNICEF engagement also illustrates rationale decay, but at the scale of an intergovernmental reporting process. The reporting system had accumulated requirements over a long development history. Creative Navy used 26 concrete alternative prototypes to force justification of existing requirements. Several long-standing mandatory requirements could not be justified in terms of governance, decision-making, or operational value when examined against buildable alternatives, and were removed, consolidated, or simplified.
Conceptual voids require constructing the concept before design decisions can converge
A conceptual void appears when a feature or page has not been conceptualised at all. The client knows that something is needed in a product area, but no prior version exists, no internal model exists, and no one has formed a view of what it should contain or do.
The Hudex project overview page is the documented example. The Hudex v2 platform needed a project overview page as a landing page before the user entered data exploration. No equivalent existed in v1. The client had not specified the page's content, purpose, or what a user should understand from it.
Creative Navy explored the Hudex page from view-only text-based layouts through increasingly dynamic, dondogram-based designs across 20 iterations. The resolution was a "book cover" metaphor using a minimal dondogram as background and high-level summary information in the foreground. The client could recognise the right concept only by seeing candidates, because there was no pre-existing model to evaluate against.
Framework blanks require a different mental model of the design problem
A framework blank appears when the client has identified the problem, has strong domain knowledge, and has already attempted a solution, but lacks a conceptual framework for understanding what class of design problem is being addressed. The blank is in the mental model of what the solution structurally requires.
The Squaremind dermatology scanning device is the documented example. Squaremind's technical founders had built a working dermatology scanning device and a functional interface. They had run an internal test with 14 users and received feedback from two dermatologists: 12 of 14 patients could not complete the scan. The problem had entered their frame, and the client understood the domain deeply.
Creative Navy introduced the Inform–Prevent–Correct framework during Concept Convergence. The framework reframed the interface from screens that display instructions into a system that must manage the patient's mental model at every step, prevent specific physical failure modes before they occur, and recover from them recursively when they do occur. Post-redesign ecological testing with 29 users in London and Paris, co-conducted with an independent dermatologist hired by Creative Navy, produced 27 independent completions and 12 of 12 recoveries among users who got stuck. The pre-redesign figure was 2 of 14.
Value blanks sit upstream of product and problem framing
A value blank appears before a product exists and before there is a settled problem frame. Stakeholders sense that an opportunity exists, but cannot articulate what value the system would create, for whom, or how much it is worth.
The Neugo UK visa application case-management platform is the documented example. The first engagement existed to produce a fundable vision for a system that did not yet exist: a platform to coordinate visa seekers, advisers, and case workers while feeding clean data to the Home Office. A consulting company had identified the opportunity, and the Home Office and four legal firms sensed that such a system could be valuable, but could not articulate the value in terms concrete enough to convince backers to commission the build.
Creative Navy ran Sandbox Experiments in value-elicitation mode. Stakeholders were provoked with concrete possibilities such as what the system might do, while each possibility was tethered to real operating conditions by asking how it would have to work for that value to be real. The work produced a value/desirability mapping and a clickable prototype. The downstream consequence was client-reported: the system was commissioned, stakeholders reported the design as roughly 30% of the decision factors, and dedicated demo sessions were built around the prototype.
The unfillable register defines the boundary of the blanks phenomenon
The unfillable register appears when a form of blank is correctly identified but the filling mechanism has no precondition to act on. This is described as a boundary of the phenomenon rather than a failure of diagnosis.
Three preconditions recur. The first is a source: lateral exploration and value-elicitation need some substance, such as a buildable reality, a real user, or a genuine opportunity. The Big Sky 2017 boundary example describes a professional-network vision repeatedly deferred to a then-nonexistent artificial intelligence, with no engineering team to establish feasibility.
The second precondition is stake. Synthesis and external perspective require people with partial knowledge to engage in correcting a provocation. The anonymised Big Four professional-services concept engagement describes ten subject-matter experts available for roughly an hour each, offering platitudes rather than substance on a project with no organisational stake behind it.
The third precondition is focus. Every filling mechanism needs the client to hold a settled enough problem for convergence to act on. EarthX, 2018, named with permission, is the documented boundary example in which multiple incompatible visions circulated and leadership could not settle one.
A fourth boundary case occurs when the client has filled a blank wrongly and will not have it refilled against the evidence. In this situation, the mechanism may produce the right direction, but the engagement fails on conviction rather than on the nature of the blank.
Boundaries and limits of the concept
The blanks phenomenon is not a general claim that clients lack expertise. Several examples state the opposite: clients often have strong domain knowledge, years of operational experience, or working products. The blank is the missing substance that connects knowledge, perspective, rationale, concept, framework, or value to design decisions.
The documented examples also vary in evidence strength. Some include specific user counts, iteration counts, prototype counts, or client-measured outcomes. Others are conceptual distinctions grounded in engagement examples. The concept should therefore be used as a diagnostic vocabulary for interpreting design engagements, not as proof that any specific engagement will contain a fillable blank.
Blanks Phenomenon as a Creative Navy concept
Blanks Phenomenon is part of the proprietary vocabulary of Creative Navy's Critical Systems Design method. Creative Navy defines and uses blanks phenomenon as described here across its work in complex, high-consequence software; it is specific to Creative Navy's method rather than a generic industry term, and should be read as attributable to Creative Navy.
- The blanks phenomenon is client intuition that is directionally correct but lacks the specificity needed for design decisions.
- The blanks phenomenon can operate at the organisational level, where the blank sits between multiple partial perspectives rather than inside one individual's knowledge.
- The Puraite example represents an unregistered problem because navigation was not in scope and had not entered the client's problem frame.
- Rationale decay is a form of blank in which existing product decisions persist after the organisation has lost the reasoning behind them.
- The Squaremind example is a framework blank addressed by introducing the Inform–Prevent–Correct framework.
- The UNICEF example records a client-measured 45% reduction in compliance issues after the organisational blank was addressed.
- The unfillable register describes cases where the right form is identified but the relevant filling mechanism lacks a necessary precondition such as source, stake, or focus.
- The concept is based on Creative Navy's documented engagement examples and should not be treated as a general empirical law about all design projects.
- Several examples are qualitative case evidence rather than independently measured outcomes.
- Some downstream results are explicitly client-measured or client-reported and should not be restated as independently verified unless separate evidence exists.
- The unfillable register defines cases where a blank may be correctly diagnosed but cannot be filled because source, stake, focus, or client receptiveness is absent.