Is Privacy Becoming Optional?

The other day I was sitting in a meeting and noticed something that would have seemed unusual only a few years ago.

One person had their phone on the table. Another was wearing a smartwatch capable of recording conversations. Someone else was using a dedicated note-taking device. Around the room were laptops running Microsoft Teams. The meeting itself was being transcribed by Copilot.

Nobody mentioned it.

Nobody asked if recording was okay.

Nobody even seemed to think it was remarkable.

That’s when it struck me. We may have quietly crossed a line where recording has become the default and privacy has become the exception.

The New Reality: Everything Can Be Captured

For most of my career, recording a meeting was a deliberate act.

You would ask permission. Someone would set up a recorder. People knew the session was being captured.

Today that friction has largely disappeared.

Your phone can do it. Your watch can do it. Dedicated devices like Plaud can do it. Teams can do it. Copilot can summarise discussions automatically. Even people who never intended to create a permanent record can end up generating one simply because the technology is there.

The barrier isn’t technical anymore.

It’s social.

And I’m not convinced we’ve caught up.

The Assumption Problem

What concerns me most isn’t the technology itself.

Recording conversations can be incredibly valuable. I use Microsoft 365 Copilot regularly to help summarise meetings, identify action items and make sure important decisions aren’t forgotten. Used properly, it improves productivity and reduces misunderstandings.

The concern is the growing assumption that everyone knows they’re being recorded and therefore automatically consents.

That’s a dangerous assumption.

If someone joins a Teams meeting and sees the recording banner, they’ve been informed.

If you’re sitting in a café, a boardroom, an airport lounge or even having a casual conversation after an event, the situation is much less clear.

Was that discussion recorded?

Who owns the recording?

Where is it stored?

Will it be used for training an AI model?

Will it be shared with others?

Most people simply don’t know.

Privacy Was Built Around Visibility

Historically, privacy worked because recording was visible.

A camera was obvious.

A tape recorder was obvious.

Even someone taking detailed notes was obvious.

Now many recording devices are effectively invisible. A phone sitting face down on a table doesn’t attract attention. A smartwatch on someone’s wrist looks completely normal. A small dedicated recorder clipped to a shirt can disappear into the background.

The social cues that once helped us understand when a conversation was becoming permanent are disappearing.

That’s a much bigger shift than most organisations realise.

The Microsoft 365 Angle

What makes this even more interesting is that Microsoft 365 Copilot is accelerating the value of captured information.

A meeting recording today isn’t just a recording.

It’s searchable.

It’s summarised.

It’s transformed into action items.

It’s available weeks later through natural language questions.

Ask Copilot what was agreed in a meeting three months ago and it can often find the answer in seconds.

That’s incredibly useful.

But it also means recordings have become far more valuable than they were in the past. The incentive to capture everything continues to increase because the return from that captured information keeps growing.

In many organisations, the question is no longer “Should we record this?”

It’s becoming “Why wouldn’t we?”

Can You Opt Out Anymore?

Here’s the uncomfortable question.

How do you avoid being recorded if everyone else is recording?

You can choose not to use recording tools yourself.

You can refuse to record meetings.

You can leave your phone in your pocket.

None of that stops someone else from creating a record.

In some environments, avoiding recording may soon become almost impossible.

That doesn’t necessarily mean privacy is dead.

But it does mean privacy increasingly depends on transparency, trust and governance rather than technology limitations.

The old protection was that recording was difficult.

The new protection has to be that people are honest about what they’re capturing and why.

What I’m Watching Next

I don’t think we’re heading towards a world with no privacy. I do think we’re heading towards a world where we need new social rules.

Technology has moved faster than our expectations and etiquette.

We need clearer conversations about consent. We need organisations to establish recording policies that people actually understand. And we need individuals to think more carefully before assuming that because they can record something, they should.

The irony is that as tools like Copilot become better at helping us remember everything, trust may become more important than ever.

Because the real question isn’t whether everything can be recorded.

