The idea of ‘technical debt’ has been around for a long time. It’s all the things you should have done to write clean code and clear documentation, to have tested everything in combination with everything else – but never quite got round to doing. The thing you built may well work, but at some point somebody is going to have to clear up the mess – so you have a debt until the time and cost of doing that have been met. There’s a clear parallel with organisations: the way they do things has all too often got disconnected from what the organisation wants and needs to get done.. So there’s a constant drag on delivery until the organisation can get itself better aligned to its current needs. That’s organisational debt – and it isn’t cheap or easy to pay it off.
Two bonus Dilbert cartoons included which make the point all too clearly.