Geyto Research · Mariano D'Angelo · Essay · · 3 min read

Why technology implementations stall after go-live

Go-live proves that a system works, not that the work has changed. What research says about the stage where implementations stall.

In brief: an implementation can finish well and still not produce the change it was meant to. Go-live closes a technical project, but the result depends on a second stage in which the work has to reorganize around the system. Research on technology implementation has described that stage for decades, and in that stage the software is only one part of the problem.

Go-live measures one thing; another is expected

On go-live day, something real is verified: the system is configured, connected and available to the people who have to use it. That is an achievement, and it deserves recognition.

What go-live cannot verify is whether the way of working has changed. M. Lynne Markus proposed a useful distinction here. She uses the term technochange for projects in which technology is the means to change how an organization works. In those projects, technical success and organizational success are two different outcomes, and the second does not follow automatically from the first.

Three reasons it stalls

1. The benefit depends on changes that were not in the plan. A new system can require changes to handoffs between areas, to who decides what, and to the information they decide with. If the project was planned as an installation, those changes have no owner.

2. Support is withdrawn when demand is highest. During the launch there is hands-on help, consultants and attention. Afterwards, the project team disbands just as the cases no one anticipated start to appear.

3. The old routine is still available. As long as the spreadsheet, the paper or the usual shortcut still works, the new system competes with it. People do not choose the worse option. They choose the one that lets them get their work done that day.

Katherine Klein and Joann Sorra defined implementation effectiveness as the consistency and quality of an innovation's use by the people who are meant to use it. They identified two conditions: a climate that supports that use in concrete ways (time, help, recognition) and a good fit between the innovation and what people value in their work. Both are prepared before the launch, but they are tested and finished after it.

Timing matters more than it seems

Marcie Tyre and Wanda Orlikowski studied how technologies are adapted once they are installed. They found that adaptation is concentrated in a short period right after introduction. Once routines settle, the room to adjust shrinks, and the problems that were not solved in that window become part of daily practice.

This changes how to read the post go-live stage. It is not a period of passive stabilization. It is a moment in which much of the shape of the work gets settled.

What to do with this

  • Separate technical success from change in the work in the plan, with different owners.
  • Keep close support in place in the stage after the launch, not only during it.
  • Look at which old routines are still alive and ask what they solve.
  • Review the initiative, not only the people: it may be asking too much, too soon, or in an order the work cannot absorb.

This is the view we develop in our approach and in Geyto Learning, the capacity side: what people and teams need for a change to become part of their work.

Geyto Research publishes essays, evidence reviews and market notes on what happens after go-live.

Frequently asked questions

What happens after go-live?

The system is available, but the way people work has not changed yet. This is the start of the stage in which people have to build the system into their routines, and it is where an implementation can stall.

Does a successful go-live guarantee adoption?

No. Go-live shows that the system is configured, connected and available. Adoption happens when the change becomes part of daily work and holds over time.

Why does an implementation that went well stall?

Research points to several causes: the benefits depend on changes to the work that were not in the plan, support is withdrawn when demand is highest, and the old routines are still available.

Sources

  1. Markus, M. L. (2004). Technochange management: using IT to drive organizational change. Journal of Information Technology, 19(1), 4–20.
  2. Klein, K. J. and Sorra, J. S. (1996). The challenge of innovation implementation. Academy of Management Review, 21(4), 1055–1080.
  3. Tyre, M. J. and Orlikowski, W. J. (1994). Windows of opportunity: Temporal patterns of technological adaptation in organizations. Organization Science, 5(1), 98–118.

Share