# Using Stepsize in your planning process
Stepsize brings a new level of visibility to tech debt.
The best way to ensure reported issues get fixed is to make good practices a habit during your sprint cycles. Stepsize is the ideal tool for this.
{% hint style="info" %}
Haven't invited your team to Stepsize yet? Open the [Stepsize web app](https://app.stepsize.com) and head to `Settings` > `Members`. Head over to our guide on inviting collaborators for more information.
{% endhint %}
## **Allocating resource to fixing issues**
Teams that have a strategy for managing tech debt [ship 50% faster](https://stepsize.com/blog/cost-of-technical-debt). When teams use Stepsize to do this, they ship [3 times faster](https://stepsize.com).
To manage tech debt effectively, pay it back quickly and regularly.
Here are two methods your team could use:
1. Allocate 15-20% of resources to refactoring code and fixing bugs in every sprint cycle
2. Allocate entire sprints to deal with tech debt on a regular basis, such as every quarter
## **Planning to fix tech debt**
Use a portion of your team's sprint planning to agree which issues to prioritise.
For example, you could
* Prioritise issues which impact the current work
* Prioritise issues which are lowering morale
## **Identifying issues to fix using the visualisation tool**
At the top of the Stepsize sidebar, navigate to `Visualisation`.
The visualisation shows you a visual representation of your codebase, which acts as a heamap for issues in your codebase.
You can filter your visualisation based on tags your team uses.
## **What next?**
Stepsize has a range of powerful tools which help you surface tech debt during your code review process. Learn more about this in the next guide.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://stepsize.gitbook.io/stepsize-documentation/workflows/using-stepsize-in-your-planning-process.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.