The morning roll-up: what needs me now
The command center is the surface; the roll-up is the ritual. Once a day it collapses every lane into one short list that answers a single question: what needs me today. If you build only one thing from this skill, build this.
The single question
Not "what is happening" - that is the whole surface. The roll-up asks "what needs me, today". An item qualifies only if both are true:
- It needs you specifically. You are the person who has to move it, not a teammate, not an automated step. Work owned by someone else, even if you care about it, stays off.
- It has a reason to act now. A clock, a dependency, a decision someone is waiting on. Work with no near-term trigger stays in its lane, not on the roll-up.
Everything that is merely in progress, or interesting, or someone else's, is suppressed. Suppression is the feature.
How to assemble it
- Scan each lane for items in a "waiting on you" state. Ignore in-progress and done.
- From those, keep only items that also have a why-now: a deadline, a blocked teammate, a time-sensitive reply, a live decision.
- Rank the survivors by leverage: what only you can move, and what breaks if it slips today, first.
- Cut to a length you can read in under two minutes. If more than a handful survive, your "needs me now" test is too loose - tighten it, do not lengthen the list.
- Present as a flat, ranked list. Each line: the item, the one action, the why-now. No sections, no scores, no preamble.
What to surface vs suppress
| Surface | Suppress |
|---|---|
| A draft awaiting your approval before it can send | A draft still being written by someone else |
| A reply a prospect or reporter is waiting on today | A thread that is progressing fine without you |
| A decision a teammate is blocked on | A decision with no deadline you can make any time |
| An event whose deadline (on-sale, RSVP, submission) is this week | An event on the calendar with no near action |
| A deliverable due today or overdue | A deliverable due next week, on track |
The trap: the roll-up that is just the surface again
The most common failure is a roll-up that lists everything on the board with a fresh header. That is not triage; it is a second copy of the surface, and it trains you to skim. If your roll-up is long, the fix is always to cut, never to reformat. A roll-up of three real items you will act on today beats a roll-up of thirty you will scroll past.
Cadence
Run it once at the start of the day, from the live surface. Running it more often turns it into a notification stream, which is the thing the command center exists to replace. One assembled read, then work from it.