Implementing Enterprise Architectures If We Build It, Will They Come? Mark L. Hess Weston Technology Management Group

2 User compliance depends upon resolving four key issues: Which standards are chosen and why? What governance model best builds user support? What benefits will the architecture deliver, to whom and when? Which implementation strategies will grow user compliance?

3 Enterprise architectures originated in the move to Open Systems and Client/Server in the 1990s The mainframe management paradigm broke The result: two of the most challenging IT management issues today: –The management of technological (and business process) complexity –The shared management of IT resources Centralized Hierarchical Distributed Heterogeneous

4 Architectures and Standards Reduce Complexity Complexity is an enterprise problem, not a user problem

5 The choice of a standard is a tradeoff between “granularity” and “workability” What is a standard? Is a standard a “product”? Does the standard need to be one “thing”? How and when will the standard evolve?

6 Standards provide strategic direction over time What Does the Standard Do? Provides identity management services (e.g., authentication, authorization, personalization, certificate handling and other application development services) and central administration of IT assets. Why is a Standard Needed? To consolidate 3 current Directory Services products to one and to develop a full-function, common infrastructure for use by application developers. To comply with corporate standards effective June What Should Users Do: The strategic direction for Directory Services is MS Active Directory. Novell E-directory and Lotus Domino will be stabilized, with no further enhancements. These products will be repaired as needed. MS Active Directory will be operational during 1QFY07. Existing HQ server migration will be piloted in 1QFY07 with data migration completed by 3QFY07. Field office migration will be piloted 1QFY07 and completed by 4QFY07. Data migration from Novell to Active Directory will be completed by Oct 07. What Should Users Avoid: Further development using Novell E-directory or Lotus Domino. Standard Timeline:

7 Which standard to choose is a trade-off Choose the most granular standard possible that users can and will adopt Economy of Scale (Granularity) User Compliance (Workability)

8 Today’s enterprises have many IS organizations Each “owns” IT resources and functions Each needs a “voice” if they are to work together to achieve a common goal –For many enterprises, EA is the first time they need to work together Governance describes who is responsible for what and how decisions will be made

9 A “constitution” is a shared management model for peer organizations Preamble – the shared goals and benefits Constituents – who is affected Executive Responsibility –who is responsible for the architecture and standards Legislative Responsibility – how will the “laws” be decided Judicial Responsibility – what is the penalty for non-compliance Amendments – how and when will the architecture and standards evolve

10 Value propositions describe what benefits will be delivered, to whom and when Enterprise architectures are developed by the enterprise, to solve enterprise problems, with the benefits accruing to the enterprise For users, compliance is a trade-off between upfront costs and potential future benefits Enterprise management and business unit management are different constituencies

11 Value propositions must address the needs of each constituency Enterprises want economy of scale –By standardizing the IT environment, complexity is reduced and consolidations become possible and support and service becomes focused Business units want interconnectivity and interoperability –Access to enterprise resources, data quality, less rework, better support and service and lower costs These are often “two sides of the same coin” Two value propositions are needed, not one

12 Value propositions must answer the “WIFFM” question Business Context –Mission (or business objectives) –Obstacles –Linkage Benefits –Efficiency – cost and productivity –Effectiveness – value Timing

13 Implementation means user compliance

14 Winning implementation strategies recognize and mitigate these barriers Seek breadth and depth Focus on new investments Find partners Develop intercept strategies Provide help Market the successes Compliance, like a snowball, grows over time as more and more users align with the architecture

15 To gain user compliance: Choose standards for “workability” Adopt a “shared management” governance model Develop two value propositions Develop implementation strategies that mitigate user constraints Expect compliance over time Develop and market the benefits “story”