Geyto Research · Juan Ferreiro · Essay · · 2 min read
Same technology, different outcomes
Two teams get the same system on the same day. Months later one uses it as part of the work and the other doesn’t. The difference lies in the relation.
Picture two teams in the same organization. They get the same system, on the same day, with the same training. Months later, in one of them the system is part of the work. In the other it sits next to the old way of doing things.
The example is illustrative, but the situation is recognisable. And when it shows up, it is tempting to look for the explanation in the people: one team adapted, the other didn't.
What changes from one team to the other
If the technology is the same, what changes is the relation between what that technology asks of each team and the capacity each team has to respond.
That ask is not the same for everyone. For one team, the new step falls in a quiet moment of the day. For the other, it falls at the peak of the shift. One has someone who knows the system a few metres away. The other has to wait for an email reply. In one, the new information is used to decide. In the other, nobody looks at it.
Capacity isn't the same either. It is unevenly spread across any organization: solid in one team, dependent on two people in the next.
Why it matters
If adoption were a property of the technology, choosing the right tool would be enough. If it were a property of the people, choosing the right people, or training them more, would be enough.
It is neither. Adoption is decided in the correspondence between what the change demands and the situated capacity to respond to it. That is why the same system can work in one place and not in another, and why the answer is not the same for every team.
A question to start with
Before comparing teams by how much they use the system, ask what the system asked of each of them. The answer may explain more than any usage dashboard.
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