The first ten minutes: reading the Mission Control grid

What the grid is

Mission Control opens on a grid, not a list. Every category the workspace watches gets a card when it needs something from you, carrying one figure and one quiet line of explanation. Everything that is clear becomes a small green chip underneath instead. Nothing disappears on a quiet day; it just gets smaller.

Click a card or a chip and a dialog opens with the rows behind the figure, every row linking into the filtered page where the work happens. The grid is a routing table, not a report.

It is also strictly read-only, which is a decision rather than a gap. Nothing on this screen changes anything, so you can open every card at speed without wondering what you just agreed to. That is what makes a ten-minute pass possible: you are not deciding here, you are deciding which screens deserve your morning.

The order it puts things in

The grid sorts itself, and the sort is the opinion. Cards come first and worst first: red, then amber, then the neutral ones that are movement rather than a problem. The all-clear chips hold a fixed order underneath, so a quiet day reads the same way every day.

Above the cards sits one line with today’s date and a count of the categories needing attention. That count leaves the neutral cards out on purpose. Today’s arrivals are not a problem to be solved, and a dashboard claiming five things need you when two of them are check-ins is one you stop believing by the third week.

Red and amber are not severity guesses either. Each category has one rule: past its due date, past the channel’s usual payment timing, above what this property normally pays for that kind of cost. Green means nothing has crossed that line. It does not mean there is nothing to do.

The cards you act on first

The grid carries a card for every category the workspace tracks. These are the ones that ask something of you most mornings.

Payouts

Bookings whose money has not arrived by the point that channel usually pays, worst first, amber up to thirty days late and red beyond it. The figure is what is outstanding across all of them. This is usually the most valuable card on the screen, because a late payout gets harder the longer it sits.

Work the oldest one first, not the largest one.

Tasks

Anything pending or in progress that is past its due date, oldest first. Two minutes here is usually enough: either do the small ones now or move the date honestly. A task list where half the rows are three weeks stale stops being read at all, and from then on the grid misleads you every morning.

Support

Open and in-progress tickets, which means somebody is waiting on you. Answer them inside the pass: the cost of leaving this one falls on somebody else.

Today

Check-ins and check-outs today, in one card with a neutral tone. Its job is orientation rather than alarm: two departures and an arrival is a turnover day, which is a different shape of afternoon from a quiet one. What a turnover really costs.

System

The scheduled jobs that keep the workspace fed: the channel sync, the nightly housekeeping, the daily email. Each has an expected cadence, and the card turns amber when one runs late and red when one misses its window by a wide margin. A job that has never run reads as neutral rather than broken, because a job that has not reached its first scheduled run is not evidence of anything.

You will ignore this card for months. The month it turns red, it stops you trusting a stale number.

A worked example: one morning

A Tuesday with three categories needing attention. The point of the last column is that a triage pass has a budget.

Four of those ten minutes went to one thing: a payout forty-one days late, which is a message to a channel rather than a click. The other six cleared three categories. That is the shape to plan for, and the argument for reading worst first: find the worst item last and you find it with two minutes left.

What it deliberately leaves out

The omissions are what make it readable in the time you actually have.

• Anything you can change from here. The grid never edits, approves, pays or dismisses. There is no snooze and no mark-as-read, so an item leaves a card only because the thing behind it changed.
• Revenue. Performance sits further down the same page, with occupancy and recent activity. What you earned is reporting, and reporting is not a morning decision.
• The long tail of rows. A dialog shows the worst fifteen and hands you the page link for the rest, so the screen never becomes the thing you scroll instead of the page that can filter properly.
• A second version of the truth. Every card reads the same data, under the same rules, as the page it links to.
• Yesterday. The grid describes the state of things now, not a feed of what happened.

One habit to take from this: a card is not a to-do list. It is a smoke alarm with a number on it, and the work is always on the page behind the row.

The email that tells you something by arriving

The same discipline runs once a day by email, sent at 07:00 UTC, which is 08:00 through British Summer Time and 07:00 in winter. The subject line is Daily Summary with the date, and it opens with a good morning and your first name.

It is built per person and carries up to five things: anything from the last day you have not read, bills already overdue, bills falling due this week, anything waiting on your approval, and documents expiring inside the next fortnight. Payouts due are folded in alongside them.

The most useful thing about it is what it refuses to do. If you have nothing in any of those five sections, you get nothing at all. No email, no all-clear, no daily noise to train yourself to ignore. Which means the email arriving is itself information, before you have opened it.

Two honest limits. There is no on and off switch for the daily summary today, and no frequency to tune: the per-type notification emails are a separate setting. And if email is not configured for the workspace the send is skipped and logged rather than retried, so check a silent week against the System card once.

A routine that holds in a bad week

A fixed order is what stops you starting with whichever card is most annoying. This one takes about ten minutes and survives a bad week.

1. 1Read the count first. It tells you whether this is a five-minute morning or a thirty-minute one before you open anything.
2. 2Take the red cards in the order given, which is already worst first.
3. 3Act from the rows rather than the headline figure, and follow the link rather than navigating by hand.
4. 4Do the amber cards only once every red one is cleared or has a date on it.
5. 5Glance at the neutral cards for shape, not for action.
6. 6Leave the green chips alone. A chip is not a chore you skipped.

Do it before you open your inbox. The inbox is other people’s priorities sorted by when they wrote; the grid is your properties sorted by what has crossed a line. Every module in the Host edition.

The ten-minute pass