The fastest way to lift almost any CV is to turn duty statements into outcomes. Most CVs are lists of responsibilities — what the person was supposed to do. Strong CVs show what changed because they did it. Learning to spot the difference, and rewrite for it, is the highest-return editing skill there is.
Why duty statements are weak
'Responsible for managing stock' describes the job, not your performance in it. Anyone who held that role could write the same line, so it does nothing to distinguish you. A reader learns that the task existed — not that you did it well, improved it, or delivered anything. Duty lists make every candidate look interchangeable.
What an outcome actually is
An outcome is what was different because you were there: a problem solved, a process improved, a cost cut, a target hit, a team developed. It answers the question a duty statement leaves hanging — 'so what?'. You do not need a dramatic result; a modest, concrete improvement beats an impressive-sounding responsibility every time.
A simple structure to rewrite bullets
A reliable pattern is: what you did, plus what happened as a result. Start with a strong action verb, describe the task briefly, then add the effect. For example: 'Redesigned the onboarding process (action + task), cutting new-starter ramp-up time and reducing early drop-off (result)'. Keep it to one line where you can; the result is the part that earns the space.
Finding the outcome when it is not obvious
Not every role hands you a tidy metric, and that is fine. Ask: did something get faster, cheaper, cleaner, more reliable, or less stressful because of my work? Did I introduce something that did not exist before? Did I fix a recurring problem? Was I trusted with more as a result? Qualitative outcomes are real outcomes — you do not need a percentage to prove you made a difference.
Before and after
A few quick rewrites show the shift:
- Before: 'Handled customer complaints.' After: 'Resolved escalated complaints and introduced a follow-up step that reduced repeat contacts.'
- Before: 'Responsible for the monthly report.' After: 'Streamlined the monthly report, cutting it from two days to half a day and making it easier for managers to act on.'
- Before: 'Managed a team of six.' After: 'Led a team of six, introducing weekly check-ins that lifted morale and reduced turnover.'
One rule: do not invent numbers
Turning duties into outcomes is about surfacing what genuinely happened, not manufacturing impressive statistics. Do not invent a percentage to look sharper — a false figure is easily exposed and worse than an honest qualitative result. If you have real numbers, use them; if you do not, describe the effect truthfully.
Common questions
What is the difference between duties and achievements on a CV?
Duties are what you were responsible for; achievements are what changed because of you — a problem solved, a process improved, a result delivered. Achievements distinguish you; duties make every candidate look the same.
How do I turn responsibilities into achievements?
Use a simple pattern: strong action, the task, then the result. Ask what got faster, cheaper, better or more reliable because of your work, and put that outcome in the bullet.
Do I need numbers for every bullet?
No. Numbers help where you have them, but qualitative outcomes — a problem fixed, a process introduced, more responsibility earned — are genuine achievements. Never invent figures to fill the gap.