The Performance Tax
There's a quiet cost line on every People budget that nobody puts in the spreadsheet. It doesn't show up as software spend or headcount. It shows up as the slow degradation of the thing your survey vendor was hired to measure.
We call it the Performance Tax.
Every act of measuring engagement extracts a small toll from the employee's willingness to engage honestly. Every monitoring dashboard that tracks "active hours" signals that the relationship is one of control, not trust. Every HRIS field that asks "career goal" without giving the employee anything in return treats the employee's career as an organizational input, not their own life.
None of these systems are evil. Most are run by sincere people trying to improve the workplace. The tax isn't a design flaw — it's a structural property of any system where the company extracts information about the employee without giving the employee something back.
What the literature actually says
The economics literature has been clear about this for thirty years. Bruno Frey argued in 1993 that monitoring crowds out intrinsic motivation by signaling distrust. Falk and Kosfeld confirmed it experimentally in 2006 — when principals chose to control agents, those agents responded by working less hard than the unmonitored control group, not more. The subsequent management literature (Jeske & Santuzzi, Ravid et al.) finds close, continuous, individual-level monitoring is associated with lower job satisfaction and affective commitment, with effects worsening when the monitoring is unpredictable or used to discipline.
The mechanism is Self-Determination Theory. As felt autonomy shrinks, intrinsic motivation drops. Employees redirect energy from doing meaningful work to looking busy and satisfying metrics. The thing you're measuring — engagement — degrades because you measured it.
This is the Performance Tax stated in academic register. In English: the closer your engagement system feels to surveillance, the less engaged your people become. The signal you read from the dashboard is partly the engagement, and partly the response to the dashboard.
Why your engagement survey runs the same tax
The engagement survey looks like the opposite of surveillance. It's anonymous (mostly), it's quarterly or annual (not continuous), and it asks employees what they think. Surely that's the safe end of the spectrum.
It is — relative to keystroke logging. But the underlying transaction is the same: the company extracts information about how the employee feels in order to make decisions about the company's programs. The employee gets, in return, a results email two months later with a few colored bar charts and a pledge to "double down on what's working." Then the cycle repeats.
That's why surveys decay. Year one, response rates are high and answers are honest. Year three, response rates are 60% and the answers reliably correlate with whichever team's manager is up for promotion review. The instrument hasn't changed. The relationship has. Employees have learned the survey isn't theirs.
This isn't a critique of survey vendors. The survey is the contract: company asks, employee tells. The Performance Tax is what that contract costs over time when nothing flows back.
The asymmetry that matters
Every measurement program has a buyer and a subject. The buyer is the company. The subject is the employee. The buyer gets a dashboard. The subject gets a survey reminder in their email.
Now consider the inverse: a program where the employee is the buyer of their own data. They capture their own wins, work through their own challenges, draft their own weekly reflection, and prepare their own 1:1 agenda before the conversation. The company sponsors the seat. The company sees that the seat is active, on which team, how many employees on that team have used it this week. The company does not see what's in it.
In this version, the employee gets value from the act of recording: they walk into their 1:1 prepared, they remember what they did when promotion season comes, they have an early read on their own engagement before anyone else does. The company's read is reduced to aggregate metadata — but in exchange, the underlying data is honest, because the employee has every reason to record it accurately.
This is the Performance Tax in reverse. By giving up the company's right to read individual content, you buy back the integrity of the signal you do get.
What this looks like in practice
A People function reorganized around this principle stops trying to read the employee directly and starts measuring whether the employee is engaging at all. The metrics become:
- Seat activity: how many seats logged a reflection, captured a win, or built a 1:1 agenda this week?
- Reflection cadence: what proportion of seats reflect weekly vs. monthly vs. never?
- Open-loop closure rate: are the things employees raise getting resolved, or piling up?
All aggregate. All team-level. All gated so teams under five active members are not reported (to prevent inference about specific individuals).
You learn whether the program is working. You don't learn what any specific employee said. And because the employees know that, they actually use the workspace honestly — which means the aggregate metrics become a real signal instead of a performative one.
The skeptical objection, and the honest answer
The objection from a research-literate HR leader is the right one: "If I can't see individual content, how do I detect problems before they become attrition?"
The honest answer in two parts. First, the things you can see — adoption pattern, reflection cadence, open-loop closure rate, individual last_active_at — are early signals that pick up most of what an engagement survey would catch, six months sooner, and without the survey tax. Second, the things you cannot see were never things you should have been seeing. The employee who's quietly preparing to leave was never going to tell that to your survey honestly; what they will do is stop writing weekly reflections. That signal shows up before the resignation email.
The trade is real. You give up theoretical visibility into content. You get back real visibility into behavior, plus an employee population that trusts the program enough to use it.
What the pilot measures
The literature underwrites the theory of change: autonomy and visible progress drive engagement; surveillance erodes the motivation it measures; structured reflection improves performance; the manager conversation is where variance actually lives. None of that proves that this specific product, in your specific org, pulls those levers as designed.
That's what the pilot is for. A six-month pilot with one team gives you adoption data, reflection cadence, open-loop closure rate, and qualitative read from the employees themselves about whether the privacy guarantee is doing what it says. We are not selling a proven outcome. We are selling a well-founded bet that you can test, in your environment, with your people, before any commitment to scale.
That's the only honest sales pitch for a product like this — and it's the only kind that survives contact with a research-literate buyer.
How Nela Helps
Use Nela to log your wins, track your challenges, and build a private 1:1 agenda from your own evidence for your next conversation. Your data is owner-only at the database — enforced by Postgres Row-Level Security, not just hidden in the UI — and only you can read it back through the app. Request pilot access.
Further reading
- Frey, B. S. (1993). "Does Monitoring Increase Work Effort? The Rivalry with Trust and Loyalty." Economic Inquiry.
- Falk, A., & Kosfeld, M. (2006). "The Hidden Costs of Control." American Economic Review.
- Ravid, D. M., Tomczak, D. L., White, J. C., & Behrend, T. S. (2020). "EPM 20/20: A Review, Framework, and Research Agenda for Electronic Performance Monitoring." Journal of Management.
- Deci, E. L., & Ryan, R. M. (1985). Intrinsic Motivation and Self-Determination in Human Behavior.
Share this post
Related posts
Most People-tech pilots optimize for the wrong signal. A six-month checklist for evaluating an employee-owned workspace honestly, written from the vendor side.
New hire success in the first 90 days correlates strongly with who their manager happens to be. That's a structural problem your onboarding program can address — by changing what the new hire owns, not what the manager does.
After Google's Project Aristotle made psychological safety famous, it became something HR put on the wall. The structural enabler is somewhere else entirely.
Get new posts in your inbox
Career growth insights. No spam. Unsubscribe anytime.