Sandbox Experiments

Sandbox Experiments in Creative Navy's Critical Systems Design method

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.

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.

Sandbox Experiments is the first exploration phase of Creative Navy's Critical Systems Design method. Its purpose is to identify and explore the critical challenges that will determine whether a system succeeds or fails. These are not feature requests. They are fundamental questions the platform must answer.

Sandbox Experiments begins by identifying 4–8 key platform challenges. These are the points where design decisions have the highest impact. Example questions include how multi-role workflows should coordinate without creating bottlenecks, how complex data can become readable under time pressure, and how a system should behave when constraints conflict.

Sandbox Experiments treats design as research rather than as concept generation followed by research

Creative Navy's Critical Systems Design method uses Sandbox Experiments as design-as-research. The team learns by building, observing how solutions perform against real constraints, and understanding the terrain through making. The phase does not treat research as a separate activity that precedes design.

Option space mapping is central to Sandbox Experiments. For each critical challenge, Creative Navy systematically explores 3–6 variants before converging. Each experiment produces evidence about what works in context, what fails in context, which assumptions do not hold, and which alternatives reveal unexpected problems.

Research is embedded in Sandbox Experiments. Creative Navy may interview users while testing prototypes, observe workflows while exploring alternatives, and benchmark competitors while building its own approaches. Discovery and invention are simultaneous: prototypes can expose the current reality and create alternative realities that stakeholders and users can react to.

Sandbox Experiments produces tested approaches before product-frame commitment

Sandbox Experiments produces a library of tested approaches for each key challenge. It also produces evidence about what works and fails, a better understanding of the problem terrain, and clarity about which problems are genuinely hard rather than only appearing hard at the start.

The phase protects against early commitment to weak product frames. In Creative Navy's Critical Systems Design method, this protection comes from testing alternative frames before the system direction is fixed. The goal is to reduce the risk of costly pivots when initial assumptions fail under real use.

Sandbox Experiments can vary in duration. Focused problems may take 2–3 weeks. Complex platforms may take 2–3 months. The documented examples include a 3-month UNICEF Sandbox Experiments phase across two organisational tiers and a 7-week Neugo Sandbox-only engagement that produced a fundable vision rather than proceeding immediately to full system design.

Unstructured situated observation is a valid Sandbox Experiments instrument when measurement would add noise

Creative Navy's Critical Systems Design method treats deliberately unstructured observation as a valid Sandbox Experiments instrument when a system is performing so poorly that systematic measurement would produce noise rather than signal. In this condition, there may be no baseline worth measuring.

The goal of unstructured situated observation is to understand the physical context, the failure patterns, and the terrain of the problem well enough to frame design work. It is not to produce a formal dataset. Choosing unstructured observation is a methodological decision rather than a methodological shortcut.

Applying structured measurement to a broken system can create the false impression of a measured baseline while missing the situated understanding that informs direction. In Sandbox Experiments, the research instrument is selected to fit the terrain rather than to satisfy a fixed research template.

Squaremind used unstructured observation to understand a failing patient interface

In the Squaremind dermatology scanning device example, Creative Navy travelled to the client in France and conducted 4 observation sessions of the existing patient interface in use. The decision not to measure was deliberate and explicit.

A prior internal test conducted by the client had recorded 2 completions from 14 users. The completion rate was so low that a structured measurement of the existing interface would have added little useful design information for the next design direction.

Creative Navy-observed evidence from the field visits produced situated understanding instead. The observation showed the physical relationship between the patient and the screen, how confusion appeared in body movement before abandonment, the scan sequence and its physical demands, and the absence of any guidance structure when a step was unclear.

This Sandbox Experiments evidence base supported the Inform–Prevent–Correct structure introduced in Concept Convergence. The observation found the terrain; the later framework organised it into a design architecture.

Prototypes can diagnose rationale decay inside an organisation

Creative Navy's Critical Systems Design method uses Sandbox Experiments not only to test interface ideas but also to diagnose what an organisation cannot see about itself. When a system has ossified over years, its requirements can mix genuine operational necessities with requirements sustained only by institutional habit.

