So I was reading XKCD last week, and I laughed out loud when I saw the “Workflow” comic that had been posted:
It’s funny because it’s true.
It can be hard to let go of a process that works, even when the foundation it’s built on is fundamentally flawed. In 2008 I built a utility that would copy records from an Access Database into Dynamics CRM. Every time the form layout changed, it would break the simplistic little utility and it irked the heck out of me. Eventually, we were able to strike a balance in the release schedule so it wouldn’t hit at an inopportune time.
I work with companies every day where we are re-engineering applications and the related processes to better support their business as a whole. Eggs get broken and when those eggs are yours. It’s unrealistic to expect that everyone will inherently find the value in a change–and even with communication like the post above, it’s easy to fall short of contented adoption.
When I think back to the most successful projects I’ve been part of in the last year, effective Change Management is a key theme. Understanding the scope of the change and the degree to which folks will be impacted is critical in providing a path showing how they can best navigate (and take advantage of) the change.
LongTimeUser4: There are better options than holding down the spacebar 🙂