Elvorta Logo
custom

Horizon

The tool was never the problem. The system around it was.

HORIZON, Human-AI Operational Risk and Integration, is a framework for diagnosing why capable AI tools go unused, half-used, or quietly worked around.

It does not audit the model. It audits the trust, workflow, authority and habits of the people meant to use it

70%

of large organisational transformations fall short of their goals overwhelmingly for human, not technical, reasons

7

domains where AI adoption tends to break, covering the human system end to end

3

levels every audit moves through diagnose the gaps, design the fix, embed the change

The adoption gap

Somewhere between the demo and a wet Tuesday in February, value goes to die. The demo is the tool at its best, on tidy inputs, run by someone who knows exactly which buttons to press. The wet Tuesday is different, messy inputs, a tired team, no time to check an answer that looks slightly off. So people fall back on the habit that has never let them down.
Explanation one - usually wrong
"The tool was no good."
Sometimes true; rarely the real story. Usually, the tool was fine, and the system around it wasn't. Blaming the tool feels good because it points outward. It also leads straight to the worst response: buy a different tool, repeat the cycle.
Explanation two - wrong and corrosive
"The people are resistant."
When someone avoids a tool, they're usually responding to something real: it's slower, they don't trust it, it makes them look incompetent, or nobody told them they were allowed to rely on it. That isn't resistance. It's feedback about the system, not their character.

Closing the adoption gap is not a matter of motivation, enthusiasm or better slides. It is a design job.

What actually kills a good tool

Broken Human connections
The pattern
It sits outside the flow of real work, so using it means stopping, switching, starting again.
People don't trust it, too little, so they ignore it, or too much, so they get burned and then ignore it.
Nobody is clear who's allowed to act on what it says, so everyone hesitates.
The information going in is patchy, so the answers coming out are patchy.
It threatens how people see their own skill and judgement.
After launch, nobody owns it or reviews it, and it drifts.
The new way was never made normal, so the old way quietly won.

Meet Horizon

Examine the system, not the tool

A technical audit asks: is the tool good? A human system audit asks: is the tool being used well? You can answer yes to the first and no to the second and it's the second that pays your invoice. HORIZON redirects attention onto trust, workflow, authority, information, collaboration, governance and habit: the seven places adoption actually lives or dies.

LEVEL 01 · DIAGNOSE

Find the gaps

Look honestly at the current situation. Where is trust miscalibrated, where does the workflow break, who is unclear about their authority? Nothing gets fixed yet a vague "it's not really being used" becomes a specific, named list of weak points.

LEVEL 02 · DESIGN

Match the fix to the cause

For each weak point, choose an intervention that fits the actual cause. A trust problem and a workflow problem need different fixes. Organisations routinely reach for training when the real problem was authority matching cause to fix is the whole game.

LEVEL 03 · EMBED

Make it survive without heroics

Pilot it, review it honestly, build it into the routine. A change that depends on one enthusiastic champion isn't embedded it's borrowed, and it leaves when they do. This is the level everyone underestimates.

Scoring

Red, amber, green

Every domain scored honestly. One red domain can sink an otherwise healthy rollout.

Red

Failing, and actively undermining adoption right now. Start here one red domain can sink an otherwise healthy rollout.

Amber

At risk. Not broken yet, but showing warning signs under pressure it will be the first thing to give.

Green

Working. People trust the tool the right amount, the workflow fits, authority is clear. Leave it alone and watch it.

The seven domains

Where AI adoption tends to break

Together these cover the human system end to end. Score each red, amber or green, involve the people who actually use the tool, and you'll go from "they're not using it" to a specific, workable list within ninety minutes.

Do people trust the tool the right amount, neither ignoring it nor deferring to it blindly?

Signs it's amber or red

  • The team tells one war story about the tool's worst miss often.
  • Staff check every answer so thoroughly the tool saves no time at all or nobody checks anything.
  • Usage splits sharply by person, suggesting trust is set socially, not on merit.

What good looks like

People can tell you specifically where it's strong and where it's shaky, trust is calibrated, not maximised, and anchored in the tool's real track record.

Miscalibrated trust rarely gets said out loud. Flagging that a tool is unreliable, or admitting you've stopped using it, can feel like a career-limiting move in a room full of people championing the rollout. If raising a concern here feels risky, that's a psychological safety problem wearing a trust costume, and it needs to be named as such, not just scored as red

The fix

Show the real track record; name the vivid early miss instead of letting it become folklore.

Does the tool live inside the real flow of work, or off to one side in a tab people have to remember to open?

Signs it's amber or red

  • Using it means a separate app, site or login away from the main system.
  • People copy-paste between the tool and their real work, the smell of a workflow seam.
  • Usage is high in week one and falls steadily.

What good looks like

