Lessons from an IT transformation failure (iii)
While in every day operations the lack of proper management practices is easy to conceal, this would most likely fail the company at its first large transformation.
Aggregated enterprise architecture wisdom
While in every day operations the lack of proper management practices is easy to conceal, this would most likely fail the company at its first large transformation.
All failed programs I know were besieged by the same problem, an inadequate problem and solution evaluation.
So we keep doing the same things same with same results.
Digital Business; teaming a ?Digital? Leader with a ?Business Manager?
EA is the diagrammatic description of the enterprise, not a figure of speech interpreted conveniently
EA should guide the transformation. A transformation architect would only make sure that that the transformation is based on EA and obeys principles.
On “Managing transformation: principles or methodology first?”
While I agree in general, I would say that the title is rather deceptive because principles are part of methodology rather than opposed to it. A framework may include inde…
Jason Bloomberg writes or more appropriately quotes a few architects on Forbes on the role of EA in “Is Enterprise Architecture Completely Broken?”.
Jason is right in saying that EA has achieved “paltry” degrees of success. But not for…
The idea that only a few consultants can guide us to see the EA at the end of the tunnel is self serving. What we all need though is a framework that enables us do the work properly.
We are proud to announce that SEAS Inc. has published t […]
The world around us is becoming more complex, it is almost accelerating away from us. Being able to plan in this ever evolving world is becoming even more difficult as time passes. New technology, and approaches almost appear daily, which makes planning for these events, almost impossible. Linear approaches to design are no longer the Read More
“Transformation” has become a highly overused, misused, and abused term. Many organizations seem to “transform” on a regular basis. We consultants are also guilty of overusing the term, partly because it represents some of the most interesting work we do, and partly because it is the rare company that can successfully pull off transformational change […]![]()
As Architects we often spend countless hours working toward delivering great artifacts, including a future state, current state and roadmap to assist our customers in developing a vision and plan toward transformation or maturity. This work is often completed and finds its place on the CIO’s bookshelf or the Lead Architect’s desk with little action or even a second look. Why is this work not actively embraced by many organizations beyond the IT walls or even within the IT organization?
Don’t misunderstand my position, I believe all of the work completed during an iterative EA process that outputs the artifacts I mentioned above add value, although if the organization is not “culturally” ready to embrace the work and transform then the effort is for not.
Culture is defined in many ways by many scholars, although I find it easiest to define culture as interactions and relationships between members of an organization or unit within that organization. This assumes there is an organizational culture and sub cultures within that organization. With this said, it is important that we as architects focus on the overarching organizational culture to better understand whether our customers are ready for an EA engagement.
Our first priority is to ensure we are engaged with the highest level of sponsorship within the organization. For instance, developing physical architectures with the platform division does not constitute Enterprise Architecture, but rather a Technical Architecture and will only have an effect on that sub culture within the organization. EAs need to ensure they are seated alongside the CIO, CFO, COO or even the Chief Executive to ensure efforts toward cultural transformation can be enabled via strong sponsorship.
In the public sector this can be a difficult task as most executives are focused on business related practices and often see the CIO and vendors as “IT focused.” It is critical for our communication during initial contact to be business focused. Conversations about technology are not held until key items, like capability modeling, guiding principles and governance structures are embraced by the organization as a result of cultural change. Once these cultural elements are embraced and socialized technology decisions will be easily facilitated with little debate or power struggles. Remember, the “sponsor” understands how important organizational transformation is at this point in the evolution and will help sub groups understand the vision. Communication and vision are critical elements at this point in the journey toward transformation.
Once we have commitment from the sponsor it is critical for the sponsor to understand the partnership needed between the EA Team and Executive Team. The EA Team is not chartered with creating mission, vision, strategy etc. but rather with understanding the Executive Team’s goals and objectives for the organization and aligning the technology investments with these goals and objectives. Every investment decision made is a direct representation of how the organization’s culture is manifesting itself physically.