Recently, I read an article written by Atos Origin. It had to do with Change Management.
Let me try to explain.
Usually, architects design the current and the future state of architecture. Or, in other words, the "as is" state, and the "target" state, as well as the roadmap to move from the current state to the future state. This movement implies change in all views of Process, Organization and Technology, where Technology includes Applications, Databases and Hardware.
Business change is ever more rapidly and some companies go as far as saying that "change is the only constant". Of course, this is not true. We may want to change quickly and flexibly, but change takes time and effort. Moving from the existing state to the target state goes via intermediate states, known as platforms.
Is it the role of the architect to manage this type of change ? In some areas, yes, especially as they relate to process and technology. As to organizational change, mainly due to politics, organizations prefer to manage this themselves.
Where will change bring us ?
"Le roi est mort", i.e. "The king is dead", viz. "the current state of architecture has changed into a new state", i.e. "Hail the (new) king", viz. "Vive le roi". But were there really that many changes ?