If you inherit a product with massive tech debt, then your first 30...

If you inherit a product with massive tech debt, then your first 30 days will define if your engineers stay or quit.

I've watched 5 engineering teams implode because their PMs made the same mistakes.

For 4 years, I had to fix a few such disasters.

Here's what actually works:

1/ First, breathe. If you're feeling overwhelmed, that's normal.

Technical debt isn't just a technical problem.
It's a trust problem.
It's a morale problem.
It's a business problem.

But there's a way through this.

2/ Most new PMs make this critical mistake:

They try to understand *all* the technical debt first.

Don't.

Instead, map the impact first:
- Which issues block new features?
- Which ones cause production incidents?
- Which ones slow down development?

3/ Your engineers are probably right about the problems.

But they're likely wrong about the solution.

They'll want to fix everything.
You need to make it strategic.

Here's how to turn angry engineers into strategic partners:

4/ Create a "Tech Debt Impact Matrix"

X axis: Business Impact (Low to High)
Y axis: Engineer Frustration (Low to High)

Plot every issue they raise.

This does two things:
- Shows you're listening
- Creates shared understanding of priorities

5/ Here's the hard truth about tech debt:

If you try to fix it all, you'll fail.
If you ignore it all, you'll fail.

The secret is to pick the right battles.

Focus on debt that:
1. Blocks revenue features
2. Causes customer pain
3. Makes good engineers quit

6/ For product leaders reading this:

Your PM needs your support here.

They're not being slow or indecisive.
They're preventing a costly crisis.

Every week of tech debt investment now saves months of emergency fixes later.

7/ Specific tactics that work:

Morning standup: "What technical issue slowed you down yesterday?"

Weekly retro: "Rate your frustration with our codebase (1-5)"

Monthly planning: "Which tech debt directly affected customers?"

Track these metrics religiously.

8/ When engineers say "We need to rewrite everything":

Ask: "What's the smallest change that would make your job 50% easier?"

Often, it's not a full rewrite.
It might be:
- Better testing tools
- Automated deployments
- Code cleanup in one critical area

9/ Your secret weapon: The 20/20/60 rule

20% of time: Must-have features
20% of time: Tech debt reduction
60% of time: Regular development

This balance keeps everyone sane.

Don't break this rule for 3 months. Watch team morale improve.

10/ Real talk: You need a system for this.

I keep my tech debt tracking templates in prodmgmt.world (it's helped hundreds of PMs in similar situations).

And if you want AI prompts to help write tech debt assessment docs, reply "prompts" below.

11/ Remember: You're not just managing code.
You're managing people.

Engineers don't quit because of tech debt.
They quit because they feel unheard.

Make them part of the solution, and they'll help you fix it.

12/ To summarize:

1. Map impact, not details
2. Create shared visibility
3. Pick strategic battles
4. Maintain the 20/20/60 rule
5. Track frustration metrics
6. Make engineers partners

Found this useful? Follow me for more PM crisis survival guides 🎯