The Green Dot Is Not a Progress Report

On a wet Tuesday in November, the 07:42 to London Paddington is cancelled. The line is flooded somewhere past Didcot. A school closure email lands at 7:15. By 8:05, the team chat has the familiar texture of a group of people pretending everything is fine: a few green dots, a couple of 'morning all' messages, and no real idea whether the thing that was supposed to be finished today is actually moving.

This is the quiet failure mode of hybrid work in the UK. We have confused presence with progress. The green dot says someone has opened an app. It does not say whether the proposal has been reviewed, whether the client question has an owner, or whether the handover that was meant to happen at 9am is now sitting in someone's drafts folder. On the days the commute falls apart, that gap becomes expensive.

The commute is a red herring

It is tempting to treat disrupted travel as the problem to solve. Buy more video call licences. Add another channel. Ask everyone to post a morning greeting so the team knows who is 'in'. But the cancelled train is only exposing something that was already there: our status updates are usually about the worker, not the work.

A note that says 'working from home today' tells me where your laptop is. It does not tell me whether the pricing page is ready for review. A note that says 'on the 08:15, signal failure at Slough' is useful for sympathy and useless for planning. What the team actually needs is a small, boring, public statement of where things stand.

In 2026, most UK teams have more communication tools than they can reasonably keep track of. The answer is not another dashboard. It is a shared habit: when the day goes sideways, write down the work.

Describe the work, not the worker

A good status update answers three questions in plain language. What is moving? What is blocked? What can someone else pick up?

That is it. It does not need a mood emoji or a location tag. It does not need to explain that the dog is barking or that the broadband is patchy, unless those things change what happens next. It needs to be legible to a colleague who is not in your head and has not read the last forty messages.

For example:

• Moving: The onboarding email sequence is drafted and ready for a second pair of eyes.
• Blocked: Waiting on legal to confirm the data retention wording before we can publish.
• Pick up: If anyone has twenty minutes, the support macro rewrite needs a sanity check.

That note takes less than a minute to write. It gives a manager something to act on, a new starter something to understand, and a teammate something to do that is not asking 'any updates?' for the third time.

The 'are you around?' tax

There is a particular British politeness to the phrase 'are you around?'. It is soft, non-committal, and often used to avoid seeming demanding. The trouble is that it asks the other person to do a small piece of emotional and logistical admin before anyone knows what the conversation is about.

On a normal day, that is a mild annoyance. On a disrupted day, it becomes a tax on the whole team. Ten people ask ten variations of 'are you around?' and suddenly the chat is full of unanswered doorbells. The person who is on a delayed train now has to scroll through a pile of vague pings to find the one that actually matters.

A simple rule helps: ask the question you actually need to ask, and include enough context for someone to answer it without a preliminary conversation. 'Are you around to look at the final paragraph of the client note before 11?' is better than 'are you around?'. 'Can you pick up the invoice check if you're online before lunch?' is better than 'hello, quick one.'

The second version is not rude. It is just more useful. And on the days when the 07:42 does not run, useful beats polite-but-fuzzy every time.

A handover-friendly block

Some teams already have a daily stand-up. Others have a morning thread. Either can work, but only if the update is written for someone who might need to take over. That means avoiding the shorthand that only makes sense to the person who wrote it.

A handover-friendly block might look like this:

Where things stand — Tuesday

• Moving: Draft of the partner brief is done. I am tightening the examples this morning.
• Blocked: Need a decision on the budget split before I can send it to the client.
• Pick up: The competitor notes are still half-finished. If someone has thirty minutes, the first two sections are ready to review.
• Not today: The newsletter copy is slipping to Wednesday. No action needed.

This is not a performance review. It is a map. It tells the team where the edges are. It also gives the person writing it permission to be honest about what is not happening, which is often the most valuable part.

Make it boring, make it routine

The mistake teams make is treating status updates as an occasional emergency measure. They write a long note when something goes wrong, then go back to the green-dot habit. The better approach is to make the update so normal that nobody feels exposed by writing one.

Keep it short. Keep it in one place. Use the tool the team already opens — a pinned note in Kula, a daily thread, a shared doc, whatever fits the way people actually work. The format should be stable enough that someone can scan it in thirty seconds and know whether they need to act.

And do not require a reply. The point is not to create another conversation. The point is to leave a trail that survives the morning.

Legible beats online

A team is not a row of green dots. It is a group of people trying to move work forward, sometimes from a kitchen table, sometimes from a train that is going nowhere, sometimes from an office with the heating stuck on. The collaboration stack can help, but only if the status updates inside it describe the work rather than the worker.

So the next time the line floods, the school closes, or the 07:42 simply vanishes, try a different kind of morning message. Not 'I'm online'. Not 'running late'. Something like: here is what is moving, here is what is blocked, here is what you can pick up. It is a small habit. It is also the difference between a team that is merely connected and a team that is actually legible.