I have always gravitated towards data because I enjoy identifying patterns to tell a story. I am also a passionate Agilist, playing the role of change agent in Agile Transformations. Therefore, my natural inclination has always been to couple the two together to drive change.

I like to think of collecting team data as just another feedback loop in an Agile environment. After all, the people doing the work know best! Therefore, why not collect data points from teams to identify areas for continuous improvement throughout the organization? I have had some success in this area, but unfortunately this approach has not always lead to the desired outcome.

Like everything else that could be used for good, data can also be leveraged for evil. I have learned the hard way that if an organization lacks an Agile mindset, and does not foster an environment of safety, trust, and experimentation, collecting team metrics can actually lead to more harm than good. However, once the prerequisite of safety is established, data no longer becomes your enemy as a change agent, but your ally, and a powerful tool in your Agile coaching toolbox.

I have had both success and failures in this areas. Join me for this interaction session where I share my experiences and help answer some of your questions on using data to drive change.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Levelset
    1. Revisit the Agile mindset and the intent of Agile; happier employees, delighted customers, and better business outcomes
  2. Agile Adoption Timeline
    1. Purpose:
      1. Highlight once the Agile mindset is acquired by the organization and leadership, there is an acceleration to better business outcomes
      2. This section sets the stage for the correlation between the Agile mindset and use of data in change initiatives
  3. Define Data Collection and Analysis
    1. Another Feedback Loop in an Agile environment that enables organizations to uncover organizational patterns they may not know exist
  4. Experience Report: The Failure
    1. Share the context and experience in which data utilization in a change initiative backfired and lead to more harm than good
    2. Examples & Takeaways
    3. Tie takeaways back to Agile mindset and Agile adoption timeline
    4. Advice for organizations who have not acquired the Agile mindset
  5. Experience Report: The Success
    1. Share the context and experience in which data utilization in a change initiative was very powerful and helped lead to better business outcomes
    2. Examples & Takeaways
    3. Tie takeaways back to Agile mindset and Agile adoption timeline
    4. Advice for organizations who have acquired the Agile mindset.
  6. Summary

Learning Outcome

  1. The Agile mindset is one that focuses on happier employees, delighted customers and better business outcomes
  2. Acquiring the Agile mindset is the turning point for an organization's Agile transformation.
  3. Collecting data in an Agile environment is an additional feedback loop used to make decisions and identify organization constraints.
  4. Command and control environments, Agile in name only, lack safety and trust. Utilizing data to drive change in these environments can lead to more harm then good.
  5. Agile Leadership environments contain safety and trust. In these environments, data becomes a change agent's ally.
  6. Aggregating data points to tell a meaningful story helps Agile coaches and leadership to uncover organizational constraints and coaching needs.
  7. Agile team fluency, safety, and happiness are leading indicators of better business outcomes.

Target Audience

Internal FTEs with the desire to drive positive change and a focus on happier employees, delighted customers, and better business outcomes.

Prerequisite

All participants should have the desire to learn, challenge the materials, and be prepared to be interactive.

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  20 hours ago
    reply Reply

    Typo on slide 36: "Data is you ally" should be "Data is your ally"