Measuring Invisible Work - MAC156

here is a specific moment this episode is built around, and you have almost certainly lived it.

You are writing up your contribution — for a review, a self-assessment, a conversation you are trying to prepare for. You know what happened. You know it mattered. You get to the word saved — "which saved us about" — and you stop. Because the next word is supposed to be a figure, and you do not have one. So you write "a lot of time" instead, and the sentence quietly dies.

That is the failure point. And it is not a laziness problem. It is a permission problem.

You believe that to put a dollar figure on your own work, you would need the real number — HR's actual turnover model, finance's actual cost-per-incident, something audited and defensible that lives in a system you do not have access to. Since you cannot get it, you conclude you are not entitled to a number at all. And so you arrive at every performance conversation armed with adjectives while the organization around you runs entirely on estimates.

The revenue forecast in that room is an estimate. The headcount plan is an estimate. The projected savings from the reorg somebody presented last quarter was, structurally, a guess with a confidence level and a name attached to it. Nobody in that room is working from audited truth. They are working from numbers somebody was willing to own. You are not missing the data. You are missing permission to estimate.

There is a second thing working against you: you will aim low. Most people place their own contribution below where outside evidence puts it, and the error runs in that direction far more often than the other. The career self-diagnostic episode (MAC-152 at managingacareer.com/152) covered this in detail — the calibration gap is real, it is directional, and knowing about it does not automatically fix it. So when you finally do reach for a number, your instinct will be to shave it. Know that going in.

Where the numbers actually live. There are three sources, and you probably have access to all three right now.

The first is public. There is a whole industry of aggregated employer data sitting in the open, and it covers exactly the metrics leadership already watches. On turnover, for instance, the pooled employer numbers put the cost of replacing someone at roughly 40 percent of their salary for a frontline role, around 80 percent for a mid-level professional, and north of 200 percent for a leader. That is not your company's model. It is a range your company's model almost certainly falls inside.

The second place is your own organization's ordinary paperwork — the one people never think to check. The job posting for the role you helped fill has a salary band printed on it. Your recruiting team's open requisitions tell you how long a seat stays empty. Your own calendar tells you how many hours a month go into the meeting you eliminated. None of that is confidential. It is just sitting there, un-mined, because you have never thought of a job posting as a pricing document.

The third place is a person. Somebody in finance, HR, or ops owns the cost you are trying to estimate, and they will usually answer one specific question if you ask it as a specific question. Not "what does turnover cost us." That gets you nothing. Try: "When we backfill an analyst on my team, roughly how long does the seat sit empty?" That is answerable in one line, and it is the only piece you were missing.

The anchor number. The thing you build out of those three sources has a name, and naming it is what makes it usable. Call it an anchor number: a public or borrowed figure you pick up on purpose, label out loud as borrowed, and use as the starting point of an estimate rather than the end of one. Forty percent of salary is not what your company pays to replace somebody. It is the number you multiply against until somebody hands you a better one. An anchor number is not your company's number. It is a number you can defend while you wait for a better one.

The one rule that matters: say where it came from. The whole thing works if you say "using the industry benchmark of roughly 40 percent of salary" and it collapses the instant you say "our turnover cost is." One of those is an estimate with its sources showing. The other is a claim you cannot back, and the moment somebody checks, every other number you have ever given them gets re-examined too.

The repricing pass — four moves. Take one entry and walk it all the way from a note to a sentence.

Move one: name the metric. Which of the four does this touch — turnover, ramp time, rework, or escalation? Pick one. Most entries touch two, and you will be tempted to claim both. Do not. Two half-credible numbers read worse than one solid one.

Move two: find the unit. Every metric has a thing you count. Turnover counts people. Ramp counts weeks. Rework counts hours. Escalation counts incidents. Figure out what you actually moved and how many of them.

Move three: attach the anchor. Price the unit using one of your three sources.

Move four: put the assumption inside the sentence. Not in a footnote. In the sentence, out loud, where the person hearing it can see exactly what they would have to disagree with.

Here is what that looks like, fully worked. The entry: I cut the new analyst's ramp from six weeks to three.

