The framework
The PACE Framework for AI Adoption
Four pillars, twelve domains, and one premise: the pillar carrying the most resistance sets the pace everything else can move at.
What is the PACE framework?
PACE is a framework for diagnosing organizational AI adoption across four pillars: People, Adaptive Culture, Capability and Evidence. Twelve domains sit under those four pillars. The premise is that the pillar carrying the most resistance sets the pace at which the whole organization can absorb the change, so correcting the loudest problem rarely moves anything.
AI moves at the speed of
the pillar with the most
resistance.
Who created PACE?
Lesley Bodine, founder of Accorda Advisory LLC in Camas, Washington, serving organizations across the United States.
PACE is the organizing structure inside AI That Sticks™, her people-first adoption methodology, and it is the framework both Accorda assessments score against. It came out of fifteen-plus years moving people through changes they did not ask for, in organizational development, leadership development and L&D, applied to a vertical where the technology usually works and the behavior does not follow. More on where it came from.
What does each letter stand for?
- P is People. Whether the people carrying the change are equipped for it, and safe enough to say what is actually happening. Not whether they have been trained on the tool.
- A is Adaptive Culture. Whether the organization can absorb a change rather than route around it. A culture that rewards on Friday what it contradicted on Monday is behaving rationally, and no amount of communication fixes a reward system.
- C is Capability. Whether the work itself has been redesigned around what the software now does. Roles redrawn, output checked before a customer sees it, and a real answer about what people are already using unapproved.
- E is Evidence. Whether anyone can produce a number showing the change is real. Evidence is the pillar that decides whether the other three get funded again.
What problem does PACE solve?
It stops a company fixing the wrong thing.
An AI stall presents as one visible symptom. A team quietly working around a tool, say. That single behavior has at least three different causes, and they sit in three different pillars:
- People. Someone is defending whether their expertise still counts.
- Adaptive Culture. It is not safe to try something and have it not work.
- Capability. Nobody was actually taught, and saying so would cost them something.
Each needs a different response. Guessing which one you are looking at is how a company spends a year on the wrong pillar, and it is why the framework reads all four rather than the one being complained about. How that plays out in practice.
How do the twelve domains sit inside PACE?
Three domains per pillar. Each one is a place adoption is known to break, and each has a sentence an owner actually says out loud when it is the one under strain.
- PPeople
- AAdaptive Culture
- CCapability
- EEvidence
See what an owner says about each of the twelve, or tick the sentences you have actually said and the page names your pillar. Two minutes, no email, nothing stored.
How does PACE relate to the assessments?
PACE is the structure. The assessments are what score against it.
- AI Adoption Gap Diagnostic™ · scores the organization
- A 12-domain stress test across all four pillars. It names which pillar is carrying the strain and what has to change first.
- Accorda Leadership Index · scores the executives and managers
- Every executive and manager scored 1.0 to 5.0 across five dimensions, placed in one of four operating patterns. It sits inside the People pillar and answers whether the leadership layer can carry the change at all.
- AI Adoption Gap Snapshot™ · free, five minutes
- The early-signal version, covering all twelve domains at a glance.
PACE is the organizing structure inside AI That Sticks™, Accorda’s people-first adoption methodology. The methodology is the whole approach; PACE is how it is measured.
How is PACE different from an AI readiness model?
A readiness model asks whether an organization is prepared to start. PACE measures an adoption that has already started and is not holding.
| Comparison | A readiness model | PACE |
|---|---|---|
| When it is run | Before the work, to decide whether to begin. | After the tools are in and the work did not change. |
| What it scores | Preparedness at a moment in time. | The gap between what the tools can do and what people actually do. |
| How it closes | A go or no-go. | Re-run months later, so movement appears in the company’s own numbers. |
Readiness is a useful word and Accorda still uses it. It is not the category. The category is adoption, and adoption has a pace rather than a finish line.
What PACE does not do
Worth stating plainly, because a framework that claims everything measures nothing.
- It does not select, implement or configure software. Implementers do that, and by the time PACE is useful the technology usually works fine.
- It does not assess technical architecture, model performance or vendor fit. Those are real questions and they are somebody else’s.
- It does not predict ROI. It measures whether the conditions that produce a return are present, and then measures again so you can see whether they moved.
- It is not a substitute for a decision. It tells a leadership team where the constraint is. Acting on it is still theirs.
What it does measure is the human layer that decides whether workable technology becomes changed behavior. That is a different question from whether the technology works, and it is the one most companies never ask.