Dummying it Down

The definition of the word “architecture” describes the art or practice of designing and building structures. With this definition, it’s easy to see that architecture has been the center of philosophical debates since Roman times. While the definition of Enterprise Architecture (EA) is generally accepted, it’s still easily confused, misunderstood, pondered and debated. Translating EA speak into your organization’s lingo can improve the credibility, practicality, and ultimately the success of your EA program.

Credibility, Practicality, Success

Describing and selling an EA program to any organization is a challenge. Translating EA speak into your organization’s jargon will add credibility to your program. First, your organization’s knowledge workers will understand the program’s impact and value to their jobs. If they just shake their heads, but don’t understand the message, your credibility as a Chief Architect can be lost immediately. This instantly labels the Chief Architect as the book smart academic that can’t apply EA into real world scenarios.

Next, communicating EA in your organization’s vernacular will improve the practicality of your program. For example, if you’re selling a new technical pattern or the concepts of technical patterns, use the analogy of a blueprint. Help your customers conceptualize the message you’re sending.

Finally, the success of your EA program will depend on your ability to communicate to your organization. You must be able to connect with your constituents on their level. You simply can't expect them to understand and learn EA immediately. While this would make your job easier, it's just not practical to expect your organization to change that quickly.

In the end, dummying down your EA program's communications will add credibility, practicality, and ultimately aid in the program's success.

Pragmatic Advice

• Use analogies wherever possible.
• Use terminology your organization if familiar with. If your organization refers to standards as operation policies, call standards operation policies.
• Don’t assume a shaking head equals comprehension and understanding.

Enterprise Architecture Metrics

These are two great blog entries from Mike Walker about obtaining Enterprise Architecture metrics:

• Obtaining Enterprise Architecture Metrics Part 1
• Obtaining Enterprise Architecture Metrics Part 2
  

Enterprise Architect: Why do you need one?

This is a very good article from CIO magazine about the Enterprise Architect role:

http://www.cio.com/article/127751/Enterprise_Architect

Educate then sell the Value!

You must sell your CXO on the Enterprise Architecture (EA) program before you begin. Before you can sell your CXO on EA, you must educate him/her on the value of EA.

Don’t use the fancy definitions that don’t make sense.

Don’t use fancy definitions when explaining EA. If you don’t catch your CXO’s attention in the first few sentences, then you’re not likely to sell him/her. Educate on the value.

Don’t try to explain the divisions of EA. Focus on the value.

Don’t waste time trying to explain the divisions between your Business, Information, and Technology Architectures. Instead focus on educating your CXO on the value of EA. Value statements could be as follows:

- Common future vision shared by the business and information technology group.
- Support the business through improved information sharing.
- EA provides guidance in business driven information technology solutions.
- EA provides a way to manage complexities of a large IT shop by setting enterprise-wide IT standards.
- Assurance to the business and customers that new IT systems are implemented through a consistent and measurable process.

Guilt always helps.

Make your CXO feel as if he/she is behind the curve. Several large organizations such as Intel, Microsoft, and BP practice EA. In addition, several federal agencies and state government agencies practice EA as well. By referencing other high-performing companies, you can instill the fact that practicing EA can create strategic value for your organization.

In the end, your EA program will never be successful unless your CXO has full buy-in. As you begin your EA Program, you’ll need you CXO’s credibility and backing to implement many of your new governance practices and EA processes. Without support, your EA program will never get off the ground.

Pragmatic Advice

• Create an EA presentation that is no longer than five slides.
• Get time on your CXO’s calendar (ask your boss to help).
• Memorize your presentation.
• Make sure you know enough to answer any high-level or detailed question your CXO may ask. Practice, Practice, Practice.
• Remember you are now your company’s EA expert!

Getting Started

Welcome to my Enterprise Architecture blog. The intent of this blog is to share my experiences in starting an Enterprise Architecture program from scratch.

Step 1: Commission an Enterprise Architecture Program
Step 2: ??????
Step 3: Profit

This blog focuses on Step 2.