"Discovered user pain points through interviews" tells a recruiter exactly nothing. You found something — great. What did you do about it? What changed? How much faster did users complete the flow?

What weak "discovered" bullets look like

Here are four bullets we see constantly. Each one wastes the recruiter's six seconds.

"Discovered usability issues in the checkout flow"
No scale, no fix, no outcome. Every designer finds issues — that's table stakes.

"Discovered that users preferred a tabbed navigation system"
Preference research without ship date or adoption metric is a study that went nowhere.

"Discovered opportunities to improve the design system"
"Opportunities" is a non-word. Either you shipped improvements or you didn't.

"Discovered insights from A/B testing that informed redesign decisions"
Passive voice hiding who decided what. "Informed" is doing no work here.

Stronger swaps — 15 synonyms

Synonym When it fits Resume bullet
Identified You pinpointed a specific problem with a scope Identified friction in onboarding flow affecting 34% of new users; redesigned 4 screens, lifting day-1 activation from 58% to 79%
Uncovered Research or analysis revealed something hidden Uncovered accessibility gaps in 12 high-traffic components via WCAG audit; remediated all to AA compliance, reducing support tickets 41%
Surfaced You brought an issue to stakeholders or leadership Surfaced retention drop at paywall step through Mixpanel cohort analysis; collaborated with PM to test 3 variants, increasing conversion 22%
Diagnosed Root-cause analysis of a design or UX problem Diagnosed mobile nav confusion via heatmaps and session recordings; redesigned IA, cutting avg time-to-task from 48s to 19s
Pinpointed Precision finding among noise Pinpointed iOS-only bug in design handoff causing 14% layout shifts; corrected Figma auto-layout specs, eliminating post-launch fixes
Validated Hypothesis or assumption confirmed through research Validated hypothesis that personalized dashboard layouts increased engagement; shipped adaptive UI, raising weekly active users 18%
Revealed Data or research made something clear Revealed through card-sort study that users grouped features differently than IA assumed; restructured 3 top-level categories, improving findability score from 62 to 88
Detected You caught an issue before it shipped or scaled Detected contrast failures in rebrand color palette using Stark plugin; adjusted 9 tokens, ensuring WCAG AA across 210 components
Exposed Brought a systemic issue into the open Exposed inconsistent button styles across 18 product surfaces; consolidated into design system, reducing QA flags 53%
Isolated Narrowed a broad problem to a specific cause Isolated drop-off at account setup to a confusing password requirement UI; redesigned inline validation, boosting completion rate from 67% to 84%
Recognized You saw a pattern others missed Recognized that mobile users abandoned cart 2.3× more on Android; redesigned touch targets and form fields, closing the gap to 1.1×
Clarified Made ambiguous user needs concrete Clarified through 12 user interviews that "dashboard customization" meant widget reordering, not theming; shipped drag-and-drop, increasing NPS 11 points
Established Proved a relationship or causal link Established via multivariate test that illustration style A increased trust scores 16% over photo-based headers; applied across 6 landing pages
Determined Concluded after analysis which path to take Determined through heatmap analysis that 71% of users ignored right-rail CTA; relocated to inline position, tripling click-through
Proved Demonstrated with evidence Proved through Figma prototype testing that simplified nav reduced task time 34%; pitched to leadership, securing Q2 roadmap slot

Three rewrites

Weak: Discovered that users were confused by the sign-up form
Strong: Identified 3 form fields causing 89% of abandonments via Hotjar session replay; removed 2, clarified labels on 1, lifting sign-up completion from 52% to 78%
Why it works: Pinpoints the exact problem, shows the fix, and proves the outcome with real lift.

Weak: Discovered accessibility issues in the product
Strong: Diagnosed 23 WCAG violations across design system components using axe DevTools; partnered with eng to fix all AA-level issues in 3 sprints, reducing legal risk and support load
Why it works: Scope, tool, timeline, and business outcome — not just "found problems."

Weak: Discovered insights from user testing
Strong: Validated through 8 moderated usability tests that checkout CTA placement below fold caused 44% of mobile drop-offs; relocated above fold, increasing mobile conversion 31%
Why it works: Method, sample size, finding, action, metric — every clause earns its space.

When "discovered" is genuinely the right word

If you're writing about a serendipitous finding during exploratory research with no hypothesis, "discovered" can work — but pair it with what you did next. "Discovered during open-ended interviews that users were repurposing feature X for workflow Y; prototyped dedicated tool, validated with 6 beta users, added to roadmap." The discovery is the setup, not the punchline.

If the role explicitly asks for "discovery" or "discovery research" in the job description, mirroring the term once can help you land in an ATS-friendly resume keyword bucket — but don't repeat it across bullets.

The "claim verb" trap

"Achieved," "delivered," "discovered," "improved" — these verbs make a claim. Without a number, they're empty. A recruiter reading "discovered UX improvements" has no idea if you found one tooltip fix or overhauled an entire flow. Claim verbs need evidence.

We see this constantly in design resumes. "Discovered insights" — okay, which insights, how many users, what changed? "Improved usability" — by what measure, for which cohort, compared to what baseline? The verb opens a promise. The rest of the bullet has to close it.

The fix is simple: pair every claim verb with a quantified outcome. "Discovered" becomes "Identified 4 friction points in checkout affecting 12K weekly users; redesigned flow, cutting steps from 7 to 4 and increasing completion rate 29%." Now the verb has weight.

If you can't attach a number, the verb is probably wrong. Swap to a verb that describes the action you took, not the result you're claiming. "Conducted 9 user interviews" is weaker than "Identified via 9 interviews that...", but it's honest. Claim verbs without proof read like resume inflation. Hiring managers skip them.

Skip the busywork — Sorce applies for you. 40 free swipes/day.

For more: devised synonym, directed synonym, displayed synonym, doubled synonym, encouraged synonym