Where Your Hours Go: A Calendar Lesson Worth Borrowing

I’ve been thinking a lot about calendars lately — mine in particular. There’s a quiet truth most of us would rather not admit: we aren’t running our calendars, our calendars are running us. Show me a fortnight of someone’s diary and I can usually tell you, with uncomfortable accuracy, what they actually care about. The hours don’t lie.

So I opened Outlook last Saturday morning and had a long, honest look at my own.

The Calendar Is the Confession

Most weeks of mine look fine on the surface. Meetings stacked tidily, deliverables ticking along, inbox manageable. But I tried something different this time — I colour-coded a fortnight of activities. Green for what energises me. Red for what drains me. The picture changed quickly. Most of the red was email triage, status check-ins that should have been a paragraph in a chat, and busywork dressed up as “real work”. I’d been treating execution time and thinking time as the same currency. They aren’t, and the account that pays out on each is very different.

The shift I’m trying to make is at an identity level. Stop measuring myself on output volume and start measuring myself on the quality of the decisions I make. A clear head making one good call beats a frantic day producing eight average ones. The problem is your calendar has to actually let you do that — and most calendars don’t.

Where Copilot Earns Its Seat

This is where Microsoft 365 Copilot has genuinely changed something in my week. Not in a flashy way — in a quietly structural way. The red activities on my audit, the energy-drain ones, are exactly the tasks Copilot is now doing for me.

Outlook is the obvious one. Copilot drafts replies, summarises long threads, and pulls out the actual ask buried six paragraphs deep. The hour I used to lose to inbox every morning is now closer to fifteen minutes. In Teams, Copilot recaps the meetings I couldn’t attend in plain prose, with decisions and action items separated — so I don’t have to sit through the recording at 1.5x speed pretending it’s productive. In Word and PowerPoint, the first draft writes itself from a few prompts, and I edit instead of starting from a blank page. In Excel, the analysis I used to wait on someone else for is now a conversation I have with the spreadsheet.

The principle behind all of this is simple. Pay someone, or something, to take low-value work off your plate so you can spend more hours on what only you can do. Copilot is the cheapest, most consistent assistant most of us will ever have. It doesn’t call in sick. It doesn’t need handover notes. And it’s already sitting inside the apps you use every day.

Design the Week First

The bit of this I’m trying hardest to apply is the simplest one. Schedule the personal commitments before the work ones. Block the gym session, the family dinner, the thinking time — then let work fit around what’s already there. It feels backwards the first time you do it, and right by the end of the week.

I’m watching my own calendar more carefully now. Not for gaps to fill, but for patterns I’d rather not repeat. If Copilot can hand me back ten hours a week of red-zone work, the question stops being “how do I find time” and becomes “what am I going to do with the time I’ve reclaimed”. That second question, I think, is the one worth answering well.

Opportunity Is the Enemy

The most dangerous moment for an MSP isn’t a slow quarter. It’s a good one.

When the calendar is full, leads are landing, and a former client pings you about “a quick idea” — that’s when the trouble starts. Suddenly you’re half-thinking about a new managed service line, a side venture with a vendor friend, a property deal someone mentioned at lunch. None of it is bad. That’s the whole problem.

I’ve watched too many capable owners chip themselves into pieces this way. The wins keep arriving, just not in the lane they originally chose. The actual business — the one paying the bills and the team — quietly slows down while they chase the next shiny thing. A year later they wonder how the work they actually built ended up running on autopilot, or not running at all.

Every shiny thing has a real cost

When someone pitches you an opportunity, the cost looks small. A meeting. A few emails. A weekend reading through a deck. Easy.

But every hour spent on something that isn’t your main game is an hour you didn’t spend on the clients, the people, and the systems that pay your mortgage. That trade is rarely visible in the moment. It shows up six months later when renewals slip, your senior tech is restless, and you can’t remember the last proper sit-down with your number one client.

The discipline isn’t in saying yes to the right work. It’s in saying no to the wrong opportunities — especially the flattering ones.

Build a filter, not a willpower contest

Relying on raw willpower to turn things down is a losing strategy. By Friday afternoon you’re tired, someone’s been charming, and the calendar fills back up.

What works better is a written filter. One short paragraph. What you do, who you serve, the size of client you take on, and the kind of work you flat-out refuse. I keep mine in a Loop component pinned at the top of my main planning page in Teams. When a new pitch arrives, I open it, re-read the filter, and the answer is usually obvious before I’ve finished the second sentence.

