Stop Measuring People. Measure Flow: Why Surveillance Metrics Backfire (and What to Track Instead)
If your metrics make people feel watched, you will get “good numbers” and bad truth. Fear makes smart adults hide problems, soften bad news, and aim for what looks safe. That is why surveillance-style measurement often creates more noise, more rework, and less real progress.
A better way is simple: stop measuring people and start measuring flow, the work moving through your system. As Dr. W. Edwards Deming warned, “We need to drive fear out of the workplace,” and “Make sure metrics…are being used to drive improvement; avoid using them as a weapon.” When leaders measure the process first, teams get calmer, clearer, and faster.
The common belief: “If I can see who’s busy, I can manage performance”
Picture a Friday staff meeting where new “special projects” keep piling up. People feel pressured to say yes. Priorities are fuzzy. Work restarts. And the leader feels a quick hit of relief after handing something off, even though the team is “energy draining for everyone.”
In that moment, it’s tempting to tighten control.
So leaders reach for metrics that are easy to count:
- activity counts
- status updates
- “how many did we do?”
- reports that try to prove effort
But the harm is not the act of measuring. The harm is what the measurement is used for.
When people think a number will be used to blame them, the safest move is to protect themselves. Deming called this out directly: when leaders focus on “someone…to ‘blame’ it causes people to game the system and to point their fingers elsewhere when problems arise.”
A hard truth: a metric can become a mask. It can hide the real story while still looking “accountable.”
What surveillance metrics trigger: silence, finger-pointing, and “invisible” work
In office work, especially, measurement often feels personal. The provided material says it plainly: “People being observed feel threatened…they are not used to being measured publicly and wonder what will happen as a result (it couldn’t possibly be good).”
And once fear is in the room, three things happen fast:
1) Bad news gets delayed
Isao Yoshino, a retired Toyota leader, taught a simple rule: “Share bad news first, no problem is a problem.”
That line sounds small, but it flips the room. If bad news is safe, problems surface early, when they are cheaper to fix.
2) Leaders chase the visible, and miss the real constraint
Some of the most important blockers in office work are hard to see. The material calls this out: “Capacity to do work is typically invisible in an administrative environment.”
If you don’t make capacity visible, you can accidentally reward overload and punish honesty.
3) Work breaks at the handoffs
Rummler and Brache called it “managing the white space,” the gaps between departments. The handoffs are where work often goes wrong.
People-tracking does not fix handoffs. Clear flow metrics can.
The better mental model: measure the process first, then coach people inside it
A calmer, stronger question is: What in our process is making it hard to win?
The material offers a clear ratio to keep leaders grounded: Deming said “85% of all performance problems…are related to the processes being used by the business, only 15% are related to the individual.”
This does not mean individuals never matter. It means your first move should be to look at the system.
That is also why visual performance is so powerful when it’s done with the right intent. The purpose is not control. It is shared reality. Good visuals create what one leader called “information democracy,” they “eliminate filters that obscure knowledge between layers of management and between departments.”
If you want a team that solves problems without being forced, give them clear reality and a safe room to respond to it.
What to track instead: flow metrics that make problems easy to see (and safer to fix)
The material draws a sharp line: most traditional metrics are “lagging indicators (after the fact), and…activity counts.” They tell you you have a problem, but they rarely drive improvement early.
So what should you track?
Start with flow and process drivers, not individual output.
1) Capacity and workload (make the invisible visible)
Ask the questions the material recommends: “Is there a backlog? Do people continue to give you work even though you cannot handle it?”
You can make this simple, a visible list of incoming work vs. available time or slots.
2) Backlog and delays (what is not getting started)
In the Martha story, the team agreed to surface delays directly: people were expected to share “If a Task/Action was delayed in getting started,” and “If they needed help.”
That is flow. It shows where work is stuck before it turns into a scramble.
3) Rework and redo loops (work that comes back)
The material suggests watching for “a rework/redo/additional requirements type problem.”
Rework is a signal of unclear expectations, missed customer needs, or weak handoffs, and it is a better improvement target than pressuring people to “go faster.”
4) Lead time and cycle time (how long work takes end-to-end)
The material lists classic flow measures: “Lead time from start to finish,” and “Cycle time…aka the bottleneck.”
These metrics expose the constraint without shaming a person.
5) Cross-functional handoffs (the “white space”)
If handoffs are where work breaks, measure what crosses boundaries. Public visuals help here because both the suppliers and customers of the work can see the same facts, and “if anyone disagrees with the data, a conversation can take place to clarify or correct the information.”
One quick filter before you choose any metric: the material asks if it is timely, understood, credible, and fair, then warns against a “laundry list of 20 or more items.” Focus on “a handful of metrics that drive improvement.”
Here’s how you do it: create a simple visual that builds trust instead of fear
The strongest change is not a new dashboard. It is a clear purpose and a team-built visual.
Use this practical checklist from the material:
Step 1: Write down the purpose (so it doesn’t turn into control later)
The material says to think ahead about “WHY you should publicly post metrics. Write it down.”
If your purpose is improvement, say that out loud.
Step 2: Build the visual with the people doing the work
“Involve the people on your team, share an initial purpose for creating a visual reporting tool.”
Ask them, “What decisions might this visual drive?” because that part matters.
Step 3: Keep it fast to update, and easy to read
The material offers three rules that save you from a useless board:
- Update in under 10 minutes if daily (or under 3 minutes if multiple times a day)
- Spot the key issues in under 10 seconds
- Do not make it complicated
Step 4: Try it for a week, then adjust
“Try it for a week, a month, or a quarter…evaluate what is happening…Continue to use and evolve.”
This matters because you will not get it perfect at first, and that is expected.
Step 5: Make “bad news first” a team habit
When you make it safe to share bad news, you “decrease fear.” Then ask, “What did we learn from this?” and “What are we doing as the next step?”
That is how metrics become a tool for learning, not a weapon.
The goal is not more control. The goal is clearer reality, shared ownership, and fewer hidden problems. Start measuring flow, and you give your team something rare at work: the sense that the truth is useful, and safe to say out loud. What would change in your team if the first question was always, “Where is the process making this hard?”