All of us have been part of an effort that, for some reason, did not turn out as we intended. It could have been something as simple as that new omelet recipe you wanted to try. Why didn’t your omelet look the same as that pretty picture on recipes.com? Or it could have been the 2013 rollout of healthcare.gov, the beleaguered web portal of the Obamacare initiative.
Somewhere along the way, something went wrong with that omelet and with Obamacare’s website. Identifying what went wrong (and quickly) is a big part of what change management is all about.
What is Change Management?
Whether the goal is to make an omelet or to roll out healthcare.gov, it is important to realize that these products came into existence only after the completion of many individual steps. In the case of the omelet, you beat the eggs, warmed the butter, diced the fillings and so forth. Your future omelet will eventually come from this soup of ingredients.
This soup of ingredients undergoes major and minor changes as you progress through the recipe. The current state of your omelet can be called your “as-is state.” From this as-is