Tech Debt Workshop

Purpose

Technical debt slows teams invisibly. This workshop makes it visible by systematically cataloging debt, assessing its cost of delay, and integrating payback into the team's regular planning.

At a glance

How to run

1. Define what counts (5 min) — Agree on the team's definition of tech debt: outdated libraries, missing tests, architectural shortcuts, documentation gaps, etc.
2. Brainstorm (15 min) — Each person silently writes tech debt items on sticky notes. One item per note.
3. Cluster and categorize (10 min) — Group similar items. Label categories: code quality, infrastructure, testing, dependencies, documentation.
4. Assess impact (15 min) — For each cluster, rate: How much does this slow us down? How risky is it? Use a simple High/Medium/Low scale.
5. Prioritize (10 min) — Dot-vote or use a cost-of-delay matrix. Identify the top 3–5 items to address.
6. Plan payback (5 min) — Allocate a percentage of each Sprint to tech debt (e.g., 20%). Create Backlog items for the top priorities.

Materials needed

• Sticky notes and markers
• Categorization labels
• Cost-of-delay or impact/effort matrix
• Backlog for capturing tech debt items

Pitfalls & common mistakes

• Tech debt is invisible to the PO — Translate debt into business impact: "This slows every feature by 2 days."
• All-or-nothing approach — Don't try to fix everything at once. Incrementally pay down the highest-impact items.
• Only developers participate — Include the Product Owner so they understand the trade-offs.
• No dedicated capacity — Without reserved Sprint capacity, tech debt always loses to features.

Inclusion & accessibility

• Use silent brainstorming so all voices are captured.
• Explain technical concepts for non-technical participants.
• Document outcomes in a shared, accessible format.

Variations

• Tech debt wall — Maintain a permanent visual wall of tech debt, updated continuously.
• Architecture decision records — For architectural debt, create ADRs to document the context and decision.
• Debt sprint — Dedicate an entire Sprint to paying down accumulated debt (use sparingly).

When NOT to use this

• If the team has no tech debt (unlikely but possible for new projects).
• If the team has no authority to allocate time to tech debt — escalate to management first.

Source & further reading

• Cunningham, W. (1992). "The WyCash Portfolio Management System." OOPSLA.
• Fowler, M. (2009). "Technical Debt Quadrant." martinfowler.com