Your managers can't tell who's performing anymore


Read on my website

In Q4 of last year, an HR leader I know attended a tense performance review meeting. One engineering manager wanted to give an employee an 'exceeds expectations' rating because their output had doubled.

Another manager disagreed, pointing out that the increase was just from using ChatGPT, while the employee's poor design choices had caused two production errors.

Because the team lacked a framework to resolve this kind of conflict, the discussion quickly broke down into an argument about fairness.

If you haven't faced this situation yet, you will soon. In an AI-driven workplace, performance reviews often turn into arguments your current goal system can't solve.

I recently published a four-part framework covering outcomes, verification, judgment, and capability in this article.

In this edition, I'll focus on how to guide your team through the goal-reset process in the AI era.

Both Managers Are Right and That’s the Problem

Most performance disputes moving forward will boil down to the same issue: your goals measure output volume, but AI has taken over most of that work.

One manager looks at the numbers while the other looks at the decisions behind them. Both are right, yet they are describing the same employee.

Until the goals change, you will keep settling disagreements that have no correct answer in your current performance system.

Stop trying to resolve these disputes during the review cycle. You cannot fix a broken measurement system through calibration.

Instead, acknowledge that your current system is transitional, document where the goals failed, and use that data to drive your reset.

The Reset Is a Change Program, and You Own It

Rolling out new goal categories is simple; managing the change is hard. When you reset targets, your team will worry that you're just raising the bar to justify layoffs. In today's climate, that's their default assumption.

Here is how to handle it:

  1. Be honest about the goals. Before moving targets, leadership must clearly state what AI productivity gains will fund: whether that’s growth, new projects, profit margins, or headcount changes. If the goal is headcount reduction, be upfront. It is better to own the message than to have it leak.
  2. Be transparent about measurement. Tell teams you are tracking AI-assisted output to set a baseline. More importantly, promise that this data will not impact current performance ratings. If you announce this after the fact then it feels like surveillance.
  3. Give managers a clear script. They will handle these resets in 1:1 meetings. Don't leave them to improvise. Provide a simple guide explaining what changed, why it’s happening, what the employee gains, and how raises and promotions work now.
  4. Share the gains fairly. If team capacity rises by 30%, don't raise targets by 30%. Raise them by 15% and dedicate the rest to quality and complex work. If you adjust targets, update pay and bonus thresholds, and roll them out on the same day. Your team will do the math immediately, so make sure the changes look fair from the start.

What This Does for Your Seat at the Table

Do this right, and you’ll earn more credibility than any other project you deliver this year.

You’ll head into executive meetings armed with role-specific productivity data that no one else has.

You’ll know exactly who is worth promoting. And when the board asks how AI is affecting your output, you’ll have a clear, evidence-based answer.

This changes the conversation during headcount planning, allowing you to make strategic decisions about funding growth rather than just making reflexive cuts.

Action Items for This Week

  1. Audit your goals. Ask: "If AI did 80% of this work, would this goal still capture the person's value?" Bring the goals that fail this test to your next leadership meeting.
  2. Identify your pilot group. Ask managers to point out employees whose performance has become difficult to measure. Use these roles to test the new framework.
  3. Prepare your managers. Draft a simple guide explaining the changes before you announce anything to the wider team.
  4. Run a test audit. Download the AI-Era Goal-Setting Worksheet and audit one team this month.

That’s it for this week. If you are in the middle of a reset and hitting roadblocks, just hit reply and let me know where you are stuck. I read and respond to every email.


New Podcast Episode

Ep. 51 - How Founders Sabotage Their Own HR Efforts

show
Ep. 51 - How Founders Sabota...
Jul 28 · Organized Chaos
18:17
Spotify Logo
 

People problems are behind 65% of startup failures, and founders cause more of them than they'd like to admit. In this episode, I break down the 5 behaviors that lead founders to sabotage their own HR efforts. You'll walk away knowing which of these behaviors you or your founder is guilty of and the 5 steps to reverse them.

Listen on your favorite podcast app or read the episode summary here.

Whenever you’re ready, here's how I can help you:

  • Need someone to build or revamp your HR infrastructure for you? The HR Sprint is a 12-week engagement where I diagnose, build, and deploy your entire people operations system — recruiting, onboarding, performance, policies, and tech stack — then hand it over to your team fully operational or run it for you.
  • Want to build your HR infrastructure yourself? The Startup HR Operating System is my complete course for HR professionals. Playbooks, templates, and expert masterclasses covering everything I've learned scaling people ops over 15+ years.

Organized Chaos

I help 7-figure companies become 9-figure ones by turning HR into rocket fuel for their growth. Subscribe to my free bi-weekly newsletter to learn how.

Read more from Organized Chaos

Read on the website The last two editions of this “layoff analysis” series covered Block's 40% cut and Atlassian's 1,600-person restructuring. Both generated incredible feedback and conversations, so I'm keeping this going. This time, Snap is in the hot seat. If Block was a story about overhiring and Atlassian was a story about a broken cost structure, Snap is something worse: a company that keeps making the same workforce planning mistakes over and over again, repackaging each round with a...

The last edition, where I broke down the real reasons behind Block's layoffs, got a lot of great feedback and a few of you reached out asking me to keep going with this kind of analysis. So here we are. This time, Atlassian is in the hot seat. Like Block, Atlassian is not a startup, but the lessons buried in what happened there are directly relevant to anyone building and scaling a team right now. If anything, the Atlassian story hits closer to home for HR and people ops leaders because it...

Everyone Is Blaming AI for Block's 40% Layoff. The Data Tells a Different Story. I'm sure you've heard this news by now. Jack Dorsey cut more than 4,000 employees from Block, taking the company from over 10,000 people to just under 6,000. I wasn't planning on writing about this, but the conversation on LinkedIn and elsewhere has been dominated by fear, hot takes, and very little actual analysis. So I decided to dig into the data and share what I found, because the story the numbers tell is...