learn-okr-with-phoebe / Leader session 5 of 6
Learn OKRs with Phoebe · Leader track · Session 5 of 6

AI in measurement: helper, not judge

AI arrives in performance management dressed as efficiency: summarise the feedback, score the productivity, rank the team. Some of that is genuinely useful and frees managers to coach. Some of it crosses a line into surveillance that the law now treats as high-risk. As the leader who signs off the tools, you set which side of that line your organisation lives on. This session gives you the distinction (support vs surveillance), the three regulatory gates every tool must clear, and the principles to hold - so AI stays a helper and a human stays accountable.

🟠 Leader track Leaders: C-level · upper mgmt No code · concepts + decisions 45 minutes
0-3 · Recap 3-18 · Support vs surveillance 18-42 · Governance + the cautionary cases 42-45 · Q&A
Part 0

The question a leader actually has to answer

Not "should we use AI in performance management" - you already are, the moment a review tool suggests wording or a dashboard summarises feedback. The real question is narrower and sharper: what are we letting AI decide, and what are we only letting it help with? Get that boundary right and AI gives managers back the hours they were spending on admin, and makes feedback fairer by catching bias a tired human misses. Get it wrong and you have built surveillance that the EU classes as high-risk, that New York already audits, and that the UK regulates through data-protection duties - and that quietly destroys the trust every other session of this course was trying to build. Tonight is about drawing that boundary on purpose.

Live - presented in session Self-study - read after class ★ Walk-through Sources covered (cited)
★ What you walk out with today A clean split between what AI can legitimately do (summarise, de-bias, draft, surface progress) and what it must never do (surveil, score, rank, auto-fire); the three governance gates - EU AI Act, GDPR Article 22, NYC Local Law 144 - that every tool must clear; and a six-principle test you can apply to any AI measurement tool a vendor puts in front of you.
Rail before we start This is awareness, not legal advice. Regulations move fast and differ by jurisdiction. Use this to ask your vendors and your counsel the right questions - not as a compliance sign-off.
Part 1 · the line

Support augments the manager; surveillance replaces judgment 7 min live

The same technology sits on both sides of the line. The difference is not the model - it is whether the output informs a human who then decides, or becomes the decision about a person. Everything on the left frees a manager to spend more time coaching. Everything on the right measures activity and calls it performance.

The line: AI can support the manager, it must never become surveillance AI as helper (support) AI as surveillance (do not) Summarise + aggregate 360 feedback Flag biased or vague review language Reduce recency bias via continuous notes Draft feedback for a human to edit Surface goal progress at a glance Free manager time for real coaching Keystroke + screen logging Per-person "productivity scores" Automated ranking of people Auto-firing on a proxy metric Measures activity, not value - and the law calls it high-risk. AI may inform a decision about a person; a human - never the tool - must own it.
🔍 Click to zoom - support informs a human; surveillance replaces one
LiveWhy the "helper" list is genuinely worth having3 min▶

The left column is not a consolation prize - done well, it makes measurement fairer than a human alone:

  • De-biasing language - a model can flag that a draft review calls a woman "abrasive" and a man "assertive" for the same behaviour, or that feedback is vague ("great attitude") rather than specific. It catches what a rushed manager misses.
  • Fighting recency bias - by summarising notes gathered all quarter, AI stops the whole review collapsing into "what happened last week".
  • Giving time back - drafting and summarising is the admin that eats the hours managers should spend actually talking to people. Automate the paperwork, not the judgment.
Real world

The test that sorts the two lists. Ask of any feature: "if this output is wrong, who catches it before it affects a person?" If the answer is "a manager reviews and can overrule it," it is support. If the answer is "the system acts on it directly," it is surveillance wearing an efficiency badge - and it belongs on the right.

Part 2 · the three gates

The governance a leader must know 6 min live

You do not need to be a lawyer, but you do need to know that measuring workers with AI is now one of the most regulated things software can do. Three rules matter most. Treat them as gates: an AI measurement tool that cannot clear all three should not go near your people.

Every AI measurement tool must clear three gates EU AI Act Annex III, section 4 AI for worker management is classed HIGH-RISK. Needs risk controls, logging, human oversight. GDPR Article 22 human-in-the-loop No SOLELY automated decision with a significant effect. Needs real human review, and it must be contestable. NYC Local Law 144 bias audit Automated hiring / promotion tools need an independent bias audit, published, with notice. Awareness, not legal advice - fast-moving law; consult counsel before you deploy.
🔍 Click to zoom - EU AI Act, GDPR Article 22, NYC Local Law 144
Self-studyWhat each gate is really protecting3 min read▶
  • EU AI Act - lists AI used for recruitment, task allocation, and monitoring or evaluating workers as "high-risk" (Annex III, section 4). High-risk does not mean banned; it means obligations: risk management, data governance, logging, transparency, and meaningful human oversight. If a vendor cannot show you these, that is your answer.
  • GDPR Article 22 - a person has the right not to be subject to a decision based solely on automated processing that has a legal or similarly significant effect (like firing or denying a promotion). The safeguard is a genuine human-in-the-loop who can review, explain, and reverse - plus the person's right to contest.
  • NYC Local Law 144 - automated employment decision tools must pass an independent annual bias audit, publish a summary of the results, and give candidates at least ten business days' notice before the tool is used on them. It exists because these tools were quietly encoding discrimination.
