Enterprise Transformation

A Pragmatic Approach Using POET


◄◄◄ Previous Page         


          Next Page ►►►

Here we see the fundamental Levels of Enterprise Transformation, laid out over the domains of the Enterprise.

The Direction part of the Enterprise feeds requirements for transformation into the Transformation part of the Enterprise which delivers change into the Operations part of the Enterprise.

It should be noted that the Transformation part of the Enterprise may also deliver change into the Direction, Support or even Transformation (the whole point of POET) part of the Enterprise but we just show Operations here as that is the most common occurrence.

These Levels of Transformation are not strict and rigid, but every journey has to be split up into parts, and these high level Levels, form the high level artefacts of the journey, by which to consider holistically, what information is required, from the formulation of Strategy to the Deployment of change into the Enterprise.

For each Level, information about the How that is effected, is done by the next Level down, and information about the Why comes from the Level above.

The white horizontal line at the top of the Transformation domain delineates the transition planning work from the project execution work. Everything below that white line is effectively “projectland” The white horizontal line at the bottom of the transformation domain delineates project execution work from the deployment work.

Our remit is not only what is happening in one of these areas. Our remit is what is happening in all of these areas. In general people work within these areas and in most Enterprises these people try to improve what they do (if they are allowed) and how they do it. This is a laudable thing to do, however, no one is looking at the whole cascade and ensuring that the whole cascade is effective and efficient. The parts are being optimised at the expense of the whole. POET provides the basis for Senior Management to address optimising the whole of Transformation, for it is the output of the whole that most important rather than the output of each Level - this in fact, may mean the de-optimisation of some or all of the parts. For this reason, everything in POET applies equally to all Levels of the Transformation cascade and is the unifying holistic and coherent context in which all Transformation work is performed.

In terms of naming these levels there are two fundamentals.

¨      Enterprise Architecture (EA) consists of all information consumed and produced, prior to project execution, namely Enterprise Context, Contextual and Conceptual.

¨      Enterprise Engineering (EE) consists of all information consumed and produced, during project execution, namely Logical, Physical, Operational and Physical World.


Questions to ponder...

Do you agree with these Level boundaries?

How does your Enterprise map onto them?

Does everyone working within the Transformation domain understand where their artefacts they consume and produce, fit into the whole?

If not, would there be a benefit if they did?

What will you do to allow people to understand how the artefacts they consume and produce, fit into the whole, and what will you use?

If so, how will you solve them?

◄◄◄ Previous Page          

          Next Page ►►►


© 2008-2019 Pragmatic EA Ltd