Skip to main content

Technical Debt - Lessons from Economic Crisis

I was reading an article titled UBS' Andy Lees on Why the US Economy Is, All Else Equal, Doomed on Zerohedge.I would recommend the article to anyone who wants to make some sense of what is happening all around us on the economic front.

While the whole article is interesting, the following captured my attention.

We are in this mess because of excessive leverage and excessive consumption, financed by excessively cheap real capital – (not just Bernanke; Greenspan but further back to the end of the gold standard, and in fact even before that as it was this misallocation of capital that forced us off the gold standard in the first place). If capital had been allocated productively, then by definition debt would fall as a percentage of GDP. Total debt may rise, but efficient allocation of capital would always mean the economy would grow faster than the debt as it means you are making a positive rather than negative real return on that capital.
Whichever way you look at it, capital has been massively misallocated for years.
Until the debt is cleared and capital starts to be properly allocated, economic growth per unit of additional debt will continue to sour.

When i think of the above, i can't but think of the concept called Technical Debt used in Software Engineering. I do believe whatever written above also holds true for Technical Debt. You run up a lot of technical debt when you dont properly use the capital (time and people) to build the application. And when you run a lot of bad debt, the return on the invested capital is lower as more capital has to be spent to get the same level of returns ( ROI from the application). This continues till the time we service the (technical) debt.

For more reading on the concept of Technical Debt, please refer here and here.

The Zerohedge article is available here (


Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …