The PUSH of Agile Causes “Trance Formations”


Push-style “transformations” look good at first, and do not last long. What is actually going on there is this: TEMPORARY EFFECTS. It turns out that when you make a change in a workplace, like changing the brightness of lights for example, the productivity goes up temporarily and reverts back to the mean. It is not lasting. If you wait awhile and dim the lights down a little, same thing. Changes like this cause short-lived increases in productivity. When people are being observed as changes are being made, they temporarily change their behavior.

The cost of these effects is very real, however. And permanent (non-refundable) in nature.

What’s being sold as “Agile transformation” today are mostly short-run productivity increases that do not actually last. Temporary improvement. New procedures, new consultants, new teams, new practices, etc.

Observation. The short-run productivity increases from these temporary effects are all very misleading. They do not actually last; they are 100% temporary. There is no actual “transformation.” Furthermore, it is often highly prescriptive programs that produce these effects. When those highly prescriptive and authoritative (and expensive!) coaches vacate, the improvement goes with them. It’s all very temporary.

Starting with Lesson 4, I explained to you the dynamics of self-management. A little later on (in Lesson 14) I explained how making decisions triggers very high levels of engagement. And how engagement is where all the improvement actually comes from. All of these topics are related: decision-making, engagement, self management, and great results. One begets the other.

Engagement is the name of the game here, and you get it by inviting teams to make some decisions that affect their work. Scrum defines some decisions that only the teams are authorized to make. There’s a good reason for that.

If you are “helping” the team to make these decisions, you are discouraging self-management and self-organization. And this is where all the improvement (if any) is going to come from.

So stop doing that. You are generating disengagement and causing team members to “check out.”

You are creating “trance formations.



If you are party to the PUSH of Agile on teams without consent, you are part of the problem. You’re pushing Agile practices, and making most all the decisions for those who are affected. Or even worse, you are literally “looking the other way” while authority figures in the organization make decisions that the teams literally need to be making to stay engaged.

So stop that. And do these things, instead:

  1. Encourage executives and managers to refrain from making decisions for the teams that Scrum very clearly defines as belonging to those teams.
  2. And then, encourage teams to make the decisions that Scrum says are theirs (and theirs alone) to make.


And after a while, everything will start to improve. In a lasting way.

Because the teams are actually engaged in the difficult work of making decisions as a team.


Agile Coaching Lessons:

[<–Previous Lesson]    [Next Lesson–>]

[Table of Contents]



If you find value in these essays and find yourself curiously drawn to them, consider investigating OpenSpace Agility, and/or  following me on Twitter and/or joining the OpenSpace Agility group on Facebook