It’s whether we’ll still know when it is.

Better Is a Direction, Not a Starting Point

I have made plenty of decisions that looked sensible at the time and less impressive a year later. Usually, I was working with the experience, evidence and tools I had then. The real test is not whether I got everything right on day one. The test is what I changed after new information arrived.

That distinction matters because hindsight can become a very comfortable hiding place. I can criticise an old process without doing anything differently today. Reflection only becomes useful when it alters the next action.

Progress needs some humility

In technology, yesterday’s good practice can become today’s unnecessary friction. A workflow built around emailed spreadsheets may once have been the most practical answer. Later, a shared file in SharePoint may remove version confusion. Then a well-designed process using Teams, Planner or Power Automate may make the work clearer again.

I do not think that means every earlier choice was a failure. It means the environment changed, the team learned and better options became available.

This is where humility matters. I need enough confidence to make a decision with incomplete information, but not so much confidence that I defend it forever. Experience should sharpen my judgement, not harden my position.

Copilot makes the learning visible

Microsoft 365 Copilot gives me a practical way to shorten this learning loop.

Imagine I have been preparing a weekly client update by opening several emails, reviewing Teams messages and rebuilding the same summary in Word. I may have done that for months because it worked. It was familiar and reliable.

Then I try a different approach. I ask Copilot in Outlook to summarise the relevant thread. I use Copilot in Teams to identify decisions and unresolved actions from a meeting. I bring the material into Word and ask for a first draft organised around progress, risks and next steps. I still review every line, because responsibility remains with me, but I have changed the process based on what I now know.

The first prompt may be average. The summary may miss context. My instructions may be too vague. That is not evidence that the whole idea is useless. It is feedback. I can refine the prompt, provide a better reference file, correct the structure and save the improved version for next week.

Getting value from Copilot is rarely one brilliant prompt. It is repeated adjustment inside real work.

Improvement is a behaviour

I often see businesses delay change because they are waiting for certainty. They want the perfect governance model, the perfect use case and the perfect training plan before anyone begins. I understand the caution, especially where client data, security and accuracy are involved. Some boundaries must be established first.

But perfection can also become an excuse. A small, governed trial with a real workflow can teach more than another month of abstract discussion. Use a low-risk task. Check the output. Note what failed. Update the instructions. Share the lesson in Teams. Repeat.

It is about creating a culture where changing your method after learning something new is considered sound judgement, not an admission of weakness.

I cannot demand flawless foresight from my earlier self, my team or my clients. I can demand honesty about what the evidence now shows. I can keep what still works, replace what does not and document why the change was made.

That is how useful progress happens. Not through shame about the past, and not through blind loyalty to it. I act responsibly with what I understand today, then make tomorrow’s work better when experience gives me a clearer view.

Curiosity Is a Professional Strength

I have sat in plenty of meetings where everyone seemed to understand a term except me. A new acronym appeared on a slide, heads nodded around the room, and the conversation moved on. For years, the temptation was to stay quiet and work it out later. I did not want to be the person who slowed things down.

Now I see that moment differently. If I do not understand something, there is a fair chance somebody else is equally lost. The difference is that nobody wants to say so.

Questions expose the real work

I have learned that a simple question can be more useful than an impressive answer. “What does that mean in practice?” can uncover assumptions, vague thinking and risks that polished language has hidden.

This matters even more with AI. The vocabulary is arriving faster than most people can absorb it. Agents, grounding, orchestration and retrieval are discussed as if they have always been part of ordinary business conversation. They have not. Pretending otherwise does not make anyone more capable. It only makes the room less honest.

When I am working with Microsoft 365 Copilot, I treat uncertainty as a starting point. If I receive a long technical email in Outlook, I can ask Copilot to explain the unfamiliar concepts in plain language, identify what decisions are being requested and suggest questions I should take back to the sender. That does not replace my judgement. It gives my curiosity somewhere productive to go.

