INSURANCE
AUTO MECHANIC FINDER
SIMPLIFIED
PRODUCT STRATEGY
USER RESEARCH
EXPERIENCE DESIGN

INSURANCE
AUTO MECHANIC FINDER
SIMPLIFIED
PRODUCT STRATEGY
USER RESEARCH
EXPERIENCE DESIGN

DURATION
4 WEEKS
MY ROLE
DESIGN STRATEGIST
DELIVERABLES
RESEARCH FINDINGS
HIGH-FIDELITY MOCKUPS
DURATION
4 WEEKS
MY ROLE
DESIGN STRATEGIST
DELIVERABLES
RESEARCH FINDINGS
HIGH-FIDELITY MOCKUPS
DURATION
4 WEEKS
MY ROLE
DESIGN STRATEGIST
DELIVERABLES
RESEARCH FINDINGS
HIGH-FIDELITY MOCKUPS
Project Overview
An auto insurance client wanted to help customers find trusted autobody repair shops for non-claim repairs through a responsive web experience—essentially an Angi-style directory for approved providers. My role was not only to design the site, but also to evaluate whether the concept offered enough customer value to justify the investment. That meant balancing UX design with early product validation.
Project Overview
An auto insurance client wanted to help customers find trusted autobody repair shops for non-claim repairs through a responsive web experience—essentially an Angi-style directory for approved providers. My role was not only to design the site, but also to evaluate whether the concept offered enough customer value to justify the investment. That meant balancing UX design with early product validation.
Project Overview
An auto insurance client wanted to help customers find trusted autobody repair shops for non-claim repairs through a responsive web experience—essentially an Angi-style directory for approved providers. My role was not only to design the site, but also to evaluate whether the concept offered enough customer value to justify the investment. That meant balancing UX design with early product validation.
KEY CONSTRAINTS
Tight Deadlines
I had less than two weeks to investigate user requirements and develop initial concepts for the responsive experience.
Tight Deadlines
I had less than two weeks to investigate user requirements and develop initial concepts for the responsive experience.
Tight Deadlines
I had less than two weeks to investigate user requirements and develop initial concepts for the responsive experience.
No Access to Users
The project sponsor did not support customer outreach, limiting our ability to validate the value proposition or test early concepts directly with users.
No Access to Users
The project sponsor did not support customer outreach, limiting our ability to validate the value proposition or test early concepts directly with users.
No Access to Users
The project sponsor did not support customer outreach, limiting our ability to validate the value proposition or test early concepts directly with users.
Internal Business Conflict
The vendor management team worried that recommending in-network providers for non-insured repairs could violate existing contracts.
Internal Business Conflict
The vendor management team worried that recommending in-network providers for non-insured repairs could violate existing contracts.
Internal Business Conflict
The vendor management team worried that recommending in-network providers for non-insured repairs could violate existing contracts.
Internal Business Conflict
Past experiences with designers left my client concerned that I might not deliver as promised
My Approach
With limited time and no direct access to users, I took a pragmatic approach to both validation and design exploration. I used a proxy focus group to test whether the concept resonated, then created responsive documentation and workflow diagrams to clarify requirements and help the Agile team understand scope. This combination gave the team enough evidence and structure to move the concept forward with confidence.
My Approach
With limited time and no direct access to users, I took a pragmatic approach to both validation and design exploration. I used a proxy focus group to test whether the concept resonated, then created responsive documentation and workflow diagrams to clarify requirements and help the Agile team understand scope. This combination gave the team enough evidence and structure to move the concept forward with confidence.
MY ROLE
Led research, concept development, and UX planning to validate the idea and define the experience.
Led research, concept development, and UX planning to validate the idea and define the experience.
ACTIVITY BREAKDOWN
EXPERIENCE DESIGN
60%
PRODUCT STRATEGY
20%
USER RESEARCH
20%

USER RESEARCH
Good Enough Focus Group
Without access to real users, I ran an impromptu focus group with employees as proxies. Their experiences revealed that customers value trusted guidance—not recommendations from insurance providers - when choosing auto repair shops.
OUTCOME
User goals that informed the jobs-to-be-done for the new app

