Reference Books

Focus Books

Study Guides


BOOK - Enterprise Transformation - A Pragmatic Approach Using POET


◄◄◄ Previous Page         


          Next Page ►►►


The concept of Transformation Debt™ (originally called Enterprise Debt) was created in 2008 as part of PEAF, based on the concept of Technical Debt.

Pragmatic EA Ltd has since clarified expanded and developed the concept into a practical and easily usable methodology.

This methodology can be easily adopted to Pragmatically mature an Enterprises Transformation capability.


Technical Debt only considered one type of guidance “Think Long Term” in relation to IT Solutions (Application, Data, Platform, Technology) - illustrated on the graphic with green lines.

Transformation Debt™ takes this basic idea and expands it in 3 very important ways - illustrated on the graphic with purple lines:

¨      Firstly, it applies not only to IT, but also (using MACE) to the Methods, Artefacts, Culture and the rest of the Environment domain (such as frameworks and locations) that IT is only a sub-domain of.

¨      Secondly, it applies not only to one kind of guidance (“Think Long Term”) but to all types of Guidance (Values, Principles, Policies, Standards, etc) that guide HOW we effect Transformation, and the Structural Guidance provided by the levels above.

¨      And thirdly, it applies not only in one phase (Constructing) but in all phases of the Transformation stack.

In this way, Transformation Debt™ sits at the heart of the Governance & Lobbying disciplines which are the glue the makes the whole Transformation cascade coherent, effective and efficient.

It provides the concept, mechanism and practical guidance that allows for problems or opportunities to be exposed (whenever and wherever they occur), and for them to then be evaluated and raised to the correct level for a decision to be made regarding their resolution in the full knowledge of the implications of doing so or not doing so.


◄◄◄ Previous Page          

          Next Page ►►►

Questions to ponder...

Have you heard the term “Transformation Debt™” before?

Do you think applying “Technical Debt” to all guidance, and all parts and all phases of Transformation is useful?

If not, why not?

© 2008-2018 Pragmatic EA Ltd