This condition is described as rationale decay. Conventional requirements-gathering may not separate necessary requirements from decayed requirements, because asking what the system needs to do often returns the existing list of requirements, including the habits.

A prototype changes the question. When stakeholders are confronted with a concrete alternative workflow, they must explain why the existing requirement exists. A requirement that cannot be justified in terms of governance, decision-making, or operational value becomes visible as decayed.

In this form of Sandbox Experiments, the prototype is a diagnostic instrument. It makes implicit organisational assumptions explicit by forcing the organisation to react to a specific, buildable alternative instead of to an abstract question.

UNICEF used prototype-driven Sandbox Experiments to interrogate an ossified reporting process

In the UNICEF internal planning, approval, and reporting tool example, the central organisation knew the system needed to change but had no clear requirements for how to change it. Its reporting processes had not been questioned in years.

The central organisation initially framed the problem as low-quality submissions caused by local-office reluctance and an inconvenient interface. Research across four intensively engaged local offices indicated a different problem: a cross-tier comprehension gap. Local offices did not understand why their input was needed or how it was used, and the interface communicated institutional indifference rather than purpose.

Over a 3-month Sandbox Experiments phase, Creative Navy produced 26 prototypes reviewed by 56 stakeholders across both organisational tiers. The prototypes were not design proposals to be approved. They were instruments for surfacing and testing assumptions.

Presenting concrete alternative workflows forced stakeholders to explain how reporting worked and why it worked that way. In several cases, long-standing mandatory requirements could not be convincingly justified and were removed, consolidated, or substantially simplified.

The Sandbox Experiments phase also produced shared understanding between headquarters and local offices by having both tiers react to the same concrete alternatives. Standards agreed during this phase were embedded structurally in the redesigned system, reducing ambiguities before users began entering data.

The documented downstream outcome was a client-measured 45% reduction in compliance issues nine months post-rollout. The documented account traces this result to Sandbox work that resolved the mental-model mismatch and rationalised requirements before production screens were built.

Sandbox Experiments can elicit value when no product exists yet

Creative Navy's Critical Systems Design method can use Sandbox Experiments at the opposite end of the product lifecycle: not to interrogate an ossified system, but to elicit value for a system that has not yet been built. In this condition, stakeholders may sense an opportunity but be unable to articulate what the proposed system would be worth.

When there is no operational system, no existing user base, and no baseline, the Sandbox runs predominantly on the invention side. The instrument is a paired prompt: what if the system did a specific thing, and how would it have to do that thing for it to work in the stakeholder's real operating conditions.

The first half of the prompt provokes stakeholders into recognising value they had not named. The second half keeps that imagined value connected to real practice rather than drifting into wish-listing. Together, the two prompts convert a directionally felt but blank opportunity into a more defensible articulation of what the system could be and how valuable it would be.

This is the blanks phenomenon operating at the level of value recognition. The stakeholder intuition that an opportunity exists may be correct, but it lacks specifics. The prototype becomes the instrument that fills the blank with substance stakeholders could not have produced by being asked directly.

Neugo used Sandbox Experiments to make an unbuilt platform legible and fundable

In the Neugo UK visa application case-management platform example, the first engagement was not a build. A consulting company had identified an opportunity for a platform connecting visa seekers with advisers who prepare applications, feeding clean data into the Home Office's downstream border-force systems.

The purpose of the 7-week engagement was to produce a prototype that could be used in a process to lobby the government to commission the system and to give backers something concrete enough to commit to. There was no existing product to interrogate.

Creative Navy ran Sandbox Experiments with the Home Office and four legal firms in value-elicitation mode. Instead of asking what the system should do, Creative Navy provoked stakeholders with concrete possibilities and asked what each possibility would need to become for it to work in their practice.

The output was deliberately visionary and conceptual: a value/desirability mapping and a clickable Figma prototype. The deliverable was not intended to specify a build. Its role was to make the system's value legible and fundable.

Client-reported evidence indicates that the engagement contributed to the system being commissioned. Stakeholders reported that the design accounted for roughly 30% of the decision factors and that dedicated demo sessions were built around the prototype. The full five-phase build followed in a separate engagement; the value-elicitation work belongs to the Sandbox phase of the first engagement.

