LEA Portal

An internal banking tool designed around legal operations, task management and day-to-day workflow clarity.

Internal toolsWorkflow designEnterprise UXInformation architecture
LEA Portal
IndustryBanking · Legal Tech
My roleLead Product Designer
Year2023
TeamSterling Bank · Revent team
Overview

LEA Portal is an internal regulatory and law-enforcement agency management platform developed for Sterling Bank under Revent Technologies. I worked on the product as Lead Product Designer, translating a sensitive, mostly operational process into a web-based system that different teams could actually use day to day.

The starting point was not a polished product brief. The bank already had a real process for receiving letters, assigning requests and following up on them, but much of that work depended on manual coordination and fragmented communication. My job was to understand how that process worked before deciding what the interface should look like.

As I worked through the product, I realised the design problem was less about adding screens and more about making responsibility visible. Every request needed a clear owner, a status, a deadline and a traceable path from the original letter to whatever happened next.

That understanding shaped the whole product: intake, tracking IDs, role-based access, task states, escalations, SLA handling, regional reporting and system administration were designed as parts of one connected workflow rather than separate features.

The portal is now used internally at Sterling Bank. Because it supports sensitive operational work, it is not publicly accessible.

The portal became part of Sterling Bank's internal workflow and helped demonstrate enough value for the bank to return for additional internal-tool work.

View design impact
LEA Portal product overview
Why the portal mattered

The first question was not “what should we design?” It was “how does this work today?”

Before I could design the portal, I had to understand how a regulatory or law-enforcement request actually moves through the bank. A letter could arrive, need to be acknowledged, assigned, worked on by different people, paused while more information was requested, escalated when time was running out, and eventually closed.

That meant the happy path was only a small part of the product. The real complexity was in handoffs, ownership and exceptions. If a request sat too long in the wrong place, the problem was not just inconvenience. Missed deadlines could create operational and regulatory consequences.

I started by breaking the existing process into a sequence of decisions: who submits, who receives, who assigns, who works, what happens when information is missing, and who needs visibility when something is late. That process map became more useful than jumping straight into wireframes because it exposed where the product needed structure.

“We need to track letters from submission through assignment, follow-up and resolution, so we always know what is outstanding and who owns it.”

The product needed to make a manual process traceable without making an already complex workflow harder to use.

Letter submission and task workflow
Roles & access

The same request meant something different depending on who was looking at it.

One of the first design decisions I made was not to treat every user as if they needed the same interface. The process involved several roles, and each role entered the workflow at a different point.

Internal staff

They needed a simple way to submit agency letters, provide the right information and understand what happened after submission without being exposed to unnecessary administrative complexity.

LEA officer

Their focus was the work itself: assigned cases, required actions, progress, missing information and deadlines.

LEA administrator

They needed a wider operational view. Their job was not only to complete tasks but to assign work, monitor delays, understand workload across a region and intervene when something was going wrong.

System administrator

They needed control over the structure behind the product: entities, regions, branches, business units, user permissions, agency categories and SLA rules.

Separating these responsibilities helped me avoid building one overloaded dashboard. Instead, I could decide what each role needed to see immediately and what could remain secondary.

User roles and access
Letter intake

Every case needed a reliable beginning.

The first major flow I worked through was letter submission. The design needed to capture enough information for the legal and LEA teams to act without turning the form into a barrier for internal staff.

I structured the flow so that every submitted letter generated a tracking ID. That single decision became important because it gave the rest of the workflow something stable to refer back to.

The tracking ID connected the original letter, the agency, the assigned work and the later follow-up. Instead of relying on email threads or memory, the request could now be searched and traced through the system.

I also thought carefully about what happens immediately after submission. A user should not wonder whether the request disappeared into the system. Confirmation and visible status became part of the experience, not an afterthought.

A tracking ID sounds small, but it became the anchor that connected intake, ownership and follow-up across the product.

Letter submission and tracking screens
Task workflow

A letter was only the beginning. The product had to show what happened next.

Once a request entered the system, the next design challenge was to turn it into work that people could understand and act on. I mapped the task lifecycle around states such as To be Assigned, Assigned, In Progress, On Hold, Overdue and Done.

The important part was not the labels themselves. I had to make the transitions between them understandable. Who is allowed to move a task forward? What information should be visible before someone acts? What happens when work cannot continue?

That led me to design assignment, progress updates and collaboration as part of one task experience. If more information was needed, the request could stay connected to the case rather than moving into an informal side conversation.

Designing these states also changed how I thought about dashboards. A dashboard should not just count tasks. It should help someone quickly identify which tasks need attention and why.

Task states and case management 1
Task states and case management 2
Task states and case management 3
Escalations & exceptions

The product became clearer once I stopped designing only for the straightforward cases.

Some of the most important design work happened around situations that did not follow a neat sequence. Certain requests required approvals, some could trigger post-no-debit actions, and others needed staff to attend an agency office or create preparation tasks for another team.

