--- id: copilot-why-prompting-matters lang: en track: copilot title: "Why prompting matters" seoTitle: "Why prompting matters for Copilot answers" description: "See how a clear prompt changes Copilot's answer more than any setting: say who it's for, what you want and in what form, and skip all the back-and-forth." part: prompting partTitle: "Prompting" partOrder: 3 order: 1 level: Beginner durationMinutes: 3 outcome: "See how much a clear prompt changes Copilot's answer, and know what makes the difference." summary: "A clear prompt changes Copilot's answer more than any setting: say who it's for, what you want, and in what form, and you skip the back-and-forth." draft: false updated: "2026-10-14" furtherReading: - title: "Write a great prompt in Microsoft 365 Copilot" url: "https://support.microsoft.com/en-us/microsoft-365-copilot/write-a-great-prompt-in-microsoft-365-copilot" note: "Microsoft's own guide to writing better Copilot prompts." - title: "Get better Copilot responses with great prompting" url: "https://support.microsoft.com/en-us/microsoft-365-copilot/get-better-copilot-responses-with-great-prompting" note: "Microsoft's tips for getting more useful answers from Copilot." - title: "Copilot tutorial: quick tips for better prompts" url: "https://support.microsoft.com/en-us/microsoft-365-copilot/copilot-tutorial-quick-tips-for-better-prompts" note: "A short Microsoft tutorial with quick prompting tips." keywords: - Copilot prompting - why prompts matter - vague vs clear prompts - better Copilot answers - Copilot prompt habits quiz: intro: "Three quick questions. Ace them all and the next lesson unlocks." passScore: 3 questions: - q: "Copilot gave you a weak answer. Whose fault is that, usually?" options: - "Copilot's, the tool just isn't there yet" - "The settings, they matter more than the prompt" - "The prompt's: a vague ask gets a vague answer" - "Nobody's, weak answers are pure chance" answer: 2 explain: "Usually the prompt's. A vague ask gets a vague answer, whatever tool you're using." - q: "What does a good prompt actually save you?" options: - "The rounds of edits you'd spend fixing a vague answer" - "Having to read Copilot's answer at all" - "Typing time, because good prompts are always shorter" answer: 0 explain: "The rounds of edits you'd spend fixing a vague answer. Thirty seconds of clarity up front beats three rounds of \"no, not like that.\"" - q: "You ask Copilot for \"a report on our sales.\" Why is that a weak prompt?" options: - "It should be typed in Word, not in Copilot Chat" - "It doesn't mention a deadline" - "It's phrased as an order instead of a question" - "It leaves every real choice to Copilot: who it's for, how long, what matters" answer: 3 explain: "It leaves every real choice to Copilot: who it's for, how long, what matters. So it guesses, and its guesses are average." pass: badge: "Perfect score" title: "You've seen what a prompt is worth." body: "Full marks. You know why a clear prompt beats a vague one and what the strong prompt does differently. Next up: the five-ingredient recipe for writing a great prompt." retry: "Check the marked answers and give it another go. You've got this." --- > **Level:** Beginner · **Reading time:** ~3 min > > **What you'll be able to do:** see how much a clear prompt changes Copilot's answer, and know what makes the difference. Two people ask Copilot the same kind of question. One gets back something they can use in ten seconds. The other gets a bland wall of text, sighs, and decides "Copilot isn't there yet." Same tool, same day. The only thing that changed was the words they typed. That's the whole lesson in one line: the prompt is the lever. Learn to pull it and Copilot gets a lot more useful. This lesson shows you the gap so you can see it for yourself. The [next lesson](/learn/copilot/prompting/how-to-write-a-great-prompt) gives you the recipe. ## Same task, two prompts Say you run a small team and you want a quick update for your boss on last quarter, drafted in Word or Copilot Chat. The weak prompt: *Write a report on our sales.* You'll get a report. Generic, a bit long, and built on facts Copilot filled in because you gave it none. It reads like a template with the blanks half guessed. Not wrong exactly, just useless. Now the strong prompt: *You're my assistant. Draft a short update for my manager on Q2 sales. Context: we sell software to dentists. Q2 revenue was 340k, up 12% on Q1. Two big wins (a 40-seat clinic chain) and one loss (a client churned over price). My manager likes it brief and wants to know what to worry about. Format: five bullets, plain English, under 150 words. End with the one risk worth watching.* Same request underneath. But the second one comes back tight, specific, and about your actual business, because you handed Copilot a situation instead of a riddle.
Weak prompt vs. strong promptTwo cards. Left, the weak prompt: write a report on our sales, generic and guessed. Right, the strong prompt: role, context, numbers and format included, tight and specific.Weak prompt vs. strong promptWeak prompt“Write a report on our sales.”Generic. Guesses fill every gap.Strong promptRole, context, numbers, formatall included.Tight, specific, ready to send.vsSame request underneath. Only the words typed changed.
## What the strong prompt did Look at what changed. The weak prompt left every real decision to Copilot: who the report is for, how long it should be, what counts as important, what the numbers even are. So it guessed at all of it, and its guesses were average, because an average guess is the safest thing to hand a stranger. The strong prompt made those decisions instead. It named the reader, the length, the shape, and the facts. You did the thinking. Copilot just did the typing. That split, you think, it types, is the point of the whole Prompting part. ## The cost of vague A lazy prompt feels faster. It isn't. You save ten seconds typing and lose ten minutes to the back-and-forth: "make it shorter," "no, that's not our product," "try again but less formal." You end up feeding Copilot the context you skipped, one grudging line at a time. Clarity up front is cheaper than cleanup after. Thirty seconds spent setting the scene saves you three rounds of "not like that." ## The habit worth building You don't need to memorise anything yet. Just catch yourself before you hit enter and ask one question: have I told it enough that a smart new colleague could do this? If a new hire would come back confused, so will Copilot. That pause is the habit. Build it and every lesson after this gets easier. ## Try it Take one request you'd normally fire off in a rush, in Copilot Chat or the sidebar in Word or Outlook. Write it your usual quick way and run it. Now rewrite it: add who it's for, one or two facts, and the shape you want back. Run that too. Put the two answers side by side. The distance between them is what prompting is worth, and you just earned it in under a minute. ## Key terms [Prompt](/glossary#prompt), [Prompt engineering](/glossary#prompt-engineering), [Copilot](/glossary#copilot)