Chemical Watch

Chemical Watch as an enterprise compliance intelligence platform

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.

Chemical Watch was a UK-based information service covering global chemical risk and regulation. At the time of the engagement, it published specialist news, analysis, and regulatory resources for compliance professionals working across REACH, SVHC, GHS/CLP, TSCA, and chemical regulation across dozens of national jurisdictions including China, South Korea, Japan, Turkey, and key EU member states.

The platform served approximately 50,500 users as of mid-2018. The user base was made up predominantly of regulatory compliance managers, product safety specialists, product stewards, and sustainability managers at upstream chemical manufacturers, midstream formulators, and downstream product companies. Users were geographically concentrated in Western Europe (44%), North America (26%), and Asia (18%).

The system being designed was a change from an existing website centred on news publication into a compliance intelligence platform. The new platform combined four core areas: a news feed and article browsing experience, a My Substances registry, a lens-view for user-configurable filtered feeds, and settings and preferences for jurisdiction and sector personalisation.

Commercial strategy translated into a product design problem

Chemical Watch's business challenge was to translate editorial strength into platform features that could support a substantial subscription price increase. The planned increase was a tripling of the subscription price, and the aim was to support movement into enterprise accounts.

The design problem was not simply to improve access to content. Chemical Watch already had differentiated editorial coverage of regulatory change across the global chemical compliance landscape. The work was to turn that editorial advantage into daily operational value for compliance professionals: personalised tracking, repeatable views, and practical orientation around substances, sectors, and jurisdictions.

The engagement also had a commercially fixed tier structure. Chemical Watch used Silver, Gold, and Platinum subscription tiers before design began. Creative Navy's design work had to make lower tiers feel like coherent versions of the same product while making premium capabilities feel like meaningful extensions, not empty withheld areas.

Sandbox Experiments separated user reality from aspirational personas

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.

In the Chemical Watch case, Sandbox Experiments exposed a gap between the client's existing personas and users' actual working conditions. Chemical Watch had personas for roles including a senior director of global product safety and compliance, a regulatory affairs specialist in Asia Pacific, and a downstream product safety and sustainability officer. The personas were directionally grounded in role and workflow, but Creative Navy-observed discovery found that they also contained assumptions about what Chemical Watch wanted users to do.

This was an instance of the blanks phenomenon: the persona structure existed, but missing operational detail had been filled with client aspiration rather than observed user need. Creative Navy's domain learning focused on the operational reality of chemical compliance, including REACH obligations, SVHC tracking, multi-jurisdiction management, and the practical problem of substance inventory uncertainty.

Substance inventory uncertainty shaped the My Substances registry

Creative Navy-observed discovery found that compliance professionals often could not produce a clean and accurate list of the substances their organisation worked with. The documented scenario included inherited inventory after acquisition, ambiguous supplier data, and colloquial material names that could cover multiple actual substances.

This finding made a complete upfront profile setup unworkable. A user could not reliably commit to a full substance register during onboarding if the organisation's actual inventory was partial, ambiguous, or distributed across inherited records.

Creative Navy's design response was a gradual accrual model. On first use, a user could see the full news feed and receive progressive prompts such as organisation location or content-type exclusions. The profile became richer over time, rather than requiring a high-confidence substance inventory before the user could access the product.

The My Substances area was then built around “new since last visit” logic. When a user opened a tracked substance, the view showed regulatory news, available guides, guide update indicators, and related resources. The backend handled multiple substance names and CAS numbers, while the interface surfaced the primary name and handled aliases behind the scenes.

Chronological news review was treated as professional practice

Creative Navy-observed exploration showed that regulatory news did not behave like general content. A Pinterest-style non-chronological feed was one of four news feed variants explored, and it failed because it disrupted the professional practice of staying current.

Compliance professionals needed chronological orientation. Users needed to understand what was new since the last review and whether recent obligations or signals had been covered. Breaking chronological order created anxiety because users could not distinguish recency from algorithmic surfacing.

The selected news feed design made temporal orientation visible at a glance. It supported review by today, week, or period while allowing filtering by substance, jurisdiction, and sector without breaking chronological structure.

Lens-view became a persistent workspace rather than a filter

Creative Navy-observed Sandbox Experiments showed that the lens-view was a latent need rather than a stated user request. Chemical Watch had an intuition that users would filter feeds to match their responsibilities, but exploration showed that these filters would be reused as persistent views.

The design implication was that a lens was not a one-time search filter. A user responsible for South Korean food contact regulation needed a named view that could be revisited each week as part of ongoing work.

The lens-view created a difficult Concept Convergence problem because it displayed articles in a feed, like the main news area, while needing to feel like a distinct configured workspace. Creative Navy's design response gave the lens a distinct navigational home, visible and editable configuration metadata, and naming conventions that let users treat lenses as continuing projects.

Semantic tagging constraints shaped what personalisation could support

Creative Navy's design work was coordinated with the semantic fingerprinting technology partner responsible for content tagging infrastructure. Creative Navy-recorded work included two workshops with the technology partner and design reviews approximately every two weeks.

The purpose of this coordination was constraint respecting. Chemical Watch had expectations for semantic fingerprinting, but Creative Navy-observed technical review found a gap between hoped-for capability and what the backend could reliably support.

The lens concept depended on reliable tagging by substance, jurisdiction, and sector. Creative Navy adjusted design features against the tagging system's actual capabilities rather than designing personalisation that could not be implemented reliably.

