Will Our Favourite Tools Outlive Us as Their Users?

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.

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.

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.

CIAOPS Need to Know Microsoft 365 Webinar – September

laptop-eyes-technology-computer_thumb

Now in our tenth year!

Join me for the free monthly CIAOPS Need to Know webinar. Along with all the Microsoft Cloud news we’ll be taking a look at implementing Local AI

Shortly after registering you should receive an automated email from Microsoft Teams confirming your registration, including all the event details as well as a calendar invite.

You can register for the regular monthly webinar here:

September Registrations

(If you are having issues with the above link copy and paste – https://bit.ly/n2k2609)

The details are:

CIAOPS Need to Know Webinar – September 2026
Friday 2nd of October 2026
11.00am – 12.00am Sydney Time

All sessions are recorded and posted to the CIAOPS Youtube channel.

Also feel free at any stage to email me directly via director@ciaops.com with your webinar topic suggestions.

I’d also appreciate you sharing information about this webinar with anyone you feel may benefit from the session and I look forward to seeing you there.

Why GitHub Copilot Doesn’t Belong Inside Microsoft 365 Copilot

The other day I was asked a question that sounds sensible on the surface.

“If GitHub Copilot is so good, why not just build it directly into Microsoft 365 Copilot for everyone?”

At first glance it feels like the logical next step. One Copilot. One interface. One AI assistant for everything.

The more I think about it though, the more I believe that would be a mistake.

The reason comes down to something that AI vendors often overlook. Different people work in very different ways.

A software developer spends their day creating, testing and refining code. A finance manager lives in spreadsheets. A salesperson works across emails, meetings and CRM records. An executive spends much of their time making decisions based on information coming from multiple sources.

Those aren’t variations of the same job. They’re fundamentally different disciplines.

The Context Is More Important Than The AI

What makes GitHub Copilot valuable isn’t simply that it can generate code.

It’s that it understands the environment a developer works within.

It sits inside development tools. It understands repositories. It helps navigate large codebases. It assists with testing, debugging and software creation workflows. The value comes from the context surrounding the AI.

Microsoft 365 Copilot has a completely different context.

When I ask Copilot in Outlook to draft a response, or use Copilot in Teams to summarise a meeting, the AI is working with conversations, documents, calendars and organisational knowledge. It is focused on helping people communicate, collaborate and make decisions.

Trying to merge these two worlds into a single experience risks making both less useful.

A productivity worker doesn’t need a sophisticated coding assistant appearing in every interaction. In the same way, a developer probably doesn’t want meeting summaries and document drafting cluttering up their coding environment.

Specialisation Usually Wins

We’ve seen this pattern before.

Nobody expects Excel to become Visual Studio.

Nobody asks Word to become a network troubleshooting platform.

Microsoft succeeds because its tools are specialised while still working together.

I think AI will follow the same path.

GitHub Copilot should continue evolving as the specialist assistant for software creation. Microsoft 365 Copilot should remain focused on helping knowledge workers get through meetings, emails, documents and decision-making processes faster.

The mistake many organisations make is assuming every AI capability needs to be available to every employee.

In reality, most people only need the capabilities that relate directly to their role.

Adding more functionality doesn’t automatically create more value. Sometimes it just creates more complexity.

The Real Opportunity Is Connection

Where I do see value is in integration.

Imagine a project manager using Microsoft 365 Copilot to prepare for a software review meeting. The assistant could pull summaries of development activity from GitHub.

A developer could use GitHub Copilot to understand changes in a repository while still accessing relevant business context from Microsoft 365.

That’s very different from forcing both experiences into a single product.

The future isn’t one giant AI assistant trying to do everything.

It’s a collection of specialised agents and copilots that share information when necessary while remaining focused on their primary role.

We’re already starting to see this approach emerge across Microsoft’s ecosystem.

Keep The Tool Sharp

One lesson I’ve learned over many years working with Microsoft technologies is that the best tools are usually the ones with a clear purpose.

A hammer becomes less useful once you start turning it into a screwdriver, a saw and a wrench at the same time.

The same principle applies to AI.

GitHub Copilot should remain the coding expert. Microsoft 365 Copilot should remain the productivity expert.

The goal shouldn’t be to squeeze every AI capability into a single interface. The goal should be to put the right assistant in front of the right person at the right time.

That’s where the real productivity gains will come from.

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.

Faster Leads Need Better Proof, Not More Noise

I see many businesses treat new leads like they are already convinced. Someone fills in a form, downloads a guide, books a call, or replies to a post, and the business immediately pushes for the next step.

That is often too early.

Most prospects do not arrive ready to buy. They arrive curious, sceptical, and carrying only a rough idea of the problem. If your follow-up assumes they are already sold, you force the sales conversation to do all the heavy lifting.

The better question is: what must this person see and trust before the sales conversation becomes easy?

Your best marketing is probably already sitting somewhere

In most businesses I work with, the useful material already exists. It is just scattered.

It might be in a proposal that explained the value clearly. It might be in an old webinar where someone answered the awkward question honestly. It might be in a customer onboarding email, a Teams meeting recap, a SharePoint document, or a PowerPoint deck that has been used quietly for years because it works.

The problem is not always content creation. Often, it is content discovery.

This is where Microsoft 365 Copilot becomes very practical. Instead of starting with a blank page and asking for more marketing content, I would start by asking Copilot to help identify patterns across Outlook, Teams, SharePoint, and OneDrive. What questions appear before prospects say yes? Which objections show up in email threads? Which documents get reused because they make the penny drop?

That is not a campaign yet. That is raw intelligence.

Sequence beats storage

Most businesses store useful content. Far fewer guide prospects through it in order.

A new lead does not need every case study, webinar, brochure, and feature sheet at once. That just creates a homework assignment. What they need is a path.

I would be looking for the small set of assets that change how the prospect sees the problem. The explainer that makes the risk obvious. The story that makes the outcome feel achievable. The short video that answers the awkward question. The document that shows the cost of waiting.

Then I would sequence those assets deliberately.

Not as spam. Not as a flood of automated noise. As a guided conversation that helps the prospect become ready faster.

A simple example: a lead comes in after reading a blog about Copilot readiness. Rather than sending them straight to a booking page, I might first send a short note from Outlook with a link to a SharePoint-hosted checklist. A few days later, I might follow with a Teams webinar recording that explains oversharing risk in plain language. Once the prospect has enough context, the consultation feels less like a pitch and more like the next sensible step.

Faster conversion comes from clearer thinking

I am not saying marketing automation fixes everything. It does not.

If the offer is weak, automation helps you annoy people at scale. If the message is vague, more content only increases the confusion. If the business has not done the work to understand buyer doubt, Copilot will not magically invent that understanding for you.

But used properly, Copilot can help you mine what your business already knows. It can surface recurring themes from meetings, summarise prospect questions from email, help reshape a useful document into a sharper follow-up, and keep the process grounded in real conversations rather than marketing theory.

That is the shift I care about.

Conversion is not just about more leads. It is about helping the right people reach belief sooner. The businesses that get better at that will not necessarily publish more. They will guide better.

That is where I would start.

CIAOPS Image comparison page

Every time a new image model from Microsoft becomes available I use the same test prompt to see what the result is and compare that to previous attempts. The last one of these was here:

https://blog.ciaops.com/2026/08/15/new-microsoft-image-model-2/

With new models coming out all the time, the latest is MAI-Image-2.6-Flash available today, I figured a better option going forward is to put them all on a single web page for comparison which I have now done here: