Greenlight

Greenlight as an early-stage workplace safety product engagement

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.

Greenlight was a London workplace safety startup founded by Samantha Gruskin, a doctoral researcher whose thesis described how incidents are recorded, escalated and followed up in real organisations. Samantha Gruskin brought deep workplace safety domain expertise, but the engagement began before Greenlight had a product frame for that expertise.

Creative Navy's work with Greenlight ran for approximately five weeks. The engagement produced an interactive prototype for investor and founder conversations, documented information architecture, a UI direction, and a roadmap of build sequencing decisions.

The Greenlight engagement was pre-product and pre-revenue. There were no operational users, no deployed system, and no performance data from real use. The case evidence is therefore evidence of product translation, early product structuring, and artefact production under bootstrapped constraints, not evidence of operational performance improvement.

Academic incident-reporting research converted into a product model

Creative Navy's design work on Greenlight began with domain learning from Samantha Gruskin's doctoral thesis, supporting articles, and presentations. Creative Navy's Critical Systems Design method was applied to extract entities, relationships, and dependencies from the academic corpus and convert them into a product-ready conceptual model.

The product model described how workplace incidents move from capture through assessment, escalation, and follow-up. Creative Navy-recorded engagement evidence describes the output as a clear model of what needed to be captured, in which order, and with what dependencies.

This translation replaced a generic reporting tool frame with a domain-specific product model. The available case evidence is specific about the kinds of structures extracted from the research: categories, severity scales, near-miss events, follow-up actions, conditional dependencies, and the sequence in which incident information had to be collected.

Option space mapping across three information architecture concepts

Creative Navy's Critical Systems Design method used option space mapping to explore three information architecture concepts for Greenlight: a linear flow, a modular approach with context-sensitive blocks, and intermediate variants. The exploration used simple flow diagrams to compare behaviour across incident types, including minor incidents, serious injuries, and near-miss reports.

Creative Navy selected a modular architecture with a consistent spine and conditional sections after tension-driven reasoning across the incident-type trade-offs. The selection was made against how different incident types behaved in the workflow, rather than against visual preference.

The Greenlight case is a specific example of option space mapping at information architecture level. The available case evidence records that three architecture concepts were explored before convergence and that the final architecture was chosen because it better handled variation across incident types.

Iterative System Building refined three wireframe versions over two weeks

Creative Navy's Critical Systems Design method moved Greenlight from information architecture convergence into Iterative System Building through three successive wireframe versions over two weeks. Each version increased fidelity and narrowed the unresolved product decisions.

The first wireframe pass focused on the core reporting journey. The second wireframe pass added incident type variations, list views, and detail views. The third wireframe pass refined wording, field groupings, and action order.

Creative Navy-observed testing evidence came from a round of testing with people who regularly dealt with workplace incidents. The documented findings were consistent: participants hesitated at form length transitions, benefited from reordering sections for clearer progression, and reduced backtracking when evidence attachments and contextual details were grouped. Simplified branching rules improved user understanding of conditional fields.

The participant count and participant roles are not specified in the available case evidence. The testing evidence should therefore be treated as credible but limited qualitative evidence, not as a quantified usability result.

Product strategy staging under bootstrapped constraints

Creative Navy's Critical Systems Design method included product strategy staging discussions for Greenlight during Concept Convergence. These sessions addressed whether Greenlight should build a single core flow for pilot organisations first or add analytics earlier, and whether partnerships with safety consultancies and training providers should shape the early roadmap.

The output was a simple build sequence that distinguished what to build first, what to postpone, and what each decision meant for cost, timeline, and risk. This is evidence of strategy work alongside UX work, but the evidence is limited to documented engagement activity rather than post-launch commercial measurement.

Constraint respecting was important in the Greenlight case because the work was shaped by bootstrapped budget constraints, mobile-first scope, and the capacity of a solo founder. Creative Navy's product decisions were made within those constraints rather than against an unconstrained product vision.

Implementation Partnership deliverables for founder, investor, and development conversations

Creative Navy's Critical Systems Design method reached Implementation Partnership in the Greenlight engagement through a documented prototype package, UI direction work, and development handover material. The interactive prototype was delivered in approximately four weeks, and the investor demo was assembled in approximately one week.

The deliverables gave Samantha Gruskin concrete artefacts that were not available from the thesis alone. She could explain the product architecture to developers, discuss scope and staging concretely, and walk investors or partners through a working scenario.

The investor-facing value of the prototype was specific: an investor or partner could see the incident reporting sequence, conditional sections, and product behaviour, rather than only reading the underlying academic research. The available case evidence does not independently measure the commercial effect of those conversations.

Longitudinal preservation after acquisition

Approximately three years after the original Greenlight engagement, the case became part of Creative Navy's longitudinal evidence set as a third-party-preservation case through acquisition. With an investor on board, Samantha Gruskin built out the product, launched it, and later sold it to a larger business.

The later evidence is Creative Navy-observed. Approximately three years after the original engagement, the larger business hired Creative Navy for an unrelated application. At that point, the Greenlight system was still live in the acquirer's portfolio and was maintained by the acquirer's own team as one of its apps.

This longitudinal evidence should be treated as third-party preservation through acquisition. It is evidence that a party with no relationship to Creative Navy kept the Greenlight system in service. It is not evidence of independent evolution, and it is not a same-system return engagement, because Creative Navy did not return to work on the Greenlight system itself.

The identity of the acquirer is not named in this page. The available evidence permits reference to a larger business, but not to the acquirer's identity or related specifics.

Evidence boundaries for the Greenlight case

The Greenlight case is smaller and earlier-stage than most Creative Navy engagements. It demonstrates translation of academic domain expertise into a product structure, early information architecture reasoning, iterative prototype convergence, and founder capability transfer under bootstrapped constraints.

The Greenlight case does not demonstrate operational performance improvement, measurable deployed user outcomes, enterprise or regulated-system complexity, or the high-consequence domain work Creative Navy is primarily known for. There were no operational users and no deployed system during the engagement.

The outcome evidence is client-reported or Creative Navy-observed. The documented outcomes include an interactive prototype delivered in approximately four weeks, an investor demo assembled in approximately one week, development handover documentation, and two UI directions for branding exploration. No independent measurement is available for these outcomes.