The tiny ritual takes the emotion out of the decision. The filter said no. Not me.

Let Copilot guard the door

The other shift for me has been using Copilot in Outlook as a first-pass screener. When a long, friendly email arrives proposing something tangential, I ask Copilot to summarise what’s actually being requested, how much time it would cost, and how it fits against my current priorities, which I keep in a short document in OneDrive.

Most of the time, the reply writes itself. Copilot drafts a polite decline and suggests someone better placed to help. I read it, tweak a sentence, send. A minute, instead of an afternoon of overthinking.

I do the same with meeting requests. Before I accept anything outside current client work, I ask Copilot to pull recent threads on the topic and tell me whether I’ve already had this conversation. Half the time, I have. That’s the meeting that quietly doesn’t get booked.

The quieter calendar

The strange part is that turning things down doesn’t make the business shrink. It makes it sharper. The clients I keep get more of me. The team gets more of me. And the work I actually built finally has room to grow into something worth defending.

Opportunity will keep knocking. That’s its job. Mine is to stop answering every time.

Treat Your Calendar Like a Scoreboard

Last Friday I sat down with my Outlook calendar open for the week ahead and felt that familiar drop in the stomach. Eighteen meetings. Two thirty-minute “quick syncs” stacked back to back. A coaching session I’d promised myself I’d run for a client. A “catch-up” with someone whose name I had to look up twice. And the actual deep work — the strategy piece I’d been telling everyone was my top priority for the quarter — nowhere to be seen.

That’s the moment it clicked properly. My calendar wasn’t a plan. It was a confession.

What the diary is really telling you

A diary is a record of where your attention actually goes, not where you wish it went. If the most important work of your year isn’t on it — blocked out, named, defended — then you haven’t really committed to it yet. You’ve just talked about it.

A lot of us treat our calendar like an inbox. Things land in it. People send invites, we accept, and the week fills up by default rather than by design. Then we wonder why the work that actually moves the business forward keeps slipping into Saturday morning.

There’s a simple test I run now. Open Outlook on a Sunday night. Look at the week ahead. Can you point to the block that represents the one thing you said matters most this quarter? If not, the rest of the week is just noise around an empty centre. And the empty centre is the bit you said mattered.

Run a weekly audit, not a weekly hope

Hope isn’t a strategy, and a calendar that fills itself isn’t one either. So I now sit down every Friday afternoon for fifteen minutes and review what I actually did against what I said I would do. Copilot in Outlook makes this surprisingly easy — I ask it to summarise where my time went, who I spent it with, and which blocks moved against my stated priorities. The answer is often uncomfortable.

Then I look at the week ahead and run every single block past one question. Is this taking me closer to the work I said matters, or further from it? If the honest answer is “further”, the meeting goes. I decline it, suggest an async update in Teams, or send a Loop component with the three things I would have said in the room. Nobody has yet complained that they got a clearer written summary instead of a half-attended meeting.

The ones that pass the test get something more important than a tick. They get protected. Title in bold, marked as busy, no overlay. I treat them with the same seriousness I’d give a paying client, because future me is the client.

The feedback loop most leaders skip

Here’s the bit that surprised me. Once I started running this rhythm, my calendar stopped being a source of guilt and started being a source of useful signal. It tells me, week by week, whether I’m actually serious about what I said matters. Or whether I’ve quietly traded it for the comfort of being responsive.

That’s the real value of reading the week before you live it. Mid-game, a scoreline tells you what to do next — push harder, change tactics, stop bleeding time on the wrong play. The diary does the same job, if you’ll let it. It doesn’t argue with you. It just shows you the score.

Copilot can draft the polite decline. Teams can absorb the conversation that didn’t need a meeting. Outlook can hold the block you’ve been avoiding. But none of that matters until you decide, every single week, what’s on the board and what’s just filler.

The Difference Between a Direction and a Walk

I’ve been watching people coach lately. Mine and other people’s. Inside teams, on calls, in coaching sessions, in the small handovers that happen between desks. And the same pattern keeps surfacing, in versions large and small.

We give directions. We rarely take the walk.

A direction is the polite, efficient gesture — the link in chat, the screenshot with an arrow, the “have a look at this, it explains it well”. It assumes the person on the other end has the time, the focus, and the confidence to follow the trail to the end. Most of the time, they don’t. Most of the time, they were asking because the trail is exactly what they’ve been struggling with.

