What you'll be able to do
- Draft and rewrite documents in Word instead of starting from a blank page
- Analyze a table in Excel and get trends and outliers, not just a formula
- Turn a Word doc or a prompt into a first-draft PowerPoint deck
- Summarize a Teams meeting into decisions, owners, and next steps
- Triage a long Outlook thread and draft a reply in your own voice
Inside the path
A focused set of five-minute lessons — each one ends with a hands-on exercise, not a quiz you can guess.
Ground it in a file 5 min
The habit that separates useful Copilot answers from generic ones: point it at a real document.
Draft and rewrite in Word 5 min
Prompt for a first draft, then tighten tone, length, and structure without leaving the page.
Analyze data in Excel 6 min
Format your data as a table, then ask Copilot for trends, outliers, and the formula behind them.
Recaps in Teams and Outlook 5 min
Turn a meeting or a 30-message thread into decisions, owners, and next steps.
Build a deck from a doc 5 min
Generate a PowerPoint from an existing document, then refine it slide by slide.
Try a sample exercise
This is the kind of card you'd practice inside Iro — you do the thinking, then get feedback.
◆ Sample exercise · Prompt practice
You're in Word with a 12-page project proposal open, and your manager wants a one-paragraph summary and the three biggest risks so they can forward it in an email.
Your task: Choose the Copilot prompt that will give you something you can send.
- "Summarize this and list the risks."
- "Based on this proposal, write a one-paragraph executive summary for a busy manager, then list the three biggest risks it raises. Quote the section each risk comes from, and keep the whole thing under 150 words."
- "Write a summary about project proposals and the risks they usually have."
- "Make this proposal better."
See why the second prompt wins
The winning prompt is grounded in the open document ("based on this proposal") instead of asking Copilot to invent content about proposals in general. It sets the audience (a busy manager), the output format (one paragraph plus three risks), a length constraint (under 150 words), and a verification hook — quoting the section each risk comes from so you can check it against the file. "Summarize this and list the risks" sometimes works, but it leaves format and length to chance; the generic option isn't grounded in your document at all. Iro drills this grounding habit across Word, Excel, Outlook, and Teams.
Copilot is only as good as what you point it at
The difference between Copilot saving you an hour and wasting five minutes is grounding. Inside the Microsoft 365 apps, Copilot can read the document you have open, the email thread you're in, or the meeting you just left, and on a licensed plan its chat can pull from your files, calendar, and messages through Microsoft Graph. When you reference a specific file (in Copilot chat you can use the "/" menu to point at one), the answer is grounded in your reality instead of a plausible-sounding average.
So write prompts that name the source and the output: this proposal, that thread, these numbers, and exactly what you want back — a summary, action items, a formula, a slide. Generic questions get generic answers; grounded questions get work you can actually use.
One skill, five apps
The same grounding habit carries across the suite. In Word you draft and rewrite; in Excel you analyze data (Copilot works best when your data is formatted as a table, so it can surface trends and suggest formulas); in PowerPoint you can generate a deck from a Word doc and refine it; in Outlook you summarize threads and draft replies; in Teams you get a meeting recap with decisions and action items. Learn to ground a prompt once and you can drive every app in the family.