Skip to main content

5 Key Components of a Successful Enterprise Architecture Function

5 Key Components of a Successful Enterprise Architecture Function

Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company.

However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies.

1. Governance

Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes. The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to talk. Pick a specific topic, typically a critical pain point, which might be some business capability, and create a dialogue about how it works today. Each function will be able to share their perspective of how it “works” and usually it’s educational for everyone in terms of learning how other groups are impacted. An enterprise effort can exist only when a cross-functional group of business functions prioritize that effort.
2. Talent

In my opinion the best Enterprise Architects (EA) must have two critical qualities – pragmatism and business acumen - in addition to deep technical skills. Yes, it is important that they have good communication skills, good influencing skills and are good at simplifying complex topics. But pragmatism and business acumen are critical as an Enterprise Architect. A pragmatic EA is able to articulate current state, propose a future state and then pragmatically articulate a reasonable way to head towards that future state. Probably the hardest job of the EA is to find a path forward that is realistic given the current state architecture and the myriad of other constraints related to budget, resources and time. Perfection is the death sentence of Enterprise Architecture because it will lead to paralysis. Doing nothing means that systems will continue to atrophy. EA must find a way to move forward leveraging a pragmatic approach.
3. Executive Sponsors

For Enterprise Architecture to get real traction, you need the most senior level executive sponsors. The optimal situation is to get sales and customer service executives because revenue and customer are usually the highest priority in most companies. Regardless, get executive sponsors who have a strong, respected voice in your company. You don’t need every executive as a sponsor but you do need a critical mass. The reason for executive sponsors is that some of the tough decisions need to be driven top-down – only so much can be lead through grass-roots activities. Common enterprise standards, policies and governance require executive sponsorship.
4. Scope

Be careful not to over-scope EA. Pick a few key enterprise-level business pain points and start with those. Most EA teams have limited resources and budget (like all of IT) so pick your priorities wisely.  Do a few things really well and avoid the trap of trying to kick off too many initiatives and spread your EA team too thin. It is sometimes difficult to reduce your scope when there are many challenges to choose from, but partner with your business partners to determine one or two key focus areas.
5. Business Value

EA must demonstrate business value. This means that the business functions MUST feel and articulate that EA is a value-add. The best way to accomplish this is to focus on improving business capabilities so that the business teams really feel the positive impact of EA. For example, if entitlement or your sales compensation process are broken AND the business sees those are critical capabilities, focus on those. Be wary of just doing “systems consolidation” projects or “technical upgrade” projects – yes these are necessary but may not provide tangible business value. Always include some “wow” projects such as mobile apps or collaboration solutions. Find visible and exciting projects that motivate your EA team and add business value.


  1. تنظيف منازل بالدمام تنظيف منازل بالدمام
    تنظيف منازل بالاحساء تنظيف منازل بالاحساء
    تنظيف منازل بمكة تنظيف منازل بمكة
    تنظيف منازل بجدة تنظيف منازل بجدة
    تنظيف منازل بالمدينة المنورة تنظيف منازل بالمدينة المنورة


Post a Comment

Popular posts from this blog

6 Key Steps to a Successful Mobile Apps Strategy

What IT Can Do to Lead a Successful Mobile App Strategy CIO’s are under pressure to deliver business capabilities on mobile devices, all while optimizing budgets, increasing operational excellence, and providing innovative, secure solutions. It’s a complex juggling act. In the mobile space, it’s tempting to just jump in and start building mobile apps. But corporate IT needs to help balance the exuberance of building apps with using a common set of success criteria. This is especially true if the enterprise wants a manageable and successful mobile app effort, defined by usage, adoption and business value. While corporate IT can provide technical design and architecture expertise, even more important is the role they play in terms of coordinating the enterprise mobile app strategy. Here are six key steps for doing so: 1. Create a cross-functional “mobile app working team” This is a group of business and IT team members that are passionate about creating mobile solutions

Quadrennial Energy Review - Jan 2017 (notes) "The electricity system we have today was developed over more than a century and includes thousands of generating plants, hundreds of thousands of miles of transmission lines, distribution systems serving hundreds of millions of customers, a growing number of distributed energy resources, and billions of enduse devices and appliances. These elements are connected together to form a complex system of systems." "The electricity sector is, however, confronting a complex set of changes and challenges, including: aging infrastructure; a changing generation mix; growing penetration of variable generation; low and in some cases negative load growth; climate change; increased physical and cybersecurity risks; and in some regions widespread adoption of distributed energy resources

The End of Solitude - Response to William Deresiewicz

I recently read an article by William Deresiewicz titled “ The End of Solitude ”. What prompted me to read the article was an interview with Mr. Deresiewicz that I heard on NPR. During the NPR interview, Mr. Deresiewicz delved into the importance of solitude, being alone and time for self-reflection. Of course, you are naturally drawn to premises that are similar to your own so I listened intently as he contrasted the present with the past regarding the lack of “alone” time that we all face today. Mr. Deresiewicz’s literary knowledge is beyond impressive – he’s an academic and is able to compare and contrast numerous thought-leaders of the past and their views of the value of solitude. In “The End of Solitude” he highlights the importance of solitude that numerous philosophers and famous authors have written about for many, many years. My personal appreciation for Thoreau’s writing, specifically Walden and more specifically “Solitude” and “Economy” immediately came to mind as I read