Jump to content

User:Mklubeck/Organizational Immaturity

From Wikipedia, the free encyclopedia

Organizational Immaturity is a state of being that exists when an organization is incapable of enterprise-wide improvement. The keys to this definition are the words “organization” and “enterprise-wide.” Organizational Immaturity is a state of being in which an organization as a whole cannot effectively improve across the entire organization. This malady adds a level to the Capability Maturity Model [1], basically a level 0, and applies to any kind of organization, not only software developers. Unlike the tongue-in-cheek Capability Immaturity Model [2], Organizational Immaturity is a serious look at an organization’s inability to change. In “Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity,” authors Klubeck, Langthorne, and Padgett explain the concept [1] in detail.

Culture

"Culture dictates whether the organization, as a living, complex organism, is either capable or incapable of enterprise-wide change.” [2] It is paramount that the culture be taken into account when attempting to change an organization. Culture should not be seen as something to overcome or bypass. The culture defines the very thing to be changed-- the organization is better described by its culture than it can ever be by its products, machinery, or the processes it employs. If the organization is immature, any organization-wide change effort will fail. For an organization to be able to change, its culture must change. [3]

Risk

The reason Organizational Immaturity is important to identify (the earlier the better) is that it will allow the prediction of success in an organizational change effort. The statistics show that “enterprise-wide improvement efforts are more likely to fail than succeed.” Klubeck[4] And rather than seek out complicated reasons for the failure or point the blame at any particular person, “many times the barrier is simply the inability of the organization to take on the improvement change in the first place.” [5]

From their book, “It is far more likely that an organization’s large-scale, quality-improvement effort will fail. Various researchers found the same disheartening results—the likelihood of failure is well over 50 percent.” And “…total quality management (TQM) efforts tend to fall below expectations—in fact,… “75% of TQM efforts fail to meet expectations.” [6] [7] [8]

So, the concept of Organizational Immaturity brings to light the greatest unspoken risk in implementing Organizational Improvement efforts – the organization may simply be incapable of the changes most methodologies recommend. “It would make sense that, if there is so much at risk, change agents would offer, and leaders would demand, an objective assessment of the likelihood of success before embarking on such a journey. This is a simple first step of determining if the organization has a realistic chance of beating the odds. It is this immaturity that should be addressed before any processes are re-designed, trainings conducted, or structures re-engineered.“ [9]

Benefits

If an organization is assessed as suffering from Organizational Immaturity, (“the lack of ability for change throughout the culture of the company” [10]), the organization can then focus on the first priority of maturing the organization to an acceptable level OR it can find methods which do not require enterprise-wide change. This will help with planning, goal setting, and improvement initiatives. “To move an organization purposefully out of organizational immaturity requires a culture change.”[11]

Traditional change models require the organization to change—not a little bit at a time, not in pockets, but as a whole. And with an organization suffering from Organizational Immaturity, this is tact is doomed to fail. Much money, resources, and time can be saved if the organization is properly diagnosed before trying to implement such a program.


References

[edit]

<references>

  1. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  2. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  3. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  4. ^ , Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  5. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  6. ^ Spector, Bert, and Beer, Michael (1994). Beyond TQM Programmes, Journal of Organizational Change, 7:63–71
  7. ^ Shields, J.L. (1999). Transforming Organizations: Methods for Accelerating Culture Change Processes. Information Knowledge Systems, 1, 2, 105-115
  8. ^ Atkinson, Philip (2005). Managing Resistance to Change. Services, 49, 1:14–19
  9. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  10. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
  11. ^ Klubeck, Martin and Langthorne, Michael and Padgett, Donald. Why Organizations Struggle So Hard To Improve So Little: Overcoming Organizational Immaturity, Santa Barbera CA: ABC-CLIO, 2010
[edit]

http://www.org-immaturity.com/