How to Build an Effective Enterprise Architecture Team
Overview of How to Build an Effective EA Team
Things to Know
Step Two - Know Your Enterprise
Step Three - Know Your Enterprise Architecture Team's Use Case
Paths Forward to Build Your Enterprise Architecture Team
Overview of How to Build an Effective EA Team
Building an effective EA team involves developing the characteristics of strong EA Teams. This means you need to ensure that your EA team:
- is focused on your enterprise architecture use case
- covers all necessary architecture domains
- has effective engagement prior to decision with the decision makers of your organization.
- has effective engagement to guide your implementation and agile development teams
- uses an optimized enterprise architecture framework
- has access to a dynamic architecture review board
- makes use of:
- analytic architecture models that answer your questions and decision criteria
- reference architectures that speed up your work and improve analytic quality
- viewpoint library that supports analysis of candidate architectures according to your stakeholder's concerns
- architecture alternatives and trade-off
- employs dynamic work management and delivers ahead of key business cycles
- is a learning organization
- employs the right skills
Several key considerations inform the development of your EA Capability Roadmap.
First, know your history. A step improvement from good-to-great differs from a re-boot. You need to know what you can use to build off and what you need to abandon.
Second, know your enterprise. Follow the definition of the enterprise used in the Leader's Guide is tied to the boundary of your architecture. You need to know the expected scope.
Third, know your enterprise architecture use case. We use a simple analogy - the recipe for the best filet mignon is not useful for a fast-food restaurant. You need to deliver support for the type of improvements your stakeholders want help with.
Once you know where you are going, use capability-based planning. There are three paths forward:
First path, engage experts. Get the support of an organization that can help deliver to your enterprise and use case. This path has the highest probability of quick success. We have a set of packaged services to help.
The second path is to train your team. This path is most applicable to a successful team that needs predictable improvements. When you know the predictable improvement, you can engage in the training you need. Be aware that irrelevant training is irrelevant to your improvement.
The third path is to Do-it-Yourself. You follow the end-to-end approach an expert would follow, leveraging available guidance and tools. This is the most common path. EA Team Leaders usually selected because of the cost of engaging experts. We know the cost of engaging our consulting team to help you. We have packaged a set of DIY tools to help build your EA Team.
Step One - Know Your History
Are you being re-stood up or re-booted?
It is the embarrassing question. We always start here. Everything is different if your team is being improved instead of re-booted.
If your team is being re-booted, you need to know why. You need a solid foundation to build your EA Team.
- How did your predecessor fail?
- Who is driving the re-boot?
- What are the success criteria?
If you are not in a reboot, are you improving or switching focus? You need to need to know if something special is going on. Corporate Restructure, Acquisition or Retrenching. Digital Transformation. Financial crisis. Special circumstances change the rules of the game.
The purpose of Enterprise Architecture is to speed up effective change. When you are facing a reboot or a switch in focus, you need to move quickly and start delivering.
Step Two - Know Your Enterprise
What is the boundary that defines the enterprise you need to architect?
Know your scope. This isn't the scope it could be. Nor the scope you want. Or even the scope you are comfortable with. This is the scope your organization expects to be architected. You will design your EA Team to cover your enterprise.
Do you cover all of your organization?
- A department?
- A set of organizations with a common mission?
- Your entire core supply chain?
You need to use an original design to build an enterprise architecture team. A design that fits your enterprise boundary.
Off-the-cuff, it sounds like a simple question to answer. Too many EA Teams get lost thinking about the scope they could cover. Or are comfortable covering.
Step Three - Know Your Enterprise Architecture Team's Use Case
What type of change do you support?
Build an enterprise architecture team around use case to ensure success.
At one extreme, you will support strategy. Everything is a variable. The EA Team supports the directional statements of the enterprise and frames key change.
On the opposite end, there's a traditional IT team handling enterprise systems. When developing IT Architecture, most things are constants in the equation.
Always start with the Enterprise Architecture Use Cases you support. Otherwise, a simple Enterprise Architecture Maturity assessment that is designed for a different use case will harm your team's development.
Your team will live somewhere between these extremes.
Path One - Engage Experts
When you are in a hurry to have a successful EA Team
The first path to paths to a successful Enterprise Architecture Team is engaging experts. Conexiam EA Consulting lives and works around the globe. We have deep experience in capital-intensive, finance, manufacturing and high-tech verticals. We have established teams for century-old organizations and start-ups. Some of the first EA teams we helped establish are still delivering value.
Time-boxed path to a successful EA Team
We start with answering the three questions. Then we pencil in an improvement roadmap.
We work on a set of fixed planning windows. Each window is 6-7 weeks long. In each window, we do four things:
- Delivery of useful architecture by your team
- Improvement in the ability of your organization to use good architecture
- Build method, references architectures, models, and templates while developing architecture
- Develop your people's skill and experience while developing useful architecture
We Start with the Hard Problem
We start with identifying the problem - why is your EA Team in the room? What is useful architecture in the planning windows? This highlights the deliverables you need to produce. Then we breakdown the deliverables into work product. Each work product will have an accountable resource and due date.
Those work products need method, reference architectures, models, and templates. Those work products get developed by everyone. Your team and our team.
We achieve success when your team delivers useful architecture. Architecture that addresses the question at hand. Architecture that helps your stakeholders change your company.
Path Two - Train your Team
Enterprise Architect technique and other critical skills
The second path to a successful Enterprise Architecture Team is training your Team.
The best training will cover specific enterprise architecture skills. The standard topics including business architecture, security architecture, modelling, analysis, using reference architecture.
We extend our training to cover working with others and thinking skills
- Problem solving
- Decision making
- Critical thinking
- Job task planning and organization
Our training is rounded out with individual Enterprise Architect mentoring. We will work with an architect over 6 months to help them work through successful delivery of useful enterprise architecture.
Path Three - Do-it-Yourself
What type of change do you support?
Build an enterprise architecture team around purpose to ensure success.
At one extreme, you will support strategy. Everything is a variable. The EA Team supports the directional statements of the enterprise and frames key change.
At the other extreme, a classic IT-oriented architecture team focused on the enterprise IT platforms, applications and infrastructure. Here, most things are constants in the equation.
Avoid simple Enterprise Architecture Maturity assessments that assume a purpose.
Your team will live somewhere between these extremes.
Do it Yourself Tools to Build an EA Team
Top-to-bottom guidance for building an effective enterprise architecture team
Industry Standard EA Capability Reference Model
Specialized guidance for building a government EA Team to support a significant initiative
Find the use case that generates the most value
Conexiam Enterprise Architecture Consulting are specialists with experience in multiple industry verticals across the US, Canada, Africa and the Middle East.
We do two things
Our approach to developing architecture that guides effective change and developing EA teams is the industry standard practice.
Building Enterprise Architecture Teams Case Studies
Most of our time is building EA teams. Proven methods that quickly establish high-functioning enterprise architecture teams.
We know there is a lot to think about. We wrote the Enterprise Architecture Leader's Guide. Purpose, domains, operating model, and who you serve.
Design your EA Team to succeed. We suspect you don't have that much time.