A design system purpose built for industrial diagnostics, not a UI kit, but a framework for moving operators from raw data to confident action.
Following its separation from Asset 360, Atonix focused on monitoring and diagnostics for industrial assets. As the platform evolved toward predictive intelligence, the existing UX could not keep pace.
Monitoring provided real time visibility. Diagnostics delivered predictive insight and recommended action. But the two lived in disconnected experiences. Operators had to carry context manually between them at exactly the moment they could least afford the friction.
DesignOI was built to close that gap: a system architected around the cognitive demands of industrial diagnostics rather than adapted from general purpose UI patterns.
Each capability was designed in isolation. The seams showed exactly where they mattered most.
| Workflow | What existed | What was broken |
|---|---|---|
| Monitoring | Real time sensor visibility across the facility | Context did not carry forward into diagnostics |
| Alerting | Alert surfacing across monitored systems | No prioritization model, no cause and effect clarity |
| Diagnostics | Separate view requiring manual investigation | Operators had to reestablish context from scratch |
| Resolution | Work executed in a separate, disconnected system | No path from diagnosis to action within the product |
Structured around the four stage process expert operators use: detect, diagnose, understand, act.
That sequence drove every architectural decision. Components were not designed to display data. They were designed to move operators through a decision, maintaining context so they never had to start over.
Each core product view was redesigned using DesignOI components, testing the framework against real operator workflows.
If a component could not support the diagnostic workflow in practice, the system was wrong. Product and system evolved together.
Context carried forward. Operators investigate, not re-orient.
Progressive disclosure replaced modals. Depth without disorientation.
| Deliverable | What it covered | Why it mattered |
|---|---|---|
| System vision and principles | DesignOI architecture, the four stage framework, governing principles | Gave teams a shared model before any component work began |
| Component library | Foundations through workflow patterns, built for dense analytical interfaces | Eliminated redundant component design across features |
| Diagnostic interaction patterns | Progressive disclosure, in place expansion, context persistence across stages | Reduced modal reliance and context loss in complex workflows |
| Accessibility standards | Full keyboard nav, screen reader structure, focus management | Prevented costly retrofits and enabled expert user efficiency |
| Engineering partnership | Early-stage component implementation, design to build handoff | Reduced ambiguity and accelerated build cycles for new features |
These estimates are directional, based on design audits, early adoption signals, and industry benchmarks. Not measured outcomes from controlled studies.
DesignOI worked because it was designed around a specific cognitive model, not because it had a comprehensive component library. The framework came first. The components followed.
I'm currently open to new design leadership roles. Whether you're building something ambitious or improving what you already have, I'd love to connect.
Get in touch