Review draft · Do not send or publish
Back to projects
Public method · Inspectable evidence
Local review only

AI Adoption Decision Evidence Lab

Start with one workflow and one decision. Find the real cause. Build safely. Defend safely. Then let a named human decide whether to scale, change, or stop.

AI adoption // Sales workflows // Learning transfer // Decision ownership
The opening

Access is activity. Adoption changes work.

HypothesisA licence, a course completion, or a champion launch cannot show that a workflow became repeatable, safer, or more valuable. The useful unit of analysis is one named workflow with a baseline, an operating owner, a human decision owner, and explicit conditions to scale, change, or stop.

Activity versus depth

Regular use can coexist with shallow use.

Reported82%

of surveyed senior leaders reported regular AI use in their teams.

Reported27% to 28%

reported strategic applications such as scenario planning or organisational design.

ReportedOne quarter

said their organisation had scaled back AI efforts during the preceding year.

Source: Chief Learning Officer survey report, more than 500 senior leaders, May 2026. Self reported survey categories. These figures are a market signal, not an internal rate for any organisation.

Failed pilot evidence

Motivation did not rescue a badly placed pilot.

ReportedMore than 20

motivated managers entered one reported AI coaching pilot.

ReportedAbout 10 minutes

of combined use was recorded across the cohort over several weeks.

The practitioner attributed the result to the wrong audience, workflow friction, and a measurement sequence that started too late in the funnel. The case does not establish a general failure rate. It shows why activation and workflow fit must be tested before satisfaction.

Source: Beyond the sandbox, Chief Learning Officer, June 2026. One practitioner account, not population evidence.

Diagnosis

Training directly treats one of six root cause classes.

UserThe lab tests six classes before choosing an intervention. This is Otman Mechbal's operating taxonomy. It is not an empirical incidence rate and has not yet been validated through a measured paid client case.

The three pillars

Build safely. Defend safely. Decide safely.

Build safely

Name the workflow, user, baseline, expected change, testable checks, and recovery route.

Defend safely

Set data and permission boundaries, verify outputs, record incidents, and define escalation.

Decide safely

Name the human owner and write the evidence required to scale, change, or stop.

Measurement

Replace vanity measures with decision evidence.

Activity evidenceDecision evidenceQuestion it answers
Attendance and completionActivation and repeat useDid anyone use the new path twice?
Logins and prompt countWorkflow penetration and output qualityDid the workflow actually change?
SatisfactionRework, support, verification, and recovery costDid the new path move or hide the burden?
Time saved estimateBuyer supplied baseline and observed outcomeIs the claimed value defensible?

HypothesisThis sequence is a synthesis informed by the reported failed pilot and Otman's measurement method. It is not presented as an industry standard or a guarantee of return.

Application lenses

One method, three places to apply it.

Enterprise AI adoption

Connect central direction to local workflow ownership, manager reinforcement, permission, and evidence.

Sales workflow adoption

Measure one seller workflow through quality, rework, support, and operating value instead of tool activity alone.

Learning transfer

Test whether learning reaches the job, changes behaviour, and survives manager and workflow friction.

These are lenses inside one flagship. They are not separate brands, project cards, or claims that every adoption problem has the same intervention.

Champion architecture

Champions are infrastructure, not the diagnosis.

Local champions

Useful when peers need translation, demonstration, and a trusted first line of support.

Embedded coaches

Useful when the workflow is complex and practice needs direct observation and correction.

Manager reinforcement

Useful when priority, protected time, review, and consequences determine whether practice survives.

HypothesisThe mechanism should follow the observed constraint. Enthusiasm alone is not evidence that a champion feels the target pain, holds local legitimacy, or has protected time.

Operator proof and boundaries

Transferable mechanisms, with the red lines visible.

User

Relevant proof

More than 700 professionals trained in practical AI adoption. An internal platform supported more than 400 EMEA sales representatives. A sustainability champion rhythm ran across four EMEA regions for approximately two and a half years, with content across 19 languages.

User

What is not claimed

No ownership of an AI champion network. The HP network concerned sustainability, not AI. No measured paid client return. No eight years under a formal learning and development title. No compliance certification.

Inspectable build

The repository carries the method and its tests.

The public repository defines the evidence schema, three simulated examples, invalid fixtures, decision gates, claim boundaries, application lenses, and the preserved legacy curriculum.

DisclosureThe repository and this page received material AI assistance. Otman Mechbal remains the human decision owner for claims, publication, and future revisions.

YouTube field notes

Four videos are planned. None is published yet.

Why AI adoption stalls after access

Video coming

Build safely, Defend safely, Decide safely

Video coming

Three champion network architectures

Video coming

From vanity metrics to workflow evidence

Video coming

No video file, thumbnail, iframe, or unavailable YouTube address is loaded. A future video will use a privacy enhanced YouTube embed, lazy loading, an accessible title, fullscreen support, and a transcript or summary link.

Conversation

Bring one workflow and one decision.

If AI activity is visible but the workflow, owner, evidence, or stop condition is not, the first useful conversation is about the gap. It is not a promise that training, champions, or automation is the answer.

Gaps
  • UnverifiedNo measured paid client case validates the full method yet.
  • UnverifiedThe four YouTube videos do not exist yet.
  • UnverifiedThis local page has not been published, deployed, or approved as a clean external export.