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

Routines are where change lives

A new system changes little if the routines around it do not change. What research on organizational routines says about technology adoption.

In brief: a new system does not change the work by itself. Work is made of routines: who does what, in what order, with what information and to whom they hand the result. If those routines do not change, the system is likely to end up off to the side. Research on organizational routines explains why. It also shows that routines can be an ally of change, not only an obstacle.

What a routine is

An organizational routine is a repeated pattern of actions involving several people: preparing an order, closing a shift, admitting a patient, approving a purchase. It does not live in one person but in the coordination among several.

Martha Feldman and Brian Pentland proposed looking at each routine in two aspects. The ostensive aspect is the shared idea of how something is done: the procedure, the diagram, "what is supposed to happen". The performative aspect is what people actually do each time, with its variations and adjustments.

An implementation plan changes mainly the ostensive aspect: the new process is drawn and the system is configured. The real change happens, or does not, in the performative aspect.

Why the previous routine holds on

The previous routine does not survive only out of habit. It also survives because it solves things: it coordinates people who already know how to work together, it covers exceptions no one wrote down and it gets the day's work done.

When the new system does not cover one of those things, the previous routine reappears as a workaround: the parallel spreadsheet, the phone call, the paper that travels alongside the system. Those workarounds can have several causes, but they are valuable information about what the change may not have solved yet.

Routines also change

Feldman and Pentland showed that routines are not only a source of stability. Because each performance is a little different, routines are also a source of flexibility and change. People adjust on the fly, try variations and, if they work, repeat them.

That mechanism is what a well-supported implementation builds on. In the study by Edmondson, Bohmer and Pisano of surgical teams, the teams that managed to take on a new technique treated it as a change in the routine of the whole team, not as an individual skill. They practised together, reviewed cases and adjusted how they coordinated.

Adaptation on both sides

Dorothy Leonard-Barton described implementation as mutual adaptation: the technology adjusts to the organization and the organization adjusts to the technology. Routines are the concrete place where that adaptation happens. Sometimes it makes sense to change the routine. Sometimes it makes sense to change the configuration, the sequence or what the initiative asks for first.

What to do with this

  • Map the routines the change touches, not only the system's processes.
  • Look at the routine as it is performed, not as it is written.
  • Treat workarounds as signals for adjustment.
  • Involve everyone who takes part in the routine, not only the person who uses the system.

More in Workarounds are evidence and in our approach.

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

Frequently asked questions

What is an organizational routine?

It is a repeated pattern of interdependent actions involving several people. Feldman and Pentland distinguished its ostensive aspect (the idea of how it is done) from its performative aspect (what is actually done each time).

Why do routines matter in an implementation?

Because the benefit of a system depends on changes to the everyday steps, handoffs and decisions. If the previous routine stays intact, the system is likely to end up off to the side of the work.

Do routines prevent change?

Not necessarily. Routines are also a source of flexibility: each time they are performed they can be adjusted. Change builds on that capacity to adjust.

Sources

  1. Feldman, M. S. and Pentland, B. T. (2003). Reconceptualizing organizational routines as a source of flexibility and change. Administrative Science Quarterly, 48(1), 94–118.
  2. Edmondson, A. C., Bohmer, R. M. and Pisano, G. P. (2001). Disrupted routines: Team learning and new technology implementation in hospitals. Administrative Science Quarterly, 46(4), 685–716.
  3. Leonard-Barton, D. (1988). Implementation as mutual adaptation of technology and organization. Research Policy, 17(5), 251–267.

Share