Concept Convergence separated premium marketing presentation from operational clarity

Creative Navy-observed Concept Convergence identified a central tension: Chemical Watch wanted a premium interface presentation, while users needed operational clarity for compliance work. The commercial team wanted the platform to “look like Apple”, but the interface patterns that looked more premium in sales material also risked adding cognitive load during regulatory judgment.

Creative Navy used tension-driven reasoning to separate two different needs. Buyers and internal stakeholders needed a clear value presentation. Users needed a production interface that made it easy to assess what was new, what required action, and what could be deferred.

The resolution was not to blend the two requirements into one compromised interface. Creative Navy designed the production UX for operational clarity and ran a separate marketing design workstream for idealised screenshots and demo videos used on the website and in sales decks.

Option space mapping covered news, substances, and jurisdictions

Creative Navy-recorded option space mapping explored four variants for the news feed, three variants for the substance register, and six variants for jurisdiction integration. The six jurisdiction variants reflected the difficulty of serving users whose compliance responsibilities crossed substance categories and geographic boundaries at the same time.

The most instructive rejected option was the non-chronological news feed. Its failure clarified that Chemical Watch's users were not primarily browsing for interesting content. They were maintaining regulatory awareness under professional responsibility.

The final design direction aligned Chemical Watch's editorial intelligence with proactive compliance awareness. The lens-view, substance tracking, “new since last visit” logic, and sector and jurisdiction overview pages served advance awareness rather than only reactive task completion.

Organizational Integration used spaced workshops during implementation

Creative Navy-recorded Organizational Integration work included three workshops during implementation, spaced eight weeks apart. The spacing gave developers, marketing, editorial, and sales time to apply what they had learned, gather questions from implementation, and bring those questions to the next session.

The core product, CTO, and design manager at Chemical Watch were embedded in weekly working sessions and absorbed the design reasoning continuously. Wider stakeholder groups had different relationships to the design: editorial needed to understand how content would be surfaced and structured, sales needed to understand the basis for the higher price point, and developers needed to implement product logic they had not participated in creating.

The workshops were shaped around those differences. The evidence indicates that understanding grew alongside the product rather than being front-loaded before implementation work existed.

Implementation Partnership produced five support requests in six months

Creative Navy-recorded Implementation Partnership evidence shows five support requests during the six months after design system handover. Two of the five requests were asset-related: additional icons and different image format specifications.

The documented interpretation is that the design system and documentation resolved enough conceptual questions that implementation decisions were mostly mechanical rather than interpretive. This is Creative Navy-recorded engagement evidence, not an independently measured maintenance outcome.

The overall engagement ran for six months from first meeting to design system handover.

Client-reported commercial outcomes and evidence limits

Client-reported evidence states that Chemical Watch successfully tripled its subscription price following the platform redesign. The price increase was planned before the engagement; Creative Navy did not originate the pricing strategy. The supported claim is that Creative Navy designed the platform features and user experience that made the value case for tripling the price achievable.

Client-reported evidence also states that Chemical Watch was acquired one year after platform release at a 24x EBITDA multiple. The documented causal chain is calibrated: design supported feature adoption; feature adoption supported commercial proof of value; the higher price point supported revenue and EBITDA; the resulting business performance contributed to the acquisition valuation. The design did not cause the acquisition.

A major enterprise technology customer reportedly said in a client meeting that the platform had the best usability they had seen in a while. This evidence is client-reported and not in writing, so it should be treated as anecdotal reported speech rather than a verified testimonial.

Enhesa lineage and observed design-system durability

The Chemical Watch engagement is the first part of a multi-year lineage. Chemical Watch was acquired by Enhesa approximately one year after the platform launched. Roughly four to five years after the original engagement, Enhesa re-engaged Creative Navy for further work on the same platform.

The strongest durability signal is that the acquirer preserved the design system Creative Navy had built. The only branding change recorded was two colours; the design system was otherwise kept intact, and later Creative Navy work for Enhesa was carried out within that earlier system.

This is observed and client-reported durability evidence, not a measured performance result. It supports a claim of same-system durability through an acquisition. It does not support a claim that the client's own team independently evolved the system without Creative Navy, because the client returned to Creative Navy for later work.

Evidence boundaries for the Chemical Watch case

The Chemical Watch case contains a mix of Creative Navy-recorded engagement facts, Creative Navy-observed design findings, client-reported commercial outcomes, and anecdotal reported speech.

The subscription price tripling is client-reported as a direct outcome after platform launch. The 24x EBITDA exit multiple is client-reported, including the client's account of how the platform and price increase contributed to valuation. The enterprise technology customer remark is client-reported, was made in a meeting, and is not in writing.

The variant counts, workshop cadence, technology-partner review cadence, support request volume, and six-month engagement duration are Creative Navy-recorded engagement facts. They should not be treated as independently measured user or business outcomes.

Related documentation

The Chemical Watch case is directly related to the Enterprise Software context because the work concerned a subscription platform for professional compliance users. It is also related to Expert Tools and Internal Systems and Regulated Products because the system supported specialist regulatory work across substances, sectors, and jurisdictions.

The Enhesa case is the downstream case in the same product lineage. The longitudinal durability evidence is relevant because the Chemical Watch design system was preserved through acquisition and later constrained subsequent work. The positioning-through-interface-quality outcome is relevant because the redesign supported a higher subscription price by changing how the product's operational value was expressed in the interface.