Agentic AI AcademyAgentic AI Academy

The 90-Day and First-Year Plan

From literacy to scaled value

Intermediate 14 minDecision-maker
What you'll be able to do
  • Sequence a 90-day and first-year AI agenda across four phases, each with a clear leadership job and exit criteria
  • Run the Days 0-30 work: build personal fluency, inventory current and shadow AI, pick a business problem, and name an executive sponsor
  • Select 2-3 high-value vertical use cases on a value-by-feasibility matrix, assess data readiness, stand up lean governance, and default to buy or partner
  • Design Days 60-90 pilots that pair end-to-end workflow redesign with human-in-the-loop and a three-tier KPI baseline, and empower middle managers
  • Operationalize the first year: redesign workflows around winners, reskill broadly, institutionalize governance, and set EBIT-linked targets
  • Explain why role-modeling AI use is the single most correlated leadership behavior with bottom-line impact
At a glance

This is the spine of your personal AI playbook: a concrete, sequenced plan that takes you from personal fluency to scaled, EBIT-linked value. You will run four phases — build literacy and an honest baseline (Days 0-30), focus on 2-3 vertical use cases with governance foundations (Days 30-60), pilot end-to-end with workflow redesign and a 3-tier KPI baseline (Days 60-90), then scale what works across the first year (Months 4-12) — while role-modeling AI use as the champion throughout.

  1. 1Why you need a sequenced plan, not a flurry of pilots
  2. 2The four-phase arc at a glance
  3. 3Days 0-30 — Orient: fluency, baseline, problem, sponsor
  4. 4Days 30-60 — Focus: use cases, data, governance, buy-vs-build
  5. 5Days 60-90 — Pilot: end-to-end, human-in-the-loop, baselined
  6. 6Months 4-12 — Scale: redesign, reskill, govern, tie to EBIT
  7. 7The right questions to carry through every phase

Why you need a sequenced plan, not a flurry of pilots

The headline of the entire AI moment is an uncomfortable gap: everyone has AI; almost nobody has AI value yet. Around 88% of organizations now use AI in at least one function, yet only roughly 39% report enterprise-level EBIT impact, and most of those attribute under 5% of EBIT to it (McKinsey, State of AI, 2025). A separate study of enterprise pilots found about 95% delivered no measurable P&L return — and named the root cause not as model quality, infrastructure, or talent, but as a learning gap: the work of redesigning workflows and integrating AI into how the business actually runs (MIT NANDA, State of AI in Business, 2025).

The lesson for you is precise: scattered pilots are exactly how value fails to materialize. What separates the few firms capturing real returns is sequence and focus — building fluency, picking a small number of high-value problems, redesigning the work around them, measuring honestly, and scaling only what moves a number. This lesson gives you that sequence as a four-phase plan you personally can run.

The bottleneck to AI value is not technology. It is leadership, learning, and organizational change — which is precisely the part executives own.

Key insight

The 10-20-70 rule frames the whole plan

