The team didn't create the technical debt.
The absence of a system that made it visible and manageable created it.
That's actually good news — systems can be built.
@mannypalachuk.bsky.social
@mannypalachuk.bsky.socialThe team didn't create the technical debt.
The absence of a system that made it visible and manageable created it.
That's actually good news — systems can be built.
@mannypalachuk.bsky.socialTwo tickets, two bounties, every week: oldest ticket + most hours logged. $25-$40 gift card to whoever closes it. Gamify technical debt and watch it disappear. Save this and run it on Monday.
@mannypalachuk.bsky.socialThe Swarming Sprint: whole team, dedicated time block, one rule.
Hunt rogues.
Oldest to newest.
Furthest outliers first.
All bets off on normal routing.
@mannypalachuk.bsky.socialHighest priority first.
Within each priority level — oldest to newest.
Old tickets can't hide in a system that always works oldest to newest.
@mannypalachuk.bsky.social@mannypalachuk.bsky.socialTechnical debt won't clear itself during normal workflow. You need dedicated hunt time. Swarming Sprint or Pinpoint Sprint — which one does your shop need right now? Drop it below.
@mannypalachuk.bsky.socialA team that tolerates 90-day-old tickets will eventually tolerate 120. Then 180.
The tail trains your team what normal looks like.
@mannypalachuk.bsky.socialMost MSP owners had no idea how bad their technical debt was until someone made it visible.
Not because they're bad operators — because nobody built a way to see it.