top of page

The Ultimate Cheatsheet for Resume and Portfolio Metrics

One of the most common issues I notice when reviewing resumes and portfolios isn’t weak experience. It’s weak storytelling around impact.


Team meeting in a bright modern office, a woman presenting with a tablet while coworkers sit and listen attentively

Many people tell me they have no idea how to describe the results of their work. Others go in the opposite direction and start adding numbers that sound impressive but immediately feel unrealistic. Hiring managers read hundreds of resumes. They can usually tell when a metric reflects real work versus when it sounds like something generated to fill space.


The challenge is not that you lack impact. The challenge is knowing how to connect your actions to measurable outcomes.



Common Mistakes When Describing Impact


Here are some common mistakes I see repeatedly:


Stressed man with glasses at an Apple laptop, hands on his head in a modern room.

Mistake #1: Using exaggerated numbers


A statement like: “Redesigned the app interface and increased user satisfaction by 80%.” sounds impressive, but it raises immediate questions.


Where did the 80% come from? Was it a survey? A usability score? A rating change? Did you actually measure it?


Large numbers are not automatically better. Real metrics tend to be grounded and traceable.


Instead of inventing dramatic improvements, ask:


What changed before and after your work?

What data source supports it?

Could this realistically happen?


Even a smaller but believable metric often creates more credibility than a giant number.



Mistake #2: Taking credit for company-wide success


Another common example:

“Implemented UX improvements that increased company revenue by 50%.”


Revenue changes usually depend on many variables: marketing efforts, pricing, sales strategy, seasonality, engineering work, and business decisions.


Your contribution may have mattered, but you should clearly distinguish between:

“I improved this feature” vs. “The entire company grew.”


A better approach is:


“Redesigned onboarding flow that reduced onboarding drop-off by 18%, contributing to improved conversion performance.”


Focus on the part you directly influenced.



Mistake #3: Using vague descriptions that say nothing


Examples like “Improved user experience significantly” and “Enhanced usability" look polished but communicate almost nothing.


Better questions to ask:

What exactly improved?

Did users finish tasks faster?

Did errors decrease?

Did engagement increase?


Specificity creates credibility.


Compare:

“Improved user experience significantly.”

with:

“Reduced average checkout completion time from 4 minutes to 2.5 minutes.”


One sounds generic. The other tells a story.



Mistake #4: Choosing the wrong metric


Sometimes the problem isn’t the number itself. It’s the connection.


For example:

“Improved accessibility and increased homepage click-through rate by 50%.”


Accessibility improvements do not automatically lead to click-through improvements.


Ask yourself:

Does this metric logically connect to my action?


Metrics should follow cause and effect.



Mistake #5: Missing the bridge between action and impact


I often see statements like:

“Conducted five usability tests resulting in a 25% increase in revenue.”


The gap between action and result is too large.

Usability testing alone rarely causes revenue growth directly.


The chain usually looks more like this:

Conducted usability tests → identified friction points → redesigned experience → improved task completion → increased conversions


Showing the steps makes your work more believable.



A Simple Action-to-Impact Cheat Sheet


If you’re struggling to quantify your work, start with the activity itself. Different research and design methods naturally lead to different types of outcomes. Rather than inventing impressive-sounding numbers, identify the decisions your work informed and the metrics most closely connected to those actions.



Hands hold a film clapperboard in a desert roadside scene, showing Roadside, Jakob & Ryan, and Thomas Taugher.

In-Depth User Interviews and Field Studies

Possible impacts and metrics include:

  • Informed product strategy, roadmap priorities, and design direction

  • Number of user pain points identified

  • Number of user needs, motivations, or goals discovered


Persona-related Research

Possible impacts and metrics include:

  • Number of personas or archetypes created

  • User journeys mapped and key touchpoints identified

  • Frequency of persona usage in internal decision-making


Card Sorting, Tree Testing, and Information Architecture Improvements

Possible impacts and metrics include:

  • Influenced navigation structure and information architecture

  • Navigation success rate

  • Reduction in time required to find information

  • Reduction in back-clicks

  • Funnel drop-off rates at critical steps

  • User satisfaction with site navigation

  • Visual hierarchy effectiveness (if measured through eye-tracking or similar studies)


Usability Testing and Design Iteration

Possible impacts and metrics include:

  • Task success rate (percentage of users who can complete tasks)

  • Time on task (how long it takes users to complete task)

  • Error rate (how often users make error)

  • Usability score (e.g., System Usability Scale - SUS)

  • User satisfaction score



Large-Scale Surveys

Possible impacts and metrics include:

  • Sample size and confidence interval

  • Opportunity size for specific product/business initiative


Design Variant Testing

Possible impacts and metrics include:

  • Informed design decisions

  • User sentiment and qualitative feedback


Onboarding and User Education

Possible impacts and metrics include:

  • Reduced onboarding drop-off

  • Increased post-onboarding retention

  • Reduced customer support requests


Engagement Optimization

Possible impacts and metrics include:

  • Increased click-through rate (CTR)

  • Reduced abandonment rate

  • Reduced funnel drop-off at critical points

  • Reduced time spent completing key tasks


Design Systems

Possible impacts and metrics include:

  • Number of components, variants, and patterns created

  • Improved design consistency

  • Increased efficiency

  • Reduced implementation and maintenance effort



Common Business Metrics to Strengthen Your Impact Statement


Beyond project-level metrics, it is also helpful to understand the larger business goals your work contributes to. Depending on the product, feature, or company stage, you can connect your work to relevant business outcomes.


Laptop screen showing a dark analytics dashboard with charts and metrics for page load, bounce rate, sessions, and page views.

The goal is not to randomly add business terms. The best impact statements show how your specific contribution influenced a meaningful product or company objective.


Table listing SaaS metrics by category: Acquisition, Activation, Engagement, Retention, Monetization, and North Star.

In real projects, you may still need to discuss with your product manager, engineering team, or stakeholders to understand how success was measured. The strongest resumes and portfolios do not simply attach random numbers. They explain why those numbers matter and how your work contributed to the outcome.



Final Thought


Most people don’t have an impact problem.


They have a translation problem.


And once you learn how to connect action with outcome, describing your work becomes much easier.


Need to refresh your resume? Book a free 15-minute consultation and learn how to better showcase your experience and impact.

Intro Consultation
15
Book Now

Comments


bottom of page