I'm having a hard time finding people who are never in a destructive state-of-mind in the IT field.
Each and every people has a good reason at a given moment to resist to change.
It seems difficult for everybody to realize that embracing changes before they occur is the key to longevity and sanity in the IT field.
The problem with IT systems is the same as with employment. Stability and Longevity are now enforced by constantly moving ahead. Trouble comes when people are in a Cobol-ish/Mainframe-ish state of mind, thinking that every single piece of an IT System is destined to last whatever happens.
In the end everyone finishes up blaming the audacious for the sake of costs and responsability.
In fact it is difficult to handle change when you're not driving it. I guess that's why I tend to go to the change orientation part, so that I can precede change instead of being its victim.
So at the end of the day is it really a matter of resistance to change or more a matter of resistance to change driven by others?
mercredi, août 09, 2006
Inscription à :
Publier les commentaires (Atom)
Messages
2 commentaires:
It is true that change is resisted at all levels. For management, change often translates to risk ; for developers, it is often assimilated as a criticism of their work.
Accepting change means to work a lot on ourselves and to further trust the people we work with. So it is clearly not a single-level one-way issue!
It is true that change is resisted at all levels. For management, change often translates to risk ; for developers, it is often assimilated as a criticism of their work.
Accepting change means to work a lot on ourselves and to further trust the people we work with. So it is clearly not a single-level one-way issue!
Enregistrer un commentaire