When the trust reading went amber and the adoption number did not move
Orien Global Services is a composite case, built from patterns across real programmes. It is not a client. Its pattern, however, is a common one. Eight weeks after go-live in a high volume decision function, the usage dashboard was green. Logins were high, tasks were completed in the system, and the programme sponsor had begun to describe adoption as done.
At the same time, the pulse measuring whether people felt safe to disagree with the AI had moved from green to amber.
Two signals, two different questions
Usage is a behavioural signal. It answers whether people are using the system. Trust and psychological safety sit in the sentiment signal, and they answer whether people feel able to challenge it. A programme can score well on the first and weakly on the second for a long time, because compliance and confidence are different things.
Nothing in the usage figure was wrong. It was measuring something other than what the sponsor was reading into it.
What an amber reading is and is not
It is not a forecast. An amber trust reading does not say what will happen to the programme, and nothing in the framework claims that it does. It says that the measured condition has moved, that it moved at a specific point, and that someone with authority should look at it before the next gate.
The temptation is to wait for a second indicator to confirm. By the time one arrives, the pattern it confirms has usually set. The point of reading sentiment alongside usage is to make the divergence itself the thing that gets examined.
When two signals disagree, the disagreement is the finding.
What to ask on Monday
Start with HR-7, which measures whether people feel safe to challenge the system, and read it beside HR-6, which instruments the behaviour itself. Then ask where the two diverge, which population it is concentrated in, and who owns the response.
If the answer to the last question is nobody, that is the first thing to fix. A signal without an owner is a number on a slide.
The absorption ceiling nobody scores
Concurrent initiatives draw on the same finite capacity, and no single programme can see the total draw. The ceiling is real, it is measurable, and almost nobody measures it.
Shadow workflows are quietly holding your adoption numbers up
Go-live does not eliminate the parallel process. It drives it underground, where it keeps the numbers looking healthy while the transformation quietly fails to land.
Nobody can prove it worked, and that was decided at the start
The inability to demonstrate return is not a reporting failure discovered at the end. It is a design decision taken in the first ninety days, when the value case was written in a form that could never be tested.
Start with the free diagnostic
Ten questions, an indicative readiness band, and one prescribed next step. Returned on screen, no call required.
See what it measures