The same approach works in Teams. After a meeting, I might ask Copilot what terms were used without explanation, where the discussion relied on assumptions, or which points need clarification. The value is not in looking clever. The value is in leaving the meeting with fewer gaps hidden behind polite nodding.

Expertise is not knowing everything

The longer I work in technology, the less impressed I am by people who always need to appear certain. Technology is too broad, and it changes too quickly, for anyone to know everything. Real expertise is often visible in the quality of the questions someone asks and in how quickly they can turn an unknown into something useful.

I would rather work with a person who says, “I have not come across that before. Show me how it works,” than someone who fills the silence with confident guesses. The first response creates progress. The second creates risk.

For MSPs, this is especially important. Clients do not need us to perform certainty. They need us to investigate carefully, explain clearly and be honest about what we know. A technician who raises a hand early can prevent hours of rework. A business owner who asks what a Copilot proposal will actually change in the client’s day can stop a shiny but pointless project before it starts.

Curiosity needs practice

I do not think curiosity is a personality trait reserved for naturally inquisitive people. I think it is a professional habit. I can practise it by keeping a short list of things I did not understand during the week, then using Copilot in Word or Loop to explore them, organise my notes and identify what deserves deeper learning.

The goal is not to remove every gap. That is impossible. The goal is to become comfortable enough with the gap to examine it openly.

I no longer see “I don’t know” as an admission of weakness. I see it as the first accurate statement in a useful conversation. What matters is what I do next: ask, test, read, listen and come back with a clearer view.

Knowledge has limits. Curiosity keeps moving.

Is the Next Franchise a Fleet of Humanoid Robots or Robotaxis?

I have been thinking about what a franchise might look like ten years from now.

For the past century, the formula has been familiar. You buy the right to operate under an established brand. You lease premises, employ people, follow documented processes and pay the franchisor a fee. The local owner supplies capital and management. The franchise supplies the system.

But what happens when the system no longer needs a shopfront or a large human workforce?

The next franchise may not sell hamburgers, clean offices or deliver parcels. It may involve owning and operating a fleet of humanoid robots or Robotaxis.

From employing people to deploying capacity

Consider the basic economics of a Robotaxi fleet. The owner provides capital, maintains the vehicles, arranges charging, manages insurance and keeps the service operating. The platform provides the software, customer demand, navigation, payments and brand.

That already sounds remarkably like a franchise.

Humanoid robots potentially extend the idea beyond transport. A local operator might own a fleet performing cleaning, warehousing, simple maintenance, stock movement or after-hours inspection. The robots could work across multiple customer sites while the owner manages utilisation, maintenance and service quality.

The valuable asset is no longer necessarily the location. It is the available productive capacity.

I can imagine a future business owner asking, “How many robots should I add this quarter?” in much the same way a transport operator currently considers another vehicle or a traditional franchisee considers opening another location.

Ownership will not mean independence

There is an important catch.

Owning the physical machine does not mean owning the business. The platform controlling bookings, software, identity, updates, safety rules and customer access may hold considerably more power than the fleet owner.

This is where the comparison with today’s digital platforms becomes uncomfortable. You may own the asset, but someone else can change the commercial rules through a software update.

That makes governance critical.

A robot fleet will require more than mechanical maintenance. Every machine will need an identity, permissions, operating boundaries, audit history and a clearly accountable human owner. Organisations will need to know what each machine is authorised to do, what information it can access and when it must stop and ask for approval.

The same questions already apply to AI agents.

The control room will be in Microsoft 365

I suspect much of the day-to-day management will look more familiar than people expect.

A fleet operator might begin the morning by asking Copilot to summarise overnight incidents from Outlook, maintenance reports stored in SharePoint and exceptions discussed in Teams. Planner could surface required inspections. Power Automate could route failures to the appropriate supplier, while Power BI shows utilisation, revenue and downtime across the fleet.

The physical work may be performed by machines, but the management layer will still revolve around information, identity, risk and decisions.

