Triopsis Workforce Management SaaS

Triopsis workforce management SaaS for utilities and road maintenance operations

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.

Triopsis was a workforce management SaaS platform for utilities and road maintenance companies. Users planned thousands of interventions per week and coordinated crews and equipment across wide areas.

The Triopsis engagement covered a 9-month redesign and a 2-year Implementation Partnership after delivery. The Creative Navy team included a UX designer, UI designer, interaction designer, project manager, product owner and researcher. At the start of the engagement, Triopsis was approximately a 10-person founder-led organisation based in London, UK.

The product already had a strong backend and had reached profitability, but growth had stalled. New customers found the interface difficult to understand, support teams answered basic questions, and sales calls became explanations of the user interface. The case evidence describes the legacy interface structure as the barrier at the point where the product needed to scale.

Three role models had to operate in one shared interface

Triopsis supported three primary roles with different operating conditions and different mental models. Schedulers needed speed, batch actions and team availability. Operations managers needed exception scanning and risk visibility across broader time horizons. Field technicians needed task detail, safety measures and confirmations that tolerated gloves, sunlight, interruptions and time pressure.

The previous interface had accumulated inconsistencies over years of development by developers and a graphic designer without a central UX framework. Modules behaved differently, and users had to scan multiple screens to make a single decision. Under peak load, this produced stress and repeated checking.

The governance environment also shaped the interface problem. Founders, developers, sales, support and key clients had competing expectations. Without a UX framework to arbitrate between them, module-level decisions remained inconsistent. This is the case evidence behind the documented use of the blanks phenomenon: the client had strong domain knowledge, but the system lacked a coherent interaction model that could turn that knowledge into consistent interface decisions.

Creative Navy's evidence base combined stakeholder, user, field, research and benchmarking inputs

Creative Navy's design work for Triopsis used multi-perspective synthesis across five evidence sources. The case records 5 stakeholder interviews, 43 individual user interviews across 21 participants, 3 in-situ observation sessions, behavioural science and ergonomics research, and benchmarking.

The stakeholder interviews surfaced competing organisational priorities: throughput, stability, safety and demo performance. The user interviews showed that roles experienced the same interface differently. Schedulers described speed problems, operations managers described exception visibility problems, and technicians described clarity and confirmation problems.

The in-situ observation sessions added behaviour that interviews did not capture. Creative Navy observed schedulers handling weather incidents, conflicting locations, overlapping jobs and sudden crew shortages. Hesitation points, repeated checking and error patterns such as incorrect sequencing and duplicate assignments emerged from observation rather than self-report.

Behavioural science and ergonomics research on colour semantics, cognitive load and decision fatigue was used to interpret the observed patterns. Benchmarking provided industry context for enterprise SaaS workflows and highlighted gaps in the legacy interface relative to competitive products.

Microtask analysis mapped 47 microtasks across 3 personas

Creative Navy-recorded microtask analysis mapped 47 microtasks across 3 primary personas in the Triopsis case. For each microtask, Creative Navy recorded when it was performed, ease of discovery, ease of understanding, what the user needed to perform it, issues, opportunities, desired outcome, pain points, patterns, frequency, cognitive load and dependencies.

The microtask analysis made role conflict visible. A layout that helped schedulers could hide signals operations managers depended on. A structure that reassured technicians could obscure timing data for planners. The case evidence treats these conflicts not as simple design errors, but as structural tensions in the organisation made visible through the microtask map.

Creative Navy's Critical Systems Design method used tension-driven reasoning to examine what produced the conflicts. The documented central tension was that three roles with incompatible mental models had to use one shared interface. The design task was to make the interface clear for each role without compromising clarity for the others.

Critical Systems Design phases used in the Triopsis engagement

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 Triopsis engagement, Sandbox Experiments included the stakeholder interviews, user interviews, in-situ observation, benchmarking, 47-microtask mapping, first usability testing rounds and initial workflow conflict mapping.

Concept Convergence resolved the multi-role tension into unified interface logic. It also identified the documented competitive vector: multi-role clarity at enterprise scale, with consistency between demo conditions and field use.

Iterative System Building included 4 rounds of usability testing with prototypes. Creative Navy examined scanning behaviour, hesitation points and error patterns at each round. The field technician compliance component and predictive conflict indicator design were also iterated in this phase.

Organizational Integration delivered the 68-component design system with more than 200 documented states. The component inventory covered 15 workflow types and documented states, conditions, transitions and conditional workflows for exceptions.

Implementation Partnership continued for 2 full years after delivery. Creative Navy clarified design decisions on request, adjusted components for new features and helped maintain consistency as the product grew.

