Open Microsoft Copilot, type “write an email to my boss”, and you’ll get something that reads like a 2004 form letter. Most people stop right there. The tool feels like a gimmick, they close the tab, and they quietly go back to doing everything by hand.
The model is rarely the problem. Copilot usually disappoints because it has no idea who you are, what you’re working on, or what the finished output needs to look like. Fix those three things and it stops being a novelty. Here’s the process, in order.
Work out which Copilot you’re actually using
Three different products share the same name, and mixing them up wastes a lot of time.
- Copilot on the web and in Windows chats, searches and generates images. Free and quick, but it can’t see your files.
- Copilot inside Word, Excel, Outlook and PowerPoint works on whatever document you have open, and nothing else.
- Microsoft 365 Copilot, the paid per-seat one, reaches across your email, calendar, Teams chats and SharePoint sites.
So “summarise the meeting we just had” works in the third one and falls flat in the other two. Plenty of bad first impressions come down to asking a tool for something it has no way to see. Before writing the whole thing off, it’s worth knowing what the current version genuinely does well, which is what this honest look at where Copilot succeeds and where it still stumbles covers.
Step 1: Give it a job, not a topic
Compare two prompts. First attempt: “Write about our Q3 sales.” You’ll get three generic paragraphs and a list of platitudes.
Second attempt: “You’re a sales manager briefing a regional director who cares about margin more than headline revenue. Using the figures below, write 150 words. Lead with the biggest surprise, name the two accounts that are dragging, and end with one decision you need from her this week.”
Same tool, completely different output. The second prompt does four things:
- Assigns a role, which sets the vocabulary.
- Names the audience, which sets the tone.
- Specifies length and structure.
- Demands a decision or a next action instead of prose.
That last point is the one people skip. Copilot defaults to pleasant, balanced writing because most requests are vague. Ask for a recommendation, a ranking or a risk, and it stops hedging.
Step 2: Point it at your own material
Vague prompts get vague answers because the model has nothing specific to work with. The fix is grounding: hand Copilot the source material and make it work from that.
In Word, that means opening your draft, pulling in the related document through the reference option, then asking “what’s missing from this contract summary compared to the supplier’s original scope?” In Teams, ask for a recap of a meeting you missed, then follow up with “which of those three actions has no owner?” In Outlook, drop a forty-message thread in and ask for a dated timeline of what was actually agreed.
A worked example in Excel
Say you have dates in column A and invoice amounts in column B, running to row 4,000. A prompt that works: “Write a formula that sums the amounts in column B for invoices dated this calendar month, and tell me which row range it’s covering.”
Then verify it. Copilot will hand you a perfectly confident formula pointing at the wrong range about as often as it nails it first time, especially when your headers aren’t in row one. Paste it, test it against ten rows you’ve totalled by hand, and only then drag it down.
One caution while you’re feeding documents in. Pasting a competitor’s report or a chunk of published journalism into Copilot and asking for a rewrite sits in murky legal territory that’s being tested in court right now, as the recent copyright suits brought by news publishers against OpenAI and Microsoft show. Summarise your own material freely. Be warier of other people’s.
Step 3: Make it argue with you
Most people use Copilot as a generator. It’s more useful as a critic.
Rather than “write me a launch plan”, paste the plan you already wrote and ask: “Identify the three assumptions most likely to be wrong. For each, tell me what would have to be true for it to hold, and how I’d find out cheaply.”
Other versions of the same move:
- “Read this proposal as the person who has to approve the budget, and list your objections.”
- “What’s the strongest counter-argument to this recommendation?”
- “Which paragraph here is doing no work? Cut it.”
You’ll get a sharper read than from a colleague who doesn’t want to hurt your feelings, and you can run it in ninety seconds.
Step 4: Turn one good prompt into a routine
A single clever prompt saves you ten minutes. A prompt you reuse every week saves you an afternoon a month.
The mechanics are boring but they work. Keep your best prompts in a OneNote page or a Loop component and paste in the blanks each time. In Outlook, set up a recurring Friday prompt that summarises the week’s client emails and flags anything unanswered for more than 48 hours. In Teams, make the meeting recap a standing habit rather than something you remember to do once a project has already gone sideways.
Speed matters more here than people admit. If you’re running the same prompt twenty times a day, a sluggish app kills the habit, which is why the recent performance and interface improvements to Microsoft 365 Copilot are worth another look if you bounced off it a year ago.
Step 5: Know where to switch it off
Not every surface needs an assistant, and Microsoft has started conceding the point. The company began pulling Copilot buttons out of Windows 11 apps after users pushed back on the clutter, and there’s now a straightforward route to a tidier desktop if the icons are getting in your way. The details of the Windows 11 Copilot button rollback are worth a look if you’d rather keep things minimal.
Same story on consoles. Microsoft shelved its Xbox Copilot feature entirely after it failed to find an audience, a useful reminder that the best answer to “can we add AI here?” is sometimes no.
What to do this week
Pick one recurring task that eats thirty minutes or more: a weekly report, a shared inbox triage, a status update you rebuild from scratch every Monday. Run it through Copilot four times, refining the prompt each round, and keep the version that works. Skip the broad rollout and the training session until one person on the team can point to a specific task that’s now measurably faster.
Expect the first two attempts to be mediocre. That’s normal, and it’s the part most people never get past. The gap between someone who finds Copilot useless and someone who leans on it daily is usually about five prompt revisions, not about which licence tier they bought.