What you are trying to do
Your team keeps making decisions in places where the decision later vanishes. A judgement call in a Slack thread that scrolls off. A "let's just" in a stand-up that nobody captured. A pull request comment that an engineer interpreted one way and the PM another, both convinced they remembered correctly.
The Inbox is where those decisions land instead. It is not a notifications feed. It is the small list of things that need your call today.
What lands here, and what does not
The Inbox holds exactly four kinds of item, and we are deliberate about keeping the list short.
Stuck work lands when a ticket has been sitting in one state too long without movement. A pull request that has been open more than 24 hours with no activity. A ticket that has been blocked for two days. A test suite that has been red for an entire night. These are the items where, without you, nothing will happen.
Improvement signals land when the same pattern of trouble has shown up more than once and is starting to look like a real problem rather than a one-off — for example, three tickets in a row skipped the code-review stage because a specialist had no fallback. The Inbox tells you about the pattern, not each instance.
Reports land on a predictable schedule. Your daily digest at the start of the day. Your weekly audit on Monday morning. A snapshot you asked for. Reports are read-and-acknowledge; they are not asking you to fix anything in the moment.
Learning captures land when an agent finished a run and noticed something worth remembering — a recurring clarification, a stage that keeps producing thin output, a pattern that worked unusually well. These are the lessons your team would otherwise have lost.
What does not land here: progress pings, status updates, "I started the run," "the run finished," routine state transitions, comments on tickets you do not own. Slack and the tracker timeline already do that work, and a notifications feed that pings you on every state change is just background noise wearing a fancier name.
What it looks like on Monday morning
You open the Inbox. You see four or five cards. Each card has a type chip on the left — STUCK WORK, IMPROVEMENT, REPORT, LEARNING CAPTURE — and a short headline. A real example from the live workspace: "Stuck work: PR #213 — no activity 24h+," with a one-line summary underneath. Below it, "Orphan tickets skipped at stage code_review" with a count badge.
You read the headline. You open the one you need to act on. You take the action. You hit Mark addressed or Dismiss at the bottom.
Three or four cards, three or four decisions. Inbox empty. Day starts.
Why this is decision work, not a feed
A feed is something you scroll through hoping not to miss anything. The Inbox is the opposite. Every item is here because it needs you, and every item leaves the moment you have made the call. If you find yourself scrolling, the Inbox is broken — too much noise has been routed in, and the filter needs tightening.
Ship will surface that a ticket is stuck. Ship will not tell you whether to unstick it by talking to a customer, by reducing scope, or by killing the ticket. Those are your calls. The Inbox is the surface where they happen and get logged.
What this changes about your week
Decisions stop vanishing into Slack threads. Every time you address an Inbox item, the call is recorded — what you decided, when, on which ticket. Three weeks later, when somebody asks "wait, who decided to kill that feature," the answer is one click away.
You also stop being the person who keeps a mental list of what needs your attention. The list lives in the Inbox now. If it is not in the Inbox, it does not need you this morning.