The main reason to use Stepsize is to make better strategic decisions by prioritising the right debt at the right time.

In this guide, we describe how to use Stepsize to improve product quality using hard evidence rather than anecdotes and opinions.

<aside> ⚠️ Have you covered the basics?

This guide assumes that you're familiar the fundamental building blocks of Stepsize: debt reports and debt items.

If you aren't, we encourage you to check out our overview of debt reports and our overview of debt items before coming back to this guide.


Identify what you want to improve

Do you want to make your product less buggy? Improve the performance of an API or service? Improve the reliability of your platform? And which parts of the codebase need improving?

Start by answering these questions — they dermine which data tracked in Stepsize you should focus on.

Look at the debt items responsible for the issues you want to address

Let's say your primary objective is to reduce the number of severe bugs in your 3rd party integrations.

  1. Find the group(s) covering 3rd party integrations

  2. Filter the list of debt items to show those responsible for the most Defect of Medium or High severity

  3. You're done — this is your prioritised list of debt to fix 🎉

Did we miss something? Do you have any questions? Reach us at