03
American Red Cross · Disaster Relief Platform · Shipped 2021

Designing for the
worst day
of someone’s life.

Displaced families waiting in shelters. Six disconnected tools. A federal clock running. I led design and delivery — one record for three roles that had never shared a system, deployed nationally inside a single disaster response cycle. It had to work for an untrained volunteer on day one, under surge, with federal oversight active from the moment it went live. It did. 1,689 cases in the first two weeks.

Client
American Red CrossNational Headquarters
Platform
Disaster Relief PlatformSalesforce SLDS
Role
Product Design Director / GM0→1 Build
Team
1 designer1 researcher1 PM2 engineers
Scale
6 monthsNational deploymentReplacing 6 legacy systems
Outcome
$847K disbursed6→1 system switches1,689 cases in 2 weeks
Responsibility
Venture GMService DesignFinancial DistributionSystems Consolidation
01
Field Volunteer · Intake
Three fields, not eight.

Two people still have to vouch for one payment. The other approved itself.

02
Caseworker · Case Detail
Seeing the whole family.

The ID had already been verified. That's exactly why changing it stopped the payment.

03
Caseworker · Follow-Up
Nothing waits in someone else's queue.

The alert doesn't clear because you saw it. It clears because you acted on it.

04
Finance Officer · Payments
Ledger as audit record.

Six flags collapse into one line — until someone decides to actually look.

05
Program Director · Command
Scales with the disaster.

Every case that lands already knows which module it belongs to.

Design System

Built to verify eligibility,
certify compliance, and catch fraud.

Eligibility Verification
Eligibility Payment Ledger
ID VerificationPass ↗
Address VerificationPass ↗
Event VerificationPass ↗
Damage AssessmentPass ↗
Accepts Financial Assistance
Fraud Hold — Second Verification Required
A prior flag on this case requires a second verifier before payment can be issued.
Verified by (Primary)
— Not yet verified —
Verified by (Secondary)
— Not yet verified —
Complete Verification & Approve Deny
Issue Payment
Issue Payment
Eligibility is verified — this releases the case's first disbursement.
Payment Method
EFT CAC Mastercard Send PayPal Zelle
Amount
$250.00
If EFT is selected
Bank Account #
Enter from client
Routing #
9-digit ABA
Payment Issued
Mastercard Send — $250.00
Authorization valid through 11/28/2026
Program Metrics
4
Open Cases
$3,700
Total Disbursed
4
Payment Pending
Export Ready
FEMA Compliance Status
Compliance Summary
Compliance Summary
Eligibility verification compliance across 23 cases
Identity83%
Address78%
Disaster Nexus100%
Primary Residence83%
Financial Need91%
Certify Compliance Export Report
Last certified by J. Alvarez · 08/14/2026 3:42 PM
Case-Level Compliance
Case #ClientIDAddr.NexusRes.Fin.
C235432Noel Ruggiero
D927473Paula Barber
GS-118820Ana Torres
GS-562264Tanya Brooks
BS-451153Daniel Osei
GS-673375Ahmed Farouk
23 cases assessed · 5 flagged non-compliant on at least one criterion
Case Stage Pipeline
Grey Sky · Declared Disaster (11 stages)
New Outreach CL Action Process DA Review Pended Payment Payment Res. Other Res. Closed LTR
Blue Sky · Single Incident (6 stages)
Intake Verification/DA Payment Follow-up Recovery planning Closed
SAF · Service to Armed Forces (6 stages)
New Outreach Eligibility Review Payment Referral Coordination Closed
Suggested Action
Same rule cascade behind the "Suggested Action" column in the Cases and Event tables — first matching rule wins.
1 Case is closed
2 Identity/address unverified, no activity yet Request Documents
3 Payment pending, 0–1 activities logged Send Reminder: Payment Pending
4 Verified + financial need, no payment yet Issue Payment
5 Has a new, unassigned referral Assign New Referral
6 None of the above On track
Also included as a column in the Cases CSV export
Fraud Detection
Duplicate payment account detected Flagged
Ana Torres and Ahmed Farouk share the same phone on file — payment hold applied automatically.
Review View Case
Payment returned
GS-784486 — recipient did not activate Zelle disbursement.
Identification changed post-verification
C235432 — ID update after GIACT sync, second verifier required.
6 alerts total · showing 3
Disbursement Ledger
DateCaseRecipientAmountStatus
02-11D927473Paula Barber$150.00Issued
01-24BS-451153Daniel Osei$190.00Voided
01-22GS-673375Ahmed Farouk$300.00Reissued
01-18GS-784486Grace Whitfield$275.00Returned
08-30C235432Noel Ruggiero$0.00Cleared
People
People Contact info Activity
Household Members
AT
Ana Torres
Preferred language: Spanish · SMS
HOH Power of attorney
ST
Sofia Torres
Relationship to HOH: Child
Minor Contact restrictions
Facilitators
PA
Priya Anand
Type: Translator · Spanish, English
View All
Duplicate Client Warning
Possible Duplicate Client
Matching name and date of birth — a record with these details already exists.
Name: Ana Torres
DOB: 1/31/1990
Phone: (713) 555-0142
Client ID: CL-04471
Existing Case: GS-118820
Continue as New Client View Existing Case
Wizard Progress & Records Match
Step 3 of 8 · Household info & members
ℹ Our records indicate that this address received moderate damage as a result of the 2026 Gulf Coast Flooding. Please continue intake.
Case creation · Head of household info · Household info & members
Damage assessment · Recovery needs · Immediate needs · Assistance details · Referrals
Eligibility Review Queue
Eligibility Review Queue
Awaiting your approval · supervisors approve, caseworkers cannot
Approve All Low-Risk (6)
6
Awaiting My Approval
2
Escalated
9
Approved Today
Case #ClientCaseworkerEventWaitingAction
D927473Paula BarberM. AlvarezDR-4821-FL
3d
Approve
GS-118820Ana TorresR. ChenGS-2201
8d ⚠
Approve
Smart Defaults & Auto-Fill
Event ID
DR-4821-FL
Damage Level MajorPre-assessed
Payment amount
$450
Recommended: EFT to Checking Account
Based on client responses: bank account available, EFT preferred.
✓ GIACT Event synced — Last synced 2m ago
Case Study 03 —— American Red Cross · Disaster Case Management

Six systems. Three roles.
One source of truth.

A new information model — not a consolidation of what existed. Six tools had grown around six functions, none designed to share data. The only path forward was to design the data architecture first, the interface second.

Complexity lives in the system, not the interface.

Three fields.
Everything else invisible.

Three fields on the intake form trigger eligibility checks, identity verification, and FEMA audit trail generation — automatically. The caseworker sees simplicity. The architecture holds everything else.

Three roles. One platform.

One record.
Three completely different jobs.

Same record, three role-specific views, zero redundant data entry. The field volunteer never thinks about FEMA compliance. The finance officer never re-enters what the caseworker already captured. One information model built to serve all three.

One record. Every scale.

A household grows.
An event grows. Same record.

Add one household member mid-case and a new need clears eligibility before the caseworker moves on. Add one disaster event and watch its own case count move as the first real case lands against it. The architecture that handles a family of three handles a national disaster — without anyone rebuilding it in between.