You’re Using AI. Your Company Still Runs Through You.

I talk to founders every week who are already deep into AI. They’ve got ChatGPT open in another tab. Someone on the team has spun up agents. There’s a Power Automate flow humming in the background. On paper, they’re doing everything right.

Yet their week still looks the same. Hard calls still queue on their desk. Staff still ping them for answers that should live somewhere else. The calendar is still a wall of back-to-backs. The tools made them faster. The organisation barely moved.

That’s the gap I keep noticing. Personal speed is not the same as company capacity.

Faster you, same bottleneck

When a founder uses Copilot in Outlook to knock out replies, or asks Copilot in Word to reshape a proposal, they finish their own pile sooner. Good. Necessary, even. But if every material decision still waits for their nod, you’ve only compressed the work that was already on their plate. You haven’t changed who the work flows through.

I see it in Teams more than anywhere else. A channel fills with questions that only the founder can settle. Meeting after meeting exists so they can “just confirm” something. Copilot can summarise those meetings and draft the follow-ups. Useful. It still doesn’t stop the next wave of the same questions landing on the same person.

The quiet cost is attention. Every interruption that only they can clear is a tax on the thinking the business actually needs from them.

Put the answers where the work happens

The shift that matters is boring, and that’s why people skip it. Stop treating AI as a private accelerator and start treating Microsoft 365 as the place your team’s answers already live.

When policies, pricing notes, and “how we do this here” sit in SharePoint or a well-kept Teams channel, Copilot can pull them for the next person who asks — without another ping to the founder. When that knowledge only lives in someone’s head or a buried email thread, no amount of prompting helps. The model can only work with what the organisation has bothered to store.

I’ve watched founders paste the same explanation into ChatGPT three times in a week, then wonder why their week still vanished. The better move was one clear page in SharePoint, shared with the right people, and a habit of pointing the team at Copilot in Teams instead of at their inbox.

Same idea with decisions. If the pattern of a decision can be written down — thresholds, who owns what, what “good enough” looks like — Copilot in Word or Loop can help a lead draft the first pass. The founder reviews the exception, not every ordinary case. That’s not abdication. That’s designing the company so ordinary work doesn’t need a royal signature.

Free the calendar by changing the meeting

Packed calendars are often a symptom, not the disease. People book the founder because the founder is still the only reliable source of context. Copilot in Teams can capture notes and actions, but the lasting fix is fewer meetings that exist only to transfer what should already be findable.

I’m watching founders who treat Copilot as part of how the team works — not just how they clear email — start to get real hours back. Not because a chatbot is magic. Because decisions and answers stop routing through one desk by default.

If your AI stack has made you personally sharper but left the company just as dependent on you, the next move isn’t another tool. It’s putting the knowledge, the thresholds, and the follow-through into Microsoft 365 where Copilot — and your people — can use them without waiting for you.

You Need You More Than You Need Them

image

A few weeks back I watched someone paste a Copilot answer straight into a client proposal without reading it. Not skimming it — actually reading it. The words went from the screen to the document to the send button in about forty seconds. When I asked why, the answer was telling: “It’s usually right.” Usually. That word did a lot of heavy lifting, and it’s the reason I keep coming back to a simple idea. You need you more than you need the tool.

The tool is fast. You are accountable.

Copilot has changed how quickly I can move. I can sit in Outlook, ask it to draft a reply to a tangled client email, and have something workable in seconds. That’s genuinely useful. But the draft isn’t the decision. The decision is still mine — the tone I want, the thing I choose to leave unsaid, the commitment I’m willing to make on behalf of my business. Copilot can hand me the first version. It can’t hand me the judgement about whether that version is the right thing to send.

I think a lot of people are quietly outsourcing that judgement without noticing. The speed is seductive. When an answer arrives fully formed and reads confidently, the temptation is to assume the thinking has already been done. It hasn’t. The thinking is the part only you can do, and it’s the part that matters most.

Use it to sharpen your view, not replace it

The way I work now, Copilot is a sparring partner, not an oracle. If I’m shaping a position on something, I’ll ask it to argue the other side. I’ll open a messy Excel sheet and ask Copilot to find the pattern I’m missing, then decide for myself whether that pattern actually means anything. In Teams, I’ll have it summarise a meeting I half-listened to, and I still go back and check the bit that felt important. The tool widens the field of view. I’m the one who decides where to look.

