Almost every time someone tells us 'Copilot just isn't very good', and we sit next to them for ten minutes, the problem isn't Copilot. It's the prompt. They've typed something like 'write a summary of the meeting' or 'help me with this spreadsheet', got back something generic, and concluded the tool is overhyped. Meanwhile their colleague two desks away is getting genuinely useful work out of the same licence, every day, because they've learned how to ask.
Prompting isn't a dark art. It's mostly a small number of habits, applied consistently. Once people pick them up, the quality of what they get back roughly doubles overnight. Here's what we teach.
Treat the prompt as a brief, not a question
The single biggest shift is to stop thinking of Copilot as a search box and start thinking of it as a junior staff member who needs a brief. A search box rewards short queries. A brief rewards context. So instead of 'write a summary of the meeting', try: 'You're summarising a 45-minute sales kickoff for our regional managers who weren't there. Pull out the three commercial decisions made, the two open questions, and the named owner of each action. Keep it to under 200 words and use bullet points.'
That's not a longer prompt for the sake of being longer. Every extra clause is doing real work. Role ('summarising for regional managers') sets the tone. Audience ('weren't there') shapes what context to include. Structure ('three decisions, two questions, owners') tells Copilot what good looks like. Constraints ('under 200 words, bullets') stop you from getting a wall of prose you'll have to edit anyway.
The four-part prompt that works for almost everything
If you only remember one thing, remember this shape. Role. Task. Context. Format. Write it in that order, and most prompts get noticeably better.
- Role: who you want Copilot to be (a finance analyst, a B2B copywriter, a paralegal).
- Task: what you want it to do (summarise, draft, compare, critique, extract).
- Context: what it needs to know that isn't obvious (audience, tone, constraints, the company, the deal).
- Format: what good output looks like (bullets, a table, 200 words, an email starting with 'Hi Sarah').
Try it on your next five prompts. You'll feel the difference by prompt three.
Anchor it in your own files
The other huge unlock in Microsoft 365 Copilot is the /mention syntax. Typing /file, /person, /meeting or /chat tells Copilot exactly which document, person, calendar event or Teams conversation to use as its source material. Without that anchor, Copilot is reasoning over a vague swirl of recent activity and will guess. With it, you're saying 'use this file, summarise this meeting, draft a follow-up to this person' and the answers get sharper immediately.
A good habit: when you start a prompt, pause and ask yourself 'what file or meeting or person should this be grounded in?'. If there is one, mention it. If there isn't, you may be asking Copilot to invent something from thin air, which is exactly when hallucinations show up.
Iterate, don't restart
Most people prompt once, get something almost-right, and then either accept it or start over. Both are wrong. The third move - 'good, now make it more formal' or 'shorter, and drop the last point' or 'redo this assuming the reader is sceptical' - is where the real value lives. Copilot keeps the conversation context, so each turn refines rather than resets. Senior users we work with rarely accept a first draft. They get a draft, then nudge it three or four times in a row. The total time is still under five minutes, and the quality is dramatically better than a one-shot.
Show, don't only tell
If you want Copilot to write in a particular style, give it an example. Paste two emails you've written before and say 'use this tone'. Paste a paragraph from your annual report and say 'match this voice'. Models are extraordinarily good at pattern-matching on examples and surprisingly bad at following abstract style descriptions like 'professional but warm'.
Build yourself a small prompt library
After a fortnight of regular use, you'll notice you keep typing variants of the same five or six prompts: weekly status updates, meeting summaries, draft replies to particular customer types, RFP first drafts. Save those. A simple OneNote page or pinned chat is enough. When you next need that task, copy the prompt, swap in the new specifics, and you're done. The compounding effect over a quarter is substantial.
What to do when the answer is wrong
Don't argue with the answer. Diagnose the prompt. Nine times out of ten, the wrongness comes from missing context (Copilot didn't know about the constraint), wrong grounding (it used the wrong file or no file), or unclear format (you asked for a summary and got an essay). Add the missing piece and try again. The tenth time, it really is a model limitation - and you'll learn to spot those quickly, because they look qualitatively different from prompt failures.
The honest summary
Better prompts beat better licences. The teams getting the most out of Copilot aren't on a special plan; they've just internalised four or five habits. Brief, don't ask. Use the four-part shape. Anchor in your own files. Iterate rather than restart. Show your style with examples. Save the prompts that work. None of that is technical. All of it is learnable in an afternoon and pays back every day after.