Metric: ramp time. Unit: weeks of one person's capacity. Anchor: the salary band on that role's own job posting — say it topped out around ninety-five thousand. Fully loaded, with benefits and payroll tax, that is conventionally somewhere around a quarter to a third above base, so call it one hundred and twenty-three thousand a year, or roughly twenty-four hundred dollars a week. A person still ramping is not producing nothing — call it a third of full output early on. So each week you removed is worth about two-thirds of twenty-four hundred. Sixteen hundred dollars. Three weeks, call it five thousand.

And the sentence: "I cut the new analyst's ramp from six weeks to three. Using the posted band for that role and assuming a new hire runs at about a third of output in month one, that's somewhere around five thousand dollars of recovered capacity — and I'd expect the same on the next two hires, because the onboarding doc is reusable."

Five thousand dollars is not an impressive number. That is the point. It is a number that survives a follow-up question, and every step of it can be walked backward in front of a skeptic. A number you can walk backward beats a bigger number you cannot.

The discipline the whole episode rests on: show the arithmetic instead of presenting the total. Label how confident you are in each input — you can be highly confident about a posted salary band and only medium confident about the output assumption, and saying so makes you more credible, not less. And when you are choosing between the modest figure you can defend and the impressive figure you would have to defend with adjectives, take the modest one. Always.

Two more examples across different work:

Rework. Entry: I rewrote the recurring report so people stopped guessing at it. Metric: rework. Unit: hours. Four people were spending about ninety minutes a month each re-deriving what the report meant — that is six hours a month, seventy-two hours a year, call it two working weeks the department stops burning. High confidence on the hours, because you can ask the four people. Medium confidence on whether every one of them actually reinvests it.

Escalation. Entry: I caught the client discrepancy on Friday before it reached their finance team. Metric: escalation. Unit: incidents. You do not have to model this one — go find the last time it was not caught. "The last time this got through, it took four people two days and a written apology." That is your anchor. It happened at your own company, and it costs you one search to find.

One number vs. a track record. This is where the episode turns on itself, and on purpose. Because the natural response to a framework this clean is to use it once — the week before your review, on three entries — and then never again.

That version mostly does not work. Not because the numbers are wrong, but because of what one number sounds like when it arrives alone. One number that appears the week before performance conversations reads as advocacy. It reads as somebody who went looking for ammunition, and the person hearing it discounts it accordingly.

Ten numbers, produced steadily over two quarters, read as something else entirely. They read as a person who tracks their own work, which is a character claim you cannot make about yourself and can only demonstrate. Nobody has to believe you about it. They just look at the record.

One number is a claim. A quarter of them is a track record.

This also matters because of where those numbers have to travel. Your manager is not your career sponsor (MAC-139) — the decisions that move you happen in rooms you are not in, made by people who have never watched you work. What crosses into those rooms is whatever your advocate can repeat from memory. "She's great with the new people" does not survive that trip. "She cut analyst ramp by half and the onboarding doc is reusable" does, because it is short, specific, and it has a number in it that somebody can defend on your behalf.

And this stops being a review-season skill fairly quickly. Walk into a salary negotiation with a one-page sheet of quantified wins, every one translated into hours, percentages, or dollars, and the conversation is structurally different. That sheet is not something you write the night before. It is a quarter of repricing passes, collected.

One more connection worth naming: in the Indispensability Ceiling (MAC-145), the episode described people who become so essential in place that they cannot be moved. Pricing your own glue work is the exit from that. The moment the value is expressed as a repeatable number rather than as you, it becomes something the organization can plan around instead of something it has to protect. That is the difference between being load-bearing and being promotable.

The episode also includes a survey ask — of the four metrics (turnover, ramp, rework, escalation), which one does your invisible work actually land on? If one runs away with the responses, it gets its own episode. The survey is at managingacareer.com/survey.

What changes and what stays the same. Nothing about the work you do is going to change this week. The mentoring, the unblocking, the quiet catch on a Friday afternoon — same work, same you, same amount of it. What changes is whether any of it arrives in a form the organization can weigh. Right now most of it arrives as an adjective, and adjectives get nodded at and forgotten. A number with its assumptions showing gets written down.

