PRODUCT DESIGN
INJURY
INTAKE
INJURY INTAKE
INJURY
INTAKE
CLAIMS
GEICO
CLAIMS GEICO
CLAIMS
GEICO
Year :
Year :
2026
2026
Industry :
Insurance/Claims
Client :
GEICO
Project Duration :
9 Months
Summary
I built the redesign of GEICO’s Injury Intake experience, a high-stress claims flow used by customers reporting injuries after an accident. The goal was to reduce friction in a complex self-reporting journey, improve confidence during claim submission, and create a clearer path for customers in a vulnerable moment. The redesign increased completion and throughput from 16,000 to 56,000+ customers.
This work combined UX strategy, prototyping, user research, and cross-functional collaboration to improve both the customer experience and internal team alignment.
The Challenge
The original injury intake flow relied on a one-question-per-page structure and asked customers to navigate detailed injury questions at a moment of stress and uncertainty. This created significant drop-off and caused many users to abandon the process and call an adjuster instead.
The experience was functionally thorough, but it did not reflect the emotional and cognitive state of a customer immediately after an accident.
Research Insights
Prototype testing with users who had experienced mild to severe injuries revealed three key issues:
the flow did not match the user’s state of mind after an accident
users wanted reassurance that they were completing the process correctly
users needed a clearer way to review and retain what they had submitted
Collaboration
Alongside the product work, I brought business partners and developers into a more collaborative design process, using Figma-based working sessions and structured design jams to improve alignment and speed decision-making across teams.
Prototype Testing
Findings from FNOL prototype testing with 10 users who had experienced mild to severe injuries while reporting a claim.
The FNOL doesn’t match the customer’s state-of-mind after an accident. Participants remarked that, while the FNOL flow was thorough and helpful, it didn’t align with their state of mind if they were expected to fill this out after an accident occurred. One participant mentioned that, having developed a concussion after an airbag deployed, she was barely able to provide or understand the information being shared with her.
Findings: The FNOL There’s no clear indication of how a customer can review what they submitted. Some participants mentioned that it wasn’t clear at the “What’s Next” page how they would be able to review or get a copy of the information they had just sent. They wanted to be able to have a record of the information they had provided and know exactly how to access it if they needed to.
Reassurance can help prevent calls to associates. A couple of participants mentioned wanting to have some way of knowing they were following the process and filling out the information correctly and completely. Some suggested having an AI or chatbot that can provide feedback or answer questions as they completed the flow. Others mentioned having indicators of when certain questions would be asked would also help alleviate this concern of if they were filling out the claim information correctly.
RESULTs
To address ongoing friction between business partners and design teams, Alejandro introduced this framework within the Claims department in 2025. It was built to improve trust, strengthen cross-functional collaboration, and create healthier, more effective team dynamics. This work later expanded into a broader coaching practice.
Design, Claims
Increased completion and throughput by
0%
0%
.
Featured Work
Featured Work
Featured Work
PRODUCT DESIGN
INJURY
INTAKE
INJURY INTAKE
INJURY
INTAKE
CLAIMS
GEICO
CLAIMS GEICO
CLAIMS
GEICO
Year :
Year :
2026
2026
Industry :
Insurance/Claims
Client :
GEICO
Project Duration :
9 Months
Summary
I built the redesign of GEICO’s Injury Intake experience, a high-stress claims flow used by customers reporting injuries after an accident. The goal was to reduce friction in a complex self-reporting journey, improve confidence during claim submission, and create a clearer path for customers in a vulnerable moment. The redesign increased completion and throughput from 16,000 to 56,000+ customers.
This work combined UX strategy, prototyping, user research, and cross-functional collaboration to improve both the customer experience and internal team alignment.
The Challenge
The original injury intake flow relied on a one-question-per-page structure and asked customers to navigate detailed injury questions at a moment of stress and uncertainty. This created significant drop-off and caused many users to abandon the process and call an adjuster instead.
The experience was functionally thorough, but it did not reflect the emotional and cognitive state of a customer immediately after an accident.
Research Insights
Prototype testing with users who had experienced mild to severe injuries revealed three key issues:
the flow did not match the user’s state of mind after an accident
users wanted reassurance that they were completing the process correctly
users needed a clearer way to review and retain what they had submitted
Collaboration
Alongside the product work, I brought business partners and developers into a more collaborative design process, using Figma-based working sessions and structured design jams to improve alignment and speed decision-making across teams.
Prototype Testing
Findings from FNOL prototype testing with 10 users who had experienced mild to severe injuries while reporting a claim.
The FNOL doesn’t match the customer’s state-of-mind after an accident. Participants remarked that, while the FNOL flow was thorough and helpful, it didn’t align with their state of mind if they were expected to fill this out after an accident occurred. One participant mentioned that, having developed a concussion after an airbag deployed, she was barely able to provide or understand the information being shared with her.
Findings: The FNOL There’s no clear indication of how a customer can review what they submitted. Some participants mentioned that it wasn’t clear at the “What’s Next” page how they would be able to review or get a copy of the information they had just sent. They wanted to be able to have a record of the information they had provided and know exactly how to access it if they needed to.
Reassurance can help prevent calls to associates. A couple of participants mentioned wanting to have some way of knowing they were following the process and filling out the information correctly and completely. Some suggested having an AI or chatbot that can provide feedback or answer questions as they completed the flow. Others mentioned having indicators of when certain questions would be asked would also help alleviate this concern of if they were filling out the claim information correctly.
RESULTs
To address ongoing friction between business partners and design teams, Alejandro introduced this framework within the Claims department in 2025. It was built to improve trust, strengthen cross-functional collaboration, and create healthier, more effective team dynamics. This work later expanded into a broader coaching practice.
Design, Claims
Increased completion and throughput by
0%
0%
.
Featured Work
Featured Work
Featured Work
PRODUCT DESIGN
INJURY
INTAKE
INJURY INTAKE
INJURY
INTAKE
CLAIMS
GEICO
CLAIMS GEICO
CLAIMS
GEICO
Year :
Year :
2026
2026
Industry :
Insurance/Claims
Client :
GEICO
Project Duration :
9 Months
Summary
I built the redesign of GEICO’s Injury Intake experience, a high-stress claims flow used by customers reporting injuries after an accident. The goal was to reduce friction in a complex self-reporting journey, improve confidence during claim submission, and create a clearer path for customers in a vulnerable moment. The redesign increased completion and throughput from 16,000 to 56,000+ customers.
This work combined UX strategy, prototyping, user research, and cross-functional collaboration to improve both the customer experience and internal team alignment.
The Challenge
The original injury intake flow relied on a one-question-per-page structure and asked customers to navigate detailed injury questions at a moment of stress and uncertainty. This created significant drop-off and caused many users to abandon the process and call an adjuster instead.
The experience was functionally thorough, but it did not reflect the emotional and cognitive state of a customer immediately after an accident.
Research Insights
Prototype testing with users who had experienced mild to severe injuries revealed three key issues:
the flow did not match the user’s state of mind after an accident
users wanted reassurance that they were completing the process correctly
users needed a clearer way to review and retain what they had submitted
Collaboration
Alongside the product work, I brought business partners and developers into a more collaborative design process, using Figma-based working sessions and structured design jams to improve alignment and speed decision-making across teams.
Prototype Testing
Findings from FNOL prototype testing with 10 users who had experienced mild to severe injuries while reporting a claim.
The FNOL doesn’t match the customer’s state-of-mind after an accident. Participants remarked that, while the FNOL flow was thorough and helpful, it didn’t align with their state of mind if they were expected to fill this out after an accident occurred. One participant mentioned that, having developed a concussion after an airbag deployed, she was barely able to provide or understand the information being shared with her.
Findings: The FNOL There’s no clear indication of how a customer can review what they submitted. Some participants mentioned that it wasn’t clear at the “What’s Next” page how they would be able to review or get a copy of the information they had just sent. They wanted to be able to have a record of the information they had provided and know exactly how to access it if they needed to.
Reassurance can help prevent calls to associates. A couple of participants mentioned wanting to have some way of knowing they were following the process and filling out the information correctly and completely. Some suggested having an AI or chatbot that can provide feedback or answer questions as they completed the flow. Others mentioned having indicators of when certain questions would be asked would also help alleviate this concern of if they were filling out the claim information correctly.
RESULTs
To address ongoing friction between business partners and design teams, Alejandro introduced this framework within the Claims department in 2025. It was built to improve trust, strengthen cross-functional collaboration, and create healthier, more effective team dynamics. This work later expanded into a broader coaching practice.
Design, Claims
Increased completion and throughput by
0%
0%
.