The Art of the Prompt · Copilot Basics

Better inputs. Better outputs. Every time.

Garrick Chow's prompt framework on LinkedIn Learning (GCSE) applies across every Microsoft 365 app: Goal (task and format), Context (audience and situation), Source (file, thread, transcript, or web), Expectations (length, tone, structure).

Prompting is a conversation, not a command. Your first prompt does not have to be perfect, iterate: shorter, more formal, stronger opening, add a section. Bad outputs are curriculum, not failure.

GCSE prompting framework

Goal, Context, Source, Expectations, four slots every strong Copilot prompt fills.

Core principles

Being too vague. Copilot guesses; it usually guesses wrong.
Too many tasks at once, break complex work into sequential prompts.
Expecting a finished product, plan to edit.
"Professional tone" without audience, context beats adjectives.
Giving up after one bad output, iterate; the cost of asking again is near zero.

Go deeper. Getting Started: prompting

Check yourself

What does each letter in the GCSE prompting framework stand for?

Do this in Copilot

Where does your prompting usually fall short, goal, context, source, or expectations?

Compare this to a weak prompt: "Write an email about the project update." Then paste the strong version:

Strong prompt (GCSE applied)

Draft an email to my project team (about 12 people, mix of associates and managers) summarizing where we are on the Q3 product launch. We are on track for timeline but over budget by 8%. The tone should be confident but honest, not alarmed. Use the meeting notes from our last sync as context. Keep it under 200 words and use short paragraphs, not bullet points.

Open Copilot →

GCSE framework
Iteration

Weak prompt to try first (see the difference): Write an email about the project update.
Practice template: [Goal: what should it create?] for [Context: who / what situation?]. Draw from [Source: file, email, or meeting?]. Format: [Expectations: length, tone, structure].
Use something you actually need to write this week, draft the GCSE prompt on paper before you open Copilot.

Draft an email to my project team (about 12 people, mix of associates and managers) summarizing where we are on the Q3 product launch. We are on track for timeline but over budget by 8%. The tone should be confident but honest, not alarmed. Use the meeting notes from our last sync as context. Keep it under 200 words and use short paragraphs, not bullet points.

Did you run this in Copilot? Mark complete when you have tried it.

Next lesson: Copilot in Your Daily Apps →