Your resume is a dashboard: is it lying?

The short answer

You can put numbers on your resume without inflating them if every number passes one test: what record backs it, and could you show it? Treat each bullet as a status light. Green only means something if someone checked what sits behind it. Below are five ways a resume can mislead without one false word, and a five-question test that catches them.

Check it now: Run your resume through the free AI review and see which lines look unsupported, generic or risky.

Where the frame comes from

Program managers know the dashboard that is green while the program is in trouble. Every figure can be accurate. The picture is still wrong.

That is the idea behind Your Dashboard Is Lying: Restoring Program Visibility Before the Decisions You Can't Undo by Dmitrii Selkov (Independently published, 2026). This guide borrows a few of the ideas the author has presented in public and applies them to a different document: your resume. It does not quote the book. The resume applications are ours, not the book's.

A resume is a status report about you, and the reader has seconds. TheLadders' 2018 eye-tracking study measured an average initial screen of 7.4 seconds. In a window that short, a reader can only skim, and titles, verbs and numbers are what stand out. Those are your status lights. Later, in an interview, someone asks what sits behind them.

Five ways a resume lies without a false word

1. The accurate number that paints the wrong picture

A dashboard can be factually accurate and still lie about the program. So can a bullet. "Reduced defects by 60 percent" may be true, and still mislead if the baseline was five defects, or if the drop came from a change in how defects were counted. Ask what the reader will assume, not only whether the figure is correct.

2. Small edits that add up

In a reporting chain, each person makes one small, reasonable edit. After many steps, the number at the top no longer reflects reality. Your resume has a chain too: your notes, a first draft, a version for each job, a recruiter's rewrite, the LinkedIn copy. Here is how one line can drift (illustrative):

• Your notes: "Trained about 40 pilot users."
• First draft: "Trained 40 users."
• Version for a rollout job: "Trained 40+ users across the business."
• Version for a leadership job: "Led enterprise training rollout."

Each step looks fine. The last line no longer says pilot, or 40, or trained. The fix is structural: keep one master list of facts and cut each version from it, never from the previous version.

3. Definitions that quietly shift

A metric can stay accurate while its definition moves, the way adjusted numbers work in finance. On a resume, the shifts are small words:

• "Led" versus "supported."
• "Team of 15": direct reports, or everyone on the project?
• "$6M program": the whole program, or your workstream?
• "Saved $400K": one time, or a yearly figure?

Put the definition in the line: "Led a team of 15 (4 direct reports, 11 matrixed)." The shift also runs the other way. People write "supported" when they ran the workstream. Understating is a wrong reading too.

4. Status words that hide what happened

"Ready" and "done" can hide what is really going on. Resumes have their own set: "responsible for," "managed," "delivered on time." "Responsible for the rollout" says what sat on your plate, not what happened. "Delivered on time" can cover a release that slipped three weeks. Replace the status word with the event.

5. Reporting status instead of enabling decisions

A project leader is a decision enabler, not a status reporter. A resume can fall into the same trap. "Held weekly status meetings, maintained the RAID log, reported to the steering committee" describes reporting. It says nothing about what the reporting made possible. Ask which decision your work put in front of the right people, and what followed.

The dashboard test: five questions for every bullet

1. Source. Where does this number come from? Name a document, a system or a person: a status report, a budget file, release notes, an email. If the only source is your memory, word it as an estimate ("about," "roughly") and be ready to explain how you estimated.
2. Baseline. Compared with what? A number with no before is a light with no threshold.
3. Definition. What counts, and who? Team, budget, scope, period.
4. Role. Did you lead it, own part of it or contribute? Use the verb your colleagues would use.
5. Decision or outcome. What changed, or was decided, because of your work? If the bullet only lists activity, rewrite it.

A bullet that passes all five is green for a reason.

When you have no number

Many roles never came with a scorecard. Honest options:

• Count things. Releases, milestones, sites, vendors, integrations, stakeholder groups, cutovers.
• Use time. "From quarterly to monthly." "In 11 weeks."
• Use before and after in words. "Approvals moved from email chains to one weekly review."
• Use a range when exact figures are confidential. Check your agreement first. If you are unsure what you may share, treat the figure as off limits until you know.

Numbers usually hide in old status reports, budget and forecast files, RAID logs, release notes, steering committee decks, sent emails and performance reviews. Keep a proof file of what you are permitted to keep. If company files must stay with the company, write down the figure and where it lived.

Mid-article check: Get a free AI review and see which of your bullets look unsupported, generic or risky.

Illustrative example: five bullets through the test

Illustrative, not a real client. The figures below are invented to show the pattern.

If you cannot name the record in the right-hand column, the stronger line is not ready to use.

Why a doubtful number costs more than a missing one

A missing number costs you one bullet's impact. A number you cannot explain can cost the credibility of the rest of the page, because interviews are where readers check. If you would hesitate to explain a line to the person who signed off on that work, rewrite it before you send it.

FAQ

What if I do not have exact numbers? Use a count, a duration or a before-and-after in words, and label any estimate as one. "About 30 users, from the pilot sign-in sheet" is stronger than "many users" and safer than "30 users" you cannot source.

Is it okay to round? Rounding is fine when the wording says so and the direction is honest. "Roughly $2M" for $1.96M works. Rounding up to a figure that reads better is the edit the whole chain of versions invites. Round to what the record supports, not to what sounds better.

What if my employer's numbers are confidential? Use a percentage, a count or a range instead of a dollar figure, and check your employment or client agreement for what you may share. PM Career Desk cannot give legal advice, so ask your employer or a lawyer if you are unsure.

Check your own dashboard

Reed is an AI career analyst. In the free review, Reed quotes your own lines back to you and marks those that are unsupported, generic or risky, with questions to answer. Reed can point at a line that lacks a record. Only you can attest that a line is true, and that part stays with you.

Check your resume with the free AI review.

Keep going

• Next: Project manager resume guide, from the project manager hub
• Further reading: Your Dashboard Is Lying, by Dmitrii Selkov.

Not ready to upload? Find your PM archetype first

Last updated: September 29, 2026