That distinction sounds small, but it changes everything about how the work feels. When you treat Copilot as the answer, you shrink. When you treat it as a way to test your own answer, you grow. The people who’ll do best over the next few years aren’t the ones who lean on it hardest. They’re the ones who bring more of themselves to it — more context, more standards, more of a point of view worth defending.

Bring more of yourself, not less

There’s a version of this technology that quietly makes people passive, and there’s a version that makes them sharper. The difference isn’t in the tool. It’s in the person sitting in front of it. Copilot will happily fill any silence you leave. If you show up with nothing, you’ll get something generic and forgettable. If you show up with a real opinion, it becomes an amplifier for that opinion.

So I keep reminding myself, and the people I work with: the tool is a multiplier, and a multiplier does nothing to zero. Your taste, your standards, your read on the situation — that’s the number it multiplies.

What I’m watching now is whether people use this moment to think more or think less. Because the tools will only get better at answering. The rare thing, the thing that stays yours, is knowing which answer is actually worth having.

The Future of MSP Support Is Not Better Search–Get my FREE publication for help

image

Get you copy here – From Search to Intelligence Just enter $0 as the price, although a donation or a subscription to my newsletter would be appreciated.

I have watched plenty of skilled technicians work a support ticket with a browser full of tabs, two admin portals open, an old ticket on one screen and Microsoft Learn on another.

They eventually find the answer.

The problem is that the next technician often starts again from the beginning.

That is the limitation of search. Search can help me locate information, but it does not automatically connect what I found with the customer’s history, the evidence in the ticket, the conversation in Teams and the lesson buried in somebody else’s inbox.

For an MSP, that repeated reconstruction is expensive.

The real shift is from retrieval to reasoning

I do not believe Microsoft 365 Copilot should replace search, technical documentation or engineering judgement. Those remain essential. The change is in what happens around them.

An engineer investigating an Exchange Online mail-flow issue may still need a message trace, an NDR and the current Microsoft documentation. Copilot can help organise that material into known facts, missing evidence, competing explanations and a safe diagnostic plan.

That is very different from asking, “How do I fix this?”

The first approach exposes uncertainty. The second invites a confident answer before the diagnosis exists.

I want Copilot helping an engineer compare evidence, challenge assumptions, draft a clean escalation and turn the verified outcome into a useful knowledge article. I do not want it making untested production changes or weakening a security control because that appears to be the quickest path to closing the ticket.

Faster guessing is not progress.

A closed ticket should improve the next ticket

One of the biggest missed opportunities inside many MSPs is what happens after a problem has been resolved.

The engineer understands what occurred. The customer receives an update. The ticket is closed with a few hurried lines. Most of the reasoning then disappears.

Microsoft 365 Copilot gives an MSP a practical way to change that. Once the engineer has verified the resolution, Copilot can help produce the internal note, create a customer-friendly explanation and draft a reusable article for a permissioned SharePoint knowledge library.

The human still confirms the facts. The human still approves the wording. The human still owns the outcome.

The difference is that valuable knowledge no longer has to remain trapped in personal memory.

An MSP that makes knowledge capture part of ticket closure starts building organisational capability from ordinary support work. The next engineer begins with more than a search box and a vague recollection that someone saw something similar last month.

This is an operating-model decision

Buying licences will not create this result by itself.

I would begin with a small service-desk group and a few support categories where research, handover and documentation consume real time. I would change the ticket template so evidence, assumptions, tests, negative results and validation are recorded. I would review permissions before allowing Copilot to surface information more easily. I would then measure the effect using the MSP’s own baseline rather than somebody else’s productivity claim.

That produces something far more valuable than a collection of clever prompts.

It produces a support method.

The MSP opportunity is not merely to answer tickets more quickly. It is to make investigations more consistent, handovers more complete, customer communication clearer and verified knowledge easier to reuse.

Search helps me find an answer.

Intelligence helps my organisation retain what it learned.

That is the transition MSPs should be preparing for, and it is the focus of my new guide, From Search to Intelligence, which is now available for free (a denotation would be welcome and maybe subscribe to my email newsletter as well.)

Character Is the Real Contract

image

I have sat through meetings where the proposal looked excellent. The pricing was sensible. The scope seemed clear. Everyone left sounding positive.

Yet something still felt wrong.

