The boards I explain at.

What your M365 dashboard shows: active users, prompts, feature usage. Necessary, not sufficient. Many organizations report strong activation while actual adoption sits far below it.

The level most programs skip — and the one that predicts everything downstream. Visible in three shifts per persona: frequency, quality, elimination.

Where the outcomes live: win rate, throughput time, quality rate, reaction time. Credible only once levels 1 and 2 are documented.

If the capability can run inside an existing, governed context — a person's Copilot, an existing system — it's a skill. Identity is the single most expensive property an agent has.

Instructions, checklists, methods and prompts that a human executes are plays. Autonomy is what makes a player — and what requires a contract, a roster spot, and a coach.

Every agent needs an owner, a lifecycle, monitoring and a shutdown path. If nobody will own it in twelve months, don't give it an identity today.

A skill travels: same play, many players, near-zero marginal cost. An agent multiplies obligations with every copy. That's exactly where the forty-agent graveyard comes from.

Without a stable base, you get injured under load. Individually that means: the core habits stick. Organizationally: permissions, data hygiene, and a baseline that shows how work happens today.

Bad technique under weight is more dangerous than no training. Individually: picking the right working mode per task. Organizationally: managers who use AI visibly and set standards — the biggest lever in the whole program.

Now weight goes on the bar. Individually: delegating real tasks to agents and reviewing like a coach. Organizationally: registry, identity and ownership, so the load doesn't become debt.

This is the stage where most programs fail — not on knowledge, on consistency. Individually: keeping the rhythm when daily business pushes back. Organizationally: a learning system that turns local wins into institutional capability.