BCG estimates successful AI at scale spends ~10% of effort on algorithms, ~20% on technology and data, and ~70% on people and process — adoption, workflow redesign, reskilling, incentives (BCG, The Leader's Guide to Transforming with AI). The 70% is what this 90-day plan is mostly about, because it is what you, not your engineers, own.

The four-phase arc at a glance

Think of the journey as a leadership arc, not a project plan. Each phase has one dominant job, and you should not advance until its exit criterion is met.

PhaseWindowYour dominant jobExit criterion
1. OrientDays 0-30Build personal fluency; take an honest baseline; pick a problem; name a sponsorYou can place AI terms in context, you have a shadow-AI inventory, and one named business problem with an executive sponsor
2. FocusDays 30-60Select 2-3 vertical use cases; assess data; stand up lean governance; decide buy vs. buildA prioritized shortlist on a value-by-feasibility matrix, an AI policy, and a default-to-buy decision per use case
3. PilotDays 60-90Run a few end-to-end pilots with workflow redesign, human-in-the-loop, and a 3-tier KPI baselineLive pilots with baselines captured before go-live and middle managers engaged
4. ScaleMonths 4-12Redesign workflows around winners; reskill broadly; operationalize governance; set EBIT targetsProven use cases scaled, stalled ones killed or reshaped, and AI tied to a P&L target

Notice the shape: each phase narrows from broad orientation toward concentrated, measured value. This is deliberate — the firms that win pick 2-3 high-value vertical use cases and go deep, rather than running many shallow experiments (McKinsey, Seizing the Agentic AI Advantage, 2025).

Tip

Scale the timeline, keep the sequence

The day counts are a rhythm, not a deadline. A large regulated enterprise may take two quarters to do what a mid-market firm does in one. What does not change is the order: fluency and baseline first, focus second, measured pilots third, scale last.

Days 0-30 — Orient: fluency, baseline, problem, sponsor

The first month is about you and an honest mirror. Four moves:

1. Build personal fluency. Use the tools yourself, weekly. This is not optional polish — BCG's AI Radar 2026 found that deeply engaged leadership teams are roughly 12 times more likely to be top-5% AI value creators, and that around 72% of CEOs now identify as the primary AI decision-maker, about double the prior year. You cannot champion what you do not personally use. Fluency here means conceptual fluency: for any AI term, you can place it in the hierarchy (AI to ML to GenAI to LLMs to agents), say what business problem it addresses, and name its main risk. Knowing the math is not required.

2. Inventory current and shadow AI. You cannot govern what you cannot see. Map current pilots, spend, data readiness — and especially shadow AI, the unsanctioned tools employees already use. Roughly half of workers report using unsanctioned AI tools, and executives are often the worst offenders (CIO, 2025). Banning it drives it underground; the fix is a sanctioned, easy, safe alternative plus a clear policy. The inventory is your starting line.

3. Pick a business problem, not 'do AI.' There is no standalone AI strategy — only business strategy strengthened by AI (Wharton). Leaders who make 'doing AI' the goal generate diffuse pilots with no P&L impact. Name one concrete problem tied to growth, cost, customer experience, or risk.

4. Name an executive sponsor. Assign a single accountable owner for AI strategy and governance. CEO oversight of AI governance ranked as the attribute most correlated with EBIT impact among ~25 tested (McKinsey, State of AI, 2025) — yet only about 28% of organizations say the CEO owns AI governance and 17% say the board does. Diffuse accountability is the clearest 'leaders get it wrong' signal.

Watch out

Do not chase the flashy function

Value concentrates in a few core, customer-facing, and engineering functions — roughly 75% of GenAI's economic potential sits in customer operations, marketing and sales, software engineering, and R&D (McKinsey, Economic Potential of Generative AI). A common mistake is launching the flagship effort in HR, legal, or finance — cost-cutters — instead of a core revenue or customer function.

Days 30-60 — Focus: use cases, data, governance, buy-vs-build

Month two converts orientation into a focused portfolio. Four moves:

1. Select 2-3 high-value vertical use cases on a value-by-feasibility matrix. Plot candidates by business value against feasibility (effort, data, risk). Bias toward the Reshape ambition level — re-engineering whole workflows, where BCG estimates the largest efficiency gains sit — and toward unglamorous high-ROI wins, not just marketing demos. Sequence quick wins first to build credibility, then transformational bets.

2. Assess data readiness. Proprietary data is the one moat rivals cannot buy, but siloed, ungoverned data is a liability: an AI agent cannot query what it cannot find. For each shortlisted use case ask: is the data it needs clean, governed, and accessible? Roughly 80% of the real AI work is data, governance, and workflow integration (MIT Sloan).

3. Stand up lean governance and an AI policy. Early stage, that is an AI Governance Committee — chaired by a CDO, CTO, or CRO with Legal, Compliance, Risk, Security, HR, and business leads, reporting to the CEO. Adopt the NIST AI RMF vocabulary (Govern, Map, Measure, Manage) as your shared language, and map to the EU AI Act and ISO/IEC 42001 where in scope. The non-negotiables: an AI policy that kills shadow AI, risk-based tiering (a chatbot is not a loan-approval model), and a system inventory.

4. Default to buy or partner. Buying or partnering succeeded roughly 67% of the time in one large study, versus about a third of that rate for internal builds (MIT NANDA, 2025). Decide per use case on two axes — value potential versus competitors, and differentiated data access versus vendors. Build only where AI is a true competitive differentiator; otherwise buy for speed and odds.

Example

The build-vs-buy 2x2 in one line

High value + differentiated data you uniquely hold → build/own. Low value or no data edge → buy. The murky middle → partner. (BCG framework.) The strategic default for most use cases, most of the time, is buy or partner.

Days 60-90 — Pilot: end-to-end, human-in-the-loop, baselined

Month three is where most programs quietly fail — by bolting AI onto a broken process and measuring the wrong thing. Avoid both. Four moves:

1. Run a few end-to-end pilots WITH workflow redesign. This is the single biggest lever. Workflow redesign has the largest effect on EBIT impact from AI, yet only about a fifth of firms have fundamentally redesigned workflows; most simply bolt AI onto legacy processes (McKinsey, Rewiring to Capture Value, 2025). 'End-to-end' means you reimagine the whole task, not insert a chatbot mid-stream.

2. Design human-in-the-loop. The governing principle is automation for execution, humans for judgment. Decide where a person stays in the loop (approving each step) versus on the loop (an escalation point). For anything where a wrong answer is load-bearing — legal, financial, safety — a human check must sit before the AI acts.

3. Set a three-tier KPI baseline BEFORE you start. Measure across three tiers: (1) adoption/usage, (2) workflow efficiency (time saved, throughput, error reduction), and (3) business/P&L impact (revenue, cost, EBIT). The classic failure is stopping at tier 1 — and worse, mistaking vanity metrics (logins, seats, token counts, suggestion-acceptance) for value. Track quality, not just volume. Capture the baseline before go-live or you will never prove the lift.

4. Empower middle managers. Executives see strategic advantage while middle managers confront AI's flaws unsupported, which stalls adoption and costs money (HBR, 2026). Involve them in planning, reduce their admin burden, and build feedback channels — they see the workflow reality you do not.

Watch out

The Klarna lesson: volume metrics hid a quality collapse

Klarna replaced roughly 700 customer-service roles with AI and looked excellent on volume metrics — then customer satisfaction deteriorated and it rehired humans by mid-2025, its CEO conceding the company had focused too much on cost and efficiency at the expense of quality (vendor and press reporting, 2024-2025). The lesson for your KPI baseline: track CSAT/NPS alongside throughput, and prefer augment-and-blend over wholesale replacement for nuanced, empathetic work.

Months 4-12 — Scale: redesign, reskill, govern, tie to EBIT

The first year is about turning proven pilots into operating reality and killing what does not move a number. Five moves:

1. Redesign workflows around the winners. Move deliberately from Deploy (off-the-shelf tools, modest productivity gains) to Reshape (re-engineered functions, where most value sits) to Invent (new AI-enabled revenue) — BCG's three ambition levels. Double down on use cases that proved out; do not let proven pilots languish.

2. Reskill broadly. The near-term story is augmentation, not replacement. The WEF Future of Jobs Report 2025 projects a net positive jobs picture by 2030 with substantial churn, and finds that around 59 of every 100 workers will need reskilling or upskilling. Close the gap between trained leaders and the frontline — disengaged frontlines stall adoption.

3. Operationalize governance. Make it routine: a full system inventory, risk-based tiering, lifecycle gates with halt/rollback, and a cadence of quarterly risk reviews, dataset-lineage records, and serious-incident reporting with one accountable executive who can explain it to a regulator. Around 51% of organizations reported at least one negative AI incident in the prior year (McKinsey, 2025) — governance is a value-enabler that lets you ship faster because trust is engineered in, not a brake.

4. Set EBIT-linked targets. Graduate from activity metrics to the metric that separates high performers: % of EBIT attributable to AI. Expect patience — most organizations reach satisfactory ROI in two to four years, not months (Deloitte). Kill or reshape any pilot that cannot show a path to a number; project-abandonment rates have been climbing precisely because firms fund on FOMO without a hypothesis.

5. Role-model use as the champion — throughout. This is not a phase; it runs across all four. High performers are about three times more likely to have senior leaders actively championing and role-modeling AI use (McKinsey, 2025). Your visible, weekly, hands-on use is itself a lever.

Key insight

Operating model: hub-and-spoke

Firms that successfully scale AI are far more likely to use a hub-and-spoke structure: a lean central hub owns guardrails, standards, and platforms, while business-unit 'spokes' own execution (Dataiku; IBM). Centralize the rules; federate the doing. The hub is an enabler, not a gatekeeper.

The right questions to carry through every phase

You will not personally evaluate models or write policy, but you must ask the questions that expose whether the work is real. Keep these on a card:

TopicThe question that cuts through
On any claim'90% accurate' — accurate how, what do the failing 10% look like, and who owns them?
On strategyIs this a tool rollout or a workflow redesign? Are we using AI to expand options, not make the choice?
On adoptionAre we empowering line managers, or hoping a central lab fixes it?
On dataIs our data clean, governed, and accessible enough to feed this?
On agentsWhat is our human-in-the-loop policy for systems that act — and can we halt and roll back?
On vendorsIs this a genuine agent or 'agent washing'? Where is our data processed, and what if you change models?

The hardest and most valuable of these is the first: never accept a confident accuracy claim at face value. Watch for automation bias — over-trusting fluent output. Final judgment and accountability stay human.

Note

Separate the durable from the volatile

The frameworks in this plan — 10-20-70, value-by-feasibility, the three-tier KPI stack, buy-vs-build, NIST's Govern/Map/Measure/Manage, human-in-the-loop — are durable. The specific statistics, vendor names, model rankings, and regulatory dates around them move fast. Teach yourself the durable principles; hand the volatile specifics to a watchlist with live sources to re-verify (see Resources).

Try it: Draft your personal 90-day AI playbook

Goal: leave with a one-page, sequenced plan you could actually run as the AI champion — the spine of your personal AI playbook. Work through the four phases for YOUR organization, not in the abstract.

1) Days 0-30 (Orient). Write three sentences of honest self-assessment of your own AI fluency and commit to a weekly hands-on cadence. Then sketch your shadow-AI inventory: list the unsanctioned tools you suspect people already use and how you'd find out. Finally, name ONE concrete business problem (tied to growth, cost, CX, or risk — never 'do AI') and the single executive who will sponsor it.

