Skip to content
scomil.co
Three months

In-Company Acceleration

Three months to take the champions named in the PDP Assessment and turn them into people who can originate their own AI work. Six sessions, every one of them half instruction and half working time, on the company’s own systems.

At a glance
Participants
Three to eight champions from one company, plus the executive sponsor
Sessions
Six group sessions, twice monthly across twelve weeks
Session format
One hour instruction, then one hour working
The plan
Drafted in month one, refined in month two, defined in month three
One-on-ones
Three rounds, an hour per champion
Executive coaching
Monthly with the sponsor, separate from the group work
Office hours
Standalone blocks in the weeks between sessions
One program, two rooms

The same program also runs as a cohort: the same teaching in a mixed room of executives, each from a different company. If you are moving one or two people rather than a champion group, that is the version you want. Executive AI Cohort.

Half instruction, half working time

Every session is an hour of teaching and then an hour of open support in the same room: questions, whatever broke, whatever did not connect. Nobody leaves a session stuck on setup, which is where most training programs quietly lose people.

The office hours in the off weeks exist because the questions that surface five days after a session are different from the ones that come up in the room. Drop in with whatever is stuck. No agenda, no obligation to attend.

The sponsor has a different job

Executive coaching sits apart from the group work. The sponsor is building their own capability and learning to lead the program, which is not what the champions are doing.

They are also the person who clears blockers that need authority. Access that has not been granted, time that was never really allocated, the manager whose numbers get worse if their team experiments. Those get raised in coaching and resolved there.

Where it ends up

By the final session each champion presents what they built, what it produces, and what it cost, with an honest retrospective on what did not work. The next ninety days get drafted by the group and presented to the sponsor in the room.

What they still need outside help with is named out loud, which both normalizes it and sharpens it.

How it runs

Three months, three sets of deliverables

Each month closes on something the company owns and keeps. Running through all three is one document: your AI plan, drafted in month one, refined in month two by what building actually taught you, and only defined in month three — because a plan written before anyone has built anything is a guess.

  1. Month 01

    Access and the first draft

    Every champion is working against real company data, and the plan exists on paper for the first time.

    You end the month with
    • A provisioned environment per champion
    • The first draft of your AI plan
    Made in

    Your working environment · Getting connected

  2. Month 02

    Judgment and repeatable work

    The company gets a written position on how it uses AI, and the first work that runs without being asked.

    You end the month with
    • A written data-use position
    • A verification standard
    • One workflow per champion, running on its own
    • The second draft of your AI plan
    Made in

    Judgment, compliance and guardrails · From tasks to systems

  3. Month 03

    Transfer

    The work moves beyond the champion group, and the plan is finished and handed to your sponsor.

    You end the month with
    • A workflow running outside the champion group
    • A capstone record per champion
    • Your AI plan, defined and owned by your sponsor
    Made in

    Building for the team · Capstone and the next ninety days

Running underneath, every month
  • Two group sessions
    Twice a month

    One hour of instruction, then one hour working in the same room. Nobody leaves stuck on setup.

  • One-on-ones
    Once a month, an hour each

    Time on each champion’s own systems, and whatever did not connect.

  • AI office hours
    The weeks in between

    Drop in with whatever is stuck. No agenda, no obligation to attend.

  • Executive coaching
    Monthly with the sponsor

    Separate from the group. Building their own capability, and clearing blockers that need authority.

What each month produces, in full
What you leave with
  • Your AI plan, drafted in month one and defined by month three, owned by your sponsor
  • A working environment each champion owns, producing against real company data
  • A written data-use position and a verification standard
  • At least one workflow per champion running on its own
  • One workflow running outside the champion group, with the context package that moved it
  • A capstone record per champion: what it produces and what it cost
  • A named, scoped list of what still needs outside help, written inside the plan
  • Every session recorded and kept, as a training asset for whoever joins next
What it asks of you
  • Paid AI seats for every champion, before the first session
  • Two hours a week per champion, formally allocated
  • An executive sponsor who attends monthly coaching
  • Admin access, or a direct line to whoever holds it
  • Real work to bring
The point of it

A group of champions who can originate and run their own AI work, and a sponsor who can lead them.

The other two

Where this sits

Not sure which one you need? The assessment scopes it, and names who from your company should go into it.

Next step

Want to talk through this one?

A conversation about where you are, what you are trying to change, and whether this is the right place to start.

Book a callStart with the PDP Assessment