I have learned to pay attention to that feeling. Commercial arrangements rarely fail because the Excel formula was slightly imperfect. They fail because one party avoids difficult conversations, changes the meaning of an agreement after the fact, or treats trust as something to spend rather than protect.

A contract matters. Character matters more.

Pressure Reveals the Relationship

I do not really know a business partner when everything is going well. I learn who they are when a project slips, a client becomes frustrated, or an unexpected cost appears.

That is when behaviour becomes evidence.

A trustworthy person raises the issue early, owns their part and helps work through the options, even when the answer is uncomfortable. Someone less trustworthy delays, obscures, redirects blame, or searches for wording that lets them escape responsibility.

I see this in MSP relationships. A new client may appear commercially attractive, but the warning signs often arrive before the agreement is signed. They speak dismissively about their previous provider. They want undocumented exceptions. They push for access before approvals are complete. They treat every boundary as an obstacle to negotiate away.

I used to think a strong process could contain that behaviour. Now I think process can expose it, but it cannot repair it.

Technology Records Decisions, Not Intentions

Microsoft 365 gives me ways to make work visible. I can capture meeting actions in Teams, keep agreed documents in SharePoint, use Planner to assign responsibilities, and ask Copilot to summarise a discussion or draft a follow-up in Outlook.

That visibility reduces ambiguity and gives everyone a shared record.

But none of those tools can supply integrity.

For example, after a client meeting I might ask Copilot in Teams to summarise the decisions, then send the agreed actions through Outlook. A good partner reads that record and corrects anything that is unclear. A bad one may stay silent, then challenge the same agreement later when it becomes inconvenient.

The technology did its job. The problem was never documentation. The problem was whether the people involved respected what the documentation represented.

This is why I do not treat governance as a substitute for judgement. Good governance supports good people. It also limits the damage caused by poor behaviour. It should never become an excuse to ignore obvious warning signs.

The Best Return Is Fewer Regrets

I still examine margin, risk, scope, payment terms and delivery capacity. I would not replace due diligence with instinct. However, I now give equal weight to how people behave during the sales process.

Do they answer direct questions directly? Do they keep small commitments? Do they respect the people who are not in the room? Can they disagree without becoming personal? Do their actions match the story they tell?

Those signals influence the future more than a polished proposal does.

I have found that the right person can help a difficult arrangement recover. They communicate, adapt and work towards a fair result. The wrong person can turn even an attractive opportunity into months of distraction, resentment and avoidable cost.

So I try to choose the relationship before I choose the transaction.

The numbers still need to work. The scope still needs to be clear. The agreement still needs to be written down. But before I commit, I ask myself a simpler question: if circumstances become difficult, do I trust this person to remain honest, reasonable and accountable?

If the answer is no, the spreadsheet is not going to save me.

Need to Know podcast–Episode 370

In this episode I ask the question about whether privacy is becoming and optional and take a deep dive into creating better data structures in places like SharePoint and Teams that help users and AI generate better results. There is also the usual look at recent cloud news from Microsoft and thoughts on how even all this is become about AI. Love your feedback.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-370-structure/

Subscribe via iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

or Spotify:

https://open.spotify.com/show/7ejj00cOuw8977GnnE2lPb

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show

Resources

CIAOPS Need to Know podcast – CIAOPS – Need to Know podcasts | CIAOPS

X – https://www.twitter.com/directorcia

director@ciaops.com

CIAOPS Blog

Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron

CIAOPS AI Dojo

CIAOPS weekly news update – CIA Brief – CIAOPS

CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS

Get your M365 questions answered via email

Join my email list

A special thanks to the CIAOPS Patron community for making this podcast possible. You can find the benefits of a subscription to the community and become a member at https://www.ciaopspatron.com

Updates

Take control of your EWSAllowedAppIDs list before EWS access changes

Microsoft is changing how Exchange Web Services (EWS) access is managed. Organizations should review and manage their EWSAllowedAppIDs list now to ensure approved applications retain access and to avoid disruptions when the new controls take effect.

Link: https://techcommunity.microsoft.com/blog/exchange/take-control-of-your-ewsallowedappids-list-before-ews-access-changes/4553534

Understanding the new 100 GB mailbox entitlement for Microsoft 365 Business suites

Microsoft explains the introduction of 100 GB mailbox storage for eligible Microsoft 365 Business plans, outlining entitlement requirements and how organizations can benefit from increased mailbox capacity.

