Do teams feel as though leaders move the goalposts every day? Do leaders understand how much pain change causes? How to make that visible?

While we embrace change in agile, there's a useful rhythm and cadence to change that helps people absorb the change and improve. Change too often and it can create resistance to the change.

What if leaders understood the disruption that too many changes in process and goals can cause? What if there was a game we could play that would help us see this more clearly?

We'll play a game (Fluxx) in groups to illustrate the impact that changing goals and changing rules has on people. How this can cause decision paralysis, frustration, and ultimately lead to complete disengagement.

We will also discover how moving people from team to team can impact teams and individuals.

1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

  • Doesn't Agile mean constant change?
  • Change and how it affects people
  • What happens when we move the goal too often?
  • Play a game that demonstrates the impact goal and process change has on teams/individuals
  • Debrief and call to action

Learning Outcome

  • Practical way to demonstrate the stress of change on individuals and the impact it has on their performance.
  • Useful considerations for when (and when not) to introduce change.

Target Audience

Managers, Leaders, Coaches, Scrum Masters, Product Owners

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Evan Leybourn
    By Evan Leybourn  ~  1 year ago
    reply Reply

    Can you please describe the game? How does it work?

    • Eric Rapin
      By Eric Rapin  ~  1 year ago
      reply Reply

      I will be using the game Fluxx with some variations to show how rapidly changing goals and processes (rules in Fluxx) impact individuals and teams in both positive and negative ways. We'll be exploring how you can effect change in more useful ways without some of the negative side effects that can occur when we change certain things too quickly (e.g. changing the sprint goal every sprint). I'll provide more detail in the description as soon as I can.

  • Rahul Ganjoo
    By Rahul Ganjoo  ~  1 year ago
    reply Reply

    But but but - isn't agile all about dealing with change? :) Can we focus this on some insights/techniques on how to avoid avoidable changes that are disruptive for teams? Not all change is bad/avoidable.

    • Eric Rapin
      By Eric Rapin  ~  1 year ago
      reply Reply

      Yes, you are absolutely correct. The point of the talk is to illustrate how change (especially very rapid shifting of goals and processes) can have a real impact on team members and how to consider good, healthy ways we can make changes and bring people along with you. We will be playing the game of Fluxx with some variations to illustrate this with discussion on how to notice the impact on teams and individuals and some strategies for mitigating the negative impacts so that the changes we want happen and actually stick. I'll work on explaining the idea better in the description.