Technical debt — we all struggle with it.
Missed deadlines. Frustrated product managers. Even more frustrated engineers. Firefighting left and right instead of focusing on the roadmap.
This will sound familiar to anyone who’s worked in a software engineering team before.
How do we balance business priorities with development sustainability ?
This is the key question every engineering organisation needs to answer. Your pace of execution, product quality, and ability to attract and retain talent depend on it.
Table of Contents
The handbook is split up into 3 sections. Feel free to dip in & out of chapters as you please.
Understanding technical debt
Managing technical debt
Managing technical debt with Stepsize
Coming soon…
About this handbook
Stepsize helps teams document and fix issues in their codebase.
We've interviewed and coached hundreds of developers, product managers, and engineering leaders over the past few years.
This was initially in service of our product. But we've decided to summarise everything we know in this Technical Debt Handbook.
We’ll publish it in chapters over the next few weeks and months. Our goal is to create the definitive manual on tech debt — where it comes from, how to track it, and what to do about it.
By the end of it, you’ll have everything you need to change how your company operates.
If you have any questions or would like to see some specific topics covered, don’t hesitate to reach out. You can talk to us on Twitter @StepsizeHQ.
Created by
Nick Omeyer
Co-founder & CPO
With expert contributions from
Alex Omeyer
Co-founder & CEO
Martin Krivobarski
Product Designer