Put the Decision First: A Clearer Way to Update UK Managers
A familiar scene: a project update begins with the history of the work, moves through several meetings, pauses on a minor supplier issue and only reaches the actual decision in the final thirty seconds. By then, the manager is checking the clock and the point has lost its force. The update was thorough. It was also difficult to act on.
UK managers are not uniquely impatient, but many work in environments where meetings are short, diaries are fragmented and decisions are expected to travel quickly. In 2026, with hybrid teams moving between London offices, regional hubs and home working, the verbal update has become more important and less forgiving. A clear structure is not a bureaucratic extra. It is a professional courtesy.
Why the First Fifteen Seconds Matter
The opening of an update sets the frame for everything that follows. If the first fifteen seconds contain dates, background and a list of activities, the listener has to work out what matters. If the first fifteen seconds contain the headline, the listener knows where to place the detail.
This is not about being blunt. It is about being usable. A manager listening to an update is usually asking three questions: where are we, what has changed, and what do you need from me? The ninety-second update answers those questions in that order.
The Ninety-Second Architecture
The structure is simple enough to use without notes. It has three parts: headline, context that changes the decision, and ask. The timing is a discipline, not a stopwatch. Some updates will take sixty seconds; some will take two minutes. The point is to keep the architecture visible.
Headline
State the status, the decision or the risk in one sentence. Avoid opening with the journey. Begin with the destination.
Examples:
- 'The Leeds rollout remains on track for 5 December.'
- 'The supplier migration is delayed by two days, and I need a decision on training.'
- 'The client proposal is ready, but I need your approval on the fee before Thursday.'
Context That Changes the Decision
Give only the context that alters the headline. This is the hardest part for narrative thinkers, because much of the backstory feels relevant. The test is simple: if the listener can make the same decision without this detail, it belongs in a follow-up note, not the verbal update.
Useful phrases include: 'The context that matters is...' and 'Two facts change the picture...' These signposts help the listener separate essential information from background.
The Ask
Close with a specific request. Name the action, the owner and the date. If no action is needed, say so clearly: 'No decision needed today; I will update you on Friday.' That sentence is more useful than a vague trailing off.
Before and After: A Status Call
Before:
'So, we have been looking at the supplier situation, and we had a meeting last week, and there were a few issues with the data test. We have been going back and forth with their team, and I think we are mostly there, but there is a question about the training date. I am not sure whether we should move it, so I wanted to talk it through.'
After:
'The supplier migration is on track for 28 November. One risk: the data test has slipped by two days. I need your approval to move the training session to 2 December so we protect the go-live date. Can you confirm by Wednesday?'
The second version is not colder. It is clearer. It gives the manager a headline, a reason to care and a decision to make.
Before and After: A Voice Note
Voice notes are particularly prone to burying the point, because the speaker cannot see the listener's face. A useful habit is to record the headline first, then add only the context that earns its place.
Before:
'Hi, it is me. Just following up on the Manchester event. We had the venue call, and there was a question about the AV setup, and then I spoke to finance about the budget, and there is a small issue with the invoice. I think it will be fine, but I wanted to check with you about whether we should approve the extra cost. Call me when you can.'
After:
'Update on the Manchester event. Headline: the event remains on schedule for 12 December. Context: the venue requires an AV upgrade at £1,200, which is within the contingency budget. Ask: please approve the spend by Thursday so I can confirm the room. No other decisions needed.'
The second version respects the listener's time and reduces the risk of a long call that could have been a short answer.
A Practice Drill for Narrative Thinkers
If your natural style is to build the case before revealing the conclusion, do not try to remove that instinct. Adapt it. Before your next update, write three lines on a sticky note or in your phone: headline, one context point, one ask. Say them aloud once. Then deliver them at the start of the update, before any history.
A second drill is the sixty-second recording. Record a practice update on your phone, listen back and stop at the first thirty seconds. Ask: has the listener heard the headline yet? If not, rewrite the opening sentence and try again. Repeat until the headline arrives naturally.
Finally, use signposting to keep yourself on track: 'The short version is...', 'The context that matters is...', 'What I need from you is...' These phrases are not scripts to recite mechanically. They are guardrails for a clear, confident delivery.
At Perfect English, we coach professionals to treat structure as a confidence tool rather than a constraint. A manager who can hear the decision in the first fifteen seconds is more likely to trust the judgement behind it. Put the decision first, and the rest of the update has somewhere to land.