Your Next Move #03 — Your First 90 Days Owning an AI Initiative You Didn't Ask For
Claim the initiative with a week-by-week 90-day operator playbook and a copy-paste stakeholder-update template — so you're running it, not reacting to it.
You didn't volunteer for this.
The initiative has your name on it now — AI integration for your function, AI-powered [workflow], AI readiness for the team — and you got it the way most non-technical managers get these assignments: someone in a leadership meeting decided you were the right person, and you found out after the decision was made.
Here's the honest frame: the first 90 days of an AI initiative you didn't ask for are not primarily about AI. They're about ownership. Specifically, they're about whether the organization's read on you at the 90-day mark is "this person is running it" or "this person is being run by it."
The difference is almost never technical. It's operational. And it's determined in the first two weeks.
Why Most "Accidental AI Owners" Lose the Narrative in Week One
The failure pattern is consistent. The newly-assigned manager does one of three things:
They disappear into research. They spend the first two weeks consuming vendor demos, reading reports, building a mental model of the AI landscape. They surface at Week 3 with knowledge but no visible progress — and leadership has already formed an impression.
They over-report inputs, not outputs. Every update is a list of things they attended, tools they evaluated, calls they took. Nobody asked for an activity log. They asked for a signal that someone is in control.
They wait for the playbook. They assume someone above them will define success, specify the scope, and hand them a clear mandate. That playbook does not exist — that's why they got the assignment.
The 90-day playbook below is designed to prevent all three.
The 90-Day Operator Playbook
One objective per phase. Everything else is a distraction until you've cleared it.
Phase 1 — Weeks 1–2: Stake the Ground
Objective: Be on record with a scope and a metric before anyone defines it for you.
Week 1 actions:
[ ] Write a single-sentence scope statement: "This initiative will [change / improve / measure] [specific workflow] for [specific team] by [specific date]." If you can't write this sentence yet, your first job is making it writable — not evaluating tools.
[ ] Identify the one stakeholder who can block this initiative if they feel bypassed. Send them a 3-line update this week (template below). Do this before your formal kickoff.
[ ] Name one success metric — the single number that determines whether this worked. Write it down. Share it with your manager. Do not proceed without agreement on this number.
Week 2 actions:
[ ] Confirm your resource reality: What is the actual budget? What staff time is allocated, and is that allocation protected or aspirational? What tools are already licensed?
[ ] Map the three highest-friction points in the workflow you're targeting. These are where AI is most likely to help — and most likely to break things if the rollout is wrong.
[ ] Schedule your 30-day read-out now. Put it in calendars before the pilot starts. The date existing in people's calendars changes how they treat the interim.
Phase 2 — Weeks 3–6: Run One Scoped Pilot
Objective: Generate one clean result from one tightly scoped test.
The scope rule: one workflow, one team, four weeks, one metric. Resist every request to expand the pilot before you have a result. Expansion is how pilots become unreadable.
What to measure: Time saved per task OR error rate OR output requiring revision — whichever your stakeholders care most about. Pick one. If you pick three, you'll have contested data at the read-out.
What to document as you go (takes 10 minutes per week):