Helpful is a description of you. A number is a description of what the company would have paid without you. Only one of those makes it into the room. And the number that finally gets you promoted usually is not the first one you wrote. It is the eighth.

This episode follows directly from The Prevention Ledger (MAC-155), which gave you a system for capturing the problems you quietly stopped. The Prevention Ledger is the input; the Anchor Number repricing pass is how you make those captured entries legible to the people making decisions about your career. The Brag Document (MAC-141) built the habit of recording wins; this episode is about pricing those wins once you have them. Together they form a complete system: capture, price, deliver.

Get the Episode + Prompts

The full episode and show notes are at managingacareer.com/156. The prompts from the action plan are below — copy them, and change them to fit how you actually work.

Prompt — the estimate.

I need a defensible cost estimate for something I did at work that nobody measured. Here's what happened: [describe it plainly — what was heading for trouble, what you did about it, and roughly how many people, hours, or weeks were involved]. Work it in this order and show every step. First, tell me which single business metric this most plausibly maps to — employee turnover, new-hire ramp time, rework, or escalation cost. If it maps to two, pick the stronger one and say why. Second, name the unit I should be counting. Third, give me a published benchmark I could use to price that unit, and say plainly what kind of source it comes from. Fourth, lay out the arithmetic in full rather than handing me a total. Fifth, give me the result as a range and label your confidence in each input as high, medium, or low. Rules. Never phrase an industry aggregate as though it were my company's own figure — "the published benchmark is," not "your cost is." If you need an input I haven't given you, ask me for it instead of substituting a typical value. If two of your inputs are themselves estimates, say so and do not multiply them together into a third. Lead with the low end of the plausible range. And don't tell me the work was impressive — I need the number, not the encouragement.

Prompt — the sort.

Below are entries from my work log. For each one, tell me which of these four business metrics it most plausibly maps to: employee turnover, new-hire ramp time, rework/duplicated effort, or escalation/incident cost. If an entry maps to none of them, say "none" — do not stretch to find a fit. If it maps to two, name the stronger one and say why. Then rank the entries by how defensible a dollar estimate would be, not by how impressive they sound. Do not compliment the work. [paste entries]

Prompt — the sourcing pass.

I need baseline figures I can cite for four cost categories: employee turnover, new-hire ramp time, rework, and escalation cost. For each, give me a commonly published benchmark range and name the type of source it comes from. Flag clearly which figures are industry aggregates versus which ones I would have to get from inside my own company, and for the second group, write me the single specific question I should ask HR, finance, or recruiting to get it. Do not present a range as if it were a precise figure.

Prompt — the rewrite.

Turn the entry below into one or two sentences suitable for a performance conversation. Requirements: name the metric, show the arithmetic in plain language, and state every assumption inside the sentence itself rather than omitting it. If you need a number I haven't given you, ask me for it — do not invent it or substitute a typical value. Give me the conservative version, not the impressive one, and tell me which single input a skeptical manager is most likely to challenge. [paste entry]

Links & References

• Research & sources — Employee turnover cost statistics — replacement cost as a percentage of salary by role level
• Research & sources — Showing quantified value in salary negotiations — the one-page brag sheet
• Related Managing A Career episodes — The Prevention Ledger: How to Get Credit for the Problems You Quietly Prevented (MAC-155)
• Related Managing A Career episodes — Which Career Body Are You? A Self-Diagnostic from Asteroid to Star (MAC-152)
• Related Managing A Career episodes — The Indispensability Ceiling — How Being Irreplaceable Keeps You Stuck (MAC-145)
• Related Managing A Career episodes — The Brag Document: How to Track Your Wins All Year So You're Never Caught Flat-Footed (MAC-141)
• Related Managing A Career episodes — Your Manager Is Not Your Career Sponsor (MAC-139)

TAKE THE SURVEY!

Are you looking for a career coach? If you reach out to me via the contact form, I will arrange an introductory session where we can talk about your career goals and how I can help. If we're a good fit, we can schedule regular coaching sessions.