AI Leadership Principles / Adoption

Should we mandate AI use or tie it to performance reviews?

A clear expectation can help, but only if it comes with tools, training and time. Assess the outcomes and quality of people’s work, not logins or usage counts. Let teams decide how they use AI, and share good examples openly.

Why it matters now

Some well-known companies now expect AI use as a baseline and include it in reviews. I understand the intent: end the debate and get everyone moving. But a mandate without support breeds resentment, and measuring usage invites people to perform it rather than benefit from it. The expectation should be about better work, not more prompts.

Common mistakes

  • Measuring usage counts and seats instead of outcomes, which invites performative use.
  • Mandating AI without providing tools, training or time.
  • Prescribing exactly how every team must use it.
  • Rewarding visible enthusiasm rather than better results.

What to do instead

  1. Set the expectation clearly. Say that you expect people to try AI in their work, and explain why.
  2. Pair it with support. Provide approved tools, training and protected time before you expect anything.
  3. Assess outcomes, not activity. In reviews, look at the quality and impact of the work, and how people improved it, not how often they logged in.
  4. Let teams own the how. Teams know their work best. Let them decide where AI helps and where it does not.
  5. Share good examples. Regularly show real uses that improved the work, including small ones.

Your first step this week

Before setting any mandate, check three things for one team: do they have an approved tool, have they had hands-on training, and do they have time to learn? Fix whichever is missing first.

All AI leadership principles and guides · 100 AI use cases by function

Sources

Want to work through
this with your team?

I help leadership teams make these decisions and turn them into working systems, as a fractional or interim AI leader.

The AI Impact Sprint ↗