Sandbox Experiments matches research instruments to the terrain

Creative Navy's Critical Systems Design method does not treat the different Sandbox Experiments instruments as being in tension. The instrument is chosen according to the terrain.

Squaremind shows Sandbox Experiments as situated observation when there is no useful baseline to measure. UNICEF shows Sandbox Experiments as structured prototype-driven interrogation when the problem is an organisation's inability to see decayed requirements. Neugo shows Sandbox Experiments as prototype-driven value elicitation when no product exists and stakeholders cannot yet articulate the value the proposed system would create.

All three forms are design-as-research. In one case, Creative Navy learns by watching a failing system. In another, Creative Navy learns by building alternatives that force articulation of an existing process. In the third, Creative Navy learns by building possibilities that force articulation of a future process.

Triangulation in Sandbox Experiments searches for discrepancies rather than only common patterns

Creative Navy's Critical Systems Design method uses triangulation in Sandbox Experiments as detective work. Each research method is used against the others to find discrepancies and hidden nuances, not only to confirm common patterns.

A feature may appear important to stakeholders because it saves time, while users may describe the same feature as important because mistakes take a long time to resolve. These statements sound similar but point to a different design problem. The underlying issue may be error resolution time rather than the feature itself.

That nuance can then be taken back to stakeholders, compared with competitive analysis, and tested against technical constraints. Each source interrogates the others.

The UNICEF engagement shows the same detective work at the organisational level. Stakeholders said the problem was that users found the interface cumbersome. Research indicated that users did not understand why the system existed. These are adjacent observations but they imply different design work: usability improvement in the first case, meaning-making and cross-tier communication in the second.

Sandbox Experiments relies on active pursuit rather than checklist research

Creative Navy's Critical Systems Design method distinguishes between performing standard research deliverables and pursuing them in a way that reveals useful information. Stakeholder interviews, user research, and competitive analysis can produce different results depending on how actively they are pursued.

Sandbox Experiments may require persisting until the most informative users are found, returning to a user after reflecting on an earlier conversation, asking a difficult question, gaining access to software that is not publicly available for benchmarking, or asking developers to reconsider constraints when a changed perspective may create value.

High-value Sandbox Experiments activities include user observation, having users teach Creative Navy how to use the system, and team members attempting to do the job as a user. These activities can reveal silent patterns, conscious mental models, how users believe a system should work, how challenges change with experience, emotional weighting, and what users would or would not be capable of if the system were different.

Context of use is treated as part of the design terrain. A tool is embedded in context, and many systems become more valuable when they are better integrated with that context.

Users may also be more open with a third party than with their own provider. In the UNICEF example, local offices were more candid with Creative Navy about experiencing central requirements as performative bureaucracy than they had been within internal reporting lines. That third-party position surfaced the comprehension gap that internal channels had not surfaced.

Architectural iteration begins during Sandbox Experiments

Creative Navy's Critical Systems Design method begins architecture deliverables during Sandbox Experiments. Iteration 1 is described as a logic-first baseline. Iteration 2 is described as opinionated extremes.

These early architecture iterations mean that Sandbox Experiments is not limited to research findings or prototype screens. It also begins shaping the system logic that later phases refine. The detailed account of all four architecture iterations belongs with Iterative System Building.

Boundaries of Sandbox Experiments

Sandbox Experiments does not aim to produce the final product design. It aims to answer the critical platform questions that must be understood before convergence.

Sandbox Experiments does not require one fixed research protocol. The correct instrument may be unstructured observation, prototype-driven organisational diagnosis, value elicitation, user teaching sessions, competitor benchmarking, or another research activity embedded in making.

Sandbox Experiments does not treat what users or stakeholders say as a direct requirements list. It compares stated needs, observed behaviour, competitive patterns, technical constraints, and prototype reactions to identify discrepancies and hidden constraints.

Sandbox Experiments does not separate discovery from invention. In Creative Navy's Critical Systems Design method, prototypes are not only representations of existing reality. They can create alternative realities that make assumptions, requirements, and value visible.