Technology Strategy & Roadmaps

The Last Business Day: What Not to Start

The last business day of the year tempts owners into starting things: migrations, cleanups, quick wins. Almost all of it belongs to January.

A white desk top with a keyboard, notepads, a coffee cup, a pen and a plant.

The last business day of the year has a peculiar energy. The office is half empty, the phone is quiet, and the owner who has been too busy all year suddenly has an open afternoon and a list. The temptation is strong: migrate the email, clean up the shared drive, start the thing there has never been time for.

Do not. The last business day is for closing, not opening, and almost everything that feels like a quick win this week is a January problem wearing a December costume.

TLDR

  • The last business day is for closing, not opening.

  • A free afternoon with nobody around is the riskiest time to change anything.

  • Legitimate last-day work cannot break anything: checks, notes, planning.

  • The drive cleanup waits for January's fresh eyes and full staffing.

Why starting feels so good today

The appeal is real. No interruptions, no meetings, a rare stretch of unclaimed hours. The problem is that the conditions that make it feel productive make it dangerous: nobody else is around, nobody is watching, and the people who would help or catch a mistake are out until January.

Every quiet-week incident story begins with someone having a rare free afternoon. The migration that "should only take an hour" takes four, breaks something subtle, and the person who would know how to fix it is on a ski trip.

The short list of legitimate last-day work

Some things genuinely belong to the last business day: confirming the backups ran, checking the January calendar for what needs preparation, writing the two or three notes future-you will need. Reading. Thinking. The year's last day is good for anything that cannot break anything.

It is a bad day for anything with an undo problem. If a task cannot be safely paused at any moment and left alone for a week, today is not its day.

The cleanup that waits

The shared drive cleanup is the classic trap. It feels like tidying, but it is actually hundreds of small irreversible decisions made fast, alone, with no one to ask. Half of what gets deleted in a year-end purge gets wanted in February.

January does this better: full staffing, fresh eyes, and the people who know what things are. Schedule the cleanup for the second week of January and spend today writing down what bothered you about the drive, so the session starts from a list.

End the year the way you want to start the next one

There is a softer reason to resist the last-day sprint. The business takes its cues from the owner. An owner who ends the year in a frantic solo sprint starts the next one the same way, and the team notices.

Close the year deliberately instead: the books on this year's projects are balanced, the notes for January are written, the doors lock on time. That is not idleness. It is the discipline of a business that knows the difference between motion and progress.

Frequently asked questions

Is any technical work safe in the quiet week?

Reading, documenting and checking are safe. Changing, migrating, upgrading and deleting are not, unless the business depends on it and help is available.

What if January is always too busy for cleanup?

Then the problem is not the calendar but the priority. Book the cleanup like a meeting in the second week of January, with the people who know what the files are.

What should the last day actually end with?

A short note to yourself: what got done this year, what did not, and the three things January starts with. Ten minutes, and the year closes clean.

A practical next step

Use the last day to write the three notes January-you will thank you for: what to finish, what to check, what to decide. If the January list already feels bigger than January, book a Decision-Clarity Call and start the year with a sorted plan.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Technology Strategy & Roadmaps

All CISO Insights
Technology Strategy & Roadmaps

When the CTO Says We Need to Rebuild

A rebuild proposal is a large bet. Test it against repair, phased replacement and doing nothing, and ask for evidence that the current system cannot scale.

Technology Strategy & Roadmaps

Shadow IT: Finding What Procurement Never Approved

Teams adopt tools without asking. Discover them, classify the risk, then decide to legitimize, replace or block. A five-step workflow for executives.

Technology Strategy & Roadmaps

Legacy System Replacement: The Go/No-Go Questions

Replace, wrap or tolerate an aging system? A go/no-go scorecard weighs business criticality, failure risk, replacement cost and migration risk.