Search Optimization

From Broken to Better

October–November 2025 | UC San Diego Health

The Challenge

Multiple teams complained that search didn't work. Media relations couldn't find their own press releases. Content creators watched as carefully crafted pages vanished from results. Leadership expressed frustration that basic searches failed. But "search doesn't work" isn't actionable feedback—we needed to understand why it failed and for whom. Was this a technical problem, a content problem, or a fundamental mismatch between how the system worked and how people expected it to work?

User Quote from Study

Business Objectives

Diagnose the root causes of search failure across different user groups and content types

Quantify the problem with measurable success rates, error patterns, and user satisfaction scores

Understand user behavior to distinguish between system failures and user education gaps

Provide actionable recommendations prioritized by technical feasibility and user impact

Create sustainable documentation to prevent future search degradation as content evolves

My Role & Responsibilities

As Lead Researcher, I designed and executed a search evaluation combining mixed-methods usability testing with 9 participants (5 external patients, 4 internal team members), quantitative performance measurement across 5 task scenarios, qualitative think-aloud protocols to capture reasoning and frustrations, and synthesis of findings into prioritized recommendations with implementation timelines.

I collaborated with the development team to understand technical constraints, the Marketing and Communications team to document their workflow challenges, and leadership to align recommendations with organizational priorities.

Icons showing research methods

Presentation slide describing tasks performed for this usability test.

Presentation slide sharing task success rate, abandonment rate, and confidence rate for one of the tasks completed by users.

What I Learned

"Search doesn't work" meant completely different things to different people: I started this project expecting to find one broken system. Instead, I discovered that external patients found search perfectly adequate for their straightforward needs while internal teams experienced total failure for their complex workflows. This taught me that user satisfaction scores can mask critical problems—the 3.5 overall rating hid the 2.8 internal user frustration that represented real operational dysfunction.

Quantitative metrics alone would have led to wrong conclusions: If I'd only looked at the 89% provider search success rate, I might have declared victory—it's just 1 point below the 90% target. But qualitative observation revealed that 100% of users missed the availability indicator and were making assumptions. The "success" was accidental, not designed. This reinforced that task completion doesn't equal good experience.

Small sample sizes can reveal big problems when patterns are clear: With only 9 participants, I initially worried the findings wouldn't be credible. But when 100% miss a feature, 75% bypass your system entirely, and satisfaction scores show a 1.2-point internal/external gap, the patterns are undeniable. I learned to trust strong signals even from modest sample sizes, especially when qualitative and quantitative data align.

Prioritization requires balancing impact, feasibility, and sustainability: I wanted to recommend fixing everything immediately. But working with the development team taught me to categorize recommendations by implementation complexity and create phased timelines. The provider availability fix delivers high impact with moderate effort, while advanced news filtering requires significant work—sequencing matters as much as identification.

 

Why This Project Matters

Search is the primary pathway to information on complex websites. When search fails, people can't find critical health resources, internal teams waste hours on basic tasks, and confidence in the entire digital experience erodes. This research didn't just identify problems—it quantified their severity, explained their causes, distinguished between user education and system failures, and provided a roadmap for sustainable improvement. By combining technical analysis, quantitative measurement, and qualitative insight, this work transformed vague complaints into actionable solutions prioritized by real impact.

Slide Preview Showing Key Points for Stakeholders

Presentation slide preview summarizing key points for stakeholders.


Research Methods: Usability testing • Task analysis • Think-aloud protocols • First-click testing • Performance metrics • Satisfaction measurement • Technical analysis • Mixed methods synthesis

Skills Applied: Study design • Quantitative and qualitative analysis • Technical system evaluation • Stakeholder interviewing • Prioritization frameworks • Implementation planning • Documentation creation • Cross-functional collaboration