AI Level Guide

AI Adoption Level Guide

This adoption canvas sets the success path for change-management — how people progress with AI and compound their systems.

Leveling is fractal

A fractal is a shape whose parts look like the whole; the pattern repeats at every scale. Leveling is fractal because every graduation gate can apply to the workflow, the person, the team or even the whole company. We tend to prioritize the person.

Figure 1 · Nested fractals

Scope within scope

Four nested scopes: one workflow sits inside a person, inside a team, inside the company.COMPANYTEAMPERSONALONE WORKFLOWa person is how their workflows add upa team is how its people add upa company is how its teams add up

The wider scope is made of the narrower one, which is why you cannot skip inward. Independent from levels, this is only what contains what.

Figure 2 · Solo fractals

The same ladder, four ratings

The same six-rung ladder asked at four scopes, giving four different answers.L0L1L2L3L4L5WORKFLOWWorkflow: Runs Monday 6am, posts itself, you skim it.PERSONALPersonal: Three skills you reach for without thinking.TEAMTeam: A shared brain the AI can query.COMPANYCompany: Scattered wins. Nothing compounds.illustrative — narrower scope runs ahead of wider scope

The same ladder in 4 contexts. Results tend to step down as the scope widens since your best single workflow will always run ahead of your company.

Figure 3 · Leveled fractals

Where each level actually happens

One company containing two teams, containing people, containing workflows — with the five levels marked as rows: a workflow of your own, a team of people, a shared workflow, chained workflows, and a chain that leaves one team, crosses company space, and enters the next.COMPANYTEAML2TEAMPERSONPERSONPERSONPERSONWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowWorkflowL1L3L4L5workflows add up to a personpeople and shared workflows add up to a teamanother team, same patternteams and chained workflows add up to a company
  1. L1
    One workflow, run by one person
  2. L2
    People with their own workflows pull from a central team brain
  3. L3
    One workflow, shared & updated across people
  4. L4
    Shared workflows chain inside a function
  5. L5
    The chained workflows cross multiple teams

Figure 1 again, with the five levels marked on it. Each rung is a specific move: a workflow becomes yours, then the team exists, a workflow is shared, developed into workflows chains, which cross over teams.

One workflow
What
Knowledge base

The files and information the work needs to be completed.

Where
Connectors / MCP

The access required to finish end to end, without you pasting things in.

How
Skill library

The sets of instructions that produce the output the same way twice.

Who
Harness

Your preferences and standards, plus the directory of what loads every session and what gets pulled on demand.

Why
Evals

What “done” and “good” mean, written down, so the system can check itself instead of you checking it.

One row per scope. Read across to watch that scope climb; read down a column to see what a single level number means at four different scales — that reading is the point. The last column is what happens when this is the only scope anyone pursues.

S1 · PersonalS2 · TeamS3 · Agents
ScopeWhat it asksL0baseL1Personal OSL2Team OSL3Function OSL4Agent OSL5Company OSIf you pursue only this
Workflow
a problem to solve
Is this one task AI-native?
The weekly trend summary
You write it from scratch.You paste last week’s in and ask for a draft.It reads the real dashboard export, not your paste.A saved skill anyone on the team can run.Runs Monday 6am, posts itself, you skim it.Flags the anomaly and drafts the follow-up unasked.Isolated wins. A brilliant workflow nobody else can run.
Personal
across responsibilities
How do I operate across all my work?
How you run your week
Docs and a calendar. AI is not in it.Ad-hoc chats when you get stuck.A context file the AI reads every session.Three skills you reach for without thinking.Your prep is done before you ask for it.You set direction, review, decide. That is the job.You improve and the team does not. Hero and bottleneck at once.
Team
operating together
How do we operate together?
How the reporting team runs
Knowledge lives in people’s heads.A few individuals experimenting alone.A shared brain the AI can query.A skill library teammates reach for unprompted.Agents produce the recurring deliverables.Your systems get adopted by other functions.A high-functioning island. Cross-function hand-offs still break.
Company
teams operating together
How do teams operate together?
How the company runs
AI is a tool a few people happen to use.Scattered wins. Nothing compounds.One company brain; context flows from real systems.Every function has its own skill library.Agents own the hand-offs between functions.Teams operate at company scale, across every function.A mandate with no adoption under it: stale context, bad outputs.

Why the person is the scope to push first

A person is the one who knows which workflows are worth having, and a team's output is essentially its people's workflows added up — so the company scope cannot move until the person scope does. It also has to be worth it to them: if someone's own week does not get better, they will not maintain the context file, and every scope above them goes stale. Adoption is not a mandate you push down, it is a personal win that spreads inside out.