Debt is trackable only when pinned to a screen and an owner
Aliases: screen-and-owner debt · locatable IOU · assignable design debt
What it is
“We have a lot of design debt” cannot be scheduled. Trackable debt is pinned to a specific screen and an owner at the same time: which view, what is missing, who is allowed to act on it in the next change. Without a screen, nobody knows where to look. Without a person, the item greys out in the list.
Location is how debt enters a plan. It is not how expensive the later edits will be, and not whether the original borrow was legitimate. An item scoped as “overall consistency” or “it feels messy” looks like debt and behaves like an unschedulable complaint.
Why it happens
Backlogs, boards, and sprints only dispatch work units that have a place and an assignee. Place turns atmosphere into something that can be opened: the empty state on checkout, the permissions copy in settings, search-with-no-hits. Owner turns “everyone kind of knows” into a name a standup can call — that person need not do the work, but must be the single point who can accept, refuse, or hand it on.
Drop either end and the tracking chain breaks. Screen without owner: the ticket ages in a shared pool while each person assumes someone else will pick it up. Owner without screen: the person is handed a bag of unnamed “UX issues” that cannot be estimated, verified, or closed. A shared screen that anyone may edit and no one is named for has many hands in conversation and none in the tracker.
Where it stops holding
Not every IOU shrinks to one screen: a component, a pattern, a cross-page navigation structure can be the place, but it still has to be a bounded object, not “the whole product.” Platform-level or multi-brand pieces often belong to the system maintainers, not a feature squad; the wrong owner makes the ticket idle inside a business sprint. Two-person teams can keep an oral map for a while; hiring, leaving, or shift changes wipe it, so a spoken list is not a written screen-and-person. Retired screens should leave the tracker or move to an archive so dead IOUs do not clog the board.
Applying it
- Rewrite vague debt as four fields: the screen or other bounded object, what is missing, the owner, and the next action (pay, roll, or transfer).
- Shared screens get one accountable owner; collaborators live in the notes, not in the owner field.
- Items that cannot name both a place and an owner go back; they do not enter a sprint.
- How to check: hand the current debt list to someone who was not in the discussion. Ask them to open the screen and say who to ask. Every wrong screen or wrong person is still untrackable.