PAGE 02 · THE FULL PROCESS

A 14-week
double-diamond.

From a fragmented brain-waste problem to a calm, sequenced, action-oriented product — the full UX double-diamond, pace, decisions, and the cuts that defined the product.

ON THIS PAGE
01 · THE BRIEF

Why this problem.

I considered eight problem spaces before committing to this one. Severance won because it satisfied three filters a senior recruiter looks for in a portfolio project:

  1. Real, underserved problem. 2.5M U.S. + 690K CA layoffs in a 2-year window. Defensible market size.
  2. Emotional design challenge. Calm-but-urgent is a tone-collision most products fail. Solving it is a craft narrative interviewers remember.
  3. Research path that didn't require institutional access. Laid-off people are reachable through r/Layoffs and LinkedIn alumni groups, willing to share if the script is respectful.

Goals

Help users see one calm action for today, avoid leaving money on the table, and feel — and look — capable in a moment that often feels neither.

Out of scope (intentionally)

Job board integration (well-served by LinkedIn / Indeed), mental-health chat (clinical risk), resume rewriter (better tools exist), tax estimator (edge case), direct API to state UI portals (regulatory).

02 · DISCOVER

Ten interviews. Two countries. Two months.

I conducted 10 generative interviews across five professions and seven U.S. states / Canadian provinces. Each session ran ~60 minutes, recorded with consent and transcribed. The full interview script and competitive audit are linked in the research deep-dive.

METHOD
Secondary research
DOL OIG, Statistics Canada, Layoffs.fyi, Pew, Kaiser Family Foundation, NELP. Sized the problem and mapped the regulatory landscape.
METHOD
Competitive audit
Six products: LinkedIn, state UI portals, outplacement (LHH), Mint/Wealthsimple, Reddit r/Layoffs, HR severance docs.
METHOD
Generative interviews
10 semi-structured 60-min sessions with recently-laid-off knowledge workers. Recruited via r/Layoffs DMs, LinkedIn alumni groups, snowball sampling.

Participant panel

IDIndustryRoleRegionWindow
P01SaaSSenior PMCalifornia1.5 mo ago
P02CryptoEngineerOntario, CA4 mo ago
P03Retail HQSenior BuyerNew York6 mo ago
P04MediaEditorTexas9 mo ago
P05Healthcare adminOperations LeadIllinois2 mo ago
P06FintechDesignerBC, CA11 mo ago
P07BankingAnalystNorth Carolina3 mo ago
P08EdTechCSMMassachusetts7 mo ago
P09AI startupMarketingWashington5 wk ago
P10AerospaceProject ManagerQuebec, CA1 mo ago

→ Read the full research breakdown, including 10 interview transcripts

03 · DEFINE

From 280 sticky notes to five themes.

Three rounds of clustering reduced 280 quote-level notes to five themes. Each theme mapped 1:1 to a design principle that became the critique rubric for the rest of the project.

22% of notes
Sequencing
"Tell me what to do today." The single largest theme. Users don't lack information — they lack ordering.

→ Principle: The home is a plan, not a feed.
18% of notes
Shock window
"I sat at the kitchen table for 40 minutes and just stared." Days 1–3 are not productive days.

→ Principle: The first three days are slow on purpose.
16% of notes
Household
"My son has a peanut allergy." Severance is rarely an individual event — it's a household event.

→ Principle: Onboarding captures the whole house.
14% of notes
Trust by specificity
"I asked our friend who's a lawyer." Generic content is dismissed. Trust is earned by location and situation.

→ Principle: No generic content. State + situation, always.
12% of notes
Runway anxiety
"I want to see the runway as a single number on a screen." Financial anxiety in this window has a specific shape — it's about runway, not budgeting.

→ Principle: One number, not a chart.
04 · DEVELOP

HMW → Crazy 8s → RICE → wireframes.

Twelve How-Might-We statements. A Crazy 8 round on the home screen. RICE prioritization across 24 candidate features. Three wireframe iterations from paper to mid-fi.

RICE prioritization

Each candidate feature scored on Reach × Impact × Confidence ÷ Effort. The features that survived into v1:

FeatureRICEOutcome
Day 30 wrap-up & reflection1440v1
Subscription audit (one-tap)1280v1
Onboarding household-composition capture1200v1
Day 1–3 calm pacing pattern1000v1
Runway Calculator (one-number tile)1000v1
Personalized 30-day plan home screen750v1
State / Province UI Filing Helper600v1
Health Insurance Decision Tool540v1
Severance Reviewer432v1
Visa / immigration timeline overlay120v1.1
Mental-health chat companion100cut
Job board integration80cut

→ See the paper wireframes and digital iterations

05 · DELIVER

Five participants. Nine issues. Two critical fixes.

Moderated, remote, think-aloud usability testing produced a SUS of 84.5 and a calm-vs-panicked Likert of 4.6/5. Two critical issues — the severance-window banner felt coercive, and the Texas state-portal fallback was missing — were fixed in v4.

SUS
84.5
"Excellent"
TASK SUCCESS
91%
Median across 7 tasks
TRUST LIKERT
4.4/5
"Would trust this with my finances"

→ Read the full usability testing breakdown

06 · WHAT I LEARNED

Four things I'll carry to the next project.

1. Restraint is a feature.

Most products try to do more. This product wins by doing less, on purpose. The calm-mode home screen — one card, empty space below — was the most-discussed surface in usability testing.

2. Tone is a design system token.

It's the most consequential token, and the hardest to defend in critique. I needed three iterations to get the calm-mode copy right. The 52-year-old test participant who said "this reads like you think I'm fragile" rewrote that screen.

3. Cross-list, don't bury.

Information architecture rarely fails because navigation is too deep — it fails because users have multiple correct mental models. Cross-listing the Severance Reviewer under both Money and Documents lifted findability from 75% to 91%.

4. Hire a critic with lived experience.

A friend who'd been laid off in 2023 reviewed the calm-mode copy before round-2 testing. Her note ("'the world can wait' assumes a kind of life I didn't have") rewrote the line and made the whole calm-mode opt-in instead of forced.

Keep going.

Pick the deeper dive that interests you most.

Research Wireframes Final Designs → Testing