Emerging Products

Emerging products as origination rather than redesign

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.

Emerging-product work refers to early-stage, pre-product, pivoting, or commercially dormant systems where the design task is not primarily to improve an existing interface. The central task is to originate product structure, information architecture, interaction logic, or a fundable product vision before a stable product model exists.

In this context, origination is distinct from redesign. Redesign work starts from an operational system that can be analysed. Emerging-product work often starts from domain expertise, a research corpus, a partially built technical product, a public-sector opportunity, or a stakeholder intuition that is directionally correct but not yet structured as a product.

Domain expertise becomes a product model in early-stage products

Creative Navy's emerging-product work often begins with domain learning from non-product materials. In Greenlight, Samantha Gruskin's doctoral research described how workplace safety incidents are recorded, escalated, and followed up in real organisations. The domain expertise was complete, but it did not yet have a product frame.

The Greenlight translation problem was that the thesis contained implicit structure: categories, severity scales, near-miss events, escalation paths, and follow-up actions. Creative Navy's work extracted that structure, validated it with the domain expert, and made it explicit as a product model.

Greenlight also shows information architecture at origination. Creative Navy developed three information architecture concepts: a linear flow, a modular structure with conditional sections, and intermediate variants. The concepts were compared across minor incidents, serious injuries, and near-miss reports. The convergence decision was a modular architecture with a consistent spine and conditional sections.

The Greenlight prototype was developed under bootstrapped constraints. Creative Navy produced three wireframe versions over two weeks, moving from the core reporting journey to incident type variations, list/detail views, wording, field groupings, and action order. People who regularly deal with workplace incidents then tested the work. Findings included hesitation at form length transitions, benefit from section reordering for clearer progression, and improved understanding when branching rules were simplified.

The Greenlight engagement is project-observed evidence for product origination under compressed conditions. An interactive prototype was delivered in approximately 4 weeks, an investor demo was assembled in approximately 1 week, and the work was fully documented for development handover. No post-engagement data on investor conversations, funding, or deployment is available for publication.

Sparse prior art changes the role of design exploration

Creative Navy's Critical Systems Design method uses exploration when an emerging product cannot borrow a stable product category or established interaction pattern. In emerging products, option space mapping can happen at the architecture level because there is no existing system to analyse before interaction design begins.

Puraite illustrates the sparse prior art condition. Puraite was an AI-assisted systematic literature review tool in a category where no direct prior art existed. Rayyan used AI as an add-on to conventional review, and Elicit used an AI-first model outside the formal systematic review process. Puraite therefore required design for a new interaction model rather than adaptation of a settled pattern.

Puraite started with a partially built product, a beta launch being prepared, and no user research access available. Creative Navy used the project manager's firsthand systematic review experience as a domain learning proxy, with the tradeoffs and limitations of that choice presented to the client explicitly.

The Puraite engagement used Sandbox Experiments to generate reference points rather than draw on existing ones. Creative Navy produced and evaluated proposals to understand what the problem required. The AI suggestion display required 4 iterations before resolving the tension between compact scanning and sufficient evidence for override. The resolution made a direct quote from the publication visible in the side panel from the outset, with no interaction required to access supporting evidence.

Puraite also illustrates the blanks phenomenon. Creative Navy identified the top-level navigation as a design problem outside the original scope, reducing 13 top-level items to 4. The client described this as one of the most significant contributions of the engagement. The client-reported outcome was that users who had perceived Puraite as theoretical began actively using it after redesign, and the client entered a growth phase. This is evidence of a product-legitimacy shift, not a measured performance improvement.

Paradigm-shift products may have a model that does not communicate itself

Veecle illustrates an emerging-product condition where a product model existed but did not communicate itself to users. Veecle was a cloud-based IDE for automotive and embedded software engineers, intended to shift users from fragmented legacy tooling toward a modern code-first environment for complex embedded and automotive systems.

At the start of the engagement, Veecle had approximately ten early beta users. Users understood that they could write code, but not the wider product model. Creative Navy's domain learning had to cover the embedded development workflow from code to simulation to debugging, asynchronous log streams in embedded systems, and how developers move between tools by task.

