managing-tech-debt
Strategic technical debt management using insights from 18 product leaders.
- Diagnose urgency by understanding the debt's nature, how it manifests (slow velocity, incidents, shipping blocks), and business context, then choose between incremental improvement, targeted refactoring, or full rewrite
- Full rewrites almost never work as planned; they take 2-3x longer than estimated and require supporting both systems simultaneously. Prefer incremental evolution and component uplift
- Tech debt is product debt owned by PMs alongside engineers, not an engineering-only concern. Quantify costs and include in Top 10 Problems to build stakeholder buy-in
- Monitor the "interest" on debt; if maintenance consumes 80-90% of engineering time, you've run out of runway. Startups should strategically take on debt early to move faster than larger competitors
- Fix bugs immediately rather than backlogging them; bug backlogs become graveyards. Create dedicated time to delete unused code, which improves velocity and clarity
Managing Tech Debt
Help the user manage technical debt strategically using insights from 18 product leaders.
How to Help
When the user asks for help with tech debt:
- Understand the situation - Ask about the nature of the debt (legacy systems, code quality, architectural limitations), how it's manifesting (slow velocity, incidents, inability to ship), and the business context
- Diagnose the urgency - Determine if this is blocking critical business needs or a slower-burning issue
- Choose the right approach - Help them decide between incremental improvement, targeted refactoring, or (rarely) a full rewrite
- Build the business case - Help quantify the cost of the debt and communicate value to stakeholders
Core Principles
Rewrites almost never work
Camille Fournier: "Engineers notoriously, notoriously, notoriously, massively underestimate the migration time for old system to new system. By the way, you still have to support the old system while you're working on the new system." Full rewrites are traps. Prefer incremental evolution - uplift specific components rather than starting from scratch.
Tech debt is product debt
More from refoundai/lenny-skills
personal-productivity
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
4.6Kcompetitive-analysis
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
1.9Kbrand-storytelling
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
1.8Kwriting-prds
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
1.8Kcontent-marketing
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
1.7Kvibe-coding
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
1.7K