Sixty Minutes Before the Inbox Wins: Building a Landing Strip for Your Working Day

There's a moment in most working days, somewhere between the kettle finishing and the first proper decision, when the day quietly decides what it's going to be about. For a lot of people in small UK firms, that decision gets made by whoever emailed overnight. The first hour isn't planned so much as inherited.

That's not laziness. It's gravity. The inbox is right there, it's full, and it feels like work. But feeling like work and being the most useful thing you could do at 8:55am are two different things, and the gap between them is worth measuring.

The audit: one week, four buckets

For five working days, log the first sixty minutes in fifteen-minute blocks. Not what you intended to do — what you actually did. Four buckets are enough:

• Reactive — email, Teams messages, a colleague at your desk, a supplier on the phone.
• Planning — deciding what the day or week needs, sequencing tasks, checking the calendar properly.
• Focused work — a single task with a defined end point. Quoting, drafting, reconciling, writing the thing.
• Drift — the honest one. News, LinkedIn, tidying a folder, re-reading a document you've already read, refreshing a dashboard.

Keep it on paper. A spreadsheet works, but there's something about a sticky note that stops you from editing the truth later.

Add one column for a single word: how the hour felt. Flat, frantic, calm, scattered. Data on mood is fuzzy, but patterns show up fast.

What the log tends to reveal

Two things usually surprise people.

The first is how much of the opening hour is reactive by default rather than by requirement. A good chunk of those emails will still be answerable at eleven. Some of them were never going to be answered today at all.

The second is how little planning takes place. In plenty of small firms, nobody has been given the job of deciding what the day is for. It happens in the gaps, if it happens.

And the drift number is often quietly embarrassing — not because anyone is lazy, but because an unstructured hour with no stated purpose will fill itself. It's the same principle as an unfilled diary slot: something will claim it.

An hour with no plan isn't free time. It's contested ground.

Designing a landing strip

Borrow the idea from aviation. A plane doesn't arrive and immediately start taxiing to a gate; there's a defined approach, a touchdown point, a checklist. Your first hour can work the same way, and it doesn't need to be elaborate.

A workable structure, in three parts:

Ten minutes of orientation. Before anything with a notification attached. What's fixed today — meetings, calls, school run, the delivery slot? What's the one thing that would make the day count as decent? Write it down. One line.

Twenty minutes of clearance. Deal with the two or three genuinely time-sensitive items and nothing else. The test: if this waits until 11am, does anything break? If not, it waits.

Thirty minutes of actual work. One task, chosen before you opened your inbox, with a stopping point you can see. Not a project. A task.

The proportions matter less than the order. Orientation before clearance, clearance before the open-ended stuff. If your role genuinely demands immediate response — a trade counter, a support line, a reception desk — then the landing strip isn't about protecting the hour, it's about protecting five minutes at the front of it. A written note of the day's priority, before the phone starts, still counts.

The solo version

If you're on your own, the risk isn't interruption. It's the absence of anyone to notice you've drifted. There's no colleague to raise an eyebrow at the third cup of tea and the fourth look at the same spreadsheet.

Two habits help more than any app. First, decide the day's one thing the evening before — your landing strip starts at 5pm, not 9am. Second, give the first thirty minutes a witness: a timer, a stated finish line, a note to yourself that says what 'done' looks like. Solo founders respond well to visible edges, because nobody else is going to supply them.

It also helps to name the trap. If your business runs on inbound enquiries, the inbox is the pipeline, and it deserves a proper slot — just not the whole first hour. Park it, then give it fifteen focused minutes at a set time. Reactive work with a scheduled home is very different from reactive work that runs the morning.

The team version

For a small team, one tweak does most of the work: agree a quiet window. Say 9am to 9:45, no internal messages, no expectation of instant replies. Externally, nobody needs to know. Your clients will not notice, because the phone still gets answered and the emails still get returned within the same morning.

Back it up with something simple — a shared note of each person's one priority for the day, visible by 9:30. Not a status report. One line each. It gives the manager something to steer by and gives everyone else permission to get on with it.

Be careful with the framing, though. A quiet window that gets described as a perk will be treated as optional, and it'll be the first thing dropped when the week gets tight. Better to present it as how the firm starts work: the same way a kitchen does prep before service.

Give it a fortnight, then look again

Re-run the log after two weeks. You're looking for one number: how much of the first hour is now planned rather than inherited. If it's moved from a scattered fifteen minutes to a purposeful forty, you've found nearly two and a half hours a week per person. Across a team of five, that's a working day — a real one — recovered from the front of the week.

Out of 168 hours, sixty minutes at the start of the day isn't much to ask. It just needs somebody to decide what it's for before the inbox does.