Creeping Into Technical and Experiential Debt

Software technical and experiential debt typically comes about because sales and marketing doesn’t know how to sell the product that has been built, or product owners don’t know how to eliminate user churn of those who have already bought it, or more than likely a combination of both. When this happens sales demands more functionality, or one-off functionality to land any sale they can, and product owners give up working on the hard stuff of how to make what they have better, and both parties end up pursuing greenfield new stuff to add. Both reactions compound the problem as you now have more code to service, all of which bleeds [churns] badly and sales still doesn’t know how to sell it. Technical and experiential debt multiplies. Don’t do this. Pivot away completely from the product or stay with it and focus on reducing churn and building a sales engine that can sell it. Either eliminate the product and start new, or eliminate technical and experiential debt before moving to the next greenfield.