2) Days 30-60 (Focus). On a simple 2x2 (value vs. feasibility), plot 4-6 candidate use cases and circle the 2-3 you'd pursue. For each circled one, note (a) whether the data is clean, governed, and accessible, and (b) a build / buy / partner call with a one-line reason — defaulting to buy or partner unless it's a true differentiator. Name who chairs your lean governance committee and the single most important line of your AI policy (the one that kills shadow AI).

3) Days 60-90 (Pilot). Pick your top use case and write the redesigned end-to-end workflow in 3-5 steps (not the old process with AI bolted on). Mark where a human stays in or on the loop. Then write your three-tier KPI baseline: one adoption metric, one efficiency metric, and one P&L metric — and the number you'd capture for each BEFORE go-live. Name one middle manager you'd put in the planning room.

4) Months 4-12 (Scale). State the EBIT-linked target you'd hold the program to, one reskilling commitment, and your rule for killing a pilot that doesn't move a number.

5) Watchlist. Finish by listing the 3-5 VOLATILE facts your plan depends on (e.g., a specific adoption stat, a vendor name, an EU AI Act date) and the live source you'd re-check each against — separating the durable principles you now own from the specifics you must keep re-verifying.

The deliverable is a single page. If a board member asked 'what is your AI plan and how will you know it worked?', this page is your answer.

