The organizations that win in the AI era are not those with the most sophisticated technology — they're those that enable their people to genuinely partner with it. Every element of this framework exists to close that gap.
Organizations spend enormous time and money deploying AI tools. They buy licenses, run training sessions, and issue policy documents. Six months later, adoption is flat. The tools sit unused or misused. Employees are skeptical or afraid. Leadership is frustrated. And the initiative quietly loses momentum.
The failure mode is always the same: organizations treated AI adoption as a technology problem, when it was a human problem all along. Tools don't change behavior. Compliance doesn't build capability. And fear — of job loss, of looking incompetent, of making mistakes in public — is the single most powerful suppressor of adoption there is.
This is the founding insight of The Enablement Imperative™. Not a reaction to a trend, but a principled response to a pattern we saw playing out in organization after organization — and a conviction that there's a better way.
"The organizations that will win in the AI era are not those with the most sophisticated technology. They are those who most effectively enable their people to partner with it."
— Manifesto for AI Enablement
The Enablement Imperative™ is founded on the premise that AI success is fundamentally a people problem, not a technology problem. It gives organizations a set of values, defined roles, a core operating loop, recurring events, and artifacts that make progress visible — bound together by clear rules.
What It Is
What It Is Not
We built this framework on a manifesto — a set of convictions about what AI enablement actually requires. These aren't aspirations. They're structural decisions that shaped every role, every ceremony, and every artifact in the framework. Like the original Agile Manifesto, the language is deliberate: we value the left side — while acknowledging the right has value too. But when there's tension, we know which side wins.
Human Transformation
over
Technology Governance
Augmentation & Partnership
over
Replacement
Behavioral & Cultural Change
over
Tool Deployment
Employee Enablement
over
Process Automation
The first belief — Human Transformation over Technology Governance — establishes that the primary challenge isn't controlling how AI is used. It's growing people's capacity to use it well. The second — Augmentation over Replacement — is both a moral and practical stance. When employees believe AI is coming for their jobs, they resist. When they believe it will make their work better, they lean in. These four beliefs aren't aspirational — they're decisions. Every role, ceremony, and artifact in the framework exists because of the left side of each line.
Values tell you what to prioritize. Principles tell you how to behave when you're in the room. These five principles shape how Praxis operates — and how we expect the organizations we work with to operate once the framework is embedded. The fifth — Empower — deserves particular attention. Every Praxis engagement is designed to make itself unnecessary.
Deep context before any prescription. The best intervention is useless if it's aimed at the wrong problem.
AI enablement belongs to the whole organization — not HR, not IT. Shared ownership is the only kind that lasts.
Small wins compound. Don't wait for the perfect rollout — build feedback loops and improve continuously.
What worked in month one may not be right by month nine. Inspect and adapt — always.
The goal is self-sufficiency, not dependency on Praxis. Every element is designed to be owned by the organization.
Notice the shape of these five principles: Understand and Collaborate set up Clarity. Iterate is the engine of Execution. Evolve is Feedback in action. And Empower is the long-term outcome of running the Ramp well — the organization no longer needs us to keep climbing.
The Enablement Imperative™ isn't built on intuition or best practices. It's grounded in three well-established bodies of knowledge that together explain why behavior changes — and why it doesn't.
Progress must be observable and measurable. Every hypothesis about adoption is tested against real behavioral data — not self-reported sentiment or training completion rates.
Adoption is a behavior change problem. The framework applies evidence-based models — habit formation, deliberate practice, scaffolded learning — to make new AI behaviors stick.
Sustainable change requires structural support. The framework embeds enablement into the organization's operating rhythm — not bolted on, but built in.
Clarity → Approach → Execution → Feedback. This is the connective tissue of The Enablement Imperative™ — the pathway that turns theory into practice, strategy into behavior, and one cycle of learning into the next. It is not a flat loop. Each pass around the Ramp should leave the organization standing on higher ground than the last.
Setting the Table
The Mindset
Muscle Memory
Closing the Loop
Then back to Clarity, on higher ground
Clarity establishes expectations, available tools, boundaries, and — critically — an honest read of the organization's actual reality: its risk tolerance, budget, economics, and employee skill set. Clarity is the filter for the noise. If your workforce is frontline staff, advanced agentic coding tools aren't on the table; if your audience is engineers, they are. Clarity means matching the approach to the organization in front of you, not forcing every organization through the same machine.
This is also where Praxis is explicit that strategy should never be built around today's specific tools. Tooling changes constantly; the organization's clarity about its own goals, constraints, and risk profile does not.
Approach is how the organization and its people decide to engage, given the clarity established. It's the mindset shift — from "AI is something that happens to me" to "AI is something I partner with." Approach is where Champions model behavior, Coaches set expectations with their teams, and the organization decides how it will work, not just what it will use.
Execution is the work itself — what people actually do, day to day, with AI as part of their workflow. This is where Enablement Blocks happen, where new behaviors are practiced until they become habits, and where the organization's stated approach either becomes real or doesn't.
Feedback gathers what actually happened — adoption data, sentiment, barriers, wins — and feeds it back into a sharper round of Clarity. Feedback doesn't just "report on" execution; it actively modifies and improves the next cycle's approach and execution. This is what makes the Ramp a spiral rather than a circle: each lap produces a better-informed Clarity than the one before it.
Clarity drives Approach. Approach drives Execution. Execution provides Feedback. Feedback improves Clarity. The loop repeats — and with each repetition, the organization ascends. By setting clarity, driving the approach, and creating proper execution expectations, the organization generates the feedback that produces better clarity, better approach, and better execution next time.
The goal of successfully implementing The Enablement Imperative™ is not a handful of AI power users. It's that the skills, knowledge, and contextual judgment for using AI well are leveled up across the entire organization — consistently and structurally, not in isolated pockets.
We call this baseline the Enablement Floor: the level of AI fluency that every person, team, and function in the organization can be relied on to meet. A high ceiling created by a few enthusiasts doesn't move the floor. The Praxis Ramp™ is designed specifically to raise it.
Every lap of the Ramp should raise the floor.
Clarity → Approach → Execution → Feedback isn't just a project cycle — it's the mechanism by which "what everyone knows and can do" keeps moving up.
The Enablement Imperative defines four roles that work together to drive transformation. All four are required for the framework to function.
Reports to CEO · Full-time at 1,000+ employees
Accountable for overall transformation success. The CAEO doesn't do all the work — they set vision and strategy, build and lead the Enablement Squad, remove organizational obstacles, and hold the organization accountable to the framework. A leadership role, not a management role: they work ON the transformation system, not IN it.
1 per 25–50 employees
Accountable for driving adoption within their function or team — the distributed transformation force across the organization. Champions model effective AI usage, coach peers, surface adoption barriers, and create social proof for AI success. Not additional headcount — existing employees who take this on alongside their functional work (typically 10–20% of their time).
Certification required
Every people manager, redefined. AI Coaches model AI usage, hold regular coaching conversations about AI development, remove barriers, and create psychological safety for experimentation. This is a trade, not an addition — for every new expectation added, something comes off the plate: fewer status meetings, lighter reporting, less administrative work.
3–7 people · Reports to CAEO
A cross-functional team — Enablement Lead, Learning Designer, Change Manager, Data Analyst, Technical Liaison — accountable for executing transformation activities: building training, redesigning workflows, analyzing adoption data, running events. They work in Enablement Blocks against a prioritized Enablement Backlog.
The Enablement Imperative defines recurring events that create rhythm, accountability, and inspection opportunities. These events are prescriptive — the framework requires them. Each maps onto a stage of the Praxis Ramp™.
Approach · Start of each Block
Selects work for the upcoming Enablement Block from the prioritized Enablement Backlog. Enablement Squad runs it; CAEO sets priorities.
Execution · Continuous
A time-boxed period (2–4 weeks) during which the Enablement Squad works to complete a set of prioritized enablement work.
Feedback · End of each Block
Inspects adoption metrics, hears from the field, and adapts the approach based on data. What did the data tell us? What barriers surfaced? What needs to change?
Feedback · After each Adoption Review
The Squad inspects how they worked together and identifies improvements for the next block. Inward-focused: what should we start, stop, or continue?
Approach & Feedback · Bi-weekly or monthly
A regular gathering of all AI Champions to share learnings, surface issues, and coordinate efforts across functions.
Clarity · Quarterly
A review of transformation progress with executive leadership and the board — maintains commitment, secures resources, keeps transformation a strategic priority.
Artifacts represent work or value. The Enablement Imperative defines three core artifacts that must be maintained.
Owner: CAEO prioritizes · Squad executes
The prioritized list of all enablement work — training to build, workflows to redesign, communications to send, barriers to remove. Always prioritized, never complete, visible to all.
Owner: Squad maintains · CAEO decides
A real-time view of AI adoption across the organization — DAU, adoption rate by function, workflow integration, sentiment, and Enablement Floor metrics tracked alongside leading-edge usage. What gets measured gets managed.
Owner: CAEO
The phased plan for transformation — which functions transform when, what milestones matter, what resources are needed. An 18–24 month view with specific near-term detail, updated quarterly.
The framework doesn't just define roles and ceremonies — it shapes the day-to-day behavior of everyone involved. These norms describe what shifts when enablement takes hold.
Old norm
Hiding AI use, "I did this myself"
Teams openly share how they partner with AI to complete work. Sharing effective prompts, workflows, and use cases becomes a sign of expertise — not a shortcut to hide.
Old norm
Managers as task-assigners and output-checkers
The AI Coach role redefines what it means to manage a team. Managers hold structured enablement conversations, review AI usage in 1:1s, and model the collaboration behaviors they expect from their teams.
Old norm
Static job descriptions and fixed task ownership
As AI takes on routine cognitive work, roles evolve. Employees develop new capabilities, take on higher-value work, and their task portfolios are actively managed through the enablement process — not left to drift.
Old norm
Fear of job loss driving silent non-adoption
Leaders and managers actively create environments where employees can experiment, make mistakes, ask questions about AI, and develop at their own pace — without the fear that honest engagement will be used against them.
Just as Scrum has a "Definition of Done," The Enablement Imperative has a "Definition of Enabled." It defines when a function, team, or individual has hit the current Enablement Floor for that level — and as the organization completes more laps of the Ramp, these thresholds get revisited and raised.
The Definition of Enabled is used in Adoption Reviews to assess progress and in Block Planning to prioritize work. It's not a finish line — it's the floor for this lap of the Ramp. Meeting it is the signal to recalibrate Clarity and raise the bar for the next cycle.
The Enablement Imperative is prescriptive about certain elements because they are essential to making the framework work. Other elements are flexible and should be adapted to organizational context.
Prescriptive (Required)
Organizations that change these are not using the framework.
Flexible (Adapt to Context)
These elements should flex to your culture, structure, and constraints.
Organizations typically implement The Enablement Imperative in phases — the organization's first full lap of the Praxis Ramp™: establishing initial Clarity, building the Approach, proving Execution, and generating the Feedback that sets up continuous cycles afterward.
Months 1–3
Months 4–9
Months 10–18
The Ramp doesn't stop at Phase 3. Embed is the end of the first lap — not the end of the framework. From here, the organization keeps cycling Clarity → Approach → Execution → Feedback, and the Enablement Floor keeps rising.