Link: https://techcommunity.microsoft.com/blog/exchange/understanding-the-new-100-gb-mailbox-entitlement-for-microsoft-365-business-suit/4548243

AI

Available today: OpenAI GPT-6 Astra in Microsoft Copilot

Microsoft has added OpenAI’s GPT-6 Astra model to Copilot, giving users access to an advanced foundation model designed to improve reasoning, content generation, and productivity experiences across Microsoft 365.

Link: https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/available-today-openai-gpt-6-astra-in-microsoft-copilot/4552808

Available today: Anthropic Claude Fable 5.1 in Microsoft Copilot

Anthropic’s Claude Fable 5.1 model is now available in Microsoft Copilot, expanding the range of AI models users can leverage for research, analysis, content creation, and complex business tasks.

Link: https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/available-today-anthropic-claude-fable-5-1-in-microsoft-copilot/4551974

Expanding model choice in Copilot with Grok

Access to Grok models is rolling out through the Microsoft Frontier Program in Microsoft Word, Excel, and PowerPoint. We are starting with a focused release to gather customer feedback and learn how customers use the model across common productivity scenarios.

https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/expanding-model-choice-in-copilot-with-grok/4555749

What’s New in Microsoft Copilot | August 2026

A monthly roundup of new Copilot capabilities, including model updates, workflow enhancements, productivity improvements, and new AI-powered features designed to help users work more effectively.

Link: https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/what%25E2%2580%2599s-new-in-microsoft-copilot–august-2026/4551960

Security

What’s new in Microsoft Security: August 2026

Microsoft’s monthly security update covering new capabilities across Defender, Sentinel, Entra, Security Copilot, and other security products, along with recent security announcements and enhancements.

Link: https://www.microsoft.com/en-us/security/blog/2026/08/27/whats-new-in-microsoft-security-august-2026/

Passkey-themed social engineering leads to identity and cloud compromise

Microsoft details a campaign where attackers used passkey-related social engineering techniques to trick users into compromising credentials and cloud identities, while also providing mitigation guidance.

Link: https://www.microsoft.com/en-us/security/blog/2026/09/09/passkey-themed-social-engineering-leads-identity-cloud-compromise/

Protecting organizations from AI-assisted executive impersonation and invoice fraud

This security guidance examines how attackers are using AI to impersonate executives and conduct invoice fraud, alongside recommendations to help organizations detect and prevent these attacks.

Link: https://www.microsoft.com/en-us/security/blog/2026/09/10/protecting-organizations-ai-assisted-executive-impersonation-invoice-fraud/

Impersonating IT support: how threat actors turn a remote session into enterprise-wide access

Microsoft analyzes how attackers impersonate IT support staff to gain remote access and expand their foothold within organizations, highlighting attack techniques and defensive measures.

Link: https://www.microsoft.com/en-us/security/blog/2026/09/02/impersonating-it-support-threat-actors-turn-remote-session-into-enterprise-wide-access/

From CIAOPS

Image Model Comparison

A practical comparison of image generation models, reviewing differences in output quality, style, and effectiveness to help users evaluate which AI image generation model best suits their needs.

Link: https://directorcia.github.io/Office365/image-comparison.html

September webinar – local AI

https://blog.ciaops.com/2026/09/10/ciaops-need-to-know-microsoft-365-webinar-september-5/

Will Our Favourite Tools Outlive Us as Their Users?

image

I was holding a hammer recently and caught myself thinking about how little it has changed. A handle. A weighted head. A simple tool that turns a human movement into a useful result. Email feels more sophisticated, but the basic relationship is similar. I decide what I want to do, then I operate the tool.

I am starting to wonder whether that relationship is about to reverse.

The tool may stay while the user changes

I do not think hammers, spreadsheets, inboxes or project boards are disappearing. I think the interesting possibility is that humans may stop being their main operators.

A robot on a building site may still use something recognisable as a drill because the drill is already an efficient way to apply rotational force. An AI agent may still use email because email remains a widely accepted way for organisations to exchange requests, approvals and records. The tool survives because the surrounding world already understands it.

What changes is who, or what, sits at the controls.

That matters because many of our tools were designed around human limitations. Email gives me time to compose a thought, send it, wait and respond later. A spreadsheet lets me arrange information into rows and columns because that is a structure I can inspect. Menus, buttons, folders and dashboards exist partly because I need visible handles for complicated systems.

