Emotional Stages of Adopting A Change
In today's business environment, there are number of strategies which explain how to implement agile methodologies in any organization. There are also various stages which guide organizations to get through this change. As any organization embarks on a journey of adopting agile and change the way it works, it is imperative to keep a check on organization’s emotions in the process. An Organization is build on people and people run on emotions. A Positive emotion can take an organization to the highest level of success and a negative emotion can demolish it. Addressing the emotional aspect of change during the course of implementing it can bring upon a fruitful result.
Attend this session to explore the emotional stages that organizations(people) go through while adopting a change. From the excitement of introducing a change, to the despair after passing the start and the resistance in the middle; nothing is quite like a roller coaster of adopting a change.
Outline/structure of the Session
- Introduction (5 min)
- The Emotional Roller Coaster of Change (10 min)
- Reactions and Responses to Change (10 min)
- How to Identify the Moment of Transformation (5 min)
- Strategies for Adopting Change (10 min)
- Q&A and close out (5 min)
- Exposure to strategies in adopting and implementing a change
- Develop an understanding of the various emotional stages while implementing a change
- Walk away with two techniques on how to use emotional intelligence to develop a plan for successful implementation of change.
individual contributors, managers, Agile coaches, Scrum masters, POs
schedule Submitted 7 months ago
People who liked this proposal, also liked:
Avinash Tripathi / Aakash Srinivasan - Agile crocodiles and dinosaurs : Adapt or DieAvinash TripathiAgile Coach | TBR Certified Trainer | SpeakerECOM Consulting IncAakash SrinivasanAgile TrainerECOM Consulting Inc
schedule 7 months agoSold Out!
“It is neither the strongest of species that survive, nor the most intelligent, but the ones that are most responsive to change - Charles Darwin”. Agility is not solely about how fast one can move. On the contrary, it is how adaptive and responsive one is to a change with minimal adverse effect. To survive in its ecosystem, an organization much like a living mammal, must grow in size as well as evolve to adapt and protect itself from predators.
In today's complex world of business and technology, Performance and scalability are key optimization opportunities for any organization. Also, a relentless focus on innovation, human capital and global expansion is pivotal for these opportunities to materialize. The ability to evolve in these areas can create competitive advantage for an organization in its habitat. To address these initiatives and ensure its success, companies need to empower their human capital with the right tools and resources to execute their strategy consistently and reliably in the midst of continuous change.
Attend this session to explore ways to realize these opportunities into tangible outcomes, thereby enabling an organization to evolve, stay competitive, think, lead and execute; driving increased revenues, profitability and market shares as the end result. We will introduce a framework that spans 6 key areas; Ideation, Nature, Vision, Engagement, Synthesis and Transition. The session will also demonstrate techniques to enhance business agility using an agility model and the dinosaur analogy.
Avinash Tripathi - Retrospectives - They Are Not Just About What Went Good, What Went Bad and What To ImproveAvinash TripathiAgile Coach | TBR Certified Trainer | SpeakerECOM Consulting Inc
schedule 7 months agoSold Out!
Retrospectives are one of the events in Scrum which give opportunities to a Scrum Team to inspect itself and create a plan for improvement. However, very often, this event tends to become boring and get away from the answers to three basic questions, What Went Good, What Went Bad and What To Improve. For that matter, at times team may not have food for thought and hence they disengage from these questions. So, what needs to be done or in fact, what can be done in such scenarios? Well, Retrospectives are all about figuring out what needs to be done. But, how do you know what to do, if you do not know what you did?. For starters, measuring a team’s progress on Sprint by Sprint basis might be a solution. Having such data might not solve many problems, but, it could certainly expose them. There are three basic metrics, which have been found to be beneficial for teams’ progress and also thought triggers in Retrospectives. As Mike Cohn once said, measure only what can be measured. Metrics can be misleading, hence it is up to us to measure what makes sense and use it to improve the team.