EXPERIENCE DESIGN
Responsive Design Documentation
I created comprehensive, color-coded responsive wireframes showing how components adapt across desktop, tablet, and mobile. This clarified layout behavior and enabled developers to build the responsive structure and content blocks earlier in the process.
OUTCOME
A shared understanding of responsive behavior that guided early front-end architecture

PRODUCT STRATEGY
User Workflow Diagramming
I created user workflow diagrams to visualize how the app would function end-to-end. This helped the Agile team understand scope and complexity, enabling more accurate estimation of development effort.
OUTCOME
A clear view of product scope that informed estimation and system requirements

USER RESEARCH
Good Enough Focus Group
Without access to real users, I ran an impromptu focus group with employees as proxies. Their experiences revealed that customers value trusted guidance—not recommendations from insurance providers - when choosing auto repair shops.
OUTCOME
User goals that informed the jobs-to-be-done for the new app

EXPERIENCE DESIGN
Responsive Design Documentation
I created comprehensive, color-coded responsive wireframes showing how components adapt across desktop, tablet, and mobile. This clarified layout behavior and enabled developers to build the responsive structure and content blocks earlier in the process.
OUTCOME
A shared understanding of responsive behavior that guided early front-end architecture

PRODUCT STRATEGY
User Workflow Diagramming
I created user workflow diagrams to visualize how the app would function end-to-end. This helped the Agile team understand scope and complexity, enabling more accurate estimation of development effort.
OUTCOME
A clear view of product scope that informed estimation and system requirements

USER RESEARCH
Good Enough Focus Group
Without access to real users, I ran an impromptu focus group with employees as proxies. Their experiences revealed that customers value trusted guidance—not recommendations from insurance providers - when choosing auto repair shops.
OUTCOME
User goals that informed the jobs-to-be-done for the new app

EXPERIENCE DESIGN
Responsive Design Documentation
I created comprehensive, color-coded responsive wireframes showing how components adapt across desktop, tablet, and mobile. This clarified layout behavior and enabled developers to build the responsive structure and content blocks earlier in the process.
OUTCOME
A shared understanding of responsive behavior that guided early front-end architecture

PRODUCT STRATEGY
User Workflow Diagramming
I created user workflow diagrams to visualize how the app would function end-to-end. This helped the Agile team understand scope and complexity, enabling more accurate estimation of development effort.
OUTCOME
A clear view of product scope that informed estimation and system requirements

USER RESEARCH
Good Enough Focus Group
Without access to real users, I ran an impromptu focus group with employees as proxies. Their experiences revealed that customers value trusted guidance—not recommendations from insurance providers - when choosing auto repair shops.
OUTCOME
User goals that informed the jobs-to-be-done for the new app

EXPERIENCE DESIGN
Responsive Design Documentation
I created comprehensive, color-coded responsive wireframes showing how components adapt across desktop, tablet, and mobile. This clarified layout behavior and enabled developers to build the responsive structure and content blocks earlier in the process.
OUTCOME
A shared understanding of responsive behavior that guided early front-end architecture