The tool appears at the moment of need,  in place; people already are. Using it is the path of least friction; the new way has fewer steps than the old one

The fix

Bring the tool into the main flow; remove steps rather than adding them.

Is it clear who decides, who approves, who escalates and what happens when a human and the tool disagree?

Signs it's amber or red
  • People hesitate to act on the tool's advice, unsure if they're allowed to.
  • When the tool and a person disagree, there's no rule for what happens next.
  • After something goes wrong, nobody can establish who was supposed to act.

What good looks like

Every person can say, without hesitation, what they're allowed to decide alone, what needs a second pair of eyes, and who they escalate to.

The fix

Write one line: who decides, who owns it, and what happens on disagreement.

Is the information going in, and what people do with what comes out — good enough to rely on?

Signs it's amber or red

  • Intake fields get filled minimally, late, or not at all under pressure.
  • The tool's answers aren't recorded, so nobody downstream knows what it advised.
  • The same information gets entered in several places, badly, everywhere.

What good looks like

Capturing good input is easy at the moment people have the information. Answers travel with their caveats, three steps downstream.

The fix

Fix the inputs upstream; simplify the form to what actually matters.

Is it clear what the AI does alone, what humans do alone, and what they do together?

Signs it's amber or red

  • People and the tool sometimes do the same work, unaware of each other.
  • Things fall through because each assumed the other had it.
  • Newer staff can't cope when the tool gets it wrong; the underlying skill was never protected.

What good looks like

Every person can describe the three zones for their work in a sentence. Hand-offs are visible in both directions.

Badly drawn zones don't just create duplicated work; they threaten identity. When the tool quietly absorbs the judgement call on which someone built their professional reputation, the resistance that follows isn't about the tool. It's someone protecting who they are at work. Redrawing the zones on purpose, with the people affected in the room, is what turns identity threat back into a defined, respected role.

The fix

Redraw what's handed over; route the right cases back to humans on purpose.

Does anyone own the tool, watch it, and review it once the launch excitement has faded?

Signs it's amber or red

  • You can't name the person responsible for the tool today.
  • Nobody has checked its accuracy or usefulness since launch.
  • "Is it still working well?" Gets a shrug or an assumption.

What good looks like

A named owner holds the remit. A light, real, scheduled review asks whether it's still accurate, used, trusted, and suited to the business as it is now.

The fix

Name an owner; set a recurring review with a route to retrain, adjust or retire.

Has the new way become simply the way things are done, supported by training that matches reality?

Signs it's amber or red

  • The old way is still available and is what people revert to under pressure.
  • Training was a one-off near launch, with no refresh.
  • Usage depends on a champion and dips when they're away.

What good looks likes

The new way is what new starters are taught as standard, and what the team now finds strange to work without. The old way has been retired on purpose

The fix

Retire the fallback; train for the real job, not the feature list.

Horizon tool

Match your pain point

What you're seeing → the domain most likely at fault

The symptom is usually easy to see; the cause is usually hidden. Use this as a starting hunch, not a diagnosis the audit still decides. But it will get you looking in the right place faster.
What you're seeing
Most likely domain
domainThe fix, in a phrase
Staff check every answer the tool saves no time
1. Trust
Calibrate checking to the stakes
Answers go out unchecked, errors slip through
1. Trust
Build proportionate checks
People open a second screen, or re-key by hand
2 · Workflow
Bring it into the main flow
I don't have time for it
2 · Workflow
Find and remove the real friction
A costly action happened and nobody will claim it
3 · Authority
Write who decides and owns it
Everyone hesitates to act on the tool's advice
3 · Authority
State plainly what people are allowed to act on
The tool's quality swings for no clear reason
4 · Information
Fix the inputs upstream
What you're seeing
Most likely domain
domainThe fix, in a phrase
The same case gets entered two different ways
4 · Information
Clarify the fields that matter
Newer staff can't cope when the tool gets it wrong
5 · Collaboration
Protect the skill; route to humans
The tool quietly took over the house voice
5 · Collaboration
Redraw what's handed over
Nobody has looked at it since launch
6 · Governance
Name an owner, set a review
A problem was found by a customer, not internally
6 · Governance
Add an early-warning signal
Your most experienced people resist hardest
7 · Normalisation
Retire the fallback deliberately
A great pilot sank once it went wider
7 · Normalisation
Design the rollout for ordinary teams
Symptoms overlap one visible problem often has two or three domains tangled in it. Treat this as a list of suspects, not a single culprit. Only an honest scoring session, with the people who actually use the tool in the room, confirms it.

Where to start

Score your most important AI tool across all seven domains honestly this week.

Most rollouts fail because they skip the diagnosis and jump straight to a solution. Ninety minutes with the right people in the room turns "they're not using it" into a specific, ranked list of what to fix first