Lean and Technical Debt
When we launch fast and iterate, we tend to build up technical debt.
When is the right time to pay off technical debt? How do we know when we're digging ourselves into a hole?
How do we avoid the knee jerk reaction of "time to refactor" whenever we start looking at a colleagues code?
Sean Murphy commented
I found this article by Reinertsen on technical debt a very insightful take, it include the cost of delay in factoring in total cost of product introduction delay into deferring work: http://reinertsenassociates.com/technical-debt-adding-math-metaphor/