Enterprise Compliance Platform
This case study reflects work completed in a consultancy environment. Client names, internal terminology, and visual artifacts have been removed or generalized due to confidentiality agreements. Because this platform was internal to the organization, original UI screens and workflow diagrams are not included. The structural challenges, leadership decisions, and measurable outcomes are accurately represented.
Overview
A transportation company managed compliance reports through separate email queues, existing portals, and several internal systems. Processing a report meant gathering information, checking records, communicating with the submitter, and updating its status across different tools.
We designed a web application that brought this work into a shared workspace. The goal was to help compliance staff receive, review, and manage reports without repeatedly switching applications.
My role
I led product design and design strategy, working with the product manager, client stakeholders, and the design team to define the experience.
My responsibilities included guiding research, developing the interaction concept, and coordinating the design work. I also worked with engineering to understand how the application could connect to existing systems while preserving email as a submission and communication channel.
The challenge
Compliance staff regularly moved between four or five applications to process reports. In one observed workflow, a single report required more than twenty separate actions.
Different report types were handled by specialized teams through separate queues. Staff had to understand each system, find the relevant information, and keep track of the report as they moved between tools.
Leadership wanted a shared view of compliance work and better coordination across teams. Staff needed that broader visibility without losing the familiar ways they organized their day.
Approach
We conducted onsite research with the people processing reports and spoke with leadership about the business goals behind the new platform.
We examined how reports arrived, what information staff needed to review them, and where work crossed between applications. Technical discussions with engineering helped establish what we could retrieve from existing systems and how email could remain part of the process.
One finding became central to the design: people were comfortable working from an inbox. The difficulty came from everything they had to do outside it.
The work
Building around a familiar inbox
I proposed an inbox-style workspace where incoming reports could be reviewed and organized.
This gave staff a familiar starting point: see what had arrived, identify what needed attention, and open a report to begin working on it.
The concept retained a recognizable interaction model while bringing more of the work into the application.
Bringing information into the report
Processing a report required information held in several existing systems.
We designed the workspace to surface relevant records alongside the report, rather than requiring staff to retrieve them separately. Attachments, submission details, and communication could be accessed in the same working context.
The aim was to reduce the amount of information people had to carry between applications.
Supporting shared and focused views
A central queue gave teams a common view of incoming work, but people still needed ways to focus on particular report types and responsibilities.
We included filtering and configurable queues so staff could organize their work within the shared system. This supported the goal of broader visibility while preserving useful distinctions between compliance activities.
Keeping communication with the work
Email was an established part of the process, and the client wanted to retain it.
We worked through how email submissions and related communication could connect to reports in the application. Staff could follow the conversation in the context of the work rather than reconstructing it from separate threads.
The proposed experience also supported collaboration when another team member’s input was needed.
Results
The application entered beta with positive initial feedback.
Early testing showed an 18% reduction in compliance ticket completion time. The shared workspace brought report information and communication together, reducing the need to move between separate tools.
These were early results rather than a long-term measure of performance. They provided an encouraging indication that the inbox-based approach could make the workflow easier to manage.