From User to Operator·Integration·10 min

Rollout: One Thing, 90 Days

Roll out the one thing that worked. Not everything at once.

Goal

You pick the single drill that gave you the most value — and build your team’s 90-day rollout around exactly that.

Why this matters

Here’s where most leaders blow it: they finish their own learning curve, get excited, and drop six new behaviors on the team at once. It overwhelms people, nothing sticks, the program stalls — the adoption gap, manufactured on purpose. One proven win, rolled out well, beats six unproven ones rolled out at once.

The drill

Build the 90-day plan around your one thing:

  1. Month 1 — you and your champions. You and two or three early adopters run the base habits and your one proven agent or workflow. Small group, real reps, work out the friction before anyone else sees it — you already know the friction, because you hit it yourself.
  2. Month 2 — your team’s Day-in-a-Life. Widen it. Run the week-2 mapping exercise with your team, by role. Help each person find their own top five and their own first win. Don’t hand them your map — help them build theirs.
  3. Month 3 — governance and outcomes. As real usage grows, get serious about two things: what’s running in your environment (the agents your people are now building — this is where your tenant’s agent governance and data protection tooling earns its place), and what changed, measured as outcomes by role — the proposals that move faster, the close that’s cleaner. Not a fake minutes-per-head number. You’ll need that story for budget season anyway.

Extra round

Take stock of what you built across the program: daily habits, a leverage map, cross-app workflows, a working agent. Write the one-paragraph version of your story — “here’s what we built, here’s what it changed, here’s the plan to scale it.” That paragraph is your budget-season opener.

Micro-win

You walk into planning season with a story instead of a vendor’s promise.

Remember

“Over the summer, my team and I built this” is the only kind of credibility that lands in a room full of AI slides. The season is won in the work nobody was watching.

Next in the plan

Back to the plan: From User to Operator →

FAQ

How do I roll out Copilot to my team after learning it myself?

Pick the single thing that gave you the most value and make it your team's first move. Run it with a small champion group, then widen by helping each person map their own high-leverage moments, then add governance and outcome measurement as usage grows.

What is a good 90-day rollout plan?

Month 1: you and two or three champions run the base habits and one proven workflow. Month 2: widen to the team, each person maps their own use cases by role. Month 3: add governance for the agents people build and measure outcomes by role. Prove value small before scaling.

Why measure outcomes instead of minutes saved?

Because minutes-per-employee is an average nobody can trace to real work, while outcomes are concrete: faster proposals, a cleaner close, better-prepared decisions. Outcome stories by role survive a CFO's scrutiny — and give you a real case for budget season.

When is the best time to upskill before scaling?

A quieter period, because it lets you do the unglamorous personal learning before planning season. Leaders who build their habits and a working agent in a calm stretch walk into budget talks with a real story instead of a vendor promise.

What should I do after finishing the program?

Turn personal capability into team capability: pick your single best result, roll it out to a champion group on a 90-day plan, help your team find their own wins by role, and add governance and outcome measurement as usage scales.