Constraint respecting shaped the redesign around the legacy system and development team

Creative Navy's Critical Systems Design method treated the existing Triopsis interface as the starting terrain rather than a clean slate. The previous interface's inconsistencies were mapped before redesign decisions were made, and 47 microtasks were analysed against the existing system.

Constraint respecting also applied to implementation. Developer sessions during implementation allowed constraints to surface early. The component inventory documented states, conditions, transitions and conditional workflows for exceptions so that developers had a coherent mental model to implement from.

The delivered design system had 68 components and more than 200 documented states across 15 workflow types. In the Triopsis case, organic system building meant the design system acted as reasoning documentation and a navigation map for the product, not only as a component library.

The case evidence records organisational capability transfer as a project output. The transferred resources were judgment about workflow optimisation in professional software, shared product intuition about how multi-role systems should behave, and reasoning capability that allowed Triopsis to extend the interface without fragmenting it.

State visibility treated exceptions as normal workflow states

Creative Navy's design work for Triopsis addressed state visibility and fault handling by treating operational disruption as part of normal workflow. Weather incidents, conflicting locations, overlapping jobs and crew shortages were not treated as edge cases requiring workarounds.

Predictive conflict indicators surfaced scheduling conflicts earlier, before users encountered them mid-task under peak load. AI-assisted sequencing supported planners during peak load. Delayed jobs, partial completions and weather disruption were designed as workflow states the interface could adapt to without forcing long corrective paths.

The field technician compliance component surfaced required steps at the right moment, highlighted dependencies, showed safety requirements and guided confirmations without overwhelming the user. In testing with technicians, this reduced uncertainty at task start and helped ensure procedures were followed consistently.

Outcome evidence distinguishes field-measured productivity from client-reported operating data

The strongest quantitative productivity outcomes in the Triopsis case are field-measured through product analytics from real users in the live system. Product analytics recorded 62% faster job discovery, 83% faster job sequence optimisation and 58% faster weekly planning.

The onboarding change is client-reported operational data. Before the redesign, new users required a 1-hour remote training session. After the redesign, onboarding used an optional 15-minute video, and approximately 90% of users began using the system without live instruction.

The support-ticket change is client-reported operational data. “How can I” questions fell to approximately 5% of previous volume. “Can the system do X” questions dropped to approximately 60% of previous volume. The case evidence distinguishes these two question types: “how can I” questions indicate discoverability failure, while “can the system do X” questions indicate capability communication failure.

The commercial outcomes are client-reported by the CEO and not independently verified. Sales conversions multiplied by four, and Triopsis began winning clients 4–5 times larger than before. The case evidence frames this as a commercial result Triopsis was able to act on after the interface change, not as an independently verified causal claim.

Tender performance is client-reported from formal tender evaluation documents. Tender scores improved by 10–20% attributable to design quality, depending on how design or UX criteria were weighted in each tender.

Longitudinal evidence records independent evolution after the original engagement

Triopsis returned to Creative Navy approximately 3 years after the original engagement. The longitudinal evidence is stronger than independent operation alone because Triopsis's own team extended the product and built a spin-off product for datacentre maintenance without Creative Navy involvement during the gap.

The documented claim is independent evolution: the system was not only still running, but had been extended coherently enough by Triopsis's own team to support a second product. This is client-reported evidence and distinct from the field-measured productivity outcomes.

The CEO, Andy Hutt, is recorded as saying, “you were the best investment I ever made in my business life.” This is an attributable client-reported quote and is not independently verified performance evidence.

Triopsis later re-engaged Creative Navy on an ongoing strategic retainer. The client's stated framing for the retainer was not simply to produce designs, but to become more embedded in the business, help Triopsis understand customers better and anticipate how customer needs change. The client's stated AI rationale was that AI lowers the difficulty of competitors evolving and shipping new features, so Triopsis judged that designing and coding well was less defensible as an advantage than before.

Evidence boundaries in the Triopsis case

The Triopsis case has different evidence strengths for different claims. Productivity figures are field-measured through product analytics from real users in the live system. Research activities, microtask mapping, prototype testing rounds, component counts and phase activities are Creative Navy-recorded engagement evidence.

Onboarding, support ticket reduction, sales conversions, client size increase, tender score improvement, independent evolution, the CEO quote, the strategic retainer framing and the AI rationale are client-reported. The commercial and longitudinal claims are useful evidence, but they should not be treated as independently verified outcome measurement.

The case evidence records that multiple navigation directions were explored and tested before convergence, but it does not enumerate the six navigation directions in the same detail as another documented case. The available Triopsis evidence is sufficient to establish option space mapping, but not to describe each structural direction publicly.