The Ten-Minute Yes: Getting a Decision Before the Office Goes Quiet

There is a particular week in December when the office is technically open but spiritually halfway to the Christmas do. People are at their desks. They are answering emails. They are even asking thoughtful questions about your project. But ask them to approve something and you can almost hear the internal committee reply: can this wait until January?

For younger professionals, this window is easy to misread. It looks like business as usual, so you keep pushing. Or it looks like a waste of time, so you quietly down tools. Both are a mistake. The wind-down is not a dead zone. It is a live test of judgement, and how you handle it tells senior people more about you than any polished January presentation will.

Timing is a leadership skill nobody teaches you

Most of us learn to write a good proposal, build a decent case and present it clearly. Far fewer of us are taught to ask: who needs to say yes, and when can they realistically say it?

That is timing, and it is a leadership skill. It is the difference between a request that lands and one that sits in a inbox until the mince pies are gone. In December, timing gets compressed and exposed. Finance teams are closing the year. Procurement is trying to get contracts signed before supplier teams vanish. HR is juggling payroll deadlines, January starters and the annual leave spreadsheet that has become a competitive sport.

If you treat all of that as one big fog, you will get vague answers and blame the season. If you map it, you can still get decisions.

Find the real cut-offs, not the rumoured ones

The first move is simple: ask the teams who actually control the dates. Not the person who heard something in a meeting. The person who owns the process.

For finance, find out the last date for invoice approvals, purchase orders and budget commitments before the year-end close. Ask whether there is a final payment run and what has to be in place for it. For procurement, ask about contract signatures, supplier onboarding and any service-level agreements that need renewing in January. For HR, check headcount approvals, offer deadlines, payroll cut-offs and what happens to anything agreed after the office goes quiet.

Do this in early December, not on the 20th. A short email to your finance business partner or HR contact is fine: I am trying to land a decision before the break. What is the realistic cut-off for approvals in your area this year? That question makes you look organised, not needy.

Once you have the dates, work backwards. If finance needs approvals by the 12th, your ask needs to be with the decision-maker by the 9th. If procurement needs a signed contract by the 15th, the conversation starts now.

Compress the ask until it can be approved in ten minutes

Senior people do not avoid decisions in December because they are lazy. They avoid them because the ask is often too big, too vague or too expensive in attention. A five-page paper in the second week of December is not a decision request. It is homework.

So compress it. Put the whole thing on one screen: what you are asking for, why it matters, what it costs, what happens if it waits, and which option you recommend. Give them the exact approval you need. Not thoughts? but can you approve option B and the £4,000 spend by Friday?

If a meeting is needed, ask for ten minutes and mean it. Send a pre-read the day before. Turn up with the decision already framed. If you can get the answer by email, do that instead. The goal is not to make your work look impressive. The goal is to make saying yes easy.

This is where a lot of young professionals accidentally overcomplicate things. We think a bigger case is a stronger case. In December, a smaller, sharper case wins. One clear recommendation, one clear number, one clear date.

The wind-down is a reputation window

There is a version of December where you disappear into a fog of out-of-office messages and unfinished threads. There is another where you become the person who quietly keeps things moving without making noise.

That second version looks like this: you tell people what you need before they ask, you do not chase the same decision five times in three days, and you leave a clear note about where things stand before you log off. You are not a hero. You are just reliable, and reliability is memorable.

It also means respecting the difference between urgency and convenience. A genuine deadline is worth a phone call. A preference is not. If your request can wait until 2027 without real damage, say so. That honesty buys you credibility for the requests that cannot wait.

When the answer genuinely has to wait until 2027

Sometimes the cut-off has passed or the decision-maker is already on leave. Do not force it. Do not send a passive-aggressive just bumping this on the 23rd. Instead, write a short note that keeps the request alive without nagging.

Keep it to four lines: the decision needed, the date you will pick it up, who owns the next step, and what you will do in the meantime. For example: Happy Christmas. Just to confirm where we landed: the supplier decision will wait until 8 January. I will have the updated cost comparison with you on 5 January and will not progress anything until then. Nothing else needed from you before the break.

That note does three things. It shows you understand the calendar. It protects the request from being forgotten. And it gives the senior person permission to switch off without feeling guilty.

Leave the year tidy, not loud

You do not need a grand final push before Christmas. You need a clear map of the cut-offs, a request small enough to approve, and the discipline to park what can wait. That is not passive. It is leadership with a calendar.

And when January arrives, the person who handled the wind-down well will not need to remind anyone. The decision will be waiting, the note will be clear, and the reputation will already be doing the work.