SafetyIQ Operational Workflows
When ambiguity is the risk, clarity is the design problem.
Shaped workflow logic across approvals, agenda views, forms, teams, and verification flows — improving clarity, responsibility, and system structure across a complex operational platform.
SafetyIQ is a safety and compliance platform used to manage operational workflows across forms, approvals, tasks, teams, and verification flows.
The product supports environments where process clarity matters, responsibilities are distributed across multiple roles, and the cost of ambiguity is high.
My work focused on designing how these workflows operate across the platform — clarifying responsibilities, reducing ambiguity, and making complex operational logic easier to understand and act on. Led design with a mid-level designer in support — working directly with product and engineering throughout.
SafetyIQ is an enterprise safety platform used to manage operational workflows across field and office teams. The stakes of getting it wrong are real — bad UX here is not just friction, it is a risk to someone in the field.
Rather than treating incoming requests as isolated features, I approached the work as a set of connected workflow problems. Every ticket had dependencies — features that shared state, responsibility, and configuration. The decision was to resolve those connections first, then design. Approval groups, for example, required zero new components because I designed them against the same structural patterns as team management.
Seven workflow areas redesigned across approval logic, agenda clarity, form configuration, team management, and mobile verification. Approval gates became first-class workflow objects with explicit states and transitions. The agenda surface now distinguishes tasks from approvals from forms. Admin tools share patterns rather than duplicating them.
The clearest signal: approval groups required zero new components — the pattern lifted directly from team management. A platform that expanded capability without adding interface complexity. Fewer support escalations about confused states, fewer developer questions about edge cases. In a safety product, structural clarity is the outcome.
The instinct to scope things narrowly is real on a fast-moving product. Resisting it — tracing connections across requests before designing — is most of the job.