Word – CIAOPS

A few weeks ago I caught myself doing something I suspect a lot of people are doing right now.

I had an idea. Instead of opening a blank document, I opened Microsoft 365 Copilot and started asking questions.

Within minutes I had summaries, suggestions, outlines, and options. It was impressive. It was also a little unsettling.

The reason was simple. I had an answer before I had really worked out what I thought about the question.

That’s something I’ve been reflecting on more as AI becomes a bigger part of our daily work. We often talk about AI helping us write, but I think the more important question is whether we’re still using writing to think.

The Value of a Blank Page

For most of my career, writing has been one of the ways I clarified my thinking.

Whether it was a client proposal, a blog post, meeting notes, or an internal strategy document, the process worked because it was slow enough to force decisions. You couldn’t hide gaps in your logic. When you sat staring at an empty page, every weak assumption became obvious.

That’s still true today.

When I open a Word or OneNote document and start typing, I often discover that the idea I thought was clear in my head isn’t quite as solid as I imagined. The act of putting words on a page exposes the fuzzy edges.

The danger with AI is that it can smooth over those edges too quickly. Copilot can generate something that sounds complete before you’ve done the hard work of deciding what you actually believe.

The output may be polished. Your thinking may not be.

Copilot Works Best as a Thinking Partner

This isn’t an argument against Microsoft 365 Copilot. Far from it.

What I’m seeing in organisations is that the most successful users don’t treat Copilot as a replacement for thinking. They use it as a way to challenge and refine their thinking.

A practical example might be drafting a proposal in Word. I often start with rough notes of my own. They are messy and incomplete. Only after I’ve worked through the problem do I ask Copilot to review the draft, identify gaps, suggest alternative approaches, or summarise the key points.

The sequence matters.

Thinking first. AI second.

If you reverse the order, there’s a risk that you’re evaluating someone else’s answer rather than exploring your own understanding.

That’s a subtle difference, but it’s an important one.

Faster Answers Aren’t Always Better Answers

Many of us spend our days moving between Outlook, Teams meetings, client conversations, and project work. The attraction of having instant answers everywhere is obvious.

The challenge is that genuine understanding usually takes longer than information retrieval.

Copilot can tell you what happened in a Teams meeting you missed. It can summarise a lengthy email thread in Outlook. It can pull key points from a SharePoint document in seconds.

That’s incredibly useful.

What it can’t do is decide what those things mean for your business, your clients, or your next decision.

That responsibility still sits with you.

I think that’s why many people who try AI for the first time are both impressed and disappointed. They’re impressed by the speed. They’re disappointed when speed alone doesn’t solve the problem they were really facing.

Knowledge is easy to access. Judgement is still hard work.

The Skill Worth Protecting

The organisations getting the most value from AI aren’t abandoning traditional skills. They’re strengthening them.

Clear writing. Critical thinking. Good questioning. Sound decision-making.

Those capabilities become more important as AI becomes more capable, not less.

The people who ask the best questions get better results from Copilot. The people who understand a problem deeply can spot when an AI-generated answer misses the point. The people who can write clearly can guide AI more effectively.

That’s what I’m watching most closely.

AI is changing how we work, but I don’t believe it changes the need to think carefully. If anything, it raises the value of that skill.

The blank page still matters.

Copilot may help us fill it faster, but the real value comes from understanding what deserves to be written there in the first place.

Most people meet Copilot in Word the same way. New blank document, click the icon, type “write me a proposal,” hit Generate.

Out comes 400 words of beige. Technically correct. Completely generic. The kind of thing that could be about your business or anyone else’s.

So they shrug, decide Copilot “isn’t that good,” and go back to writing from scratch.

Here’s the thing. They weren’t using Copilot wrong. They were using the worst part of it and ignoring the best part.

A blank page is the one thing Copilot is genuinely bad at. Give it nothing and it gives you nothing — just confident, well-punctuated filler. The magic isn’t in asking it to invent. It’s in pointing it at what you already have.

What is Copilot in Word, really?

Forget the demos where someone conjures a document from a one-line prompt. That’s the party trick, not the job.

What Copilot in Word actually does well is take your material — a file, an email, a meeting, a folder — and reshape it into something new. The official term Microsoft uses is grounding. The button you press is Reference a file.

That’s the whole ballgame. You’re not asking a stranger to guess what your last client proposal looked like. You’re handing it the last one and saying “another like this.”

So the question stops being “can Copilot write?” and becomes “what do I already have that Copilot can stand on?” For most SMBs, the answer is a lot. Years of proposals, reports, policies, and SOWs sitting in OneDrive, doing nothing.

Step-by-Step: drafting from something you already have

This is the workflow I show every client. It takes about ninety seconds.

Open a new document

Start a blank document in Word, then click the Copilot icon. You’ll get the Draft with Copilot box. Don’t type your prompt yet.

Reference the file first

Click Reference a file (the paperclip), and start typing the filename. Pick the document you want Copilot to learn from — an old proposal, a strong report, a policy you’re proud of. You can attach more than one. Microsoft has the full walkthrough in Draft and add content with Copilot in Word, and the Welcome to Copilot in Word page confirms it only ever looks at the files you choose — nothing else.

Write your prompt

Now tell it what you want, and point it back at what it’s holding:

			
Draft a one-page proposal for Acme Pty Ltd.
Reference: /Northwind-Proposal.docx /Acme-Discovery-Notes.docx
Match the structure and tone of the Northwind proposal.
Keep it under 400 words.

Notice what’s missing? Nowhere do I explain what a proposal is. I’m not teaching Copilot to write. I’m showing it how we write and telling it to do that again.

Keep, regenerate, or bin it

Copilot drops the draft in. Keep it, Regenerate for another go, or Discard. Then you edit like a human — because you still have to.

Why this actually changes behaviour

Before: “Copilot, write me a client report.” → generic mush you rewrite anyway. After: “Copilot, write this report the way I wrote the last three.” → a first draft that already sounds like the business.

That second one is the difference between a toy and a tool.

Here’s the real win for MSPs. Grounding turns your clients’ own document history into an asset they didn’t know they had. Every good proposal becomes a template. Every solid SOP becomes a pattern. The licence they’re already paying for suddenly does something a free chatbot never can — because the free chatbot can’t see their files.

And it’s not just drafting. Flip it around and Copilot becomes a reading tool. Open a long contract, type Summarize this document, and it’ll hand back the gist with citations back to the source — chat with Copilot about your Word document covers that side. Summarize before you read. Draft from what you’ve got. Same tool, both directions.

Don’t ask Copilot to know your business. Show it.

If you’re rolling Copilot out to clients and the first thing you teach them is “type a prompt on a blank page,” you’ve handed them the weakest trick in the box and you’ll get the predictable shrug.

Teach Reference a file first. That’s where the value lives, and it’s the bit nobody stumbles onto by accident.

Reference a file isn’t there to help you write faster. It’s there to make sure what gets written already sounds like you.