Architecture Team...The Reformation...
I have had conversations with IT leaders in 4 different companies recently and they all shared that they are going through some form of reorganization. I find it interesting and oddly coincidental that this trend is going on.
This reformation of architecture can have some significant benefits:
--> Increased architecture awareness
--> Realignment of resources in a way that better meets the emerging IT demand
--> Increased propensity of the architecture team to drive change to the portfolio
--> Common techniques for measuring value and assessing new work
--> Change always broadens experience and exposure to new problems
into the IT Portfolio
There are risks too:
--> Identity crisis
--> New onboarding process
--> Distraction from current expertise
--> Misperceptions from customers
What I am interested in hearing from the community on is this:
Is your organization realigning the architecture model?
If so, why?
Are you driving the change internally or working with a consultant/integrator?
What insight can you share?
I look forward to your comments!
posted by JT at 9:31 PM
5 Comments:
Where they really "leaders" or simply "managers" who hijacked the term?
Are these four companies using the same consulting firm? I suspect so...
If you mean "reformation"...that's my coin.
Two of the companies are working with the same firm, one I do not know, and the last is reorg-ing due to the addition of a new CTO.
Did you see this post? http://blog.amber.org/2006/04/13/your-pedestal-is-showing/
Yes, our organization (Microsoft) has been reorganizing IT. Architecture was not on the slides last year. It is central to the reorg now. Much of the credit goes to our new CIO, Stuart Scott, who joined us after spending time as one of the CIOs inside General Electric.
EA doesn't drive the reorg. The need to modernize our delivery, improve our cost picture, and reduce complexity... these are some of the things that drive our reorganization.
But I'm not complaining. It is good to see EA get the attention it deserves.
Nick,
EA is important. Its foundationally good for any Fortune 1000 company to have an EA discipline.
Its sad but true (as a peer once reminded me) that we often get more accomplished when the architecture leadership is working below radar...
Thanks again for posting and I will include you in my roll.
-JT
Post a Comment
<< Home