For MSPs, this points to a new type of managed service. Clients may not only need their users, devices and Microsoft 365 environment managed. They may need someone to govern fleets of agents, robots and autonomous vehicles as one connected operational system.

The franchise is becoming a platform relationship

I do not know whether humanoid robots or Robotaxis will become the dominant version first. The technology, regulation and economics still have plenty to prove.

However, I believe the direction is worth watching.

The future small-business owner may employ fewer people directly while controlling far more productive capacity. Their competitive advantage will come from choosing the right platform, managing risk, maintaining utilisation and protecting customer trust.

The franchise of the future may not have a counter, a uniform or even a front door.

It may have a charging depot, a Microsoft 365 tenant and a dashboard full of machines waiting for their next job.

The transition from labour-priced services towards automated capacity, governance and outcome-based offerings also aligns with the strategic direction examined in 20260902-Cowork-Fable-51.

Wealth Starts as a Way of Thinking

I have met plenty of people who earn good money and still feel poor. Every decision is made from fear. Every new idea is dismissed because it might fail. Every purchase is supposed to prove something to somebody else. The bank balance may look healthy, but the thinking behind it remains fragile.

I have also met people with modest means who are already building something valuable. They are curious. They learn. They delay easy rewards. They see a problem and ask what it can teach them. Their financial position may not have caught up yet, but their direction is clear.

The first asset is how I think

Long before income grows, I believe a person has to become comfortable with creating value. That means looking beyond the next invoice or pay cheque and asking better questions.

What do I know that solves a real problem? What can I learn that makes my work more useful? Where am I wasting time because I have never challenged the process? Which relationships deserve more attention?

I see this in technology all the time. Two businesses can buy the same Microsoft 365 licences and get completely different results. One treats the subscription as another monthly cost. The other uses it to improve how knowledge is captured, decisions are made and customers are served.

The technology is identical. The thinking is not.

Better tools should produce better judgement

Copilot is a good example. I can use Copilot in Outlook to make an email sound polished, then move straight to the next message. That saves a few minutes. Useful, but limited.

Or I can ask Copilot to summarise a long client thread, identify the unresolved concerns, and help me see where my communication created confusion. Now I am not merely processing email faster. I am improving how I communicate and how I make decisions.

The same applies in Teams. After a meeting, I can use Copilot to revisit the discussion and examine where assumptions replaced evidence. I can take those lessons into the next client conversation. Over time, that compounds.

I do not become more valuable because I possess an AI licence. I become more valuable when I use that tool to sharpen my judgement.

Mental wealth compounds quietly

A stronger financial position is usually visible. Better thinking often is not.

No one sees the Saturday morning spent learning a new capability. No one applauds the decision to document a repeatable process in SharePoint rather than keeping it in my head. There is no instant reward for asking Copilot to challenge a business plan in Word before I commit money to it.

But those small choices alter what happens next. I make fewer avoidable mistakes. I spot opportunities earlier. I become more useful to clients. I create systems that keep working when I am tired, distracted or away from the office.

That is where the real compounding begins.

Money can increase my options, but it cannot create discipline, curiosity or judgement for me. Those have to be built first. If they are missing, more money often makes the weakness larger. If they are present, even limited resources can be used intelligently.

I have come to believe that financial progress is often a delayed reflection of internal progress. The visible result arrives later.

So I am less interested in looking successful and more interested in becoming capable. I want better questions, sounder habits, stronger systems and clearer decisions. The bank account is important, but it is a lagging indicator.

The real work starts much earlier, in the way I choose to think.

There’s No Such Thing as "Ready"

I’ve lost count of how many times a business owner has told me they’ll bring Copilot in “once we’re ready”. They mean it kindly. They want their data tidy, their policies signed off, their people trained, their SharePoint folders renamed from Final_v3_actual_final. And then they wait. Months pass. The readiness never quite arrives, because readiness isn’t a destination. It’s a story we tell ourselves to justify not starting.

