A web app for legal pros that helps clients stay compliant

  • Client

    Morgan, Lewis & Bockius, LLP
  • Role

    Product Manager


No items found.

Key Features

No items found.

Project Description

Problem Statement

When a company wants to hire someone on an H1-B visa, they're legally required to do the following things:

  1. File a Labor Condition Application ("LCA") with the Department of Labor
  2. Notify their U.S. workers that they've filed the LCA

This app doesn't help with submitting the LCA's themselves. Instead, it handles LCA notices: simple bulletins via email or print that essentially say "Hi everyone, just letting you know we've submitted an LCA."

Our stakeholder already had an app for this, but they hated it. So, they asked us to redesign it.

Thus, LaborSnap was born.


First, let's talk about the functional goals. These were rather straightforward CRUD operations required with any database application.

  • Create notice
  • Read a notice
  • Update a notice
  • Delete a notice

With these came design goals.

  • Rebrand the old layout to match the stakeholder's branding
  • Simplify flows
  • Improve performance speed

And with these broad goals in mind, we set out to start researching.

Research and Discovery

User Interviews

We had the benefit of interviewing internal staff to get their feedback about the current tool. About 5-10 people, to start.

These conversational interviews revealed a few constant pain points.

Top Pain Points

Can't edit a notice without deleting and reposting it

This would be frustrating in any case, but here, it's especially damaging. You see, compliance requires notices remain published for 10 consecutive days. If a notice is removed for any amount of time at all, that 10-day countdown restarts. In other words, correcting a typo will delay the company's hiring cycle by 10 days at minimum. Every time.

Can't add notices directly to the app

If you imagine a job-board-like app, what kind of UX do you imagine? You probably imagine clicking a "new notice" button that opens a form where you type in the job title, the description, the compensation range, and so on. Right? 

To create a new notice in the old app, you had to follow these steps:

  1. Write the LCA notice in Microsoft Word
  2. Print it out
  3. Scan the printed copy to a JPEG
  4. Upload the JPEG to the app
Exporting unnecessarily complicated

Viewing a notice you've already uploaded an was equally convoluted process:

  1. Click the notice name
  2. In the background, the app retrieves the JPEG and then converts it to a PDF
  3. PDF downloads immediately without preview
Can't limit user access

This feedback came from higher-ups on the legal aid team. They needed to be able to limit which notices each of their team members could access, both for security and safety reasons (users keep accidentally deleting things).

Competitor Analysis

Apps this niche never have direct competitors, but it's structurally similar enough to a job board that we could look at LinkedIn and Indeed for inspiration.

Design System


The color system for ProjectL is identical to that used for VizBridge, as they're both branded for Morgan Lewis. For more details, please see the color section under VizBridge.

That being said, the way we used the color system is quite different.

Differences from VizBridge

  • Backgrounds and surfaces are true neutral (saturation = 0) instead of tinted with the primary token
  • Most primary actions use Primary Container instead of Primary
  • Uses two-tone iconography


Like VizBridge, this app uses GoldenType.


To get a feel for the application, take a look at the following slide deck. These are from the first version of the application.