Geyto Research · Juan Ferreiro · Essay · · 2 min read
Installed is not adopted
A go-live tells you that a system works. It does not tell you whether the work has changed. Why installed and adopted are not the same thing.
Technology projects end with a date. The system goes live, accounts are created, training has been delivered, data starts to flow. The project closes.
None of that is wrong. But all of it describes the technology. Very little of it describes the work.
What go-live actually tells you
A go-live is a good test of whether a system works: whether it is configured, connected and available to the people who are supposed to use it. That is a real achievement, and it deserves to be recognised.
What a go-live cannot tell you is whether anything about the way people work has changed. A system can be live and still sit next to the old routine — the parallel spreadsheet, the paper handover, the workaround everyone knows about and nobody mentions in the steering committee.
A system can be live and still not be part of the work.
Why the old routine survives
When the old routine survives, one explanation is resistance: people don't want to change. Sometimes that is true. Another possibility is simpler.
The new step arrives at the busiest moment of the shift. The support that existed during the launch leaves with the project team. The training covered the tool, but not the judgement calls that come up on an ordinary Tuesday. Nobody resisted. The work simply had no room for what the change was asking.
Two questions instead of one
At Geyto we start from two questions, held together:
- What does this change demand of the people and teams who have to carry it — in tasks, timing, judgement and coordination?
- What capacity is situated to respond and sustain it — in a particular shift, team or site, not in the organization in general?
Adoption happens in the relation between those two. When they correspond, a change has somewhere to land. When they don't, it stays installed.
Either side can move
This framing matters because it opens both sides to adjustment. Sometimes capacity needs to be built: support, practice, time. Sometimes the initiative itself needs to change: its sequence, its timing, what it asks for first.
Treating adoption as something that only the organization has to achieve misses half of the picture.
What to look for after go-live
Instead of asking only whether people are using the system, it helps to ask:
- Is the workaround still needed? What is it doing that the new system doesn't yet do?
- Has the new routine survived a busy week, a new hire, an exception?
- Have people's questions moved from how does this work to why do we do it this way?
None of these are scores. They are signs that a change is becoming practice — or that it hasn't yet.
Geyto Research publishes essays, evidence reviews, market notes and framework notes on what happens after go-live. If you are working on a change that has gone live but hasn't yet landed, we would like to hear about it.
Share