Nobody learns to swim by reading about water. You learn by getting in, going under a little, and coming up knowing something you didn’t know before you got wet.

Confidence Is a Result, Not a Prerequisite

The people I see getting real value from Copilot didn’t feel ready either. They just opened Outlook one busy Tuesday, hit the Copilot button, and asked it to draft a reply to a client email they’d been avoiding. The draft wasn’t perfect. They fixed it. Next time it was faster. That small, slightly awkward first attempt taught them more than any rollout plan ever could.

Waiting to feel confident before you start gets the order backwards. Confidence is what you earn after you’ve fumbled through the first few goes. Ask Copilot in Teams to summarise a meeting you half-missed, and yes, the first summary might skate over the thing that actually mattered. So you learn to prompt it better. That’s not failure. That’s the lesson doing its job.

Small Goes Under, Not a Deep End

Drowning a little every day doesn’t mean throwing your team off the boat. It means deliberate, survivable exposure. Pick one repetitive task this week and hand it to Copilot. Draft the weekly client update in Word. Ask Copilot in Excel to explain what’s driving the number in a spreadsheet you inherited and never fully understood. Have it pull the three key points out of a forty-message channel in Teams before your Monday catch-up.

None of these are bet-the-business moments. Each one is a small go under the surface. Some will work beautifully and some will come back wrong — and the wrong ones are where the real learning lives, because they teach you where the tool’s edges are and where your own judgement still has to sit on top.

The businesses that stall are the ones treating adoption like a single, perfect dive that has to be flawless. The ones that get somewhere treat it like laps. A bit every day. Slightly uncomfortable. Steadily better.

The Water Was Never Going to Be Warm

Here’s the part nobody wants to hear: it never feels comfortable at the start, and that discomfort is not a signal to wait. It’s the signal you’ve finally begun. The team that’s “not ready” but using Copilot daily is six months ahead of the team that’s still perfecting its readiness checklist — because they’ve been quietly getting better the whole time the other one was preparing.

You don’t need clean data to draft an email. You don’t need a governance framework to summarise a document. You need a task, a first attempt, and the willingness to be a bit rubbish at it for a week.

What I’m watching now is how quickly the gap widens between the businesses that started imperfectly and the ones still waiting to feel ready. My honest read? The water’s fine. Get in.

You’ll Likely Fail… and That’s Okay

A few weeks ago I sat with a business owner who’d been quietly avoiding Copilot for months. Not because he doubted it — because he was worried he’d look foolish in front of his own team. He’d typed one clumsy prompt, got a mediocre answer, and decided the whole thing wasn’t for him. I told him the honest truth: your first attempt was always going to be a bit rubbish. Mine were too. That’s not the exception. That’s the process.

We’ve built up this strange expectation that new tools should work perfectly the moment we touch them. AI has made it worse, because the demos look so slick. So when reality delivers a bland summary or a reply that misses the mark, people don’t think I need to adjust — they think this doesn’t work. And then they stop.

Getting It Wrong Is the Point

Here’s what I’ve noticed working with people on Copilot. The ones who get value fastest aren’t the smartest or the most technical. They’re the ones willing to look a little silly while they learn. They’ll ask Copilot in Outlook to draft a reply, read it, wince, and then say “no, make it shorter and less formal.” That second and third pass is where the magic actually happens. The first prompt is just you clearing your throat.

I watched someone ask Copilot in Word to pull together a proposal from three older documents. The first version was a mess — it grabbed the wrong figures and buried the point. Instead of giving up, she told it exactly what was wrong. Ninety seconds later she had something genuinely usable. If she’d walked away after attempt one, she’d have told everyone Copilot “couldn’t do proposals.” Instead she’d learned how to steer it.

Small, Low-Stakes Failures

The trick is choosing where you’re allowed to get it wrong. Don’t stake your reputation on a board paper for your first go. Start somewhere forgiving. Ask Copilot in Teams to catch you up on a meeting you missed and see how close it lands. Have it summarise a long email thread in Outlook before you reply. If it’s off, you’ve lost nothing and learned how it thinks. These little experiments cost you a minute and quietly build the instinct you’ll lean on later.

