ORA & Retire Ready
Role
Lead Product Designer (Retire Ready)
Supporting UX/UI & Mobile Designer (ORA)
Industry
GovTech · B2B2C
Duration
ORA ~1 year · Retire Ready 3 months
This project is part of a presidential initiative to modernize the federal government’s digital infrastructure. Before the initiative, federal employees had to navigate complex paper forms to receive their benefits, which could take up to 7 months. The system now helps 2.3 million federal employees get their first paycheck approved in under 7 days, with no paperwork.
Retire Ready is a pre-retirement tool employees can use months or years before officially retiring, reviewing service history, testing retirement-date scenarios, and fixing errors before they become blockers. For HR, it means fewer surprises and less noise to manage. It exists because 80% of delays in ORA's fastest cases traced back to one thing: incorrect military service records. Catching that early made instant retirements possible for far more people.
Simplifying without duplicating ORA. Retire Ready needed to ask nearly the same questions as ORA, but lighter, reliable enough for an accurate estimate, simple enough for someone a decade from retiring. Progressive disclosure and plain language let complexity scale up only when it's needed.

Knowing what to flag. Not every update matters to HR. An incorrect military service record gets flagged even ten years out, since it's the one thing that blocks an instant retirement later, but HR isn't pulled in over every minor suggestion from someone who isn't close to retiring. Contextual flagging like this cut down HR's workload significantly, and a pre-defined set of dismissal reasons kept every response consistent, replacing scattered chat messages and personal emails with something structured and easy to track.

The real challenge was designing for both sides at once: employees needed something interactive and easy to understand, while HR needed rapid-action forms built to get things done, not to be lingered over.

ORA is the platform federal employees use to officially retire, replacing the paper obstacle course with a step-by-step guided wizard on desktop and mobile.
Retire Ready's "Let's confirm your service history" screen, listing each employment period pulled from official records with a total credible service summary and an option to flag a correction.
Retirement calculator card view, showing three retirement-age scenarios (57, 60, 62) side by side with their gross annuity, FERS supplement, and total monthly income.
Retirement simulator table view, comparing the same scenarios row by row across payroll, High-3 salary, and service details.
Retire Ready resources library, showing 23 guides, FAQs, and calculators grouped by topic (Getting started, Your annuity, Service history, and more), with a "Recommended for you" banner tailored to time left until retirement.
Building a new "Retire at 62" scenario in Retire Ready: planned retirement age, years of service, and High-3 average salary sliders, plus retirement-type and military-service options, updating the estimated annuity live as each is set.
Progressive disclosure in Retire Ready: a simple military-service toggle expands via "Go deeper" into survivor benefits, then insurance elections, then an eligibility check, then full option details — each layer only surfaced once the one before it is confirmed.
Retire Ready service history review, listing each employment period with a "Why does this matter?" explainer and click-to-correct rows.
Suggest a correction modal in Retire Ready, letting someone edit a service period's department, dates, agency, service type, and system, with an optional reason, before sending it to HR.
HR-side edit suggestions queue, showing a submitted correction with its reported reason, an editable dismissal reason, and Approve/Dismiss actions.
Four states of the HR dismissal flow: choosing a dismissal reason, the resulting automated message to the employee, editing that message, and confirming it with a specific form attached.
Contextual flagging on the HR service-history table: an "Incorrect retirement code" tooltip on the flagged date, a status column per period, and a "1 Pending" indicator surfacing only what actually needs review.
Creating a PIN in ORA to securely sign retirement documents, part of identity verification before the application begins.
Family details step in ORA, asking whether the employee is currently married since that determines which survivor-benefit options they can choose from, with the estimated annuity updating live alongside it.
Life insurance elections in ORA, with four coverage options each showing their effect on monthly cost and the estimated annuity.
ORA status screen after submission, shown on desktop and mobile side by side, confirming the application was sent to HR and laying out every remaining step through the first monthly payment.
PreviousNext