AI adoption · the human layer

Where is your AI investment bottlenecked?

Where people meet their conditions. Usage goes up, the work stays the same. The organisation changes the conditions; people own the judgment. We make this visible in one or two workflows and reach a decision for each.

90 minutes · in person · free · with two of your own workflows

weaksupportive
Illustrative. Change the conditions: the people stay the same, the friction between them eases. Every piece of work passes through a person's touch.
Usage is highThe work hasn't changed
Pilots multiplyNone of them scale
An error in AI outputWho caught it, who owns it?
Evidence of the problem

Usage is rising. The number of organisations getting value is not.

9 in 10

Organisations use AI regularly in at least one business function.

37%

Share reporting any enterprise-level EBIT impact.

~6%

Share of "high performers" getting significant value from AI. This share stays roughly flat.

Source: McKinsey, The State of AI in 2026, global executive survey. Figures are self-reported and evidence the problem, not our method. Linking the gap to the human layer is our interpretation.

Improving what isn't the bottleneck doesn't speed up the flow.

One more licence, one more training, one more pilot. If the bottleneck is elsewhere, none of these change the outcome. First find where the flow is stuck.

The organisation changes the conditions; people own the judgment.

People meet AI with their own patterns. Patterns aren't judged; they're made visible. We intervene on the conditions that shape the behaviour:

CapabilityTrust calibrationRole valueClarity and ownershipTeam climateTask fitSystem conditions
Method · five steps

Find the bottleneck, open it, then move to the next one.

01 · Identify

Find the bottleneck

Read one workflow with three questions: does AI fit this work, is it in the real work, who makes the call?

Try the map →
02 · Exploit

Start with what you have

No new tool or platform. One screen from your usage dashboard and the names of two workflows are enough.

What happens in the briefing →
03 · Subordinate

Your programme stays as is

Training, licences and pilots are planned around the bottleneck. The human layer doesn't replace your programme; it plugs into its stages.

How it plugs in →
04 · Elevate

Change the condition

Human Layer Sprint: 6 weeks, 1–2 workflows. Intervening on conditions, field tests and one decision per workflow.

Sprint →
05 · Repeat

Move to the next workflow

Ninety days later we check: did it hold, plateau or slip back? From a workflow that delivered, we move to the next.

Measurement →

The five steps adapt the five focusing steps of Eliyahu Goldratt's Theory of Constraints to AI adoption.

Step 1 · Adoption Quality Map · 1 minute

Your dashboard doesn't show this.

A usage dashboard tells you how many people opened AI. It doesn't tell you where the work actually stands. The map reads one workflow with three questions and places it in one of five zones. It describes the work, not the person. No score; your answers never leave your browser.

Full version of the map with examples →

Step 2 · Exploit · free briefing

No new tools. Start with what you have.

New investment made before the bottleneck is found doesn't speed up the flow. So the first step is to read what you already have: your dashboard, your programme and two of your workflows.

Free · 90 minutes · in person

Executive briefing

Two leaders join: the business-unit leader who owns the work and a leader from HR or transformation.

The briefing commits you to nothing.

  • BringOne screen from your usage dashboard and the names of two workflows. No raw data or names.
  • LookBoth workflows are read on the map; what the dashboard shows is set against where the work actually stands.
  • Leave withA one-pager: a first reading of both workflows, the questions you couldn't answer, the conditions at play and a candidate workflow for the Sprint.
Step 3 · Subordinate · plugs into your programme

Your programme sets up the tools. Where it gets stuck is the human layer.

If your organisation already has an AI adoption programme or partner, it stays as it is. The human layer doesn't replace it; it plugs into the diagnosis, implementation or scaling stage and runs on the Conscious AI Adoption method.

Stage 1 · Diagnosis

Existing programme: maturity, use cases, readiness.

+ HUMAN LAYERA seven-axis reading, the team's AI working map (anonymous), interviews. Where will pilots get stuck in people?
Stage 2 · Implementation

