Practical application

A US-based technology and innovation company has completed a twelve-month digital platform rollout. The system was live across the organization. Training had been delivered to every department. Twelve months in, adoption was sitting at 30 percent. In leadership reviews, the team consistently described the rollout as on track. In day-to-day practice, the platform was being used in fragments, and the work it was meant to enable was not happening.

The standard response to a moment like this is to add more communication, more training, or more leadership pressure. Each of these treats the symptom, low adoption, as the problem to solve. The readiness framework starts from a different question: is the team in a position to absorb what is being asked of them, and what is in the way, fears, structural obstacles, or both, on top of what they are already carrying?

Across four dimensions and three layers, two scores stood out at baseline.

Both well below the threshold the framework defines as adequate for absorbing significant new ways of working. The data was pointing at something the leadership team had not been able to name: the team was not resisting the platform itself. They were resisting what the platform represented to them. New ways of working they had not yet tested. New skills being asked of them in public. The unspoken question of whether the system was there to help them do their work, or to do parts of it for them.

That is what the readiness gap looked like in practice. Not unwillingness. Not bandwidth. A team that had not been given the conditions to work through what the change meant for them, and who quietly held back until they had.

Over the following ten weeks, facilitated group sessions and continuous pulse tracking were targeted to the two dimensions the diagnostic had flagged. The work was not about the platform. It was about how the team communicated under pressure, how they handled uncertainty out loud, and how they could surface what the change actually meant to them without it costing them standing.

Daily individual check-ins tracked whether the development was holding. Facilitation reports captured what the data could not, the patterns of who was speaking up, who was pulling back, and where the unspoken concerns were sitting.

There was no additional training on the platform itself. The platform had not been the problem.

The leadership team's own reflection from the engagement debrief, paraphrased: they had spent twelve months trying to push adoption up. The shift came when they stopped working on the rollout and started working on what the rollout meant to the people carrying it.

That is the difference the readiness framework introduces. It does not replace the rollout, the training, or the strategic plan. It identifies, before the work begins, whether the people are in a position to deliver, and what is sitting between them and the work being asked of them. And it gives leadership the data to act on what it finds.