Avoid-the-13-worst-ea-practices-and-navigate-to-ea-success.pdf

This preview shows page 1 - 3 out of 21 pages.

Avoid the 13 Worst EA Practices and Navigate to EA Success Published: 25 February 2016 ID: G00300233 Analyst(s): Saul Brand, Betsy Burton Despite best efforts, many EA programs fall from "best practices" to "worst practices." EA practitioners must be constantly vigilant and navigate away from 13 worst practices that could sink EA efforts. Here, we identify the 13 worst EA practices and what can be done to avoid them. Key Findings Without "linkage" to business strategy and to targeted business outcomes — which inform enterprise architecture (EA) efforts and provide guidance — it is very dif cult for EA practitioners to make business and IT recommendations that they can act and deliver on. Organizations are not "doing" enterprise architecture if they are only doing IT or technology-only architecture in isolation. Focusing on IT or technology-only architecture is not the same as EA. A current-state rst architecture focuses attention on today's pain points and problems, leading to a tactical strategy of xes or more of the same. When governance and assurance become excessive, bureaucratic and time-consuming and add no value, business and IT teams do their best to avoid or ignore EA. Recommendations Proactively work with business and IT leaders in an innovative, collaborative and consultative manner to drive the organization's business as well as digital business strategies and to ensure a balance between innovation and running and growing the business. Start or refocus EA efforts by de ning a business outcome statement, and use it to inform, guide and drive business, technology, information and solution decisions. Understand and document the current-state architecture driven by the future-state vision — not the other way around. Focus on de ning just enough governance and standards to help guide the organization toward a business-outcome-driven future-state vision, rather than putting the business at risk by over-
focusing and overwhelming users with too much governance and too many standards that often get ignored. Table of Contents Introduction ............................................................................................................................................ 2 Analysis .................................................................................................................................................. 3 1. No Link to Business Strategy and Targeted Business Outcomes .................................................. 3 2. Confusing Technology Architecture With Enterprise Architecture ................................................... 6 3. Focusing on the Current-State Architecture First (or Primarily) ....................................................... 7 4. Excessive Governance and Overbearing Assurance ..................................................................... 8 5. Creating a Standard for Everything ............................................................................................... 9 6. Engrossed in the Art and Language of EA Rather Than Business Outcomes .............................. 10 7. Strict Adherence to EA Frameworks and Industry Reference Models .......................................... 11 8. Adopting an "Ivory Tower" Approach to EA ................................................................................. 12 9. Lack of Continuous Communication and Feedback .................................................................... 13 10. Restricting the EA Team to IT Resources Only .......................................................................... 14 11. Lack of Key Performance Metrics ............................................................................................. 15 12. Purchasing an EA Tool Before Understanding the Use Cases and Critical Capabilities Required by the Organization ........................................................................................................................ 17 13. "We're Done" ............................................................................................................................ 18 Gartner Recommended Reading .......................................................................................................... 18 List of Figures Figure 1. Business-Outcome-Driven EA .................................................................................................. 4 Introduction Just as there are best practices to follow, there are "worst practices" to avoid. Over the last ve

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture