Glossary

Behavioural governance covers behaviour specification, behaviour enforcement, behaviour documentation, and behaviour verifiability. It focuses on the operational behaviour a product produces in use, not only on the technical integrity of the code.

A behavioural requirement specifies product behaviour at the interface level in a defined situation. It is specific, testable, connected to a rationale, and distinct from functional requirements, user stories, and design principles.

Cognitive load describes the mental effort required to work with a system. In interface design, cognitive load reduction focuses on removing extraneous interface-imposed demands without reducing the capability or domain complexity of the underlying task.

A decision boundary defines where an automated or AI-assisted workflow requires active human judgment. The term distinguishes nominal intervention points from functional interaction designs that make informed human decision-making possible in practice.

Decision quality describes how well an interface supports informed judgment at the moments when judgment matters. It is affected by state accuracy, information completeness, cognitive load, trust calibration, and whether the interface supports judgment rather than replacing it with procedure.

A degraded mode describes continued operation under reduced capability, often caused by a faulted component, lost input, lost connection, or operating condition beyond designed parameters. The term is used to distinguish persistent reduced operation from momentary errors and complete failures.

An error-likely condition describes a predictable interface or operating state that makes user error more likely. The term is used to shift analysis from blaming user behaviour toward identifying structural interface properties that increase error probability.

High-consequence is a consequence-profile term. It describes contexts where interface failure is difficult to undo, whether the harm is immediate or deferred.

Human oversight describes meaningful human review or intervention in system decisions. In design terms, it depends on whether the reviewer has the information, time, cognitive support, and independence needed to exercise judgement at the point of review.

Operational clarity describes whether interface information is organised, weighted, and surfaced so users can act without translating what the system shows into what the task requires. It is especially important in time-pressured and high-consequence contexts, where translation cost can compound.

State visibility describes whether users can read the current condition of a system under real operating conditions. It is especially important in complex systems where multiple components can occupy simultaneous states and transition independently of user action.

Transition clarity is a design property of state changes. It covers whether users detect that a change occurred, understand what changed, and see a display transition that matches the actual system transition.

Trust calibration describes whether users trust system outputs, recommendations, or decisions at a level that matches their actual reliability. In AI interfaces, calibration depends on confidence communication, uncertainty communication, capability and boundary transparency, override parity, and temporal sequencing.

Workflow robustness describes how well a workflow continues to function when users, inputs, sequences, or operating conditions differ from the expected case. A robust workflow handles exceptions as designed workflow states and degrades gracefully when parts of the workflow cannot proceed.

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.

A strategic competitive vector describes the advantage direction revealed when real product tensions are resolved at the level of market forces, user needs, and organisational capability. The concept is used with care because the phrase has other meanings in mathematics and strategy literature.

Constraint respecting is a Creative Navy concept for distinguishing constraints that must be preserved from assumptions, technical debt, or failed implementations that should be redesigned. It applies to legacy interfaces, technical limits, organisational boundaries, process dependencies, regulatory standards, design systems, physical contexts, and multi-party working patterns.

Domain learning is a Creative Navy concept for the work required to understand a domain from within its operational conditions before design decisions are made. It may involve immersive observation, practitioner shadowing, task performance, literature review, client knowledge extraction, AI-system logic clarification, expert-proxy use, or analysis of prior design work, depending on the context.

Inform–Prevent–Correct defines three layers for designing high-consequence sequential interactions: Inform, Prevent, and Correct. Creative Navy introduced the term during the Squaremind engagement and used it to map the patient-operated dermatology scanning flow, including recovery paths after confusion events.

Microtask analysis treats behaviour in complex systems as a space of discrete actions rather than as a designed sequence. It records what users do, when they do it, what each action depends on, and where discovery, understanding, cognitive load, or operational constraints create friction.

Option space mapping is used in Sandbox Experiments to delay convergence until multiple solution directions have been built, examined, and tested against relevant constraints. The output is a map of what each direction reveals about the problem space, not a menu of concepts to choose from.

Organic system building, also referred to as growing systems organically, describes a way of developing designs through exploration, ambiguity, constraint respecting, and simultaneous attention to micro-level user actions and system-level coherence.

Performance in reality is Creative Navy's recurring principle that useful product performance is concrete, condition-dependent, and evidenced under operational constraints rather than assumed from controlled demonstrations or abstract design reasoning.

Progressive specification describes the sequential movement from research to requirements to specifications to system. It treats specificity as something earned through exploration rather than assumed at the start.

Sense Decay describes a system condition in which procedures, specifications, and internal coherence remain intact while the system no longer matches operational reality. The concept is used to explain why a system can appear to work, comply with its design, and still fail its users.

Tension-driven reasoning treats conflict between local optimisation and system coherence as useful evidence. It asks what drives the conflict, what would need to change for the conflict not to exist, and what the tension indicates about product direction.