When the solution seems clear, but reality is not

In recent weeks, we have explored the fictional case of GameStudioX, a company that tries to be agile, although in reality it only "does agility."

Today we want to stay within the scenario: we are still part of the team, and someone has brought a very elaborate proposal with changes to improve things: metrics, conversations…

And some questions come up:

• Do you think the proposal will be inspiring? Intimidating? Or perhaps it will generate rejection?
• How have you felt when a change is proposed that sounds good, but doesn't fit the reality or the energy of the team?
• Have you experienced improvement attempts that didn't work?

We also invite you to think about a small, realistic change. Something that could be done as individuals without everyone changing first. It could be adapting a practice, having a difficult conversation, or simply changing something we do in our day-to-day work.

Thank you for following the series up to here!