Copilot 101 for an MD
Sixty minutes, in person, three people in a room. Half demo, half his own inbox. The exec session.
↯Pivot map — read the room, not the script
AWhat you need open
BPre-flight
- Deploy the assets if they are not already there: .\deploy-to-colin.ps1 -Status then -Deploy.
- Book the room 10 minutes early. In person means cables, and the room seats six.
- Sign in to Caldova as ColinB in a dedicated Edge profile BEFORE they walk in.
- Open the 'Exec demo' mail folder and the Session Demos/Exec folder so nothing is hunted for live.
- Confirm Nick has an M365 Copilot licence assigned. If he does not, the second half changes completely.
- Have the prompt list ready to paste into a chat or email at the end - he will ask for it.
- Decide in advance which THREE prompts he will run himself. Do not improvise this.
- Close every other window. Small room, big screen, nothing personal on it.
!Things that will bite you
Do not open with what Copilot is. Open by finding out what his Thursday actually looks like. Everything after this is shaped by the answer, and if you skip it you will demo the wrong thing for an hour.
Before I show you anything - what does a bad Thursday look like for you? Not the strategy part. The bit where you are behind and you know it.
I am going to show you three things on a demo tenant so nothing here is real, and then I want you to run two or three on your own inbox while I am in the room. The second part is the one that matters. If it does not work on your data it does not count.
A lot of what I am about to show is more useful to you than to Nick, because you are the one in his inbox at seven in the morning. I will point out which ones as we go.
One thing out of the way first, because it is the question everyone asks and it deserves a straight answer rather than a slide.
Search my files and email for the delivery partner decision. Tell me what has been decided so far, what is still open, and who is waiting on whom. List your sources.
Scroll to the sources and OPEN ONE. Say: this is how you check it. If an answer is going to change what you do, open at least one source first. Ten seconds, and it is the difference between using this well and badly.
That is the whole governance conversation for today. If you want the deeper version - what an admin can see, what is retained, what happens with sensitivity labels - that is a different hour and I will bring the right person.
Session Demos / Exec / 'Partner selection - executive decision paper.docx'. Open it in Word, then Copilot from the Home tab. Both prompts say 'this paper' and need a document to point at. If you prefer the chat, attach the file first with the paperclip - the prompts are identical either way.
Here is an executive decision paper. Nine sections, about two thousand words, lands on a Friday, decision on Thursday. You have all had this document.
Summarise this paper for someone who has not read it and has five minutes. One paragraph on the decision being asked for, then the options with the strongest argument for and against each, then what I am specifically being asked to decide. No more than one page, plain sentences, no adjectives.
Useful. But that is the summary anyone would write. Here is the one that is actually worth something.
Based on this paper, what are the three hardest questions I am likely to be asked in the meeting, and where is the weakest answer in the document? Tell me which section each one comes from.
The scorecard favours Ashcroft but the recommendation is Beckworth, and the paper's own reasoning is that the regional rollout cannot be in phase one. A good answer spots that the recommendation contradicts the scorecard and explains why. That is the moment this stops looking like summarising.
Notice it did not leave the document. No web, nothing invented. Everything it said is in the paper and you can check it.
This is the pivot point of the session. Stop demoing. He runs these on his own inbox with you sitting beside him. If you demo this on Caldova instead, you have wasted the hour - he already believes it works on fake data.
I want you to run this one, not me. It is your inbox, and if it does not work on your inbox it does not count.
Review my unread email from the last three days and group it into three lists: needs a decision from me this week, needs a short reply but is not urgent, and no action needed. For each item in the first list give me one line on what the decision is and who is waiting on it. Put the list in the order I should deal with them, not the order they arrived.
What has happened in my email in the last week that I have not replied to and probably should have? Tell me who is waiting, how long they have waited, and what they asked for.
Catch me up on everything about this topic across my email and files over the last month. What was decided, what is still open, and what is the single most recent position. Tell me where each point came from.
Who is waiting on me and how long have they waited is the prompt that lands hardest with every executive who has ever run one. It is uncomfortable in exactly the right way.
If the answer is not right, do not start again. Tell it what was wrong in one line - too long, you missed the board paper, ignore anything from the all-staff list - and it revises. Correcting is faster than re-prompting and it is what gets you the answer you wanted.
On Nick's own calendar this needs nothing open — it reads his real meetings. For the DEMO version, reference both of these with the / picker: '/Executive team minutes - 3 September 2026' and '/Executive team minutes - 17 September 2026', both in Session Demos / Exec. The prompts below say 'this' and 'the same material', so without those two files referenced you will get a vague answer.
This is the one I would put money on you using every week. Open your calendar and pick a meeting you have next week that you have not prepared for.
I have a meeting about this next week. Pull together everything I need: what was agreed last time, what has happened since, what is unresolved, and who is bringing what. Then give me the three questions I am most likely to be asked and a one line answer to each.
Looking at the same material, what is the thing most likely to be raised that nobody has prepared for? Tell me why you think that and what I would need to know.
The 17 September minutes carry actions forward from the 3 September set rather than closing them, which is exactly the pattern every governance meeting has and nobody tracks.
Say directly to her: you could run this the evening before and put the answer at the top of his brief. That is a ten minute job that saves him twenty and makes him look prepared.
She runs his inbox, his calendar and his prep. Half the value of this hour lands on her. And she is the one who will still be using it in three months, which means she is the one who makes it stick.
Go through the mail that arrived overnight and write me a short brief: what needs his decision today, what needs a reply from me, and what he needs to know before his first meeting. Three short lists, one line each, no preamble.
Draft a reply to this on his behalf. Courteous and direct, four sentences at most, no adjectives, and do not thank them more than once. Match the tone of how he normally writes to this person.
Who has he asked for something in the last month and not received it? List the person, what he asked for, when he asked, and how long it has been outstanding.
Look at his calendar for next week and tell me which meetings need preparation from me, what that preparation is, and which ones have no agenda and probably should.
That last one is my favourite. It is not a summary, it is a judgement about what is missing, and it is the sort of thing that takes an experienced EA five years to learn to spot.
Everything so far you have to remember to do. This is how it happens without you remembering.
- Run a prompt you liked, for example the triage one.
- Save it, so it is one click next time rather than retyped.
- Schedule it, so it runs before you get in and the answer is waiting.
- Point out the Prompt Gallery - there are good ones there and they are worth five minutes of browsing.
Say: the difference between people who get value from this and people who do not is not skill, it is whether it became a habit. A scheduled prompt is a habit you only have to decide once.
The meeting is titled Copilot and Cowork so it has to be mentioned. But it is a different product with a different conversation and it will eat the hour if you let it.
If that is interesting I would rather bring it back properly than squeeze it into five minutes. There is a good cost and control walkthrough I can show you in twenty.
If he wants to go deeper, point him at the Cowork Cost and Control demo on the same site rather than improvising it here.
An exec session that ends with one concrete habit and something in his inbox is worth more than one that showed two more features and ran to the bell.
One thing. Not ten. Tomorrow morning, before you open your inbox properly, run the triage prompt. That is it. If it works for you once, the rest of the card is there when you want it.
- Send the prompt list to both of them while you are still in the room. Do not promise to send it later.
- Ask Alle directly which two of hers she will try this week. Naming them makes them happen.
- Offer the follow-up: thirty minutes in three weeks to see what stuck and fix what did not.
- Ask him one question: who else in his leadership team should get this hour.
That last question does two things. It tells you whether the hour landed, and it is how this turns into eight more sessions rather than one.
Grouped by the job to be done, not by feature. An exec does not care which app it is in.
RIf something goes wrong
✓Truth ledger
- Microsoft 365 Copilot can be grounded on work content or web content and the toggle is visible
- Copilot cites its sources and each one can be opened
- Files can be referenced in a prompt by typing a forward slash
- Copilot is available in Word, Outlook, Excel, Teams, Edge and at m365copilot.com
- Prompts can be saved and scheduled to run on a recurrence
- https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy
- https://support.microsoft.com/en-us/copilot-m365