The one question that clears most of this "Show me where a named human reviews the output, can overrule it, and where the affected person can contest it." If a tool has no such point, it fails all three gates at once.
Dates and jurisdictions, as of August 2026

Regulation moves, so hold these loosely and check them before you rely on them. EU: the Annex III classification stands, but the AI Omnibus (in force 27 July 2026) pushed the compliance duties for standalone Annex III systems from 2 August 2026 to 2 December 2027. You have design time, not a pass. New York City: Local Law 144 is already live, in effect since January 2023 and enforced since July 2023. UK: there is no AI Act and no high-risk classification - worker-management AI is governed through data-protection duties (UK GDPR, ICO guidance), and the Data (Use and Access) Act 2025 replaced the near-prohibition on solely automated significant decisions with a safeguard-led regime. So if your organisation spans the EU and the UK, the same tool sits under two different rulebooks. None of this is legal advice; it is what to ask counsel about.

Walk-through 1 of 2

Two cautionary cases, read as a leader ★ 10 min · think it through

Both companies were sophisticated and well-resourced. Both crossed the line anyway - which is exactly why you cannot delegate this decision to a procurement checklist. Walk each one back to the boundary from Part 1.

Microsoft Productivity Score (2020). A feature let managers see per-employee activity - emails sent, chats, document edits, meeting attendance. Critics called it workplace surveillance; after public backlash Microsoft removed the individual-level view and apologised.

Amazon warehouse "time off task" (reported by MIT Technology Review). Systems tracked idle time and, per reporting, could generate warnings and terminations largely automatically - people managed by an algorithm measuring seconds.

Locate each on the Part 1 line. Both sit firmly on the right: per-person activity scores, and automated action on a proxy - with the human either absent or reduced to a rubber stamp.

Ask the diagnostic question: did the metric measure value delivered, or just activity observed? In both cases, activity - which is precisely what Goodhart's Law tells us people will then game.

The same story, told two ways
Design choiceSurveillance framingSupport framing
Unit of measurethe individual, rankedthe team + the workflow
Who acts on itthe system, automaticallya manager, accountably
What is measuredactivity (keystrokes, idle time)outcomes + blockers
The person can...nothing - it is opaquesee it, question it, contest it
The technology was similar in each column. The design choices - and the leadership behind them - are the whole difference.
Walk-through 2 of 2

Audit your own AI touchpoints against six principles ★ 8 min · your org

You almost certainly have more AI in your performance stack than you think - in the HRIS, the review tool, the recruiting funnel, the productivity dashboard. Take each place AI touches how people are measured and run it through the principle set.

List every point where AI touches performance or measurement - drafting reviews, summarising feedback, scoring candidates, ranking, flagging activity, monitoring.

For each, test the six principles: augment not replace, transparency (people know it is used and how), contestability (they can challenge it), human accountability (a named person owns the decision), measure outcomes not surveillance, and proportionality (the least intrusive method that works).

Flag any touchpoint that fails augment-not-replace, transparency, or contestability - those are the three that also map to the legal gates.

Real world

Proportionality is the quiet one. Even if a monitoring tool were legal and transparent, ask whether you need it at all. If a weekly outcome conversation would tell you the same thing as continuous keystroke logging, the logging is disproportionate - and every hour of it is a withdrawal from the trust account. The most defensible answer is often to measure less, and talk more.

Homework

Try it yourself - this week ◐ 30-45 min total

Source material

Sources covered (cited)

Taught from the AI-governance and worker-measurement canon. This session covers:

✓EU AI Act (Annex III, sec. 4); GDPR Article 22; NYC Local Law 144Part 2 · the three governance gates for AI worker measurement
◐Microsoft Productivity Score backlash (2020); Amazon warehouse "time off task" (MIT Tech Review)Walk-through 1 · surveillance cautionary cases
Check yourself

Three questions before you go 🎯 ◐ 90 seconds

1 · What separates AI as support from AI as surveillance?

Same technology, different design. If a manager reviews and can overrule the output, it is support. If the system acts on a person directly, it is surveillance - and the law now treats that as high-risk.

2 · What does GDPR Article 22 require for a decision with significant effect on a person?

Article 22 protects people from purely automated decisions like firing or denying promotion. The safeguard is a genuine human who can review, explain, and reverse, plus the person's right to contest.

3 · The Microsoft Productivity Score and Amazon "time off task" cases both went wrong because they...

Both measured per-person activity rather than value delivered, and removed or minimised the accountable human. That is the surveillance side of the line, and exactly what Goodhart's Law predicts people will game.

Leader session 5 cheat sheet · pin this

Support vs surveillanceinforms a human who decides = support; becomes the decision = surveillance.
AI can helpsummarise 360s, flag biased language, cut recency bias, draft, surface progress, free time.
AI must notkeystroke-log, "productivity score" people, auto-rank, auto-fire on a proxy.
EU AI Actworker-management AI = HIGH-RISK (Annex III): oversight, logging, transparency. Duties apply 2 Dec 2027.
GDPR Article 22no solely automated decision with significant effect; real human-in-the-loop, contestable.
NYC Local Law 144independent annual bias audit, published summary, 10 business days' notice. Live since 2023.
Six principlesaugment not replace, transparency, contestability, human accountability, outcomes not surveillance, proportionality.
Next sessiona6 - rollout, cadence, and the culture that makes measurement work.