Debt is Normal: The “burning house” mindset for product leaders scaling messy systems

Hook

If you’ve shipped anything meaningful, you have debt. The question isn’t whether debt exists, it’s whether you’re paying interest in outages, slow delivery, and customer distrust.

Thesis

Treat debt like a controlled burn: continuously contain it so it doesn’t become an unplanned wildfire that consumes quarters.

Debt isn’t a moral failure

Debt is the gap between today’s constraints and tomorrow’s ambitions. Shipping creates it. Growth exposes it. Avoiding it just means you pay later under worse conditions.

The ‘burning house’ mindset

Don’t wait for the whole house to be on fire. Run small, continuous burns:

• Fix the top recurring incident class
• Remove the scariest module dependency
• Automate the top manual ops task

You’re buying down risk while keeping momentum.

Make debt visible in product terms

Replace ‘refactor’ with customer-impacting contracts:

• data freshness and completeness
• correctness guarantees
• permission/audit requirements
• performance SLAs

Now debt work has a user story.

How to keep it from becoming politics

Create an explicit budget (for example, 25%) and a visible backlog with impact. Stop debt from being a debate and make it a managed investment.

Actionable takeaways

• Assume debt exists; manage it like risk.
• Prefer continuous paydown over heroic rewrites.
• Translate debt into customer-visible contracts and SLAs.
• Make capacity explicit to avoid constant negotiation.

---