The 20 People In Your Organization Who Need Enterprise Architectureposted by Anna Mar, March 11, 2013
Few people are successful unless other people want them to be.
~ Charlie Brown
Enterprise architects are leaders. They're near the top of the technical food chain in any organization. As leaders, there are a lot of people in the organization EAs can help. It's by helping these people that EAs add value.
1. Chief ArchitectEnterprise Architects usually report to the Chief Architect. He/she is likely to tell you exactly how they expect you to help them.
2. CIOThe CIO may have his/her own ideas about how you can help. Alignment of business and IT strategies, IT transparency, etc.
3. CTOEAs can help to identify inefficient spending, inaccurate ROI predictions, doomed projects, etc.
4. CEOThe CEO is often interested in IT metrics, IT strategy, IT cost control, innovative technologies, etc.
5. COOThe COO is interested in operational efficiencies driven by IT automation and tools. The COO may also be interested in special architectural topics.
6. Business CXOBusiness CXOs may be interested in virtually any aspect of EA. One thing that tends to come up is business strategy and its mapping to IT initiatives.
7. CTOThe CTO will have a keen interest in technology architecture.
8. IT DirectorsIT directors want to be part of the architectural decision making process. They may have enterprise-wide architectural initiatives they need help with.
9. IT ManagersIT Managers want to ensure their projects get through the EA governance process without any hiccups. They will also be involved in the EA process of blueprint and strategy development.
10. IT Risk ManagerIT risk needs to understand architecture at the enterprise level. They may also require hooks into the EA governance process.
11. IT SecurityIT security should be involved in the EA governance process. Security is an integral part of enterprise architecture.
12. MarketingThe marketing team may require architectural opinions in regards to product development initiatives.
13. Shared Services DepartmentsThe managers of teams such as ESB and BPM need the support of the EA process to promote the adoption of shared services.
14. Business ArchitectsIn some cases, business architecture falls under EA — when it doesn't a high degree of collaboration is required.
15. Data ArchitectsData architects and EA work together on enterprise taxonomies, blueprints, strategy, etc.
16. Technology ArchitectsBoth EA and IT architecture teams often report to the chief architect. In any case, there needs to be a high degree of collaboration between the two teams.
17. Project ManagerEA can help project managers to bulletproof project architecture in early project phases. EA taxonomies are also of interest to project managers.
18. Business AnalystsBusiness analysts need to understand how their projects fit into the bigger picture.
19. Solution ArchitectsEAs can help solution architects to improve their solutions and to understand how their solutions fit into the global context. EAs can also mentor SAs who are interested in enterprise architecture as a career.
20. General StaffWhen EA publishes and maintains a current state blueprint people in the organization use it. People will use it to facilitate conversations with their business, as training materials, etc.
Special RequestsIt isn't unusual for EA to get requests for help from virtually anyone in the organization. Don't be surprised to get a call from the legal department, HR or even the chairman of the board.
Don't take it too farI don't know the key to success, but the key to failure is trying to please everybody.
~ Bill Cosby
An an EA, there are a lot of people in your organization who need your help. You're going to have to prioritize your time. The good news is that EA has no lack of opportunities to be of value.
A guide to information security including cheat sheets, best practices and checklists.|
Technology reference cards (executive overviews).|