Taking the walk is different. It means putting down what you were doing, getting up out of your chair (literally or in the digital equivalent of it), and going with them. It is slower, it is less elegant, and it is the thing that almost always works.

Why this hits hardest with Copilot right now

The reason this is sitting on top of my mind is what I’m seeing inside Microsoft 365 rollouts. Copilot is now embedded across Outlook, Word, Excel, Teams, OneNote, Loop — every surface a knowledge worker touches. The interface is right there. The documentation is right there. The training videos are right there.

And the gap is still enormous.

That gap isn’t a documentation problem. It’s a companionship problem. People know Copilot is in their email. What they don’t know is what to type when they actually have to reply to a customer who is upset, or summarise a three-week Teams thread, or pull the relevant lines out of a contract sitting in SharePoint. They need a person beside them the first time. Not afterwards. Not in a wiki. The first time.

When you sit next to somebody — sharing a screen in Teams works just as well as sitting at the same desk — and you open Copilot in their inbox, in front of their actual unread emails, two things happen. First, the prompt becomes specific. Generic prompt libraries are useless; their prompt for their email at this moment is electric. Second, they see you make a mistake, refine it, try again, and get somewhere usable. That’s the part documentation never teaches.

The handover is part of the coaching

The other thing I’ve come to value is the handover. Coaching isn’t finished the moment somebody can do the thing once. It’s finished when they have somewhere to go the second time.

In Microsoft 365 that means leaving a trail the next person — or the same person on a different morning — can pick up. Pin the prompt you just shaped together into a Loop component the team can see. Drop a note in their Teams channel calling out what worked. Connect them with the colleague who is already three months ahead. The point is that the next time they reach for help, the path ahead is already lit.

What I’m trying to do less of

I’m catching myself in the act of pointing more often than I’d like to admit. The instinct to send the link is strong; it costs me nothing, it looks like I helped, and it gets the conversation off my plate.

But the version of me that other people actually need isn’t the one with the curated bookmarks. It’s the one prepared to push the chair back and say, fine, let’s go and look at it together.

That’s the coaching that compounds. Everything else is signage.

Do an Audit of Who’s Actually In Your Corner

A few weeks ago I was on a long drive home from a client meeting and I started running through the names of people I’d actually spent real time with over the past year — not the LinkedIn list, the actual list. The ones who’d had my ear, my weekends, my energy and, in some cases, my best thinking. By the time I got home I realised something a bit uncomfortable. A handful of those names didn’t really belong on it anymore. Not because they’re bad people. Because they’re not pulling in the same direction I am.

That’s the part nobody likes to say out loud.

The question worth sitting with

There’s one question I think every business owner should ask themselves once a year, and it’s blunt: is the time I spend with this person making me sharper, or just making me comfortable?

Comfortable is the trap. Comfortable feels like loyalty, like history, like the easy lunch where nothing hard ever gets said. Growth tends to live somewhere else.

I’ve started using Copilot in Outlook to actually look at the data. I’ll ask it to pull together who I’ve met with most over the last three months and the answer is sometimes a surprise. The people I think I’m investing in and the people my calendar shows I’m investing in are not always the same list. Calendars don’t lie. They quietly show you where your time really goes, and once you’ve seen it laid out on a page you can’t unsee it.

Three filters I run people through

When I’m doing this stocktake, I look at three things, and I try not to overthink any of them.

The first is how I feel walking away from the conversation. If I leave a coffee buzzing with ideas and a list of things to try, that’s a signal. If I leave flat and quietly wanting a nap, that’s also a signal. The body keeps a fairly honest scoreboard, even when the head is trying to be polite about it.

The second is whether they’re actually moving. Movement doesn’t have to be loud — I know plenty of quiet operators who are building something serious. But if someone has been telling me the same story about the same plan for three years running, that stagnation will start to drag on you whether you notice it or not.

The third is whether they’ll tell me I’m wrong. The people who only ever agree with me have very little to offer me. The ones who push back, who ask the awkward question, who say “are you sure about that?” — those are the ones I keep close. Anyone who’s only ever told me what I wanted to hear has never once helped me improve.

The hardest cuts are the kindest people

The brutal part of this exercise isn’t the obvious ones. It’s the genuinely lovely humans who just don’t fit where you’re heading next. Lovely doesn’t equal useful. You can wish someone well, mean it completely, and still recognise that the season of regularly being in each other’s diaries has run its course. That’s not betrayal. That’s adulthood.

