The Unmeasured Advantage

Two teams presented at the same budget review. The data team went first. Their manager put up a backlog counted at 214 items, a rerun rate tracked weekly, and two risks named with dollar figures attached. Then the questions started, and they did not stop for half an hour. Why is the backlog at 214? What is driving the reruns? Are the two risks under control? Fair questions. Necessary ones. The manager had answers, and a few of the answers were “we don't know yet,” said plainly, on the record.

The team next door went second: a roadmap, a timeline, and a slide titled “On Track.” Ten easy minutes. A few nods, one question about dates. No numbers came up, because no numbers were on the wall. Both managers walked out with their asks still in play. Only one of them walked out tired.

The first deck took three quarters of work to become possible. The team built the intake queue, started tracking its reruns, published its quality number, and put its own misses on the record. Leadership asked for visibility. This team delivered it. And every hard question in the room found it, because the second deck held nothing a question could grab.

The review compared one team's numbers to another team's benefit of the doubt.

The blank page won.

A named risk can be questioned: escalated, discounted, held against you. An unnamed risk cannot. It does not read as danger. It reads as fine. So the team with an honest list of its own problems looks like the team with problems, and the team with no list looks healthy. Not because it is. Because nothing says otherwise.

Honest empty boxes beat quiet names: that was the last piece's argument, inside a single map. This piece is about what happens when that honest map sits next to a neighbor's quiet one. What holds up inside a team turns into a handicap between teams. Visibility gets priced team by team, and the first team to pay full price ends up covering for every team that doesn't. That extra share never shows up on paper. It gets paid in harder questions, longer defenses, and trimmed asks, and it goes to whoever kept their numbers to themselves.

The version of this that shows up most often is small. A manager publishes a quality number because publishing it was the right call. Two review cycles later, the number shows up in someone else's slide as proof the team is struggling. The manager spends twenty minutes of a budget meeting defending a figure nobody made them share. They defend it well. The ask still gets trimmed. And somewhere on the drive home, a question forms: should we keep publishing that number?

That question is the real event. Not the meeting. Up to that point, honesty was the team's default: automatic, unexamined, just how the team ran. After it, honesty is a decision, weighed each quarter against what it cost last quarter. An organization can survive one team doing that math and still choosing to share. It cannot survive teaching every team to do the math, because the math only comes out one way.

What follows looks like nothing. Estimates arrive with a little more padding. Status language drifts from numbers to adjectives: “trending well,” “mostly stable.” A dashboard misses an update, then another, and nobody can say when it stopped being current. The next capability map has fewer boxes than the last one. No one wrote a memo. No one changed a policy. No one even argued against being open. The organization taught the lesson one review at a time, to the exact people who were best at being open. The lesson lands easily because the fear is already there: in one well-known study of employee silence, 85 percent of people said they had faced an issue they believed was important and felt unable to raise it with a supervisor. The most common reason was fear of how it would make them look.

Give it a year and the reviews themselves improve. Decks get tidier. Backlogs shrink on paper. Fewer risks get raised, and the ones that do arrive come pre-softened. Meetings run shorter, everyone leaves on time, and the distance between what leadership sees and what is actually happening grows a little each cycle. It looks like maturity. It is a room full of people who learned.

None of this needs a villain. The executive pressing the visible deck is doing the job right: you ask questions where answers exist. The team next door is not scheming; it got its tooling later, or never had the people to build the tracking, or simply never volunteered, and nothing in the process asked it to. The failure is structural. Measurement arrived one team at a time, and the comparisons ran as if it had arrived everywhere at once.

The obvious answer is to measure everyone and be done with it. True, worth pursuing, and years away in any real organization. Rollouts happen in order. Some team is always first. The in-between years are how every rollout actually runs, and no organization gets to skip them. Anything that begins “once everyone is measured” is a plan to lose the most honest teams first.

What actually helps in the meantime is smaller, and most of it belongs to whoever chairs the review. It starts with a sentence, said out loud before any teams get compared: these numbers exist because this team measured; that blank exists because that team has not yet. Ten seconds. And everything after it lands differently, because the data team's 214 stops being a mark against them and becomes proof of work the other team has not started.

Timing carries most of the rest. A team that spends two review cycles as the only measured one in the room has spent enough. After that, if the neighbors still cannot show numbers, the fair comparison is the team against its own trend line, not against silence. And the people who went first deserve to be named as first, in the same decks that carry their numbers. One line under the chart: self-reported, published by the team, third cycle running. A risk a team told you about is not the same as a risk you dug up. It can be asked about. It should never be quoted back as evidence against the team that raised it.

None of this is free. Reviews run longer. The clean side-by-side ranking everyone wanted stays off the table until the field actually levels. Steering decks look less decisive, and leadership sits with not knowing which team is really healthier. Good. That not-knowing was always there. The only question was whether it sat with leadership or got billed to the one team honest enough to show it.

Teams stop doing what costs them. Being open is the fastest case of that rule.

This week, look at one cross-team review you sit in. Find the team whose risks everyone can name and the team whose risks no one can name. Then check which one got the harder questions last cycle. If it was the team with the numbers, your organization is charging extra for honesty, and that team is learning the price.

Sources

Milliken, F. J., Morrison, E. W., & Hewlin, P. F., exploratory study of employee silence (research summary: Institute for Public Relations, instituteforpr.org/employee-silence-and-upward-communication).