PRODUCT STRATEGY
User Workflow Diagramming
I created user workflow diagrams to visualize how the app would function end-to-end. This helped the Agile team understand scope and complexity, enabling more accurate estimation of development effort.
OUTCOME
A clear view of product scope that informed estimation and system requirements
Design Solution
Trust, transparency, and convenience emerged as top priorities when choosing an autobody repair shop. Our design focused on clear data privacy practices and personalized search filters to help customers find the repair options that suited their needs and circumstances. In addition, early feedback from users indicated that recommendations from their auto insurance providers were not perceived as trustworthy as project sponsors had assumed.
Design Solution
Trust, transparency, and convenience emerged as top priorities when choosing an autobody repair shop. Our design focused on clear data privacy practices and personalized search filters to help customers find the repair options that suited their needs and circumstances. In addition, early feedback from users indicated that recommendations from their auto insurance providers were not perceived as trustworthy as project sponsors had assumed.
Design Solution
Trust, transparency, and convenience emerged as top priorities when choosing an autobody repair shop. Our design focused on clear data privacy practices and personalized search filters to help customers find the repair options that suited their needs and circumstances. In addition, early feedback from users indicated that recommendations from their auto insurance providers were not perceived as trustworthy as project sponsors had assumed.
KEY DELIVERABLES
RESEARCH FINDINGS
HIGH-FIDELITY MOCKUPS
KEY DELIVERABLES
RESEARCH FINDINGS
HIGH-FIDELITY MOCKUPS
An Issue of Trust
The focus group made it clear that trust was central to how people chose an autobody repair shop. When participants lacked personal experience with a vendor, they relied heavily on recommendations from friends and family. That meant the website’s core purpose was not just helping users find a shop, but helping them feel confident the work would be done honestly and well. I also uncovered an important concern: some customers were wary of insurer recommendations, fearing it could affect their rates later.
PARTICIPANT THEMES
Repair Privacy Concerns
“I’m not comfortable with my insurer knowing every time I take my car in. Could that raise my rates?”
Repair Privacy Concerns
“I’m not comfortable with my insurer knowing every time I take my car in. Could that raise my rates?”
Questioned Motives
“Even I’m not sure I’d trust the insurer’s repair shop recommendation. What’s in it for them?”
Questioned Motives
“Even I’m not sure I’d trust the insurer’s repair shop recommendation. What’s in it for them?”
The Family Mechanic
“My family has gone to the same mechanic for years, so I’d probably go there.”
The Family Mechanic
“My family has gone to the same mechanic for years, so I’d probably go there.”
Data Privacy Matters
To address privacy concerns, we proposed a clear disclaimer explaining that personal information shared with a repair shop would not be accessible to the insurance provider without explicit consent. The language outlined how customer data would be protected, reinforced users’ privacy rights, and clarified how consent would be granted if information ever needed to be shared.
This approach was intended to build trust, increase transparency, and give customers greater confidence in how their data would be handled.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.


Trust Meets Convenience
Alongside trust and fairness, participants also prioritized convenience when choosing a repair shop. Convenience meant more than location or business hours; it also included factors like language support and the availability of specific services. To make those considerations easier to evaluate, this information needed to be clearly surfaced in each listing’s About section and reflected in the search filters.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
Visuals have been restyled for confidentiality. Functionality and user experience remain unchanged.
LISTING
DETAIL

Lessons Learned
This project reinforced the importance of validating the premise behind a product—not just designing the experience around it. The sponsor assumed customers would trust repair shop recommendations from their insurance provider, but our proxy research revealed a more complicated reality: people valued trusted guidance, yet some worried that using an insurer-recommended shop could affect their rates or compromise their privacy. That insight shifted the concept from a straightforward provider directory toward an experience that needed to actively earn trust through transparency, consent, and clear communication. It also demonstrated how lightweight research and early design documentation can reduce uncertainty when ideal conditions are unavailable. The proxy focus group could not replace direct customer research, but it exposed assumptions that required further validation, while the responsive wireframes and workflow diagrams gave the Agile team enough clarity to estimate the effort and begin planning.

Lessons Learned
This project reinforced the importance of validating the premise behind a product—not just designing the experience around it. The sponsor assumed customers would trust repair shop recommendations from their insurance provider, but our proxy research revealed a more complicated reality: people valued trusted guidance, yet some worried that using an insurer-recommended shop could affect their rates or compromise their privacy. That insight shifted the concept from a straightforward provider directory toward an experience that needed to actively earn trust through transparency, consent, and clear communication. It also demonstrated how lightweight research and early design documentation can reduce uncertainty when ideal conditions are unavailable. The proxy focus group could not replace direct customer research, but it exposed assumptions that required further validation, while the responsive wireframes and workflow diagrams gave the Agile team enough clarity to estimate the effort and begin planning.

Lessons Learned
This project reinforced the importance of validating the premise behind a product—not just designing the experience around it. The sponsor assumed customers would trust repair shop recommendations from their insurance provider, but our proxy research revealed a more complicated reality: people valued trusted guidance, yet some worried that using an insurer-recommended shop could affect their rates or compromise their privacy. That insight shifted the concept from a straightforward provider directory toward an experience that needed to actively earn trust through transparency, consent, and clear communication. It also demonstrated how lightweight research and early design documentation can reduce uncertainty when ideal conditions are unavailable. The proxy focus group could not replace direct customer research, but it exposed assumptions that required further validation, while the responsive wireframes and workflow diagrams gave the Agile team enough clarity to estimate the effort and begin planning.