I keep a private Loop page with my thinking on this — a few names, a few notes, no judgement attached. Copilot helps me draft the reflection prompts when I’m not quite sure what I’m trying to articulate. It’s not a kill list. It’s a way of being deliberate about where my hours go next year, because nobody else is going to be deliberate about it for me.

If you’ve never done a Friendventory, do one this month. Block an hour in your calendar, pour something decent, and walk through the names honestly. The people in your corner shape the business you build next. Pick them on purpose, because by default you’ll just keep whoever was around when you started.

AI Is Starting to Feel Like the Petrol Bowser

I filled up the car last weekend and did that thing we all do now — glanced at the price per litre, winced a little, and worked out whether to fill the tank or just put in enough to get me through the week. It struck me, standing there, that I’ve started having the exact same conversation about AI.

For a while, AI felt free. You paid your subscription, you used it, and the meter never seemed to run. That era is ending. Token prices, usage caps, premium request limits — the cost of running AI is becoming visible, metered, and impossible to ignore. For a small business, it’s shifting from a novelty into a line item. And like petrol, it’s no longer optional. You can’t really run the business without it, but you can’t ignore what it costs either.

A running cost, not a one-off

The mistake I keep seeing is treating AI like a piece of software you buy once and forget. It isn’t. It behaves far more like fuel or electricity — something you consume, in varying amounts, every single day. Some weeks you’ll barely touch it. Other weeks, when you’re deep in a proposal or cleaning up a quarter’s worth of numbers, you’ll burn through it.

That changes how you should think about it. A running cost needs watching. It needs a budget. And it needs someone, every so often, asking the plain question: are we actually getting value for what we’re spending here?

Spend where the work actually is

Here’s where it gets interesting for a small business. You haven’t got an unlimited tank, so you have to decide where AI earns its keep. For most of the small operations I work with, the answer isn’t exotic. It’s the boring, repetitive, time-sapping work — the email triage, the first draft of a report, the summary of a long meeting nobody wants to rewatch.

That’s exactly where Copilot inside Microsoft 365 pays for itself. Asking Copilot in Outlook to clear and draft replies to a morning’s backlog saves real hours. Having it summarise a Teams meeting you missed, or pull the key figures out of an Excel workbook, turns an afternoon into a few minutes. The trick is to point your spend at the tasks that are costing you time and money today — not the shiny demos that look clever but never touch your actual week.

Economise without going without

The same way you don’t leave the car idling in the driveway, you don’t want AI burning through your allowance on low-value busywork. Be deliberate. Use the everyday Copilot features that already come with your licence before you reach for premium-priced add-ons. Give your people a quick steer on what’s worth asking and what’s just noise. And look at the bill — actually check where the consumption is going, the way you’d question a sudden jump in the power account.

None of this is about spending less for its own sake. It’s about spending on purpose.

Where I’ve landed

Petrol taught small business owners to think in terms of value per trip, not just price per litre. AI is heading the same way. The ones who do well won’t be those who spend the most or the least — they’ll be the ones who know exactly what they’re buying and why. Watch your usage, back the work that matters, and treat AI like the utility it’s quietly becoming. The meter is running now. Best to know what it’s running on.

The Clients You Need to Let Go

Last Saturday morning I sat down with a coffee and went through my client list properly. Not the polished version on a spreadsheet — the honest one. The list where you stop and ask yourself which names make your shoulders drop when they appear in your inbox.

Out of every hundred clients, maybe twenty fit that description. They weren’t bad people. But they were the ones who turned a thirty-minute call into ninety. The ones who treated every standard you set as optional. The ones who had a complaint queued up before they’d even tried what you suggested.

And here’s the part most MSP owners don’t want to admit out loud: those clients aren’t just slightly more work. They quietly run the place.

The Maths You’ve Been Avoiding

Sit down and add up the hours. Not the billable ones. The total ones. The Friday afternoon you spent re-explaining MFA for the fifth time. The Sunday email you answered because they wrote at 9pm and you didn’t want them to think you’d ignored them. The team meeting that ran twenty minutes long because someone needed to vent about a client who refuses to follow the playbook.

If you log it honestly for a fortnight, the pattern is uncomfortable. A small handful of clients eat a disproportionate slice of your week, your team’s morale, and your own headspace. The rest of your book — the ones who pay on time, listen to your advice, and treat your team with respect — get whatever scraps of attention are left over.