Existing programme: pilots, workflow design, training.

+ HUMAN LAYERA leader lab and field tests in the chosen workflow: small moves that test where the pilot gets stuck in people.
Stage 3 · Scaling

Existing programme: roll-out, measurement, governance.

+ HUMAN LAYERA persistence check at ninety days: did it hold, plateau or slip back, and why?

For AI adoption partners · the Human Layer Module

Delivery

The stuck workflow reaches a decision: scale, target, fix the system first, stop or investigate.

Expansion

From a workflow that delivered, you move to the next. The engagement carries into a follow-on phase.

Differentiation

Your proposals cover a layer that sits outside the scope of technical adoption programmes.

You can send this page to your client. No outcome or ROI claims, exclusions stated plainly, privacy rules published. The method is in its founding-pilot phase and we say so.

Step 4 · Human Layer Sprint · 6 weeks

One decision per workflow.

The Sprint exists to make a decision, not to produce a report. Evidence and field tests lead to one of five decisions.

SCALEScale

Value is real and judgment is owned. Ready to roll out.

TARGETTarget

AI in these steps, not in those; decision owner and check criteria written down.

FIX THE SYSTEM FIRSTFix the system first

Access, ownership or incentives block the right use.

STOPStop

This work doesn't suit AI; it is set aside on purpose.

INVESTIGATEInvestigate

Evidence isn't enough yet; what to test is written down.

Three reports with every decision

  • 01Two maps per workflow: the work's quality map and the team's AI working map (anonymous).
  • 02System issues with owners: what blocks the right use, who fixes it, by when.
  • 03A tested case portfolio: leaders' real cases and field tests, anonymous.
Step 5 · Repeat · +90 days

Did it hold? Then the next workflow.

We look at the workflow at the same three points: who holds the decision, did the conditions change, is it safe to say "I don't know" in the team?

  • T₀Baseline: who holds the decision, which conditions are at work?
  • T₁Sprint end: what did the field tests change? A decision per workflow.
  • T₂ +90Is the decision applied, did the condition improve? Momentum, plateau or retreat?

Then the cycle starts again.

A plateau is a diagnosis, not a failure report; it usually points to a condition. From a workflow that delivered, we move to the next and repeat the same five steps on the new bottleneck.

Evidence and limits

What we say, and what we don't.

The method is new and in its founding-pilot phase: we designed it and will test it with organisations in the first pilots.

What we will report

  • In how many cases an observable change occurred
  • Which hypotheses were revised or rejected
  • Which system issues became visible, and their owners
  • Where usage and output quality diverge

What we won't claim

  • "Validated" or "psychometric"
  • An adoption score or maturity level
  • That the work created revenue or ROI
  • Anything our sources don't support

Privacy

  • Personal results stay with the person; HR and leaders see no individual results
  • The team map is anonymous; groups under five are not shown
  • No one is diagnosed, no one's history is examined
  • Every finding is labelled observed, reported or inferred
Not tool trainingNot therapyNot a governance canvasNot a validated psychometric testNot personality typing
Request

See the bottleneck in two of your own workflows.

Free · 90 minutes · in person

Executive briefing

A first reading of two of your workflows and a one-page output. It commits you to nothing. Details →

If you continue · founding pilot

Human Layer Sprint

Six weeks on one or two workflows; one decision per workflow, three reports and a persistence check at ninety days. Paid, below standard pricing, for the first three organisations. In return: structured feedback and, if you agree, a named reference.

Request

Your details are sent through a form service (Formspree) and used only to reply to your request; they are not processed for any other purpose.

Eda Evren Karaismailoğlu
Founder · learning architect

Eda Evren Karaismailoğlu

For 14 years in retail and technology retail (NEXT, LC Waikiki, BGN, Altınbaş, Gratis, Apple) I embedded new systems into how people work. For the last 8 years I have worked on human capacity and learning systems with Mindfulevren Academy.

Gratis · Learning and Development ManagerHBS Online · AI for LeadersAbout →