Skip to content
The AIΒ TechΒ Lead Path
The path
2516 min read Β· 220 XP

Capstone: role charter & 90-day plan

Define the role before it defines you.

0%

Pull the whole path together into the artifact that sets you up to succeed: a one-page role charter plus a 90-day plan and a metrics baseline. Bring it to your sponsor β€” leading the definition of your own role is the first proof you're right for it.

Key ideas

  1. 1

    Done means: a one-page charter (mandate, scope, authority, metrics, operating model, backing, protected time) + a 30/60/90 plan + a baseline of 4–6 metrics.

  2. 2

    Lock authority explicitly: what you can mandate (e.g. the paved road) vs advise, and your budget.

  3. 3

    Agree 4–6 success metrics with your sponsor now, before you're judged on someone else's assumptions.

  4. 4

    Sequence the 90 days: listen & quick win β†’ paved road β†’ scale via champions β€” don't jump to scaling.

  5. 5

    Secure visible exec backing; it's what makes influence-without-authority work across BUs.

Write the charter (one page)

  • Mandate & scope: which teams/BUs; own vs influence vs advise.
  • Authority & budget: what you can mandate vs recommend.
  • Success metrics: the 4–6 numbers you'll be judged on.
  • Operating model: hub-and-spoke + champions endorsed.
  • Backing & protected time: exec sponsorship; ~20–30% build time guarded.

Plan & baseline

  • 30 days: listen, map, one quick win, stand up the guild.
  • 60 days: eval harness + gateway POC, recruit champions, baseline metrics.
  • 90 days: scale to 3–5 teams across β‰₯2 BUs; first impact report.
  • Baseline now: adoption, DORA, cost, eval scores β€” so you can show deltas.

Watch

Do the work

0/5 Β· 0%

Test yourself

Question 1 / 3

Why draft the charter yourself instead of waiting for one?

27 chapters Β· progress saves automatically