Skip to content

// Technical Debt

Debt you can see.

Stop letting tech debt hide in Slack threads and TODO comments. Catalog every shortcut, outdated dependency, and architectural issue in one board your team actually checks.

// Board Preview
04 columns

Identified

3

Migrate legacy jQuery widgets to React components

High Impact

Remove deprecated Stripe v2 API calls

Tech Debt

Replace hand-rolled CSV parser with papaparse

Low Effort

Prioritized

2

Upgrade Node.js from v18 to v22 LTS

High Impact

Consolidate three overlapping logger libraries

Low EffortTech Debt

In Progress

2

Refactor monolithic user service into bounded contexts

High Impact

Add TypeScript strict mode to shared packages

Tech Debt

Done

2

Replace moment.js with date-fns across 47 files

Low Effort

Extract inline SQL queries into parameterized repository layer

High ImpactTech Debt
// How to use this template
04 steps
01

Capture debt as you find it

When you spot tech debt during feature work, create a card immediately in the Identified column. Include why it matters, what it blocks, and a rough effort estimate in the description.

02

Prioritize by impact and effort

Use High Impact and Low Effort labels to surface quick wins. Move the highest-value items to Prioritized so your team tackles debt that actually speeds up future development.

03

Dedicate capacity each sprint

Reserve 10-20 percent of each sprint for tech debt cards. Pull from Prioritized into In Progress alongside feature work so debt reduction is continuous, not a one-off event.

04

Celebrate completed paydowns

Move finished items to Done and review them in retros. Tracking completed debt paydowns builds team morale and gives leadership visibility into engineering health.

// FAQ
03 questions
01

What is a technical debt tracker?

+

A technical debt tracker is a board that catalogs shortcuts, outdated dependencies, and architectural issues in your codebase. Each card represents a specific piece of debt with context on its impact, making it easy to prioritize and chip away at it over time.

02

Can I customize the labels for my team?

+

Yes. Flux labels are fully editable. Rename them to match your classification system - Refactor, Dependency, Architecture, Security - or add effort estimates like Small, Medium, Large alongside impact labels.

03

How does Flux help manage technical debt?

+

Flux gives you real-time board updates so the whole team sees debt priorities change as they happen. Use the multi-board view to track debt alongside your sprint board, checklists to break down large refactors, and the AI assistant to draft debt descriptions from code context.

// Pay it down

Track debt, ship faster.

No credit card. Manage technical debt with labels, priorities, and real-time team visibility.