Key takeaways

  1. 1The central problem is the adoption-value gap: most organizations use AI but few capture EBIT impact, because the bottleneck is leadership, learning, and workflow redesign — not technology (McKinsey and MIT NANDA, 2025).
  2. 2Days 0-30 (Orient): build personal fluency, inventory current and shadow AI, pick a real business problem rather than 'do AI,' and name a single accountable executive sponsor.
  3. 3Days 30-60 (Focus): select 2-3 vertical use cases on a value-by-feasibility matrix, assess data readiness, stand up a lean governance committee plus AI policy, and default to buy or partner.
  4. 4Days 60-90 (Pilot): run a few end-to-end pilots WITH workflow redesign and human-in-the-loop, set a three-tier KPI baseline before go-live, and empower middle managers — tracking quality, not just volume (the Klarna lesson).
  5. 5Months 4-12 (Scale): redesign workflows around winners, reskill broadly, operationalize governance, and set EBIT-linked targets — killing or reshaping pilots that do not move a number.
  6. 6Role-modeling AI use is not a phase but a constant: engaged, hands-on leadership teams are dramatically more likely to be top AI value creators (BCG and McKinsey).

Quiz

Lock in what you learned

Check your understanding

0 / 4 answered

1.A division head proposes launching the company's flagship AI transformation in the legal department to cut review costs. Based on where AI value concentrates, what is the strongest objection?

2.Your team wants to start building a custom AI system in-house for a capability that several vendors already offer and where you hold no unique data advantage. What does the evidence suggest?

3.During a Days 60-90 pilot review, the team proudly reports that AI now handles two-thirds of customer chats and average handling time has dropped sharply. What is the most important thing for you to ask before declaring success?

4.Twelve months in, several pilots show strong adoption dashboards and lots of usage, but none can demonstrate a path to revenue, cost savings, or EBIT. What does the plan call for?

Go deeper

Hand-picked sources to keep learning