The Train Fare Is Already Spent: Making Anchor Days Worth the Journey

There's a certain kind of Tuesday that has become very familiar in UK offices this year. Half the team has made the effort to come in. The other half is dialling in from a kitchen table in Leeds. Everyone then spends the morning in back-to-back calls with people who aren't in the building, queues for a meeting room at eleven, and by four o'clock the booked desk is doubling as a coat rack while they finish the day on headphones.

That is an expensive day. It cost somebody a return fare, two hours of their life and a decent chunk of goodwill. And almost nothing happened in it that couldn't have happened at home.

With attendance expectations getting firmer through 2026, the useful question isn't how to get people in. It's what actually happens once they arrive.

The cheapest training hour you will ever buy

Look at the maths honestly. If someone is already travelling in, already caffeinated, already sitting three metres from a colleague who knows how to do the thing they're stuck on, then the marginal cost of forty-five minutes of learning is close to zero. No venue. No travel. No evening slot that eats into the school run.

Compare that with the alternative most teams default to: a webinar at 6pm, attended by twelve people with their cameras off, half of whom are making dinner.

Anchor days are the one moment in the week when the room is already full. Wasting that on status updates is the actual scandal — not the commute.

What the format needs to work

Three conditions, and honestly they're not complicated.

A predictable slot. Same time, every anchor day, so nobody has to guess or re-plan their week around it.

A short format. Nothing that needs a facilitator with a flip chart and a two-day booking.

A reason to be in the room. The session should be better in person than on a screen, or it should be a recording.

The shape of the day

Skill clinics — 25 minutes, run twice

One person who genuinely knows a thing shows four or five others how to do that thing, in the actual tools, on the actual screens.

Not a course. A clinic. The difference is that everybody leaves having done it once themselves, badly, with someone leaning over their shoulder saying 'no, the other tab'.

The subjects are almost embarrassingly ordinary. Writing a brief that doesn't come back three times. Getting a pivot table to behave. Raising a credit note without a phone call to finance. Using the CRM the way it was designed to be used rather than the way it's been used since 2019. Taking minutes that someone might read.

Run it at half ten and again at two. That single decision solves most of the flexibility problem — parents doing the school run, part-timers, anyone whose morning has already collapsed. Nobody has to choose between the clinic and their actual job.

Peer demos — 10 minutes, one per anchor day

One person, one thing they've worked out, fixed, or learned since the last anchor day. Screen shared or whiteboard, no slide deck, no preamble.

This is where the culture does more work than the content. People volunteer for demos when they've watched three colleagues do it and nobody got judged for a scrappy explanation. It also quietly surfaces the quiet experts who never put their hand up for anything else.

The close — 20 minutes, at the end

Not a debrief. A short, structured finish: what did we cover, what goes on the shared page, who's demonstrating next time, and what still needs sorting out.

Twenty minutes, diary it, write it down. A close that produces three named actions is worth more than an hour of reflection.

Keeping the hybrid bit honest

None of this works if it becomes compulsory attendance dressed up as development. So:

• Record the demo and share it the same afternoon.
• Keep a one-page written summary of each clinic so the people who weren't in aren't disadvantaged.
• Never, ever push it into the evening to 'protect the working day'.
• Leave most of the day alone. People came in to do their jobs, see their teammates and have a proper conversation by the kettle. Fill the whole day with structured activity and you'll get compliance for two months, then quiet resistance.

The trap to avoid

Anchor-day learning dies the moment it's treated as a meeting. Once it's a recurring calendar invite with a Teams link, a pre-read and an agenda item called 'AOB', it's over.

Guard the slot the way you'd guard a client call. No laptops in the clinic. No status updates relabelled as training. If somebody can't make it, that's fine — that's what the recording is for.

Start embarrassingly small

Month one: one clinic, one demo, one close. Ninety minutes of the day, tops.

If it lands, add a second clinic the following month. If it doesn't, you've lost ninety minutes and learned something useful about what your team actually needs.

Anchor days will not be rescued by pizza, a table football table or a guest speaker. They'll be rescued by being worth the fare. Give people one thing each time they come in that they could not have picked up at home, and the journey starts to make sense again.

And the person who ran the clinic? They'll have learned more than anyone in the room. That's usually how it goes.