Copilot Can Show You What You Already Suspect

Here is where Microsoft 365 quietly earns its keep. Ask Copilot in Outlook to summarise the volume and tone of messages you’ve exchanged with a particular client over the last quarter. Open your Teams channels and let Copilot in Teams surface the recurring complaints by topic. Pull up the recap from your last quarterly review with that client and read it back without the emotion of being in the room.

You will see it plainly. The same three issues raised four quarters in a row. The same standards politely ignored. The same tone in every second message. Copilot isn’t telling you anything new. It’s just laying out the evidence you’ve been too busy or too loyal to read properly.

I have started doing this every quarter. It takes about twenty minutes per client, and it removes the wishful thinking. You stop asking “are they really that bad?” and start asking the more useful question: “Why am I still putting up with this?”

The Conversation Itself

When you do decide to end the relationship, do it cleanly. Refund what is fair. Offer to hand over their data in a tidy package via OneDrive. Recommend a provider who is genuinely a better fit for them — not a punishment, just a different match.

I draft the offboarding email in Word with Copilot’s help, sit on it overnight, then read it again in the morning. If it still says what needs saying, I send it. No long justification. No door left ajar. A short, professional close.

What You Get Back

The first time I did this properly, three things shifted within a month. My team felt lighter. Monday mornings stopped starting with dread. And the clients I genuinely respect — the ones who do the work, follow the advice, ask good questions — got noticeably more of me.

That last shift is the one that matters. The people paying for your best work deserve your best attention, and you simply cannot offer it while a small group is quietly running off with the fuel.

The Hiring Shift Copilot Has Quietly Forced

A few weeks ago I watched someone forward a Copilot-drafted email to a client without really reading it. The tone was off. A figure was wrong. The client picked it up before they did. Nobody was being lazy — they were being efficient, in the exact way we’ve all been trained to be efficient. Get the task done. Move to the next one. That small moment has stuck with me, because I think it points at something much bigger that’s quietly reshaping how small businesses need to think about the people they hire, and the behaviours they reward.

For most of my working life, businesses hired people to do things. Send the email. Build the report. Process the invoice. Update the spreadsheet. Speed and responsiveness were the metrics that mattered most. If you could turn incoming requests into completed work quickly and reliably, you were valuable. That model held up because doing the thing was the hard part, and doing it well took real skill, attention and time.

The work that used to be hard isn’t hard anymore

Copilot has quietly upended a lot of that. Drop into Outlook and you can have a draft reply in seconds. Open Word with a half-formed idea and Copilot will hand you a structured first pass before your coffee has cooled. Excel will summarise a sheet, flag the anomalies, and suggest a formula it thinks you wanted. Teams will catch you up on the meeting you missed and tell you what was decided and who owns what. Every one of those tasks used to be where someone earned their keep. Now they’re table stakes.

What’s left isn’t the doing. It’s the deciding. Was that actually the right answer? Does the draft fit the specific client we’re dealing with, or the average client Copilot has imagined? Is the figure it pulled from SharePoint the current number, or one from two restructures ago that nobody got around to archiving? Should we even send this email, or is there a phone call hiding behind it?

We’ve been training people out of asking

Here’s the part I find uncomfortable. A lot of small businesses have spent years quietly training their people out of pausing. We rewarded responsiveness over reflection. Inbox zero over inbox thoughtful. Closing tickets over questioning whether the ticket made sense in the first place. Over time, some genuinely good people got very fast at moving work between systems without really engaging with any of it.

That worked when the slow, expensive part of the job was producing the output. It doesn’t work now. The slow part is the human bit — the read, the sense-check, the quiet moment of “this doesn’t sit right with me” that keeps a business out of trouble with a client, a regulator, or its own future self.

The maths has flipped

When output was expensive, mistakes were rare almost by accident. There was friction in the system, and friction gave people time to second-guess themselves. A bad proposal took half a day to write, so it usually got read twice before it left the building. A bad proposal now takes ninety seconds, and so do the next ten after it.

The businesses that come out of this next stretch in good shape won’t be the ones with the fastest Copilot adopters. They’ll be the ones that have quietly shifted what they recognise and reward — from doing the thing, to noticing when the thing isn’t right. That’s a hiring conversation, a performance review conversation, and most of all a culture conversation. And in most of the small businesses I see day to day, it’s well overdue.