AI does not necessarily need those handles. It may use the underlying service directly, faster and more consistently than I can. Yet it may continue producing emails, documents and spreadsheets because people, businesses and compliance processes still expect them.

Outlook may become a machine workspace

I can already see the early shape of this in Microsoft 365 Copilot. Today, I might ask Copilot in Outlook to summarise a long thread and draft a reply. I am still the operator. I read the summary, check the wording and press Send.

The next step is not difficult to imagine. An agent monitors the inbox, recognises a routine supplier request, checks the relevant SharePoint record, prepares the response and routes only the exception to me. Email remains. Outlook remains. SharePoint remains. But my role moves from operating every tool to supervising the work performed through them.

For me, this is a more useful way to think about AI than asking whether it will replace a particular application. A familiar tool can remain everywhere while becoming almost invisible to its former human users.

Efficiency is not the only measure

I do not believe the most efficient operator should automatically make every decision. A machine may swing a hammer more accurately or process an inbox more quickly, but speed is not judgement. Context, responsibility and consequences still matter.

If an AI sends the wrong email, approves the wrong variation or updates the wrong customer record, someone still owns the outcome. That means I expect the valuable human skill to shift. Knowing where to click will matter less. Knowing what should happen, what must never happen and when an exception needs attention will matter more.

The practical question for every business is not simply, “Which tools can AI use?” I think it is, “What authority are we prepared to give it, and how will we know when it is wrong?”

I suspect many tools I love will survive for decades. I may just use them less directly. The hammer, inbox and spreadsheet could become part of a machine-operated layer beneath my work.

I will not miss every click. But I do want to remain accountable for where the work lands.

The Ambition Has to Start With You

image

I have noticed something uncomfortable about ambition. People are often happy to encourage a plan once it looks sensible, funded and likely to work. Very few will stand beside you when it is still just a rough idea that sounds too large for your current position.

That is not cruelty. Most people are busy carrying their own doubts, deadlines and responsibilities. They cannot see the picture in your head. If I wait for someone else to give my idea permission, I may be waiting forever.

Other people see the risk first

When I describe a bold goal, the first response is often practical. Who will pay for it? Where will the time come from? What happens if it fails?

But practicality can become a hiding place. It is easy to keep refining a modest plan because it attracts less criticism. It is harder to admit that the smaller plan does not really interest me.

I see this with business owners considering AI. They start by asking how Microsoft 365 Copilot can save a few minutes writing an email. That is useful, but it is rarely the biggest opportunity. The larger question is what the organisation could become if its people had more time to think, decide and serve customers well.

A bigger vision might involve redesigning how work moves through the business. I might use Copilot in Outlook to identify the recurring questions filling an inbox, then bring the themes into a Word document and map a better process with the team. The technology helps me examine the work. It does not choose the destination for me.

Start before the applause

The early stage of any worthwhile idea is usually quiet. There is no audience, no case study and no reassuring success story. There may only be a notebook, a half-built plan and a nagging sense that I should keep going.

That is where personal responsibility matters. I have to make the first version. I have to block out time. I have to test the idea while it is still easy for others to dismiss.

Copilot can help turn that private ambition into something I can work with. I can ask it to challenge assumptions in a business plan, summarise competing options, or turn scattered notes into a draft proposal. I can use Teams to bring the right people into the conversation once the idea has enough shape to discuss. None of that replaces courage. It simply reduces the friction between thinking and doing.

Build evidence, not permission

I do not need everyone to believe at the beginning. I need enough evidence to justify the next step.

That may be one customer conversation, one working prototype or one improved internal process. Small proof points matter because they change the discussion. A vague ambition becomes an observable result. People who could not picture the idea can finally see part of it.

This is also how I avoid confusing ambition with fantasy. A large goal still needs discipline. I can think expansively while testing carefully. I can hold onto the destination without pretending I already know the entire route.

The important thing is that I remain responsible for the direction. Advisers can sharpen it. Colleagues can strengthen it. Copilot can help me explore it. But none of them can want it on my behalf.

If there is an idea I cannot stop thinking about, I take that seriously. I write it down, give it structure and take one real step towards it. Support may come later. Momentum may attract people who could not see it at first.

But the first belief has to be mine.

Is Privacy Becoming Optional?

image

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.