Established the UX foundation for an enterprise investigation platform, from zero

Role

Senior UX Designer, UX Researcher & UI Designer

Focus

Enterprise workflow transformation, design systems, high-fidelity prototyping

Tools & methods

Workflow mapping, information architecture, Fluent UI, high-fidelity prototyping, stakeholder validation

Overview

A global operational organization relied on spreadsheets, email, local trackers, and disconnected communication channels to investigate events and assemble service-quality reports. I helped establish the original UX foundation for a centralized platform, including the full high-fidelity design and component system, that brought investigation, collaboration, reporting, and knowledge capture into one structured experience.

The challenge

Report creation involved multiple contributors working across three to four disconnected channels

Version inconsistency, duplicate work, unclear ownership, and manual coordination introduced delay and quality risk

The replacement experience needed a scalable visual system and developer-ready interaction patterns

The product had to support investigation, incident tracking, report creation, and consolidated information from multiple sources

My approach

01Foundational workflow definition

I mapped the reporting and investigation experience and reframed it into three clear phases: Describe, Build, and Finalize, each one separating foundational context, collaborative contribution, and final decision-making.

02Information and interaction architecture

I defined the page structures, user flows, role transitions, and interaction patterns needed to move work from initial description through collaborative report development to final output.

03Design-system strategy and full UI design

I selected a mature enterprise UI framework and used it to define button hierarchy, spacing, grids, states, iconography, and typography, then designed the complete high-fidelity application on top of that system rather than building every component from scratch.

04Prototyping and validation

I built a working prototype from the high-fidelity designs and ran walkthroughs with product owners and users to validate comprehension of the phased workflow and its fit with the original problems.

Key deliverables

Current-state workflow and pain-point model

Three-phase reporting architecture (Describe, Build, Finalize)

Investigation and collaboration flow designs

Full high-fidelity application designs

Reusable enterprise UI component patterns

Interactive prototype

Selected artifacts

Actual screens from the shipped product. Employer references, vendor account details, and client names have been redacted to protect confidentiality; everything else reflects the real design.

Onboarding screen — introduces new users to the Describe, Build, Finalize workflow before their first report.

Incident Request queue — the Describe phase, where new reports enter the system for triage.

Report builder detailed discussion, the Build phase

Report Builder — the Build phase, where contributors collaborate on the detailed discussion section.

Report finalize form, the Finalize phase

Finalize phase — structured fields replace freeform email threads for closing out a report.

Technician's dashboard view — role-based visibility into processed reports and their status.

Reviewer's dashboard view — a different role, a different set of relevant columns and priorities.

Want a closer look at the real work? Get in touch.

Outcome

The design was approved and moved into development. The platform later operated as a production solution with event investigation, incident tracking, reliability analytics, final report creation, and consolidated information management. A later adoption update showed real, meaningful usage across participating regions — I'm not publishing the exact figures here, since they're specific enough to be identifiable.

What this demonstrates

Enterprise product design from zero to oneWorkflow decomposition and role clarityDesign-system selection and applicationHigh-fidelity UI designPrototype validationHonest attribution between foundational work and later platform scale

What I'd validate next

I'd want to see usage data broken out by the phase that was actually struggling, Describe, Build, or Finalize, since the adoption number on its own doesn't say whether the phased model is working as intended or whether one phase is the bottleneck.

Have a similar problem?

If a product's structure has stopped matching how people actually use it, I'd genuinely love to hear about it.

Say hello