X: The riskiest ticket in your sprint is not blocked. It is unowned.
Standups show what people are doing. Boards show what is assigned. Neither shows the limbo queue: issues everyone sees, but nobody owns the next decision on.
That is why teams still jump on a “quick call” to reconstruct context.
Control starts when every acknowledged issue has a decision owner, not only a future implementer.
Yesterday in my diary I wrote “control before reporting.” This is the same rule in practice.
More field notes at @egewrk.
LinkedIn: Fresh pattern from this week:
On X, I saw engineers debating explicit ownership in async teams and why “just ask someone” fails when context is split across time zones.
On Reddit, I saw a thread asking what to do with problems that have no owner. The strongest line was: “The gap was not information. It was that nobody had made an explicit decision about who was responsible for the next step.”
On HN, I saw the same shape in another form: teams can trace code and tickets, but still lose the why behind decisions.
My takeaway:
Most teams have a system for active work. Very few teams have a system for work in limbo.
That limbo queue is where bugs age, ownership drifts, and surprise calls happen.
A simple fix I am testing: for any issue that is acknowledged, log one “decision owner” before anything else. Not necessarily the fixer. The person who owns deciding what happens next.
This connects directly to yesterday’s diary theme for me: control before reporting.
Reddit: Subreddit: r/ExperiencedDevs Title: How do you handle issues that are acknowledged but still have no decision owner? Body: I noticed a pattern across several threads this week and wanted to sanity check it with people running real teams.
We are pretty good at tracking active work:
- who is coding what
- what is blocked
- what is in review
But we are weaker at tracking limbo work:
- issues everyone sees
- nobody explicitly owns the next decision
- they stay open until pain gets loud enough
This feels different from normal backlog prioritization. It is more like “decision ownership debt.”
Has anyone put a lightweight process around this?
Example:
- once an issue is acknowledged, assign a decision owner within 24h
- not necessarily the person who will implement
- just the person responsible for deciding next step and pulling needed context
Curious what worked for you and what became overhead.