Its Been A Busy Summer

Wow, it’s been 2 months since my last post. I can’t believe it’s been that long. Things have surely heated up this summer . Outside of spending some quality R&R with the family, I have been extremely busy in three…

Categories Uncategorized

Ten Ways to Kill An Enterprise Architecture Practice

Have you seen practices that you know could kill an Enterprise Architecture practice?  I have.  A recent LinkedIn thread asked for examples, and I came up with my top ten.  I’d love to hear your additions to the list.

How to screw up an EA practice

  1. Get a senior leader to ask for EA without any idea of what he is going to get for it. If necessary, lie. Tell leaders that EA will improve their agility or reduce complexity without telling them that THEY and THEIR BUSINESS will have to change.
  2. Set no goals. Allow individual architects to find their own architecture opportunities and to do them any way they want.   Encourage cowboy architecture.
  3. Buy a tool first. Tell everyone that they need to wait for results until the tool is implemented and all the integration is complete.
  4. Get everyone trained on a “shell framework” like Zachman. Then tell your stakeholders that using the framework will provide immediate benefits.
  5. Work with stakeholders to make sure that your EA’s are involved in their processes without any clear idea of what the EA is supposed to do there. Just toss ’em in and let them float.
  6. Delete all the data from your tool. Give no one any reason why. You were just having a bad hair day.
  7. Get in front of the most senior people you can, and when you get there, tell them how badly they do strategic planning.
  8. Change your offerings every four months. Each time, only share the new set of architectural services with about 20% of your stakeholders.
  9. Create a conceptual model of the enterprise that uses terms that no one in the enterprise uses. Refer to well known business thinkers as sources. When people complain, tell them that they are wrong. Never allow aliases.
  10. Every time you touch an IT project, slow it down. Occasionally throw a fit and stop an IT project just for fun. Escalate as high as you can every time. Win your battles at all costs.

Your career will be short. 🙂

Enterprise Architects are more than “problem solvers”

One of the most common mistakes that people make about Enterprise Architects is the notion that we are problem solvers.  Yes, EA solves problems, but to frame EA in those terms is like saying that an ER Doctor is a bandage changer. 

To help clarify the distinction between a “problem solver” and an Enterprise Architect, I will illustrate the logical argument for both, and show their differences.

Problem Solver Enterprise Architect
Task: understand the problems and solve them Task: understand the opportunities for the enterprise to be better aligned to its vision and focus attention on them.

Methods:

  • Find people who know what the problems are, and ask them.
  • Look for root causes to those specific problems, narrowing focus to the ones that contribute to a desirable outcome.
  • Describe solutions to those problems

Methods:

  • Collect and analyze information to understand the organization.
  • Design the organization to meet the desired level and type of value delivery.
  • Design ways to change the organization and ask why they didn’t already change on their own.
  • Look for root causes and underlying challenges.
  • Focus attention on the obstacles that prevent normal mechanisms from addressing the problem.
Results: well understood problems that are commonly ignored get  solved (without addressing “why they were ignored”). Results: opportunities that no one wants to see or problems that people are afraid to solve are discussed and addressed.

 

The left column is what business analysis is for.  It is what solution architecture is for.  It is NOT what Enterprise Architecture is for.  I don’t care how good you are at doing the stuff on the left.  I don’t care how well it has worked for you in the past while working as an EA.  The “raison d’être” of EA is not to solve well-understood problems.  It exists to find out why the organization hasn’t seen the obstacles that actually prevent success, hasn’t removed them,  and hasn’t figured out how to cope with them.

Five blind men describe an elephant, each in different ways.  The EA is the sixth blind man.  He listens to the other five and says “the problem is not that an elephant is like a fan or a rope or a wall… the problem is that it is standing in the living room, and dropping large amounts of waste on the floor.  Problem solvers try to find a better way to feed the elephant and remove it’s waste.  Enterprise Architects asks why everyone is standing in the same room as an elephant.

Categories Uncategorized

Do Enterprise Architecture Frameworks matter?

Last week I explained why embracing organizational change is important.  This week I will talk about Enterprise Architecture frameworks and whether or not they matter.
What is an Enterprise Architecture framework?
An Enterprise Architecture framewor…

Categories Uncategorized

Building a High Performing IT: Atos and Troux

bg outline

Ben Geller, VP Marketing, Troux
 

peak condition 090313 3 01Today we’re excited to welcome a new partner in Europe, Atos Germany. Atos is an international information technology services company with an annual revenue of $11.6 billion US and 76,400 employees in 47 countries. 

Atos brings experience in strategic planning, transforming and running massive IT landscapes with many moving parts and stakeholders across a multitude of functions. A shining example of this is the work that Atos has done for the past twenty years as the Worldwide IT Partner and Lead Integrator for the Olympic and Paralympic games. There are very few IT projects on Earth that require an IT services company to set up operations every two years in completely unknown territory and then deliver on an extraordinary scale under the scrutiny of the entire world.

At Troux, we are eager to join forces with such an impressive organization. Combined with Troux’s expertise in helping business leaders make more informed strategy decisions by connecting business context to IT, the new partnership will provide customers of both companies with advanced IT solutions and outsourcing services with a global reach.

Like the athletes that come from all corners of the earth to participate in the Olympic Games, IT organizations cannot stand still gaining extra weight and failing to improve efficiency and peak performance. To remain relevant, agile and lean, IT needs to continuously assess and improve how it functions and what people, processes and technology are necessary for an optimal environment.

Together with Atos, we give executives a clear line-of-sight across the entire IT landscape, to better understand which assets are needed to function at its best and to make well- informed investment and divestment decisions focused on the needs of the business. 

For more details on the Troux and Atos partnership, please visit our press room

 



New Call\u002Dto\u002DAction

Categories Uncategorized

Future Technologies

By Dave Lounsbury, The Open Group The Open Group is looking toward the future – what will happen in the next five to ten years? Those who know us think of The Open Group as being all about consensus, creating … Continue reading

SOA Knowledge Exchange, 1 day event, Bristol, 27th September 2013

About the event ******** SORRY, THIS EVENT IS NOW FULL  ********** We are holding a workshop in Bristol this month for Enterprise Architects, Technical Architects or those in similar roles at Universities in the UK. The general aim of the event is to gather and discuss the SOA roadmap strategies we are developing within our […]