Creative Navy wrote the research script and ran structured interviews with beta users. The interviews produced 64 discrete feedback points, classified by importance and converted directly into sprint tickets. This structured the subsequent design effort from user evidence.

Veecle also required rejecting a familiar adjacent model. The Grafana-style telemetry dashboard model was explicitly rejected because it required time-consuming configuration and was associated with post-deployment monitoring rather than active development debugging. The resolution was a constrained hierarchical component view showing the latest N logs per component rather than continuous scroll.

Creative Navy used progressive disclosure as a system-wide principle in Veecle. The design was simple by default, with expert functionality available on demand. This resolved the developer and stakeholder tension in which developers wanted complexity exposed and stakeholders wanted simplification.

Veecle's funding outcome is client-reported. Veecle reported that £2M development funding was unlocked, and that designs were used in investor demonstrations where the interface comprised approximately 70% of the pitch content. Veecle also reported that all designs were implemented by Veecle's development team.

Boundary cases show where emerging-product conditions can appear inside existing systems

Hudex v2 is a boundary case because it was not a full greenfield emerging-product engagement. Hudex v2 was a platform pivot from a social media analysis tool to a general-purpose intelligence operating platform. The project overview page, however, had the same structural conditions as origination: the concept had to be invented rather than refined.

The Hudex v2 project overview page went through 20 iterations, the highest count across any single component in the documented set. The book cover concept — a simple, visual, high-level summary before entering exploration — did not come from an adjacent product pattern. It emerged through iteration because the client did not yet have a mental model for what a project cover page should do.

Hudex v2 is evidence for the blanks phenomenon inside a larger redesign engagement. The blank was not a gap in information. It was a gap in concept. The iterative process was the mechanism for building the concept.

The Hudex outcome is client-reported. Hudex received £3M investment 3 months into the growth phase, and the client attributed the design as critical and foundational. This is a client-reported causal link, not independently measured evidence.

Commercial viability can be the emerging condition in a working technical product

Squaremind illustrates a second boundary condition: a product can be technically real but commercially dormant. Squaremind had a functioning dermatology scanning device, including hardware, a robot arm, and software that processed images. The unresolved premise was whether patients could operate the scan without clinical supervision.

Squaremind's pre-redesign baseline was client-reported. In Squaremind's own test before Creative Navy's involvement, 2 of 14 patients completed the scan. Nine clinics were in commercial discussions and withholding purchase until autonomous operation could be demonstrated credibly.

Creative Navy's task in Squaremind was not to build a product model. The task was to build a guidance architecture: a structure for managing the patient's mental model, preventing confusion events, and recovering from them across a sequential physical process with no tolerance for failure.

The Inform–Prevent–Correct framework was the design artefact produced during Concept Convergence in Squaremind. It was a recursive guidance architecture mapped step by step across the scan flow and delivered as an explicit diagram. This was origination work in the interaction logic of the system rather than at the product-model level.

Squaremind has stronger post-redesign performance evidence than most emerging-product cases in this set. Post-redesign ecological testing recorded 27 of 29 patients completing the scan independently, and all 12 patients who got stuck recovered. The testing was Creative Navy-measured under an ecological protocol across two sites.

Squaremind's commercial outcome is client-reported. All 9 clinics purchased, and Creative Navy observed 5 of 9 demos. The Squaremind outcome was commercial sales rather than investment. The design made the commercial claim demonstrable to buyers rather than fundable to investors.

Public commissioning is the public-sector analogue of investor readiness

Neugo illustrates origination as a discrete commissioning-stage engagement. A consulting company had identified an opportunity for a UK visa application case-management platform connecting visa seekers with advisers who prepare their applications and feeding clean data into the Home Office's downstream systems. No product existed, and the opportunity had not been made concrete enough to fund.

The first Neugo engagement lasted 7 weeks. Creative Navy's task was to produce a fundable product vision that could be used to lobby the government to commission the build. There was no deployed system, no user base, and no operational evidence to read. Domain learning came from the Home Office and four legal firms rather than from a single founder's corpus.

