Modernizing examiner workflows at federal scale

The complexity was not a flaw in this product. It was the domain. The domain, inconveniently, had excellent reasons. The domain, inconveniently, had excellent reasons.

The platform supported bank-examination work across a large federal regulatory environment. Its users were experts managing institutions, examination scope, issues, workpapers, evidence, deadlines, reminders, ratings, and review states. Simplifying the work itself was neither possible nor desirable. The design problem was to make that work more understandable, navigable, and coherent.

The existing experience distributed related tasks across separate surfaces. Users could move from a dashboard to an institution, into an issue, across to a workpaper, out to supporting evidence, and back again. Each transition required them to reconstruct where they were, what they had learned, and what needed to happen next.

The interface was making users repeatedly unpack and repack the same mental suitcase.

A better experience would not come from redesigning individual screens. The platform needed a stronger workflow model underneath them. I organized the experience around a repeated operational loop:

1. Identify what requires attention.
2. Enter with the relevant institutional and examination context intact.
3. Review evidence and related work.
4. Record a judgment or action.
5. Return without losing priority or place.

That model became the connective tissue across the dashboard, institution views, issue tracking, workpaper review, documents, and reminders.

The client did not yet have a mature design system. I used an open UI kit as temporary visual scaffolding and invested the design effort in the structure beneath it: information architecture, object relationships, task logic, states, and navigation.

I built a comprehensive clickable prototype spanning the core examiner journey. Stakeholders could move through assigned examinations, institution detail, issue remediation, milestones, evidence, workpapers, documents, comments, and reminders as one system. That shifted reviews away from debating disconnected screens and toward evaluating how the work actually held together. Enterprise software already had enough tabs.

The workpaper review experience made the broader design principle tangible. Examiners needed to read a document, compare it with regulations or prior evidence, and respond to comments from colleagues. A conventional interface would distribute those materials across tabs, windows, or separate document states, because apparently the examiner was not already busy enough. I designed a three-part review posture instead:

• Reference material opened on the left.
• The workpaper under review remained stable in the center.
• Comments stayed anchored to the relevant passages on the right.

The evidence, the judgment, and the team's discussion could remain visible at the same time. An examiner could verify a citation, consider a colleague's concern, and continue reading without surrendering their place.

This was not simply a screen arrangement. It was the product principle in physical form: preserve context whenever the work asks users to compare, interpret, and decide.

The project produced a connected workflow model and a clickable prototype for the platform’s core examiner experience. More importantly, it made the proposed system concrete enough to interrogate: where priority should surface, how institution and examination context should persist, how issues connect to evidence, and how collaborative review should behave.

The design did not remove the domain’s complexity. It gave that complexity a structure the product team could evaluate, test, and build against.