Tech debt prioritization template
Sort tech debt by impact and effort so the team fixes quick wins first and plans the big ones.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Quick wins — high impact, low effort: do next sprint
- Flaky checkout test · Slow CI cache · Missing DB index on orders.user_id
- Big bets — high impact, high effort: plan it
- Split the monolith's billing module · Upgrade to the new framework major
- Fill-ins — low impact, low effort
- Remove dead feature flags · Lint warnings
- Money pit — low impact, high effort: don't
- Rewrite the admin UI from scratch
Also on the board
- ↑ Impact
- Effort →
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Paste a table. Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
- Paste code as code. Paste a snippet and it becomes a code block with syntax colouring; Tab indents inside it.
- Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
Good for
- tech debt
- prioritization
- refactoring
- engineer
- planning
- Designing a schema or an API before writing it
- Explaining a tricky flow in a code review or design doc
- Agreeing on team conventions such as branching and reviews
Related templates
ER diagram (database schema)
Entities as tables with columns, types and keys, joined by one-to-many relationships — sketch a schema before the migration.
UML class diagram
Classes with fields and methods, associations with multiplicity, and an interface with two implementations.
State machine
Every state an order can be in and the events that move it — the source of truth for status logic and tests.
Sequence diagram (request flow)
Numbered steps across Client, API gateway, service, database and a third party — how one checkout request really travels.
Solution architecture canvas
Frame a solution on one page: goals, stakeholders, scope, qualities, constraints, integrations, decisions, risks and roadmap.
Now / Next / Later roadmap
An outcome-based product roadmap without fake dates: what we're doing now, next, later, and what we're not doing.