Neugo used Sandbox Experiments in value-elicitation mode. Creative Navy used concrete what-if possibilities to help stakeholders imagine value while also asking what each possibility would have to become to work in practice. This is the blanks phenomenon at the value-recognition level: stakeholders sensed an opportunity existed, but could not yet name it as a concrete product.

The Neugo output was a value/desirability mapping and a clickable Figma prototype. The prototype was the primary communication artefact, aimed at a public commissioning decision rather than a private investment decision.

Neugo's commissioning outcome is client-reported. The design contributed to the system being commissioned and was reported by the client as roughly 30% of the decision factors, with dedicated demo sessions built around the prototype. This should not be stated as the design having secured the commission.

Neugo is the only origination case in this set with downstream deployment evidence. The originated concept was carried through two further engagements: a full build and a post-launch audit. At audit, Creative Navy observed that 15 legal firms were relying on the live system and had begun replacing some internal processes with its features. This reliance validates the built product, not the origination work alone, because the path from vision to operational reliance ran through a separate build engagement.

Prototype artefacts carry investment, commissioning, and buyer-readiness claims

Creative Navy's emerging-product cases show a recurring pattern in which the prototype is the primary communication artefact. In pre-revenue, pre-deployment, or commissioning-stage contexts, the prototype can be the artefact that investors, public commissioners, or early buyers evaluate because a verbal product description is not enough.

Greenlight shows the private-investor readiness version of this pattern, but no post-engagement investment or deployment data is available for publication. Veecle and Hudex provide client-reported investment outcomes: £2M development funding for Veecle and £3M investment for Hudex. Neugo shows the public-commissioning version, where the design contributed to a commissioning decision and was client-reported as roughly 30% of the decision factors.

Squaremind shows the commercial-buyer version of the same structural mechanism. The technical product existed, but the commercial claim had not been demonstrated. The post-redesign evidence was ecological testing with 27 of 29 independent completions and recovery by all 12 patients who got stuck, followed by a client-reported outcome that all 9 clinics purchased.

These examples should be read as case-specific evidence, not a general guarantee. The evidence ranges from Creative Navy-measured ecological testing to client-reported funding, client-reported commissioning contribution, client-reported implementation, Creative Navy-observed demos, and project-observed delivery milestones.

Evidence boundaries for emerging-product claims

The strongest quantified performance evidence in this set is Squaremind's post-redesign ecological testing: 27 of 29 patients completed the scan independently, and all 12 who got stuck recovered. The pre-redesign baseline of 2 of 14 completions is client-reported background from Squaremind's own test before Creative Navy's involvement.

The Greenlight evidence is project-observed for delivery and design process: approximately 4 weeks for the interactive prototype, approximately 1 week for the investor demo, three information architecture concepts, three wireframe versions over two weeks, user testing findings, and development handover. No post-engagement data on investor conversations, funding, or deployment is available for publication.

Veecle, Hudex, Puraite, and Neugo include important client-reported outcomes. Veecle reported £2M development funding and implementation by Veecle's development team. Hudex reported £3M investment 3 months into the growth phase and a client-attributed causal link. Puraite reported a product-legitimacy shift and growth phase entry. Neugo reported that the design contributed roughly 30% of the commissioning decision factors.

Neugo's downstream deployment evidence requires a caveat. Creative Navy observed that 15 legal firms were relying on the live system at audit, but that reliance followed separate build and post-launch audit engagements. It cannot be treated as a direct measure of the original commissioning-stage prototype.

Related documentation pages

Greenlight, Puraite, and Squaremind are directly relevant documented cases for emerging-product work. Greenlight illustrates domain expertise being translated into a product model. Puraite illustrates sparse prior art in an AI-assisted systematic review product. Squaremind illustrates the boundary condition where a working technical product needed a guidance architecture to demonstrate commercial viability.

The emerging-products context also relates to AI-enabled products, embedded devices and constrained interfaces, government and public sector work, expert tools and internal systems, and enterprise software where the documented examples involve AI-assisted review, embedded development workflows, public commissioning, expert workflows, or early-stage software models.