What surprised me most is how quickly that instinct transfers. Once you’ve learned to nudge Copilot in Excel toward the right analysis, you already know how to nudge it in PowerPoint, or in a Loop page, or anywhere else. The skill isn’t the tool. The skill is being comfortable with the first answer not being the final one.

Give Yourself Permission

So I’d offer the same thing I offered that business owner. Give yourself permission to be a beginner again. Expect the early attempts to disappoint you. Treat each poor result as a clue, not a verdict. The people falling behind right now aren’t the ones failing — they’re the ones so afraid of failing that they never start.

I’m watching this play out across dozens of businesses, and the pattern is consistent. Comfort with imperfection is becoming its own competitive advantage. The willingness to fumble, adjust, and try again is quietly separating the people who’ll thrive with these tools from the people who’ll keep waiting for them to be “ready.” They already are. The question is whether you are.

Your Best Marketing Asset May Already Be Sitting in Teams

Most businesses I speak with think content creation starts with a blank page. That is usually the first mistake.

The better starting point is buried in work already being done. A client workshop. A recorded training session. A checklist built to explain something tricky. A Teams meeting where someone finally understood the issue and asked the question every other client is probably thinking as well.

That material may not have been created for marketing. Good. That is often why it works.

Real content comes from real work

I have never been a big fan of content that sounds manufactured. You can usually spot it quickly. It has the right keywords, the right structure, and no pulse.

The content that lands tends to come from delivery. It comes from explaining MFA to a business owner who wants fewer account compromises. It comes from walking a client through why SharePoint permissions matter before Copilot is enabled. It comes from showing someone how to use Outlook and Teams differently so their day is not ruled by the inbox.

Those moments have weight because they are connected to a real problem. If one client needed that explanation, another business owner probably needs it too.

That is where many MSPs and consultants miss the opportunity. They treat training as something that happens once, inside the client relationship, then disappears. I would rather see it as operational proof. It shows how you think, what you believe matters, and how you help people move from confusion to action.

Capture the explanation, not the performance

This does not mean every client session should become a public article. Confidentiality matters. Context matters. Permission matters.

But the lesson can often be separated from the client. The pattern can be reused without exposing the details.

After running a Copilot readiness session, I might open Word and ask Copilot to help turn rough notes into a plain-English outline. Not a finished post. Not something I publish without thinking. Just a starting structure based on what I actually explained.

I might then drop the key points into a private Teams channel, add the questions that came up, and use that as a source of future newsletter topics, blog ideas, short videos, or client conversation starters. SharePoint becomes the library. Teams becomes the capture point. Copilot becomes the drafting assistant. My job is still to apply judgement.

That workflow matters because it keeps content close to reality. You are not guessing what the market wants. You are listening to what clients already needed help understanding.

Proof beats polish

The market is full of polished noise. Everyone can publish more now. AI makes that easier. That also means the value of generic content keeps falling.

What still stands out is evidence of experience.

A session that helped a client understand sensitivity labels is more useful than a vague post about data protection. A walkthrough that helped a leadership team decide how to govern Teams is more useful than another article saying governance is important. A practical explanation of what Copilot can and cannot see in Microsoft 365 is more useful than a broad claim about AI productivity.

The trick is not to turn every client interaction into a campaign. The trick is to notice the teaching moments already happening in the business and preserve them before they vanish.

That may be a few notes after a meeting. It may be a transcript summary. It may be a reusable diagram. It may be a short internal explanation that later becomes external education.

If your clients keep asking similar questions, that is not an interruption. That is your editorial calendar tapping you on the shoulder.

The best content is not always created in a marketing session. Sometimes it is created while you are helping someone understand their business better. Capture that, shape it carefully, and you will sound far more useful than the people still staring at a blank page.