"Quantify your impact" might be the most repeated line in résumé advice, and the intent behind it is correct. Numbers carry information adjectives cannot. "Reduced onboarding from 23 days to 14" beats "dramatically improved onboarding" every single time.
The advice is still doing damage. Not because of what it says, but because of when people are told to follow it.
What the advice actually produces
Picture the moment the advice lands. Someone is rewriting their résumé under deadline, for a posting that closes Friday, reconstructing projects from three employers ago. The guide says every bullet needs a number. They do not have the numbers. Nobody wrote them down, the dashboards are behind a login they lost two jobs ago, and the manager who would remember has moved on.
So they estimate. And then, because "roughly 30%" looks weak next to the confident bullets in the example résumés, the estimate firms up. Improved efficiency by 30%. Saved approximately $500K. Increased adoption by 40%. Plausible-sounding, unverifiable, and invented.
This is not a fringe failure. In a survey of over 2,000 US adults, 64.2% said they had stretched the truth on a résumé at least once, with skills and work experience among the most commonly inflated items. The advice did not create dishonest people. It set an expectation of precision at the exact moment the precise information was gone.
Here is why that is worse than no number at all: a specific claim is a commitment. The interviewer who asks "tell me how you measured that 30%" is not being difficult; they are doing exactly what a specific number invites. And a claim that dissolves under one follow-up question does not just lose that bullet. It re-prices every other line on the page.
The odds are not in favor of it going unnoticed either. In that same survey, 81.4% of people who embellished were eventually found out, and among those caught, most lost the offer or the job. An invented number is not a small stylistic liberty. It is a bet with poor odds and an expensive downside.
What "quantified" actually means
The escape is realizing that quantification means establishing magnitude, not manufacturing percentages. Magnitude has many honest forms:
Volume: 75 stakeholders, 12 facilities, 14 workstreams. Money: a $2M budget, a $600K contract. Time: a six-month implementation, a 10-day cycle cut. Reach: enterprise-wide, five countries, every clinical specialty. Quality: passed the audit, zero critical defects. Consequence: the go/no-go decision, the executive approval, the escalation you owned.
You almost always know several of these cold, even years later, because they are facts about the shape of the work rather than measurements of its effect. "Led a six-month implementation across 12 facilities on a $2M budget" contains three numbers, every one of them defensible in any interview, and it never claimed a percentage at all.
And when you truly have the outcome number, use it, with its honest label. "Estimated 30%, based on before-and-after ticket volume" is a stronger sentence than a confident round number with nothing underneath, because it survives the follow-up.
The real fix is upstream
But notice what all of this is working around: the numbers were never captured when they were free. The week a project ends, the metrics are sitting in the open, on dashboards you can still see, known by people you still talk to. Five minutes of writing them down then means never facing the invent-or-look-weak dilemma at all.
"Quantify your impact" is bad advice for the night before a deadline. It is excellent advice for the week the work actually happens. Same words. Everything depends on the timing.
Standing Proof records the measure with the work, honestly labeled, at the moment it still exists, and its AI is built to never invent a number for you. Read the method.