Written by Adrian Campbell
A good analogy for an Enterprise Architecture capability is to think of it as the equivalence to an intelligence corps in the military.
Military Leaders and business decision makers will use this Strategic Intelligence capability to:
- Know what their current capabilities are
- Know the capabilities of the enemy (competitors) are
- Understand and gain awareness of the market situation
- Understand the nature of the environment (the market place)
- Understand the chances of success (costs and revenue)
- Help define their goals and objectives
- Help plan their strategies and tactics
- Help create plans of attack or defence (a roadmap for transformation ad change)
- Help to make new plans as the situation changes (a plan is always the first casualty of war)
The military intelligence corps is responsible for gathering, analysing and disseminating intelligence and knowledge about the military situation.
Enterprise Architecture is a business capability that collects information about the whole enterprise and uses various modelling and analysis approaches to create knowledge about the enterprise, provide advice and guidance to CxOs and heads of business units, and provide intelligence in support of their strategic decisions.
Most enterprises maintain some kind of business intelligence capability to collect information and analyse it, but this is not enough. An enterprise architecture capability is also needed.
For a long time the high level decisions made by executives and senior managers have often purely been based on intuition, personal experience and anecdotes.
Often their experience is 20+ years old and no longer relevant. Unfortunately most CxOs didn’t ever learn about enterprise architecture in their MBA courses, or were never taught about it in the first place. This is woeful ignorance in todays fast moving and complex business environment. Don’t let other players on the golf course make your decisions for you.
Often CxOs and senior decision makers are simply copying the decisions made by their competitors, for better or worse. If one of their competitors is playing with Blockchain, so that must be a good strategy right? Right? Another silver bullet or a waste of money? Does your enterprise architecture capability give you a competitive weapon?
Companies that want to succeed should put their trust in real strategic Enterprise Architecture.
Q. How many CxOs does it take to change a light bulb?
– They get their Enterprise Architects to enable the strategic change.
Connections between components in an enterprise architecture model are the basis for identifying, creating and providing knowledge, analysis and intelligence.
In other words, Enterprise Architecture creates the Situational Awareness model for the organisation. The battle map on which the strategies and tactics can be plotted.
Enterprise Architecture models include the strategy, business architecture, information/data architecture, application architecture, infrastructure architecture domains etc.
EA Models also includes a study of the behaviour of their contacts, customers, competitors, vendors and suppliers, from both a strategic and tactical perspective. Both for the current state and future target state, or indeed multiple alternative future states based on alternative business scenarios. The target operating model is the same as the target enterprise architecture model.
The Enterprise Architecture capability provides valuable knowledge, intelligence and experience of the dynamic changes going on and not just as a static set of deliverables or inflexible process. When the strategic situation changes, then the Enterprise Architecture body of knowledge and intelligence needs to rapidly provide the answers. Keeping pace with today’s dynamic markets requires an Enterprise Architecture capability to enable and deliver a strong strategy and amplify it. A better way to change that light bulb.
Achieving a company’s full potential and stimulating creative needs, innovation and knowledge needs answers to lots of known and unknown questions.
Leaders focus on the most important decisions, answering questions such as:
- What if a competitor does this?
- What if the regulations change?
- What can we do to help?
- How to persuade the customer to buy more?
- How to increase profits?
- How to improve our service?
- How to stay competitive in a changing market?
- How can we innovate?
Achieving instant readiness with Enterprise Architecture is better than not being ready at all, or too late.
If you (the CEO) don’t act now to establish an Enterprise Architecture capability now then you will lose out on competitiveness and efficiency.
The most successful leaders in business already have a Strategic Enterprise Architecture capability established, providing the organisation with Intelligence and Knowledge.
Strategic Enterprise Architecture (Intelligence corp) capability includes the following sub-capabilities that enable the most successful leaders in business.
An Enterprise Architecture Capability:
- Provides the ability to envision and visualise an ideal future state based and create a roadmap in order to realise it (situational awareness and winning the war)
- Provides the ability to understand trends that present threats or opportunities for an organisation (countering the enemies threats)
- Provides the ability to identify, analyse, integrate components and connections required to achieve a business strategy (organising your forces)
- Enables and motivates people to work together to realise a strategic business transformation. (ensures success and keeps up morale)
- Enables governance and compliance of strategic relationships with vendors and suppliers, including for cloud services (maintains direction and momentum)
..I love the smell of Enterprise Architecture in the morning. Smells like victory…
6 October 2016
What is an Operating Model?
The term Operating Model is a fuzzy one. What does it really mean? What is in an Operating Model?
It appears that often some consultants totally go out of their way to avoid mentioning Enterprise Architecture and instead focus solely on the term Operating Model.
This may well be a side effect of the misunderstanding of Enterprise Architecture as only concerned with IT Architecture. Or may be because those consultants want to invent new terminology to make their services sound unique?
And by Enterprise Architecture of course I don’t mean just the IT Architecture domains, but all the EA domains which now include:
- Strategy & Motivation
- Business Architecture
- Information/Data Architecture
- Application and Application Service Architecture
- Technology & Infrastructure Architecture
- Physical Architecture (I.e. Archimate 3 Physical Elements)
Why do we need an Operating Model?
- Business Model (BMC)
- Business Motivation Model (BMM)
- Wardley Model
- Strategic Map/Balanced Score Card (SMBSC)
- Business Capability Models
– The business processes that needs to be performed
Organisation and people
– The people and roles performing the processes and how they are grouped into organisation units
Locations, buildings and other assets
– The places where the work is done and the technology, infrastructure and physical equipment in those places needed to support the work
– The Information, data and applications needed to support the work
Sourcing and partners
– External entities, people and organisations outside the enterprise also performing the work
– the management processes for planning and managing the work
A secondary question that I always ask myself is why don’t Business Masters (MBA) courses teach executives and management about Enterprise Architecture?
This may indeed be the source of the fuzziness and lack of preciseness of the term Target Operating Model?
Target Enterprise Architecture Model
Strategic Architecture Domain
Business Model (BMC)
Business Motivation Model (BMM)
Strategy Map / Balanced Score Card Model
Value Chain Model
Customer (Outside In) Domain
Business Scenario Model
Customer Journey Model
Business Services (value proposition) Model
Business Events Model
Business Service Flow Model
Business Capability Model
Capability Dependency Model
Component Business Model
Governance and Compliance Domain
Business Rules Model
Organisation Structure Model
Business Locations Model
Business Roles Model
Business Process Domain
Business Process Flow (Value Streams) Model
Knowledge/ Information/ Data Domain
Business Information Flow Model
Business Information Object Model
Logical Data Object Model
Physical Message Model
Physical Data Storage Model
Application Landscape Model
Application Integration Model
EA Roadmap Model
Project Roadmap Model
Programmes and Project Portfolio Model
16 July 2016
I had an interesting conversation recently about the use of Wardley maps as part of an Enterprise Architecture and Digital Transformation programme recently. I had looked at using Wardley maps some time ago but now I think it is a good time to incorporate their use into normal Enterprise Architecture/ Business Architecture work. They are a very useful addition to the bag of techniques and approaches that I recommend should be used by Enterprise Architects working on the Strategy and Business Architecture domains as well as for the IT architecture domains.
Wardley Maps are useful for understanding the dynamics of what is needed to support a user’s needs. The underlying dependencies between user needs are constantly evolving and many organisations do not recognise this when they come up with a dry list of Business Strategies, Goals and Objectives using a Business Motivation Model. A Wardley map makes strategies much clearer and contributes towards better situational awareness which is critical.
When asked about their strategy the CxOs often simply mention similar lists of ideas that they see other organisations talking about and copy. Often they don’t really understand the buzz words. For instance, what does ‘Digital’ really mean? Is doing Digital sufficient to claim an innovative advantage in the blue ocean? A situational Awareness map will help visualise the buzzwords and their relative importance. It will also allow the organisation to better understand where it can gain an advantage.
Wardley maps help to position the user needs and dependencies in a continuum from the genesis of an idea through to the commoditisation of the same idea, at the same time as creating a value chain as a directed graph and not just as a high level list of business functions. The Wardley map combines the Value chain view with an Evolution and dependency view which helps to identify where the strategies (Both Business and IT) should attack to produce a competitive advantage.
Upstream of Wardley maps, User needs can be identified from modelling Business Scenarios and Customer Journeys. It will be very likely that multiple Wardley maps will be needed.
The dependencies between user needs is similar to the dependencies that can be identified between Business Capabilities. Also the provision of Value to a customer is also the outcome of a Business capability. I can easily see a mapping between a grouping of Business Capabilities or groupings of dependencies between Business Capabilities and a a set of Wardley Maps.
Capability Increments can map to groupings within a Wardley map and dependencies between User needs can be associated with dependencies between Capability Increments.
These complementary techniques will reinforce each other and ensure the resulting EA Roadmap of Initiatives and subsequent Project roadmaps will be well designed and stay meaningful and relevant.
Obviously it is important to remember that the evolutions of user needs identified in a Wardley map are dynamic and the resulting EA roadmaps also need to be constantly kept under review, as business and IT trends evolve.
The best strategy is one that can help identify where to attack when things change.
16 July 2016
Digital strategy is not simply about marketing. It is about a better engagement with potential and existing customers. It is about the perception of the brand created with customers though close interaction via social media and close communication leading to a value proposition that can better serve their actual and future needs.
As with any business strategy, the enterprise architecture discipline is there to support the business transformation to success with a design strategy. It is useful here to remind everyone that enterprise architecture is not just another name for an enterprise wide view of the IT Architecture and the underlying infrastructure architecture
The term ‘Enterprise’ in Enterprise Architecture refers to the greater scope of the organisation which includes the Customers, contacts, stakeholders in the wider market environment which is addressed by the Digital Strategy.
Enterprise Architecture will help organisations to drive innovations and new business capabilities across their entire value chain and to better understand the digital environment in which they will be operating.
Joe Tucci, Chairman and CEO, EMC Corp.– “To stay relevant in this new, always-connected digital universe, businesses in virtually every industry are reinventing their business models for unprecedented customer access, interaction, speed, and scale.”
Using Enterprise Architecture to provide a blueprint for digital strategy
Enterprise architecture consists of the following primary architecture domains.
- Performance Architecture
- Business Architecture
- Information/Data Architecture
- Service/Application Architecture
- Infrastructure/Technical Architecture
- Business Transformation/ EA Roadmap
In addition to these usual enterprise architecture domains, I propose that further Architecture Domains are required for supporting a Digital Strategy.
|Additional Architecture Domains|
|Modelling the Customers’ own Environment, their processes, usage scenarios, customer journeys. Includes the communication channels used for communications directly to the customers and other external stakeholders.|
|Market Architecture||Modelling the outside-in view of what is happening outside the organisation boundaries in the Environment in which the enterprise does business, Social media, Competitors, Competitors Value propositions.|
|The branding, value proposition, projected identity that provides value to the customers for the lifecycle of the business. Includes generic communication to the customer and market, advertising the brand and value propositions.|
Figure 1 Enterprise Architecture for Digital Strategy
Obtain clarity on the goals, objectives and principles guiding your digital strategy Business strategy /Digital strategy
- Business motivation model
- Business Model
- Goals and objectives
Identify the environmental, industry and internal factors that are influencing the digital strategy.
- Market environment
- Modelling what the competition is doing
- Competitors and their activities
- Who else is in your space?
- How do you differentiate?
- Market trends
- Threats and opportunities
- Blue ocean
- Search topics
As usual this means developing Business Scenarios and Customers Journeys, but also modelling the customers (potential and actual) own business processes.
These models will help to understand the customer touch points with the organisation and their desired brand and product experiences.
The Customer Architecture will also include a Connection Model to understand the relationships with customers, communities, to better understand the customers own information and process flows.
A current state Connection Model will capture the Communities, External online nodes, web sites, collaboration social networks (Facebook, Twitter), mobile platforms (IOS, Android) and cloud platforms (Evernote, Google Drive, DropBox, OneDrive) where content exists and customers will go to visit. This Connections model will also include Search sites (Google),
multimedia sites (Flickr), advertising (Ad-Words), entertainment and gaming sites eCommerce sites (Amazon, eBay ), Mobile applications (from Apple Store, Google Play), Smart TV applications etc.
This is similar to a Context Diagram showing interaction between the Organisation and its Stakeholders, but in this case the organisation is not in the centre of the diagram and may not be shown at all in a current state (as-is) Connection Model. The organisation will however be shown in a target state Connection Model.
In a target state Connection model, it will be important to model how the organisations internal models will be coordinated and aligned to the Customers connection Model.
- Outside-in perspectives
- Obtain clarity on who the customer, consumer, partners are, their roles and their values.
- Business Scenarios
- Customers journeys
- Wardley Models
- Customers own processes
- Understand the customer touch points and the desired brand and product experiences
- Connect relationships with customers to better understand them over time
- Customers own information and process flow
- External online nodes, web sites, networks, platforms where content exists and customers visit
- Obtain clarity on how the organisation means to listen and respond to consumers.
- Multi-channel / Omni channel communications
- Communications flows both ways via whatever channel the customer is comfortable with
- Customers’ ideas
- Many channels and many messages
- Understanding and analysis of those messages
- Gaining customers’ attention
- Earning their trust
- Customers motivation
- How customers share content
A brand’s look and feel and tone of voice is as important as its identity, experiences and value proposition.
- Creating brand experiences
- Brand story
- Brand Strategy – Developing a creative brand strategy that is fit for purpose, up to date and distinctive is key to establishing all marketing communications.
- Who engages with your brand?
- Selling the Experience
- Understand the customer touch points and the intended brand and product experiences
- Insights about Customers – observations that trigger innovations
- Blue ocean strategies
The internal mode of the organisations Brand will need to be part of the Value Proposition model and show where the Brand messages will be projected.
- Modelling what the customers will love to buy
- Modelling how customers interact via social media
- Causal loop model (system dynamics)
- Modelling what customers are interested in.
- Mapping to the value proposition
- Minimum viable concept
- Behaviour change model
- Value and truth about the value propositions offered
- Value propositions
- Business Services
Business model canvas
Create the structure required to understand the business model required to realise your digital strategy
Create transparency and traceability across the market model, products and business services model, and the target operating model
Business capability model
- Create a view of the organisational capabilities across people, process, information and technology required to deliver the brand and product experiences.
- Capability assessment against goals and objectives
- Business Capability based Requirements
- Improve the way you manage your digital requirements
- Business Capabilities can be informed by the user needs identified by using Wardley models
Manage information from data architecture and information security through to delivering key messages to the market environment
- Content management
- Understand the content management approach and how it is enabled.
- Value of each bit of content.
- Relationship of content to value proposition
- System dynamics model (stocks and flows / cause and effect)
- System thinking
Provide clarity over decision making across the digital architecture
Business Transformation / EA roadmap
Create an understanding of the extent at which your current capabilities are able to support your digital strategy
Create clarity of the EA roadmap required to support the digital strategy
Obtain consensus, commitment and support for your digital strategy and roadmap which we believe are critical to the success of your strategy
Obtain clarity on your measures of success and identify plans to measure and monitor them
- Investment case
- Programme/Project Portfolio management
- Delivery plan
As usual if you don’t measure, then you can’t manage. However, it is surprising just how many enterprises fail to measure anything at all, including what they have done and what they plan to do.
- Define Metrics and create measures
- Critical Success factors
- Capability Maturity models
5 August 2014
Business transformation involves significant changes to all areas of an enterprise. It focuses on the future strategies.
These includes strategies, business models, operating models, business processes, information & data, systems, products, business services and channels. These are exactly the deliverables developed by enterprise architecture to understand the current state of an enterprise, to envision and design the future state of the enterprise, to discover the gaps between them, to identify the opportunities for investment in change and to plan the enterprise architecture roadmap to achieve the change initiatives.
This sounds just like what Business Transformation approaches do, doesn’t it?
In fact Enterprise Architecture and Business Transformation disciplines have much more in common, than they have differences.
It’s clear that real Enterprise Architects play a critical role in business transformations. The Chief Enterprise Architect is the most important member of the senior management team leading a business transformation and ensuring that it is effective.
By the way Enterprise Architecture, by definition, should not be misunderstood as only being about IT Architecture or Technical architecture, used just to support IT solution development. This is not what real enterprise architecture is for. Business transformation is rarely limited just to IT projects.
The CxOs are the business leadership responsible for providing business direction, identifying the needs for the business transformation in the first place and making the investment decisions. But the Enterprise Architects will work directly with the CxOs to drive out the devil in the details, planning the future transformation roadmap, developing future scenarios, making projections and forecasting future options. Acting without enterprise architects is equivalent to failing to make proper preparations and is asking for trouble. The enterprise architects perform the important task of analysis and evaluating the impact of strategies and proposed changes in detail, identifying risks and prioritising the transformation initiatives into a viable roadmap. They manage the complexity of transformations and are essential to achieving success and effective transformational changes. Enterprise architecture is about bridging the gap between the transformation vision and strategy and its realisation.
What approach should be taken for leading business transformation?
The recommend approach is based on the books by John Kotter, “Leading Change”, “A Sense of Urgency” and The Heart of Change Field Guide”, together with real enterprise architecture approaches to managing strategic change.
Creating the conditions for business transformation
1 Increasing urgency
For Business Transformation to be successful, then the whole enterprise needs to understand the need for it. The whole enterprise needs to have a view of the current state and the motivation for change. Enterprise Architecture provides an understanding of the existing problems and the desired future vision. Avoid complacency and business as usual behaviours. Business transformation means new behaviours and new ways of working.
2 Building a joint Enterprise Architecture/Business Transformation team
A Business Transformation team should not be a group isolated from the enterprise architecture team, but completely integrated with it. Remember that a real enterprise architecture team is responsible for the future business change within the enterprise (and is not just an IT development function), typically up to between 2 and 5 years into the future. Seriously, how can they be kept separated from a business transformation programme?
Identify the members of the Enterprise Architecture/Business Transformation (EABT) team. Look for a mixture of strong management leaders and include a good influential people from a continuum of all job titles, levels of authority and statuses. Remember that enterprise architects are strong and effective change leaders and already cross cut the whole enterprise. Non-enterprise architects in the EABT team will probably have greater political and financial skills whereas Enterprise architects will have cross domain knowledge about the whole enterprise in detail, analytical skills and significantly greater modelling skills. All team members should have good vision and leadership skills.
Hold honest and convincing discussions, dialogues and workshops. Enterprise architects are often useful as facilitators at this stage.
Ask for emotional commitment from all EABT team members and commitment to work together for the common good of the enterprise.
3 Establishing the Target Transformation Vision models and Strategy
What does business transformation success look like?
Planning the strategies and confirm the business motivation. Enterprise Architects and C-level managers will use a Business Motivation Model for this, identifying Strategies, Goals, Objectives and performance measures.
Analyse the various ideas and options to develop an understanding the various Business Models for the target transformed enterprise. Alternative business models can be produced by the enterprise architects using a Business Model Canvas approach and these can be compared with multiple measures, including total cost of ownership and potential revenue.
Avoid thinking in terms of systems and IT solutions too early, after all this is the job of the enterprise architects later on and business transformation is a business problem. Allow for unfettered innovations to emerge from discussions.
Identify stakeholders including customers, partners and suppliers.
Examining the Outside In views from the perspective of these customers and partners.
Creating detailed Business Scenarios, Customer Journeys and Partner Journeys using any suitable story telling approach. Remember that stories are powerful, especially if they come directly from your customers. The enterprise architects will capture and analyse these business stories, but remember that at this stage these are not detailed IT requirements or user stories/use cases from an Agile software development perspective. Those kinds of deliverables will be defined much further downstream.
Identify opportunities and innovations. The team should consider approaches such as a Blue Ocean Strategy (see the book).
Definition the transformation Vision, Values, Motivations.
Defining the transformed value propositions
Analyse and understand the risks, their probabilities of occurring and their potential mitigation.
Engaging and enabling the Enterprise
4 Communicating the Transformation Vision and strategy
Communication is essential for all business transformations if they are to be successful.
There will be detractors and strong opposition to some of the transformation vision. The enterprise architects in the EABT team will ensure that fact based decisions can be made.
Publish and communicate the business transformation models as widely as possible. This will help make the right decisions and solve problems. Don’t assume either the C level managers or the enterprise architects have a monopoly on good decisions. Challenges need to be addressed and responded to.
Obviously some aspects of the transformation vision and strategy will be commercially sensitive and should not be communicated to the competition without careful thought. However, ultimately remember that the enterprise will want support from all customers, internal stakeholders, outside stakeholders, partners and suppliers and this support and buy in cannot be won without communication. Talk often and modify the transformation visions as needed. The enterprise architects will keep track of alternatives and decisions in the transformation model. The Vision and strategies need to be tied back to all aspects of the transformation model. This becomes infinitely easier using a flexible EA management tool (such as ABACUS) and avoiding spreadsheets and Visio diagrams which rapidly become unmanageable.
Ensure that the joint Enterprise Architecture/Business Transformation (EABT) team is able to lead by example by speaking about the transformation vision at any time and to always evangelise about it.
5 Enabling Action
Enabling transformation change is about removing the barriers to change and empowering staff. It involves removing resistance. Often resistance to change from staff is tied to functional divisions and people who are not measured by enterprise’s transformation success but only by fulfilling their own their own personal goals. Paradoxically, it may be the way they are measured and rewarded by the C-level managers that causes people to resist and avoid supporting transformational change.
To enable the right actions, the authorities, responsibilities and rewards need to be re-aligned with the business transformation vision, goals and objectives.
It is the enterprise architect who takes the business strategies and business model and successfully realise them on behalf of the whole enterprise, so are often best placed to also identify the authorities and responsibilities needed to focus people on benefits to the enterprise.
Ensuring that the Enterprise Architecture /Business Transformation (EABT) team has the right authority is also essential, and is able to resolve competing priorities. This authority is also exercised in relation to the governance and compliance stage.
Establish the appropriate metrics and measures, and maintain a scorecard for the business transformation vision, goals and objectives. It is strange how often performance is ignored and enterprises do not know how to measure success, or align performance to desired outcomes. Costs and revenue need to be balanced with other measurement dimensions. Measures should be aligned to transformation changes in the EA management tool.
6 Define Investment Opportunities
Examine the investment opportunities and develop an investment case. The Enterprise Architects will be best placed to determine how realistic and feasible a specific investment opportunity will be, and determine the fine details. Whereas the C-level management will understand the balance of costs and revenue developed in the Business Model.
Enterprise Architects will use a Business Capability model to scope and plan which business capabilities will be modified by a transformational change.
Transformational changes will typically be classed as short term or long term changes. However by definition, transformational changes will tend to be large and disruptive rather than “low hanging fruit”. Short term transformational changes will however be useful for maintaining the transformation momentum across a number of iterations.
Changes to business capabilities are identified as a number of capability increments. The dependencies between these and their priorities will form the first draft enterprise architecture roadmap and provide the scope and context for subsequent change iterations.
Implementing and sustaining the business transformation
7 Keep up the momentum
It is important to keep up momentum for a business transformation. The EABT team must keep communicating and clarifying the business transformation changes.
The business transformation model must be regularly published and all opportunities taken to speak to all stakeholders about it and inform them on status and progress. Capture feedback and responses to continually validate the vision and measure its effectiveness.
Address the fear, uncertainty and doubt from detractors and sceptics and motivate supporters to evangelise about the transformation. Encourage desired culture and values that reinforce the transformation changes. Keep your eyes on the roadmap and don’t assume everything is done after the success of the first iteration and let performance and concentration levels drop. Don’t let the EABT team get diverted into other side projects. Perseverance is important. Remember that change is the only constant.
Develop communication material including web sites, brochures and posters. Posters can be very effective as information radiators.
8 Enterprise Architecture Governance and Compliance
C level managers will be making the investment decisions and providing funding for investments in change.
Establishing an enterprise architecture governance and compliance capability will ensure successful realisation of transformation changes, and help them become permanent business as usual.
Detractors will often try to derail changes but the formal governance and compliance approaches will enforce decisions made but will also provide a platform for challenges and objections to be discussed openly and objectively.
9 Realising Transformation Changes
Business transformation needs many kinds of potential future changes to occur, not least of which are the key cultural changes and organisational changes.
Business Process changes, Information changes, system changes and procurement changes are also important. However for these I recommend designing for flexibility and adaptability not going for a fixed solution which may be cheaper but will invariably be difficult to change the next time. Business transformation should be thought of as a continuous process, enabling an enterprise the rapidly respond to changing forces in the market environment.
Before changes are executed, it is a good idea to conduct a Change Readiness Assessment, if you have not already done this earlier in the Enabling Action stage. This will help find out how prepared the enterprise is for the transformational changes and identify the enterprise’s overall competence, knowledge, skills and capabilities. Any shortfalls will be addressed by planning suitable skills training, and addressing the shortfalls.
For maximum success in strategic business transformations, an enterprise needs to completely and fully use their enterprise architecture resources and enterprise architects. You have to work hard and plan carefully. Building the proper foundation with an enterprise architecture model for the scope of the business transformation will make everything very much easier.
There is no good reason why real Enterprise Architecture and Business Transformation should not be merged as a single discipline. The skills needed for each hugely overlap, especially the Business Architecture domain of enterprise Architecture.
A joint Enterprise Architecture Business Transformation team is essential to achieving successful and viable transformations.
11 November 2013
I was reading this today:
27 June 2013
The Enterprise Architecture team has a lifecycle of its own, but doesn’t operate in a vacuum. The Enterprise Architecture capability fails if it is seen too much as blue sky thinking in an ivory tower.
The Enterprise Architecture team will interact closely with all the other management processes in an organisation, especially the IT management processes. When all these processes work together effectively, an enterprise will be able to successfully manage strategic changes and drive business transformation effectively and efficiently. Often in organisations little thought has been given to the integration of the EA processes to the other management processes. This contributes to making the EA team into an ivory tower, seemingly unconnected with everything else. The aim of this post is to shine some light the EA lifecycle and its interactions.
One of the goals when establishing or maturing an enterprise architecture capability is to make sure that the enterprise architecture a fundamental and normal part of the business-as-usual decision making flow rather than considered as an afterthought.
Too often I have seen major changes apparently started directly at the project initiation phase before there has been any serious appraisal of the business fit, technical fit and feasibility of that change undertaken, not least by the enterprise architects.
The Enterprise Architecture capability is driven by understanding the business strategy and strategic scenarios which drive the business and IT enabled changes in an organisation. It is there to ensure that any strategic change is viable in the future, but it also identifies the dependencies, feasibility, risks, issues, costs, and informs the subsequent investment decisions that need to be made.
The current state and future state enterprise architecture models will be developed (typically using the TOGAF ADM).
In the EA roadmap, the strategic changes will be prioritised and arranged into a meaningful sequence to inform the decisions made by the programme and project portfolio management and before any projects are initiated.
The Enterprise Architecture capability will govern what parts of the future state enterprise architecture are developed and delivered by the projects, and thereafter ensure that the delivered solutions and services remain compliant with it. The compliance stage will also capture and approve any innovations that are identified as useful. The enterprise architecture team and/or a technical design authority will provide design assurance for the projects, to ensure that principles, standards, patterns, policies and guidelines are being followed.
It’s worth noting that the EA lifecycle is not a part of the project solution development lifecycle as many organisations seem to imagine it is, but is a separate lifecycle that operates in parallel at a strategic level. Neither is the EA lifecycle the same as the TOGAF Architecture Development Method.
After a solution has been delivered, the enterprise architecture team will harvest the results in order to update the current state enterprise architecture, to measure performance and to publish a dashboard for the senior management team.
The following diagram illustrates the major stages and processes that are undertaken by an Enterprise Architecture team, for each iteration they undertake.
These Enterprise Architecture processes can be best understood in the wider scope and context of all the processes defined by the COBIT5 framework for the governance and management of enterprise IT. http://en.wikipedia.org/wiki/COBIT http://www.isaca.org/cobit/pages/default.aspx
I’m surprised that COBIT is not used more in UK based organisations, but it is more popular in Europe. I would recommend COBIT5 is used as a broad framework for assessing the risk and value of IT and the governance of all IT management processes.
The following view is broadly based on the COBIT processes, and illustrates the position of the Enterprise Architecture processes relative to the other IT management processes identified by COBIT.
Starting from the Strategy & Vision there is an overall clockwise cycle through all the processes. The Enterprise Architecture capability is responsible or accountable for the processes shown in red, and is consulted and informed about the other processes. The responsibilities will, of course, vary in each organisation and in many cases the enterprise architecture team will be additionally responsible with many more of the Solution Development processes (for example, Select, Acquire, and maintain COTS software products).
In a more mature enterprise Architecture environment, all these processes will be expected to consume and contribute to the knowledge, information and models held in the Enterprise Architecture repository (illustrated in the centre of the diagram). The management dashboard of performance metrics, charts and graphs will be generated from the EA repository.
The above diagram is based on the COBIT processes. The latest version of COBIT5 is more explicit about enterprise architecture than earlier versions were. The following table shows the COBIT5 processes that directly relate to or are supported by an Enterprise Architecture team and an Enterprise Architecture Governance Board.
|APO03||Managing Enterprise Architecture|
|APO02||Define Strategy (in this context this usually means the IT strategy)|
|APO04||Manage Innovation (via the Enterprise Architecture Governance Board)|
|BAI08||Manage Knowledge (via the EA Repository)|
|BAI06||Manage Changes (i.e. Strategic changes and IT enabled Business changes that drive the future state enterprise architecture)|
|MEA03||Monitor and assess compliance with external requirements (via the Architecture Governance Board)|
|APO05||Manage Portfolios (with EA Roadmap)|
|APO011||Manage Quality (via EA Appraisals)|
|APO012||Manage Risk (via EA Appraisals)|
|EDM01||Set and Maintain Governance Framework|
|EDM02||Ensure Value Optimisation|
|EDM03||Ensure Risk Optimisation|
The following table shows who is Responsible, Accountable, Informed or Consulted in regard to the services provided by the Enterprise Architecture team and an Enterprise Architecture Governance Board.
Implementing the EA lifecycle and integrating it with the IT management processes in an organisation will help the Enterprise Architecture capability to avoid the challenges and misperceptions that it is some kind of ivory tower that can be wilfully ignored and disbanded when looking for budget cuts.
Senior management teams will instead come to appreciate the valuable contribution that Enterprise Architecture makes to strategic planning, appraising investments in change, driving business transformations, finding opportunities and innovations, and to understand the value EA has to the organisation as a whole.