How was Training?


The course clearly exposed what is required for Enterprise Architecture to be recognized and successfully managed within an organization. - Associate Director (EA), PPDI, USA, Sep 2010

Recommend PEAF?


Yes - Generic practical approach. - Manager, Information Strategy & Planning, ACC, New Zealand, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

Negativity around EA is widespread but it is not a surprise. Most people and Enterprises have just enough knowledge to be dangerous!

A lot of people have heard of EA. Unfortunately, most of them have only heard parts of the story and from sources of varying quality and completeness. Also those parts of the story may have been heard or told at different points in time. Myths, inaccuracies and untruths abound. With this in mind it's hardly surprising that a lot of people's understanding of EA is inaccurate, incomplete, erroneous and inconsistent.

Many people may think that EA is all a bit hypothetical and ivory tower. This is not surprising as there is no shortage of people who will wax lyrical for hours on end about EA. In fact an entire industry has built up that does just this. Seminars are frequent but never seem to offer much Pragmatic advice or things people can actually use. Consultancies will come and talk to you (for a large fee) about EA but getting them to actually deliver something of value, that's a different story. With all this posturing, style over substance and sound bites, it's hardly surprising that people can think EA is hypothetical and ivory tower.

Many people think EA is of little practical value because they have heard (and continue to hear) stories about how people have failed at "doing" EA. There is certainly no shortage of failure stories but why are those failures happening? The reason is bad implementation. EA frameworks are just tools and like any tool, if used incorrectly they are liable to not "work". Don't blame the hammer if you can't chop wood.

The benefits that EA is supposed to deliver are generally well known and yet most implementations tend not to deliver them. Apart from bad implementation another reason is that either no metrics are used or bad metrics are used. How can you know if something is successful if you do not measure it or measure it in the wrong way?

The Head of Strategy and Architecture of a large UK Government department I worked for once said "EA - it's just something invented by consultants to get them paid more money". To be honest that view is hardly surprising considering all we have mentioned so far. The key problem there though is a lack of understanding about what EA is actually about and how to actually do it rather than the important people in expensive suits waxing lyrical whilst charging you an arm and a leg. When the Head of Strategy and Architecture thinks that EA is useless we have really big problems. This is why education and exposing Pragmatic information about EA and how to do it in a Pragmatic way is so important.


Do you hold these types of views?

Do you know people that hold these types of views?

Do you think exposing the truth behind them is helpful?



2008-2016 Pragmatic EA Ltd