What is Enterprise Debt (it's worse than technical debt) and how to manage it? 

As usual a very concise and informative video. Excellent work Dr. Raj.👏

Simple but profound explanation.Well articulated

Thanks for your clear explanation

This was so illuminating, thank you so much.

As always, eloquent and simple way of describing the enterprise debt. While systems and processes can be complex to change, the biggest challenge is really the people part and the Change Management associated with it. People get so comfortable with how "things have always been done this way", unless there is an outside-in approach or a smart and enterprising executive that it is challenging to push the envelope. My 2 cents.

When I think of Enterprise Debt, a term I did not use before watching this insightful video, I think of good housekeeping. The more you delay doing it, the harder it becomes to manage, enjoy and improve your household and the overall user experience of living in it, just drops dramatically. Great work by Dr. Raj!

What piqued my curiosity were the words 'how to manage it". The author of this video (Dr, Raj Ramesh) very eloquently stated the problem about the two kinds of debt (Enterprise & Technical). I was keen to see how he explained how to manage both. At 4' 22" he stated "Architecture can help organisations understand and manage this well". I was keen to see how he addressed the concept of this 'architecture'. At 5' 22" he stated "If they can architect the integration of their data using cloud vendor services the application integration problem goes away". I have 2 questions: 1) What are the underlying tenets behind this 'architecture' & 2) How does any 'architecture' overcome the 'if' question posed at 5' 22" According to my experience & research every architected approach, designed to reduce both forms of debt, have only increased the debt by using 2 insidious, non scientific, techniques: 1) Brainstorming: Developed by an advertising executive c1939 (A Osborn) to try to elicit business requirements (BR) & 2) Normalisation: The 7 normal forms developed between 1970 & 2003 by Codd, Boyce, Fagin, Date, Darwen & Lorentzos to try to design databases from data-items to support said BR So how do these manage the situation? Regards Charles Meyer Richter Principle Information Architect Ripose Pty Limited

Great video Ramesh. It is more important than ever to think strategically today. Thanks for the insights.

you are best Dr.

Still working as of today, ty!

Great video! I love the diagrams too.

Thank you raj sir for your effort to make the most difficult thing explain so easy. I am also in ai/ml field and one thing I learned from you to say things in a simple manner.

Brilliant - so clear. Will be sharing this with all the right people. Would appreciate your insights as they relate to eliminating or minimising “debt” and maximin value, in regards to transformation programs and where they are set up in a siloed way (vertical - business-led) way, rather than top-down / from an enterprise level? Thank you.

Enterprise debt. Technical debt. I think both are the result of failure at enterprise thinking. Thank you Dr.

Great video. Would like to see something that shows a better approach from start to maturity - talk about if/how you think debt is good and then how to manage it (assuming you think it is OK).

Hi It is very good subject . please tel me about your tools which you use for drow and making this video

in the example above, if fridge, washing machine and dishwasher have their own bounded contexts with hexagonal architecture, diesnt it help in reducing these debts?

Excellent explanation Dr. Raj 👏