How was Training?


I thought it achieved the purpose of explaining EA and how to put it in place, and it was helpful that the instructor integrated the education with a reasonable understanding of what we already have in place. - IT Architect, Hasbro, USA, Jan 2013

Recommend PEAF?


Yes - An enterprise approach to business - Consultant, Pioneer Information Services, USA, Jun 2010

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

The Architecture Paradigm exists to help people deal with the Structural Complexity and Transformational Volatility of things.

Many people use the building analogy when talking about architecture and while there are a lot of generic similarities they differ in two extremely important respects. Firstly, the architecture of a lot of things is mostly important to be able to build them, like Buildings, while the architecture of the Enterprise is mostly important to be able to change it. To Transform it. Secondly, what is produced in the Building world is tangible, physical things that can be seen and touched - they are bound by the laws of physics, and it doesn't matter how important you are or how much money you have, you cannot install the light fittings before you have erected the ceiling. Physical anomalies that make no sense cannot be hidden and forgotten about. However, in the world of Enterprises there are no such limitations, people can, and frequently do install "the lights" before "the ceiling", or decide that an "effluence outlet" would be a good idea in a "kitchen". There are no physical limitations and the scope for hiding or ignoring things that are bad is immense.


2008-2016 Pragmatic EA Ltd