Designing a personalized application experience that established a foundation for modernizing federal benefit applications.
Applying for Medicare requires people to navigate complex eligibility rules, enrollment periods, and decisions that can have lasting financial consequences. Traditionally, claims specialists help applicants understand these requirements and determine which circumstances apply to them.
Our challenge was to translate that personalized guidance into a self-service digital experience.
Working with a multidisciplinary team, I helped redesign SSA's Medicare application to respond dynamically to applicants' circumstances, ask relevant questions, and communicate complicated requirements in understandable language.
The project also became an important foundation for SSA's broader application modernization efforts. Building on an approach first established with the Lump Sum Death Payment application, Medicare demonstrated how reusable design patterns, components, and production-oriented prototypes could support the delivery of more complex benefit applications.
SSA needed to replace an aging application built on technology scheduled to be sunset. This created an opportunity to do more than update the interface.
We wanted to create an experience that could adapt to individual applicants much like a knowledgeable claims specialist would.
Medicare presented several challenges. Applicants could be approaching their initial enrollment period, enrolling later in life, or applying under circumstances that affected their available options. Their decisions could have long-term consequences, including lifetime premium penalties.
A static questionnaire risked presenting everyone with the same questions and explanations, regardless of whether they were relevant.
Our central design challenge was to make the application responsive to each applicant's circumstances while maintaining consistency with complex policy requirements.
The experience needed to ask the right questions at the right time, explain why information mattered, and help applicants navigate consequential decisions without relying on a claims specialist.
I worked collaboratively with two other UX designers across the design process, contributing to discovery, flow diagrams, Figma designs, prototyping, research planning, usability testing, synthesis, and iteration.
My work included shaping application flows, developing content strategies to make complex requirements easier to understand, and evaluating design alternatives through research.
Our team worked closely with policy experts and claims specialists to understand the rules governing Medicare enrollment. We also collaborated with developers to translate those requirements into interactive prototypes that could be reviewed by stakeholders and tested with the public.
This was a shared design effort rather than a project with individually owned sections. My contributions were part of the team's broader work to create a coherent, adaptable application experience.
We began by working with people who understood how Medicare claims were processed, including claims specialists and policy experts.
These conversations helped us identify which questions were necessary, which circumstances affected an applicant's options, and where additional explanations or documentation might be required.
We translated those rules into application flows that could respond to an applicant's age, enrollment timing, and answers.
The goal wasn't simply to reduce the number of questions. It was to collect the information needed to determine benefits while avoiding questions and explanations that weren't relevant to a particular applicant.
This required balancing policy accuracy with an experience that felt straightforward and understandable.
One example of the application's adaptive behavior involved people requesting Medicare Part B outside their Initial Enrollment Period.
Depending on their circumstances, these applicants could face a lifetime premium penalty. However, certain qualifying situations, including some forms of group health coverage, could make them eligible for a Special Enrollment Period.
Rather than treating every late enrollment the same way, we designed the application to investigate circumstances that might change an applicant's options.
When an applicant requested Part B outside their Initial Enrollment Period, the experience could ask additional questions about group health insurance or other circumstances that might qualify them for a Special Enrollment Period.
Where documentation was needed, the application made relevant forms available so applicants could provide evidence supporting their circumstances.
The challenge extended beyond conditional logic. The questions and explanations also needed to communicate why the information mattered, without requiring applicants to understand Medicare policy terminology.
Testing a dynamic application required more than showing participants and stakeholders a series of static screens.
We worked with developers who built interactive prototypes that could be configured around specific applicant personas and circumstances.
These configurations allowed us to explore how the experience behaved when important variables changed, such as an applicant's age or application date.
The prototypes gave policy experts, claims specialists, and other stakeholders something concrete to evaluate. Rather than discussing abstract rules, we could walk through realistic scenarios and identify where the experience needed to change.
later used these prototypes in research with members of the public.
This approach allowed us to evaluate the application as a connected experience, including how earlier answers influenced later questions, explanations, and available options.
We conducted more than five rounds of usability testing, generally involving five participants per round. Participants were adults aged 65 and older, reflecting a key audience for Medicare enrollment.
I contributed to research questions, facilitator guides, test facilitation, note-taking, synthesis, and design iteration alongside the other designers.
The research helped us understand whether applicants could follow the experience, interpret the questions, and navigate different enrollment circumstances.
Participants frequently described the application as easy, straightforward, or simple to use.
Those reactions were encouraging given the complexity of the underlying policies. They suggested that applicants could experience a relatively uncomplicated process even when the application was making nuanced decisions behind the scenes.
Research also helped validate the broader approach of tailoring questions and content to an applicant's circumstances rather than exposing everyone to the full complexity of Medicare enrollment.
Medicare was the second application developed using a modernization approach initially established during the Lump Sum Death Payment project.
That earlier work introduced a faster design and development workflow. With Medicare, we extended the approach to a significantly more complex application.
For our project, we used Figma rather than Axure, which allowed us to move more quickly. Others at SSA are still using Axure. We also worked with reusable page components that reduced repetitive design work and supported consistency throughout the experience.
Our collaboration with developers was particularly important.
Instead of creating prototypes that would be discarded after research, developers built testable experiences that could later be carried forward into service integration.
This reduced the need to recreate validated interactions during implementation and helped the team move more efficiently from design and testing toward production.
The approach demonstrated that thoughtful UX design, reusable components, and close collaboration with engineering could support both the quality of the applicant experience and the speed of delivery.
Although the Lump Sum Death Payment application established the initial approach, Medicare demonstrated how it could support a larger and more complex benefit application.
The patterns, components, and approaches developed through this work informed the subsequent Retirement application and later modernization efforts for Disability and Supplemental Security Income (SSI).
Some questions and personal-information patterns were reused across applications, reducing the need to solve the same design problems repeatedly.
By the time I left the project, Medicare and Retirement had launched, while Disability and SSI were still in development.
The team's design and development workflow contributed to a faster path to market.
Reusable page components, efficient design tools, and prototypes that could move into service integration helped reduce duplicated effort.
The speed of delivery was appreciated internally at SSA and helped demonstrate the value of the modernization approach.
Usability research indicated that applicants could navigate complex Medicare enrollment decisions through an experience they frequently described as simple and straightforward.
The application adapted to individual circumstances, presented relevant questions, and provided explanations and supporting forms when needed.
The redesigned Medicare application also formed part of a broader modernization effort that included Straight Through Processing, enabling eligible applications to move through automated adjudication.
This created an opportunity to reduce the amount of manual processing required of SSA technicians, although I don't have verified figures for the operational impact.
One of the most important lessons from this project was that personalization can make a complicated experience feel simple without oversimplifying the underlying rules.
Applicants didn't need to understand every possible Medicare enrollment scenario. They needed an application that recognized their circumstances and provided the information relevant to their decisions.
I also saw how design and engineering practices could influence an organization's ability to deliver services. Reusable components and production-oriented prototypes weren't simply efficiencies for the project team. They became part of an approach that could be extended to other benefit applications.
One challenge was determining how much time to spend exploring uncommon enrollment scenarios.
We investigated edge cases involving applicants with unusual coverage or premium circumstances, including people who hadn't accumulated enough qualifying work history for premium-free Part A.
These scenarios were important, but not all of them were within the scope of the initial release.
At times, we spent considerable effort exploring scenarios that ultimately weren't prioritized for the first version. In some cases, information provided by subject matter experts also changed months later, requiring us to revisit design decisions.
Looking back, I would work to establish clearer boundaries between scenarios required for the initial release and those better addressed in subsequent iterations.
That would help preserve the team's ability to explore complex requirements without losing focus on the decisions needed to deliver the immediate product.
The Medicare redesign reinforced my belief that effective UX design is about managing complexity on behalf of the people using a product.
The underlying system may be governed by complicated policies, exceptions, and technical requirements. The experience doesn't need to expose all that complexity at once.
By combining policy expertise, adaptive application flows, plain-language content, iterative research, and close engineering collaboration, we created an experience designed to respond to individual applicants' needs.
Just as importantly, the work demonstrated an approach that could extend beyond Medicare, establishing a foundation for modernizing other SSA benefit applications.
Helping people navigate consequential retirement decisions through clear content, evidence-based design, and a reusable application framework.
View case studyTurning a static content style guide into a reusable AI-assisted workflow for developing clearer, more consistent government services.
View case study