Difference between revisions of "Change"

From Pearl Language
Jump to navigation Jump to search
m (→‎Sources: typo.)
(→‎Sources: += Seth’s Blog » Seth Godin » Done to us vs. things we do)
Line 27: Line 27:
*[[50 reasons why we cannot change]]
*[[50 reasons why we cannot change]]
*{{web|url=http://blogs.hbr.org/2013/11/the-pace-of-technology-adoption-is-speeding-up/|site=HBR|person=Rita McGrath|title=The Pace of Technology Adoption is Speeding Up}}
*{{web|url=http://blogs.hbr.org/2013/11/the-pace-of-technology-adoption-is-speeding-up/|site=HBR|person=Rita McGrath|title=The Pace of Technology Adoption is Speeding Up}}
*{{web|url=http://sethgodin.typepad.com/seths_blog/2014/02/done-to-us-vs-things-we-do.html|site=Seth’s Blog|person=Seth Godin|title=Done to us vs. things we do}}

Revision as of 07:28, 19 February 2014

  • All change in organizations is belief change. So, create belief statements.
  • PDCA has been around for decades and pretty much any feedback loop tool/method whether it be Toyota Katas, Agile Retrospectives and even Lean Startup are re-inventions of that cycle
  • Each organization is unique and a custom approach to change is absolutely necessary
  • change is really hard and unpredictable
  • involve the people who are being asked to change in the change itself
  • ADKAR method.

Organizations that take a mechanistic approach to managing work and people would likely go the route of a re-org because the hierarchy and structure is how work gets done. Organizations that take an organic approach to organizational design will watch how the structure emerges and that's a scary concept for many people. Spotify and Valve are great examples of that.

80% of change programs fail. Fail means negative ROI.

Trying to improve the practices of the engineering department without paying attention to the rest of the organization is similar to trying to change an organ within a body without understanding the impact on the rest of the body.

Sources