These scenarios forced me to think beyond a standard task manager. I had to understand what information should travel with a case, what decisions needed explicit approval and where the system should notify or escalate automatically.

SLA rules became especially important here. Instead of treating a deadline as a passive date on a screen, I designed around what should happen as that deadline approaches or is breached.

This was also where I had to work most closely with stakeholders. I would map a proposed flow, question assumptions, then adjust the design when I learned that the real legal or operational process behaved differently from what I initially expected.

The exception paths taught me more about the product than the happy path because they exposed where responsibility could become unclear.

Approval, escalation and exception workflows
Regional oversight

The administrator needed to see patterns, not just individual cases.

After working through the case-level flows, I stepped back and looked at the administrator's problem. An LEA Admin could not manage a region effectively by opening cases one at a time.

I designed the dashboard around the questions an administrator is likely to ask first: How many letters are waiting? Which tasks are in progress? What is overdue? Where are SLA breaches happening? How long are cases taking to complete?

This led to metrics such as total letters submitted, tasks in progress, overdue work, tasks completed within SLA, SLA breaches and average completion time.

I treated those metrics as entry points rather than decorative reporting. The useful part of a metric is what someone can do after seeing it, so the dashboard needed to help administrators move from a high-level signal into the underlying work that required attention.

LEA Admin dashboard and performance metrics
System controls

A product like this only works if the rules behind it are manageable too.

As the product expanded, I had to think about the system that supported the visible interface. Regions, branches, business units, regulators, agency categories, user access and SLA rules all needed to be configurable.

That changed the design from a collection of user flows into a more complete operational system. I had to make sure the administrative side was powerful enough for the bank without exposing unnecessary complexity to people who only needed to submit or work on cases.

Access control was especially important because this was an internal banking tool. Internal users were tied to Sterling Bank's existing identity structure, and system-level access had to remain controlled rather than allowing open registration.

This part of the work reinforced a lesson I had already started learning elsewhere: enterprise products often become easier for end users only when the invisible administrative model is designed carefully.

Administration and dashboard designs
After launch

The strongest outcome was that the tool became part of the work.

The portal moved from design into real internal use at Sterling Bank. For me, that was more meaningful than inventing a percentage improvement that the project never measured.

The value of the product was practical: requests could be tracked, ownership became visible, deadlines and escalations were built into the workflow, and administrators had a clearer view of what was happening across the system.

The relationship also continued after this project. Sterling Bank returned to work with the team on additional internal tools, which was a useful signal that the work had built enough trust to extend beyond one product.

Because the portal is an internal system, its success is less visible from the outside. But the fact that it became part of the bank's operational process is the most important outcome of the work.

Live internal-tool workflow
What I learned

I had to learn the domain before I could design the product well.

This project pushed me into concepts I did not already understand. I had to research how legal and regulatory requests are handled, what different agency interactions mean, how service-level agreements affect work, and why certain cases require approvals or escalation.

At the beginning, some of the terminology and process logic were unfamiliar. I learned not to rush past that discomfort. Instead, I asked more questions, documented what I was learning and used flow diagrams to test whether I actually understood the process before translating it into UI.

I also learned how different designing for a legal and operational workflow is from designing a more conventional consumer product. The consequences of ambiguity are higher. A missed state, unclear owner or hidden deadline can affect real work, so clarity has to be designed into the system rather than added later.

The project made me more comfortable working in unfamiliar domains. I do not need to arrive already knowing every concept, but I do need a process for learning the domain quickly enough to make responsible design decisions.

Most importantly, I came away with a stronger understanding that internal tools are not 'just admin screens.' They are products with real users, real pressure and real consequences, and they deserve the same level of product thinking as customer-facing experiences.

Design impact

What the design changed.

The strongest impact is practical adoption: the portal became part of Sterling Bank's internal workflow and led to more internal-tool work.

01LIVE

Used inside Sterling Bank

The portal supports the bank's LEA and legal operations in day-to-day work. It is an internal tool, so it is not publicly accessible.

02

Ownership became visible

Letters, cases, assignees, deadlines and progress can be followed through one system.

03

Escalations are built into the workflow

SLA rules and task states make overdue or blocked work easier to identify and act on.

04

Different roles see what they need

Internal staff, LEA officers, LEA administrators and system administrators work from role-appropriate access.

05FOLLOW-ON

The relationship continued

Sterling Bank returned to build additional internal tools after the portal project.

One more for the road?

That’s one story. There’s more where that came from.

MoneyKids product screens
Fintech · EdTech · B2C

Money Kids | Financial learning for kids

MoneyKids needed to teach money without feeling like homework. I redesigned the experience around gamification, lessons, progress, rewards and parent visibility, making the learning journey clearer while keeping it playful enough for children to want to return.

Product DesignerUX/UIProduct StrategyGamification
View case study