Meet LE Nexus

Meet LE Nexus

Meet LE Nexus

A clearer way for finance teams to document, review, and trace changes to legal entity records.

Team size

Design, Research, Product, Engineering, and Business

Role

Lead Product Designer

Status

Shipped Live

Duration

12 months

01 / Summary

Making legal entity changes easier to explain and review

Making legal entity changes easier to explain and review

Making legal entity changes easier to explain and review

My role

I led UX design from research synthesis through interaction design and prototyping. I turned findings from 23 interviews into a journey map and role-specific flows, then led weekly design reviews.

What we built

LE Nexus gave teams a workflow for preparing and reviewing changes, with information relevant to each line of business, more readable rationale fields, and a dedicated audit history. These records feed timely updates to regulators, so accuracy here is a legal risk as well as a usability problem

What we heard

In an evaluation with seven participants, users described a more streamlined workflow and said they relied less on outside sources. Audit history drew particular praise.


Satisfaction (CSAT) rose from 2.9 to 4.25.

02 / Understanding the problem

Understanding the problem

Understanding the problem

Understanding the problem

Where it started

Business preparers, reviewers, and administrators used the same legacy tool for different jobs. People had to sift through information unrelated to their work, manually import and export data, and track down explanations for changes.

What wasnโ€™t working

The rationale field was so small that people struggled to read their own entries and explanations left by teammates. Data discrepancies made records harder to trust. Without an online audit trail, users had no clear way to retrace changes inside the tool.

The insight

A reviewer needs the reasoning behind an adjustment to make sense of it. That reasoning had to carry through the workflow, from the person entering the change to the person reviewing it later.

The principle

Give each role the information it needs, and keep the rationale with the record it explains.

03 / From idea to product

From Abstract to Tangible

From Abstract to Tangible

From Abstract to Tangible

01 / Mapping the work

I synthesized all 23 one hour interviews into a journey map and traced the responsibilities of preparers, reviewers, and administrators. We worked with 15 reviewers, 6 preparers, and 2 administrators in the legacy tool LEBMI. Mapping their work together helped us see where one person depended on information from another.

02 / Designing the handoff

I translated the map into flows for each role. The preparerโ€“reviewer handoff gave us a concrete design problem: how could a preparer explain an adjustment clearly enough for a reviewer to understand it?

03 / Refining the experience

I moved from wireframes to high-fidelity designs through weekly reviews. We refined which information each role needed, made the rationale easier to read, and designed a place to trace changes over time.

04 / Ready to ship

Engineering built the initial workflows as design work continued. Once the MVP was available in the test environment, we could see how people completed tasks in the working tool and get feedback on proposed enhancements.

Working through constraints

At the design kickoff, I shared the proposed nine-month MVP plan so stakeholders could flag constraints early. We aligned on five goals: seamless and intuitive interactions, a robust data model, reusable concepts and flows, scalability across lines of business, and design system and accessibility compliance.

What we chose not to build

We scoped the MVP to a smaller set of workflows, starting with Public Finance, and held other lines of business for later. The trade-off was a narrower first release. The reason was simple: a working tool in users' hands would teach us more than a larger build nobody had tried, and the nine-month plan gave stakeholders a chance to flag constraints while the scope was still taking shape

04 / A clearer experience

From Tangible to Delightful

From Tangible to Delightful

From Tangible to Delightful

Protect the essentials

The old tool showed people information from outside their line of business. We designed around the records and fields relevant to the work in front of them, with enough room to read the explanation behind a change.

*not actual image of real legacy tool; similar imagery

Give people control

We designed a maker-checker workflow. One person prepares a change and explains it. Another reviews it with the record and its rationale in view.

05 / Making value visible

The core features

The core features

The core features

Audit history

Audit history gives users a place in LE Nexus to look back at changes to a record. It addresses a gap we heard about repeatedly in discovery: people had no online trail they could consult in the legacy tool.

Putting the history in the tool made it easier to revisit a change after the original review. When participants praised audit history in testing, they pointed to the same thing they had missed before: a clear trail they could follow.

Rationale

The rationale needed enough space to be scanned and read. We added clear rationale fields to the system so that preparers could add them and reviewers could look at them easily.


That mattered because the next person in the workflow depended on it to understand the adjustment.

Bulk upload and edit

Manual imports and exports had made routine maintenance time-consuming. Bulk upload and edit was one of the enhancements we explored to support people updating multiple records. Participants described it as a highly anticipated feature during evaluation.

Honest information

We used shared interaction patterns across the tool while accounting for differences in the data each line of business needed.

AUDIT HISTORY *Recreated visual

RATIONALE FIELD + RECORD MANAGER

06 / Behind the scenes

The key to success

The key to success

The key to success

The day-to-day

The design kickoff gave business, product, and engineering a chance to respond to the plan while it was still taking shape. I carried that into weekly design-led reviews, using wireframes and prototypes to make decisions concrete and give stakeholders a regular place to raise questions and sign off.

Testing it

Once the MVP was built, we ran task-based usability testing in the working environment and used the same sessions to explore proposed features with a live prototype. That gave us feedback on what people could do in the MVP and which additions they most wanted to see.

07 / Outcomes

What I learned and why it matters

What I learned and why it matters

What I learned and why it matters

For people

Participants reported a more straightforward workflow and fewer trips to outside sources. Audit history stood out because users could trace changes in the same tool where they worked.

*Seven participants is a small evaluation, so we treated the praise for audit history as a signal to test further, not a final verdict

For the business

The MVP established a workflow for preparing, reviewing, and tracing changes, starting with a smaller set of workflows and Public Finance as the first line of business. The working MVP gave users something to try, and the roadmap called for expansion to other lines of business after that first phase.

The number

Satisfaction (CSAT) rose from 2.9 to 4.25. The UAT environment also ran faster, with less load time than the legacy tool.

Key takeaways

The relationships I built through weekly reviews outlasted my first year on the project. When I returned part-time after moving to another team, I could pick up the work with the team and bring what I'd learned about scalable components and design systems into the tool's migration to Salt.

Have a good story to tell together?

Have a good story to tell together?

Have a good story to tell together?