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. Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker. 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 a specific business capability, and create a dialogue about how it works (or doesn’t work) today. Each business function will be able to share their perspective of how it “works” and usually it is 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 hard and soft skills. In terms of hard skills, an EA must have deep technical skills and deep business acumen . In terms of soft skills, an EA must be a great influencer and be pragmatic. It is important that they have good communication skills, good influencing skills and are good at simplifying complex topics. 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. My two favorite exec sponsors are the COO and the CFO. COOs care about operational excellence and CFOs care about efficiency and optimization. The COO and CFO should be tightly aligned to EA and EA should leverage the relationship to address foundational architecture issues.

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. Simpler is better.

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 visible business value. Articulate the business value of what EA does in quantifiable terms by using the business KPIs. 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.