End at 45 Past: The Meeting Reset UK Project Teams Need

I sat in a project review last month that had 11 people, a 60-minute slot and no written decision at the end of it. The meeting was not bad. It was just long. By the time we reached the actual choice — whether to re-sequence the integration work — half the room was watching the clock because the next call was already starting.

That is the quiet tax on UK project teams in 2026. Not dramatic failures. Not big blow-ups. Just the default one-hour meeting, repeated across SMEs and delivery teams, slowly turning decisions into a diary problem.

The hour is a habit, not a law

Most UK calendars still default to 60 minutes. Outlook and Teams will happily suggest the top of the hour. But nothing about project work requires a meeting to run from 10:00 to 11:00. We do it because we always have. Parkinson's Law then does the rest: work expands to fill the time available, and a 60-minute meeting will often find 60 minutes of things to say.

A 45-minute meeting is not a gimmick. It is a constraint that forces a team to separate information from decision. Pre-reads carry the context. The meeting does the choosing. That is the whole point.

The 45-minute template

Here is the format I have been using with project teams. It is deliberately simple.

1. A one-page pre-read, 24 hours ahead. Not a deck. Not a 14-tab spreadsheet. One page: the decision needed, the options, the recommendation, the risks and the deadline. If it cannot fit on one page, the meeting is not ready. This is the part UK teams skip most often, and it is the part that buys back the most time.

2. A named decision owner. Not the chair. Not the most senior person in the room. The person who actually owns the outcome and can say yes, no or not yet. In too many UK project meetings, everyone attends and no one decides. A named owner changes the conversation from a briefing to a decision.

3. A one-page decision log. One line per decision: date, decision, owner, rationale, follow-up date. Keep it in the same place every time — a shared doc, a project wiki, a Teams channel. The log is not bureaucracy. It is the memory of the project. It stops the same debate returning three weeks later with a different slide pack.

4. A clear follow-up rhythm. Decisions need a home. If an action is agreed, it gets an owner and a date before the meeting ends. If a decision is deferred, the log says why and when it will be revisited. The follow-up rhythm can be weekly or fortnightly, but it should be predictable. Predictability is what stops the diary from becoming the project plan.

What to do with the extra 15 minutes

Do not fill it. Use it to write the decision log while the context is fresh, book the follow-up, or walk back to your desk without being late for the next thing. That small gap is where the value lives. It gives people time to process, and it gives the project a chance to breathe.

There is a practical UK angle here too. Many SME teams are juggling client work, supplier calls and internal delivery in the same day. A 45-minute meeting respects the school pick-up, the train to Leeds, the Friday afternoon handover. It is not soft. It is realistic.

Measure the drag, not the vibe

Shorter meetings feel better, but feeling better is not evidence. If you want to know whether the format is working, track a few simple measures:

• Decision cycle time: how long it takes from a decision being raised to being logged and owned.
• Action closure rate: the percentage of actions closed by the next meeting.
• Pre-read rate: the percentage of meetings with a one-page pre-read issued 24 hours ahead.
• Attendee hours: total meeting hours multiplied by attendees. This is the number that makes finance directors pay attention.
• Repeat debate rate: how often the same issue comes back without new information.

You do not need a dashboard. A simple spreadsheet is enough. The point is to test whether shorter meetings are improving momentum or just moving the same chatter into a smaller slot.

The catch

A 45-minute meeting will not fix a project with unclear ownership, weak scope control or a client who cannot make decisions. It will expose those problems faster, which is useful but uncomfortable. If the pre-read is empty and the decision owner is missing, the meeting should be cancelled, not shortened.

The default hour is not evil. It is just lazy. For UK project teams in 2026, the 45-minute rule is a small operational choice with a disproportionate effect on decision speed. End at 45 past. Keep the plot.