Vague resumes fail for a structural reason: claims arrive before the evidence, so the reader stops believing. This order makes you build evidence first, then cut, then test the result on a stranger. Each step feeds the next, since the number you dig up in step 2 is the number your story ends with in step 3.
Step 1: Open with the action you took
Everything downstream depends on this rewrite, because steps 2 through 5 only work if the bullet already names a real verb. Open the file, pick one line written in passive or vague language such as 'responsible for onboarding,' and replace it with the specific thing your hands did: 'Trained 9 new hires on the intake system.' If you cannot name the action, you probably inherited that duty rather than performed it, which is worth knowing before you claim it. People skip this because a soft opening feels safer and less boastful. It is not safer, it is unreadable. Keep the tense consistent with the rest of the document, past for old jobs and present for the current one, and hold it to one line so the scan stays fast. Do this to a single bullet now, not the whole resume.
Step 2: Attach a number you can defend
Numbers are the fastest proof a stranger can check, and step 1 has just given you a verb to hang them on. Go back to that same bullet and ask what changed in countable terms: how many people, how much money, how many hours a week, how many days shaved off a process. Truthful small numbers beat vague large ones, so 'cut invoice errors from 14 a month to 3' outperforms 'significantly improved accuracy.' If nothing was ever measured, estimate honestly and label it as an estimate, for example 'roughly 20 calls a day.' Avoid percentages with no base; 'reduced costs 30%' says nothing if the total was $200. The usual failure here is padding in an impressive-sounding metric with no relationship to the work, which a hiring manager dismantles with one interview question. Place the number where it lands hardest, right after the verb.
Step 3: Turn a duty into a story
Problem-action-result is the shape a human brain reads fastest, and now that step 2 has surfaced numbers, the story can end on one. Take a duty like 'managed social media' and split it three ways: the problem (posting was inconsistent across three accounts), the action (built a shared calendar and a one-page voice guide), the result (output went from 6 posts a month to 20 at the same headcount). Keep the whole thing to two or three lines, because this is a bullet, not a paragraph. A frequent shortcut is writing only the action and calling it a story; without the problem the result reads as luck, and without the result the action reads as busywork. Reuse the figures you already attached rather than inventing new ones, and when the outcome was a decision rather than a metric, name the decision: 'leadership approved the pilot.'
Step 4: Delete one phrase that fits anyone
Read the top half of the page and highlight any phrase that would still be true of a thousand other applicants: 'detail-oriented,' 'team player,' 'results-driven,' 'excellent communication skills.' Pick exactly one and delete it, not rewrite it. The space it frees is more valuable than the claim, because steps 3 and 5 have already supplied real evidence, and a vague phrase sitting beside evidence actively weakens it by implying you needed filler. Where people go wrong is swapping one cliché for a slightly fresher cliché, so that 'detail-oriented' becomes 'meticulous.' Meticulous is the same claim wearing a better shirt. If removing the phrase leaves an obvious gap, treat that gap as an instruction: write a bullet that demonstrates the trait, or leave the space empty and let the page breathe. Do not delete a phrase carrying real information, like a certification or a language.
Step 5: Anchor a skill to actual proof
Skills sections fail when they are a list of nouns with nothing attached. Since step 3 handed you at least one problem-action-result story, use it as the anchor: choose one skill that story genuinely required, then either fold the skill into the story's action line or add it to the skills section with a pointer back up the page. 'Excel (built the invoice tracker described above)' reads as evidence; 'Excel, advanced' reads as a wish. Pick the skill a hiring manager would actually test in an interview, not the one that sounds most impressive on a list. Skipping this step leaves a resume with one story at the top and a disconnected keyword cloud at the bottom, which makes the story look like a fluke. Two or three anchored skills beat twelve unanchored ones, and each should be traceable to a line above it.
Step 6: Let someone read the top half
After five rewrites you have lost the ability to read your own resume the way a stranger does, which is why this step comes last and requires someone else. Hand it over, ask them to read only the top half for thirty seconds, then take it back and ask a single question: what do you think I am good at? Do not prompt them with the answer you are hoping for, and do not explain anything before they read. Their reply is the resume's actual message, and it is often narrower or stranger than intended, so 'you seem organized but junior' is useful data rather than an insult. The common failure is asking 'does it look good?', which only invites politeness. Write their answer down verbatim, then compare it with the sentence you would use to describe yourself. Wherever the two diverge is the bullet to fix next.
A phone reminder disappears the second you dismiss it, leaving no trace that anything was done. A paper strip taped where you will see it visibly gets shorter with each cut and stays there until the last line is gone. Six bullets is one evening's work, and the order above is what keeps it from turning into a full rewrite.