There’s a version of leadership that gets repeated so often it’s become wallpaper: don’t bring me problems, bring me solutions. Most people nod at it and move on. Fewer people apply it to how they consume information.
Open any feed on a given morning and you’ll find the AI and tech space running on a different rule entirely. A headline warns that a model will replace an entire profession. A thread declares that some new capability spells the end of privacy, or trust, or human judgment. The alarm is loud. The proposed remedy is almost never there. You finish reading and you know what to fear, not what to do about it.
That gap is the problem. Not the technology. The commentary.
The Pattern
Fear travels faster than nuance, and hot takes are built for speed. A prediction of collapse gets shared. A measured breakdown of trade-offs gets skimmed and forgotten. The incentive rewards the loudest framing, not the most useful one, and over time the discourse trains people to expect alarm as the default posture toward anything new.
Watch closely and the pattern repeats across almost every wave. New capability arrives. A chorus declares the sky is falling. A smaller, quieter group asks what changes for the people who have to work with this tomorrow morning. The second group rarely gets the same reach, but it does the actual work.
I’ve sat across the table from clients who read the alarm and absorbed it as fact. They arrived at the discovery call convinced a tool would either replace their team or fail spectacularly, with no room for the middle ground where most real outcomes live. Untangling that fear took longer than it should have. Someone upstream chose the take that traveled instead of the one that helped.
I’ve heard death pronounced so many times, for so many platforms, and still find myself across from customers asking how to implement the dearly departed. The thing most fear mongers fail to take into account is adoption, and the rate at which organizations can feasibly absorb the latest and greatest. Another item that goes uncounted, especially in AI, is the actual use case. Daily I sit with customers looking for viable use cases that fit their organization. Daily, I have to walk customers back from the ledge, because they heard, and didn’t quite see.
I’ve heard AGI declared, and apps promised to build themselves from nothing but a prompt, only to watch some of the biggest vendors quietly walk it back once the bill came due. The claim shrinks into a footnote a few announcements later, while the original headline keeps circulating as though it still holds. It would be a mistake on my part to repeat that headline to customers big and small just because it read well. They deserve an honest read of what a platform can do this quarter, not what a keynote implied it might do someday.
The Standard
Bring me problems, bring me solutions isn’t a rejection of concern. Concern is often correct. A new capability can shift power, displace work, introduce risk that didn’t exist before. None of that should be waved away.
The standard is what comes after naming it. If a piece raises an alarm, it owes the reader a next step: a mitigation, a framework for thinking it through, a boundary worth drawing, a question worth asking before adoption. Absent that, the piece isn’t analysis. It’s noise wearing the costume of insight.
This is the filter worth applying before you share, and before you let something reshape how you think about your own work. Ask what the piece is asking you to do differently. If the answer is nothing except to feel worse, that’s the tell.
The Takeaway
The next time a hot take crosses your feed, don’t ask whether it’s alarming. Ask whether it’s useful. Fear without a path forward is just weather. Anyone can report on it. The people worth listening to are the ones still standing there after the storm, pointing at the door.
Stop Guessing: How Prompt Coach Trains You to Actually Talk to Copilot
I’ll start with a confession. After spending some serious time with Microsoft 365 Copilot’s Prompt Coach agent, I came to a humbling realization: for thirteen years, I have been giving my wife improper instructions. Maybe my ambiguity has resulted in some strange lover’s quarrels and to that end, I must also apologize to my spouse…its partially my fault.
“Can you grab something for dinner?” is a prompt with no goal, no context, no constraints, and no format. It is the marital equivalent of typing “help me with the project” into Copilot and being mildly offended when the output is useless. My wife, bless her, has been doing the work of an LLM for over a decade. Inferring intent. Filling in gaps. Producing a reasonable response from input that, frankly, did not deserve one.
Next time I’ll ask Q if she’d just stop at our favorite Jamaican restaurant and get me some curry goat, rice and peas, and cabbage.
Most people who try Microsoft 365 Copilot for the first time have the same experience. They type something vague, get back a generic, soulless response, and quietly conclude the hype was overblown. The hype isn’t overblown. The prompt is. The gap between a mediocre output and a genuinely useful one almost always comes down to how you structured the request.
The good news is that Microsoft has baked an answer to this directly into the platform. It’s an agent called Prompt Coach, and it teaches you the fundamentals of effective prompting while you work, not in some separate training module you’ll never finish. The better news is that the skills transfer. Once you internalize how to talk to Copilot, you’ll find yourself accidentally becoming a better communicator with humans, too. Over time, your spouse will thank you.
This article walks through Microsoft’s GCSE framework for strong prompts: Goal, Context, Source, and Expectations. And it shows how Prompt Coach reinforces each one until clean prompting becomes muscle memory.
What Prompt Coach Actually Is
Prompt Coach is a pre-built agent template available in Microsoft 365 Copilot. You can install it from the Agent Store and run it inside the Copilot app, where it acts less like a tool and more like a patient teacher sitting next to you, gently judging your life choices.
It does four things: helps you generate well-structured prompts, analyzes prompts you’ve already written, fixes the broken ones, and walks through worked examples that explain why a given prompt is effective. It works through an iterative feedback loop. You give it a rough idea, it asks clarifying questions, and you end up with something far sharper than what you started with.
Prompt Coach is my go to. As a Power Platform developer I use it to refine prompts I embed into Power Automate flows, and to help me generate instructions for agents in Copilot Studio. The point is this: use it as long as you need to. Over time, it will become second nature to write prompts that net you the outcomes you actually want, instead of whatever Copilot guessed you wanted while you weren’t looking.
The Four Pillars: Goal, Context, Source, Expectations
Microsoft’s own internal framework for prompting is referred to as GCSE: Goal, Context, Source, Expectations. Every strong prompt answers four questions before Copilot ever sees it. Whichever vocabulary you prefer, the mental model is identical.
1. Goal: What do you actually want?
The goal is the non-negotiable piece. If your prompt has nothing else, it needs this. A goal is the specific outcome you want Copilot to produce. A draft email. A summary. An analysis. An outline. A comparison.
The mistake most people make here is confusing context with a goal. “I am a consultant who regularly requests access to my clients’ environments. Rewrite this email to ask IT for environment access” gets you part of the way there, but it’s mostly background, not an objective. “Rewrite a professional email requesting IT environment access” is a goal.
Where Prompt Coach helps: when you feed it a vague goal, it pushes back. It asks what kind of output you want, what success looks like, and whether you’re trying to inform, persuade, decide, or summarize. That nudge alone fixes maybe half of all bad prompts.
2. Context: Why does it matter, and who’s involved?
Context is the background information that lets Copilot tailor its response to your actual situation. This is where you tell it who the audience is, what the project is about, what’s already been decided, what tone is appropriate, and any history that affects how the response should land.
A status update for your skip-level executive reads very differently from one for your peer engineering team. Copilot can’t infer that from “draft a status update,” and honestly, neither could I. But it absolutely can deliver if you say “the audience is our CFO, who hasn’t been close to this project and cares mostly about budget impact and timeline risk.”
Where Prompt Coach helps: it consistently asks the “who is this for and why” question. Over time, you start front-loading that information without being prompted, which is the whole point.
3. Source: What should Copilot ground itself in?
Source is where you specify which information Copilot should draw from. A specific SharePoint folder. A Teams channel. A particular file. Emails from a date range. Standard corporate language from a given domain. Grounding your prompt in the right sources is what separates a generic output from one that’s actually accurate and relevant to your situation.
Where Prompt Coach helps: it flags when you’ve referenced something without being specific about it. If you mention “the project document” without naming it, Prompt Coach will ask which one. That habit alone prevents a surprising number of hallucinated details.
4. Expectations: What are the boundaries and format?
Expectations cover both your constraints and the shape of the output. Word counts. Tone restrictions. Things to avoid. Scope limits. And the format itself: bullet list, table, paragraph, email, slide outline, JSON, executive summary, FAQ.
Specifying expectations isn’t a nice-to-have. The same content delivered as a wall of prose versus a clean three-column table is, for most business purposes, an entirely different deliverable. Expectations are what stop Copilot from producing a 2,000-word essay when you needed three bullet points.
Where Prompt Coach helps: it routinely suggests format improvements you wouldn’t have thought of. Asking for “an analysis” might prompt it to suggest a table comparing options against criteria, with a short narrative recommendation underneath. That’s a better answer than what you would’ve asked for, which is a mildly insulting thing to admit but here we are.
Prompt Coach in Action: A Worked Example
Here’s what this looks like in practice. A consultant submits a reasonable but under-specified prompt to Prompt Coach: “I am a consultant that needs that regularly requests access to my clients environments. Rewrite this email to ask IT for environment access.” Prompt Coach recognizes the instinct to improve the prompt is right, and responds with a plan to do three things in one pass.
First, it analyzes the original prompt. The prompt does have some things going for it: it states the role, identifies the task, and names the audience. But Prompt Coach calls out exactly where it falls short.
The prompt is under-specified. Goal clarity, context, tone expectation, constraints, and output expectations are all missing or vague. Copilot will guess at each of these and guessing is what leads to weak or unusable drafts.
Next, Prompt Coach rewrites the prompt with all four pillars in place: a clear goal, full context, grounded source material, and explicit expectations for tone and output format.
That improved prompt then produces a clean, professional email ready to send not a template that needs another hour of editing.
The quality of Copilot’s output is directly tied to how complete your prompt is. By clearly defining Goal, Context, Source, and Expectations, you turn Copilot from a “rewriter” into a reliable drafting assistant.
Why Prompt Coach Beats Reading a Cheat Sheet
Cheat sheets and one-off training sessions don’t move the needle on Copilot adoption because prompting isn’t an information problem. It’s a habit problem. People know they should add context. They forget in the moment because they’re busy and the blank prompt box doesn’t ask for anything specific. It just sits there, mocking you with its emptiness.
Prompt Coach changes that by interrupting the bad habit at the exact moment it’s happening. You write a weak prompt, the agent flags it, asks the missing questions, and you end up with a strong prompt and a small lesson about why it’s stronger. Repeat that loop fifty times across a couple of weeks and the structure stops feeling like a checklist and starts feeling like the only sensible way to ask for anything.
That’s the real value here. Not that Prompt Coach writes your prompts for you, but that it trains you to write them yourself. And once you’ve internalized Goal, Context, Source, and Expectations, every other Copilot experience in Microsoft 365 gets dramatically more useful overnight.
Getting Started
Prompt Coach is available as an installable agent from the Microsoft 365 Copilot Agent Store. Install it once, pin it in your Copilot app, and use it as your sparring partner for any prompt you’re not sure about. Especially the high-stakes ones, where a generic output would actually cost you time.
The first week will feel slow. By the third week, you’ll be writing prompts that include all four pillars without thinking about it, and the people on your team who skipped this step will be wondering why your Copilot outputs are so much better than theirs.
It’s because you stopped guessing.
And, if you’re lucky, your spouse stopped guessing too.
