Copilot for Executives — The Field Guide
↗ written for executives — the ones who don't have time for a 90-minute course but need to model it for their org.
On this page
Microsoft 365 Copilot for executives is a different conversation to Copilot for everyone else. The use cases are different. The stakes are different. The accountability when it goes wrong is different. So while the prompting fundamentals carry across, the way you reach for it as a leader needs its own framing.
This is that framing. It’s what I’d say if I had 45 minutes with you and one whiteboard.
If you’re a people leader (manager of a team), there’s a companion piece for you: the Copilot for People Leaders Field Guide — same framework, calibrated for 1:1s, team meetings, performance check-ins, hiring, coaching, recognition.
📚 Three posts on M365 Copilot prompting — pick where you are:
- 🌱 Field Guide — start here if you’re new. Four-block framework, per-app prompts, the mistakes everyone makes.
- 🧑💼 Persona Playbook — your direct reports’ role-specific worked prompts.
- 🎯 Executive Field Guide (you’re reading this) — for leaders. Board prep, leadership comms, decision support, trust and governance.
🏃 TL;DR — if you have 60 seconds
Three reasons to keep reading:
- Prep for board / ELT meetings faster — 90-second briefings, devil’s-advocate stress-tests, Notebooks for board cycles.
- Stress-test decisions without outsourcing judgement — three prompt patterns, executive-grade governance, the hard line throughout.
- Improve high-stakes communications — town halls, regulator letters, customer escalations — your voice intact, your draft 20 minutes closer to send-ready.
The hard line: Copilot drafts. You decide. If you take nothing else from this post, take that.
What’s in here: 7 use-case clusters · 16 features called out individually (including Cowork) · 10 C-suite role playbooks · 20 named scenarios · 60+ ready-to-paste prompts · first-90-days starter · 30-day rhythm.
Skim path for 5 minutes: Plain language → Hard line → Your role playbook → bookmark the scenario library and prompt library.
People leader instead of executive? See the Copilot for People Leaders Field Guide.
Three paths in — pick yours:
⏱ 5-min skim — you want the gist + the hard line + your role’s biggest win. → Plain language → Hard line → Your C-suite role playbook → bookmark, come back.
📚 20-min walk-through — you want to install the patterns, not just hear about them. → Read end-to-end in order. 7 use-case clusters → 16 features → 10 C-suite role playbooks → 20 named scenarios → 60+ prompts → 30-day rhythm. About 20 minutes; install one habit per week.
🗂 Reference — come back when you need a specific thing
- Features: Copilot Chat · Outlook · Teams · Word · Excel · PowerPoint · Researcher · Analyst · Cowork · Notebooks · Pages · Search · Memory · Custom agents · Scheduled prompts · Sensitivity labels
- C-suite playbooks: CEO · CFO · COO · CIO/CTO · CHRO · CMO · CISO · CSO/CRO · Board · Chief of Staff / EA · You’re also a people leader
- Use-case clusters: 1 Strategy · 2 Comms · 3 Time & Meetings · 4 Notebooks · 5 Researcher/Analyst · 6 Search · 7 Cowork
- Scenarios + prompts: 20 exec scenarios · 60+ prompt library · Three prompt patterns
- Governance: Trust essentials · Trust deep · What to model · Failure patterns
- Onboarding: First 90 days · 30-day rhythm · Where to next · FAQ
👥 Who this is for
Executive leaders — CEO, CFO, COO, CIO, CTO, CHRO, CMO, CISO, CSO, board members, ELT members. The lead examples in each use-case cluster are written with your work in mind. The 10 C-suite role playbooks speak directly to each seat at the table. The 20 named executive scenarios cover board prep, regulator response, M&A pre-screen, town halls, crisis comms, and the rest.
If you’re a people leader (manager of a team, team lead, head of department, frontline manager): the Copilot for People Leaders Field Guide is the companion piece for you — same framework, calibrated for 1:1s, team meetings, performance check-ins, hiring, coaching, recognition.
🖨 Save this for later — print or PDF. Browser → File → Print → “Save as PDF” gives you a clean, print-ready version (nav and footer stripped). Bookmark it, mark it up, or carry it into your next leadership offsite. Page breaks are tuned for headings — no orphaned section titles at the bottom of a page.
Why Copilot matters for executives now
There’s a version of this conversation where I’d start by quoting analyst stats on productivity gains. I’m not going to. The data is real, but it’s not what changes minds in a board room. What changes minds is this:
Four things compound for executives that don’t compound the same way for individual contributors:
1. Drafting cost has collapsed. Every executive I know spends a meaningful portion of their week producing first drafts — board commentary, leadership messages, stakeholder follow-ups, talking points. The marginal cost of a first draft is now close to zero. The marginal cost of getting from a first draft to a finished piece of work is still your judgement, but the staircase you’re climbing starts on the fifth floor, not the ground. Microsoft’s own enterprise-wide deployment (covering 300,000+ employees and external staff per the public InsideTrack documentation) describes drafting and synthesis work as the most-cited productivity gain across roles. Published case material from early CFO adopters has reported meaningfully shortened monthly reporting cycles — sometimes by an hour or more — though precise gains vary by team and starting baseline.
2. Synthesis across sources is now ambient. A typical executive day touches twenty to forty different sources of information — emails, meetings, board papers, financials, customer notes, market updates. Microsoft’s executive enablement material puts typical executive inbox volume at 400+ emails per day. Until 2024, synthesising those was either done badly (in your head, between meetings) or expensively (delegated to a chief of staff). Copilot makes lightweight synthesis a few-second prompt away. It doesn’t replace your chief of staff. It makes the ones you haven’t yet hired less essential.
3. The strategic edge shifts from “what you know” to “what you ask”. Executives have always been judged on the quality of their questions. What’s changed is that the cost of getting an answer to a sharp question is now measured in seconds, not days. The executives who win this transition are the ones who get faster at asking better questions, not the ones who get faster at memorising more things.
4. Visible executive sponsorship is the single largest adoption multiplier. Published Microsoft case studies (including Insight Enterprises) report very high adoption rates — driven not by training spend but by the intensity of executive sponsorship. Where the executive team uses Copilot visibly and talks about it, adoption compounds. Where the executive team is silent, adoption flat-lines regardless of investment.
💡 Tip — If you do nothing else after reading this post, install one habit: every time you’re about to ask a colleague to “look into X for the board”, ask Copilot first. Then ask your colleague to validate. You’ll find roughly half of your “look into” requests resolve in 90 seconds.
Copilot in plain language for leaders
You don’t need the full architecture diagram to use this effectively. You do need three things straight in your head.
What it is
Microsoft 365 Copilot is an AI assistant that sits across the Microsoft 365 apps you already use — Outlook, Word, Excel, PowerPoint, Teams, OneNote, SharePoint, and the standalone Copilot Chat surface at microsoft365.com/chat. It reads from and writes into the files, emails, meetings, and chats that you already have access to. It does not — and cannot — see anything you don’t already have permission to see.
What it does
Three categories cover 95% of how an executive will use it:
- It drafts. Emails, summaries, board commentary, leadership messages, briefing notes.
- It analyses. Documents you upload or reference, spreadsheets, meeting transcripts, sets of files.
- It retrieves. Across your email, files, meetings, and SharePoint — like a single search box for your work.
What it does NOT do (read this twice)
- It does not have your job context outside the M365 tenant. It doesn’t know about your strategy unless you’ve put your strategy into M365 in a form it can read.
- It does not make decisions for you. Every output is a draft for your judgement.
- Memory features can save preferences across sessions, but behaviour varies by tenant configuration and user controls. Don’t assume continuity; review what’s actually saved.
- It does not learn from your individual prompts to improve its own model. Your prompts stay in your tenant.
⚠️ Heads up — The biggest source of executive disappointment in the first month is unspoken expectation. Executives assume Copilot knows the company’s strategy, the org chart, the political dynamics, and the recent context — because they would. It doesn’t. The fix is to ground it explicitly with the documents and context it needs. Once you’ve installed that habit, the perception flips.
Where your data goes
This is the question every CIO will brief you on, but it’s worth being able to explain it in your own words.
When you type a prompt into Microsoft 365 Copilot, three things happen:
- The prompt and any grounded data (files referenced, meetings cited, emails attached) are sent to the AI model.
- The model produces a response, which is returned to you.
- The prompt and response are stored in your tenant’s compliance log (accessible to your IT and compliance teams under standard governance, not casually browsed).
Microsoft does not use enterprise Copilot prompts to train its public AI models. The conversation stays inside your tenant boundary.
This is fundamentally different to consumer chat tools (free ChatGPT, Claude.ai, Gemini consumer). Those tools have different terms, different data flows, and should never be used with company information. The five-second test: if you wouldn’t email it externally, don’t paste it into a consumer AI tool.
For deeper governance reading, see the SharePoint oversharing controls guide and the content safety controls guide — both more technical, but useful as a foundation for the conversations you’ll have with your CIO.
The hard line — what Copilot must NOT do
Before we get into use cases, the hard line. This is the thing I cover first in every executive session.
Copilot drafts. You decide.That’s it. That’s the whole rule.
Concretely, that means Copilot must not be the basis (or the sole basis) for:
- A hiring, performance, promotion, or termination decision about an individual.
- A lending, credit, or insurance decision about a customer.
- A financial commitment to the board, regulator, or market.
- A safety decision in an operational context.
- Any decision a regulator would want to see human reasoning behind.
This is not a soft preference. In most jurisdictions, it’s a hardening regulatory expectation. In all jurisdictions, it’s basic professional accountability. The reason it sits at the top of the field guide and not buried in the governance section is that the temptation to outsource judgement only grows the more useful Copilot becomes. Install the rule early. Lead with it visibly. Hold yourself to it.
💡 Tip — A useful prompt-rewriting habit: every time you catch yourself typing “should we…”, rewrite it as “compare for me…” or “what are the trade-offs of…”. The first asks Copilot to decide. The second asks Copilot to structure your thinking so that you can decide. Same task, completely different relationship.
1 · Strategy & Decision Support
The category executives reach for first, and the category where Copilot’s value compounds fastest.
What “good” looks like here
The strongest pattern: using Copilot to stress-test your own thinking, not to do your thinking for you. Three sub-patterns are doing most of the heavy lifting for the executives I coach:
1. Board paper brief-down. Take a 40-page board pack. Drop it into Copilot Chat. Ask for a 90-second briefing structured around bottom line, options, risks, decisions required. Read the brief on the way to the meeting. Use the original paper for any item that needs deeper attention. Reclaim two hours.
2. Devil’s advocate. Take any recommendation — yours or your team’s — and ask Copilot to build the strongest possible counter-case using only the source material. The output is rarely an actual change of mind. The output is usually a sharpening of your reasoning before you walk into the room.
3. Options comparison. When you’re choosing between three or four genuine alternatives, ask Copilot to lay out the trade-offs in a structured table. Force structure. Force trade-offs. The output is the start of your decision conversation, not the end of it.
Worked example — board paper brief-down
Prompt:
Summarise this board paper into a 90-second briefing for the CEO who hasn’t read it yet. Use four sections: (1) bottom line in one sentence, (2) the three options on the table with one-line trade-offs each, (3) the top 3 risks I should be alert to, (4) the specific decisions I’m being asked to make.
Why this prompt works: It tells Copilot the audience (CEO who hasn’t read it), the time budget (90 seconds), the structure (four numbered sections), and the format of each section. It also strips the editorial preference (briefing, not summary) so you don’t get a generic regurgitation.
Worked example — devil’s advocate
After the brief above lands, follow up:
Now play devil’s advocate. Make the strongest possible case for Option C using only what’s in this paper. Be specific.
This is the prompt that earns the most “oh, that’s clever” reactions in executive demos. It’s also the most under-used. Most people stop at the first prompt. The compounding value is in the second.
Worked example — options comparison
For a decision-mode prompt that keeps you in the driver’s seat:
Compare Options A, B, and C from the attached strategy paper across four dimensions: short-term EBITDA impact, medium-term optionality, organisational disruption, and signalling effect to the market. Use a table. Don’t recommend — I’ll decide.
Notice the last clause: “Don’t recommend — I’ll decide.” It’s worth saying out loud. Copilot is trained to be helpful, and helpful sometimes means recommending. When you want pure structure for your judgement, ask for pure structure.
💡 Tip — For the most-prepared 5% of the executives I work with, Strategy & Decision Support is the cluster they automate first — typically by saving 3-5 of these prompts as templates they re-use weekly. The Prompt Gallery inside Copilot Chat is the right place to store them.
2 · Leadership Communication
The category where Copilot looks the most obvious from the outside (“oh, it writes your emails”) and where the actual value is the least obvious until you’ve used it for a month.
What “good” looks like here
The trap is treating Copilot as a writer. It’s not. Copilot is a refiner. Your voice still has to come from you. What changes is the cost of iteration — going from version 1 to version 4 of an exec message used to be an hour of staring at a screen. Now it’s two minutes.
Three sub-patterns dominate:
1. Acknowledgement before action. When something has gone wrong — a results miss, a public criticism, a team setback — the hardest part of the comms is the first sentence. Use Copilot to draft three different opening paragraphs that acknowledge without being defensive. Pick the one closest to your voice. Edit. Send.
2. Tone calibration. Same content, three different audiences (board, exec team, all-staff). Same message, three different tones (direct, warm, urgent). Copilot makes the variations cheap; you keep the editorial judgement.
3. Pre-meeting talking points. Before any high-stakes meeting — board, regulator, major customer, senior all-hands — paste the agenda into Copilot, attach the relevant context documents, and ask for talking points structured around your three intended outcomes. Edit ruthlessly. Carry into the meeting.
Worked example — town hall refinement
You’ve got a rough draft of a monthly all-hands message. It’s too long, too buzz-wordy, and doesn’t acknowledge the quarter’s softness. The prompt:
Refine this town hall message for an audience of 600 staff. Specifically: (1) cut to under 200 words, (2) replace every buzzword (“doubling down”, “crushing it”, “leverage”) with plain English, (3) add a one-sentence acknowledgement of the [recent issue] without being defensive, (4) end with a single specific ask of staff for this month, (5) keep the warmth but lose the corporate tone.
The five numbered requirements aren’t bureaucratic — they’re surgical. Each one closes off a way the output could go wrong. Vague prompts produce vague refinements. Specific prompts produce specific refinements.
Worked example — tone calibration
Take the message above. Give me a second version in the same structure, but pitched slightly more direct — the kind of tone a CEO would use when they want their leadership team to read it and act, not just feel acknowledged.
You now have two versions. You pick. You edit. Your voice is intact. The iteration cost has collapsed.
Worked example — board chair reply
The hardest emails to start are the ones where the stakes are high and the relationship dynamics matter. A board chair has sent you a pre-read with three sharp questions and a closing line about trust. The temptation is to draft six times. The pragmatic move:
Draft a reply to this email from the Board Chair. Direct, candid, no defensiveness, no excuses. For her first question, acknowledge this is the first surfacing of the revised number, explain the two drivers honestly, and propose a process for surfacing similar timeline changes earlier. For her second question, admit it wasn’t included, commit to a Tuesday delivery. For her trading update concern, agree and commit to a revised paragraph two by Tuesday close of business. End with a short note acknowledging the trust point she raised in her closing paragraph. Three or four short paragraphs total. Warm but plainspoken.
The output is rarely send-ready. It is reliably 20 minutes closer to send-ready than a blank page. That’s the win.
⚠️ Heads up — Resist the urge to send Copilot’s first output unedited, ever. Not because it’s bad — but because the discipline of editing every output keeps your editorial voice strong. Lose the editing discipline and your messages start sounding like Copilot. Your team will notice within a fortnight.
3 · Time & Meetings
The category where the biggest behavioural shift happens, often without the executive noticing.
What “good” looks like here
Three sub-patterns:
1. Recap any meeting in 60 seconds. Recorded Teams meetings now produce structured recaps automatically. The shift is using them — not just letting them sit. Read the recap before you read the chat thread. Pull actions from it. Time saved per week: typically 90 minutes.
2. Prep for any meeting in 5 minutes. Before any meeting on your calendar, ask Copilot: “what do I need to know for this meeting?” It pulls the recent emails, prior meetings, files attached, and recent chats with attendees. You walk in calibrated, not cold.
3. Catch up on a meeting you couldn’t attend. Joined late, missed entirely, or only listened to half. Copilot turns the recording into “what was decided, what was disputed, what was unresolved, what was unsaid” in seconds.
Worked example — board meeting recap
Inside the Teams meeting recap (or pasting a transcript into Copilot Chat):
Summarise this meeting into four sections: (1) decisions made and by whom, (2) actions assigned with owner and due date, (3) outstanding questions for next meeting, (4) tone observations — anything in the language that suggests under-the-surface tension I should be alert to.
The fourth section is the executive-specific addition. Operational meeting recaps stop at decisions and actions. Executive meeting recaps benefit from the unsaid signal — who was quiet, where the tension surfaced, which language was sharper than the words alone.
Worked example — meeting prep
The day before a quarterly business review:
I have a quarterly business review with [Division X] tomorrow morning. Pull together: (1) the last three months of significant emails from that team, (2) any major files they’ve shared with me, (3) anything from our last QBR meeting that was left as unresolved, (4) any commitments I made to them I should be tracking. Structured as a one-page brief.
The output is rarely complete the first time. The second prompt — “what’s missing” — usually fills the gaps. Two iterations, one page of prep, ten minutes total. The QBR itself runs differently when you walk in calibrated.
💡 Tip — The single highest-ROI prompt in Time & Meetings is one most executives never try: “What’s likely to come up in this meeting that I haven’t been thinking about?” It surfaces a thread from a recent email, a customer escalation, a competitor move. Make it a Monday morning prompt for your toughest meeting of the week.
4 · Notebooks for Board Prep
The most under-known executive feature in Microsoft 365 Copilot. If you’re new to Notebooks, this section will be the most useful one in this guide.
What a Notebook actually is
A Notebook in Microsoft 365 Copilot Chat is a workspace where you’ve grounded a set of files (and optionally links, pages, and other sources). Every prompt you make inside that Notebook is grounded against those sources by default. Notebooks persist — you can come back to one next week and pick up where you left off.
For executives, the prototypical Notebook is “Board Prep — [Month]”. The sources are: the latest board paper, the financials, the risk register, the competitor watch, recent material correspondence, last month’s board minutes. Every prompt is grounded against that working set. The grounded set goes away when you close the Notebook out at the end of the cycle.
Why this matters at the executive level
Without Notebooks, the way most people use Copilot is: paste file, ask question, get answer, repeat. The friction is constant, the grounding is one-shot, and the cognitive overhead of “which file was that in” doesn’t go away.
With Notebooks, you set up the working surface once, then think against it. The grounded set is the same for every prompt. Cross-file questions become trivial. The cognitive load drops.
Worked example — cross-file board prep
Inside a Notebook with the board paper, risk register, financials, and competitor watch loaded:
Across all the files in this notebook, which of our Top 15 risks are most reinforced by what we’re seeing in competitor activity and Q1 financials? Give me three risks ranked by combined evidence, and for each one, quote the specific lines from each source that supports the ranking.
The output should cite specific lines from specific files. The discipline of asking for quoted evidence keeps Copilot honest and gives you a fast read of which risks are now genuinely board-conversation-worthy.
Worked example — pattern hunting
Looking across the board paper, the risk register, and the competitor watch, what story is being told that we haven’t yet explicitly named? Be specific — name the pattern and quote the supporting evidence.
This is one of those prompts that occasionally produces a “huh, I hadn’t put those together” insight. It also occasionally produces nothing useful — Copilot is not infallible at pattern recognition. The two-minute cost makes it worth trying anyway.
Worked example — closing the loop
At the end of a board prep cycle:
Summarise everything I should retain from this notebook for next quarter’s board prep. What questions did the board ask this cycle that I should pre-empt next cycle? What did we promise to come back on?
Closing-the-loop prompts are how Notebooks compound across cycles. The first cycle, the prompt produces a short list. By the third cycle, the prompt produces a working memory of how your board engages — which questions recur, which commitments outlast which board members, which themes need refreshing.
⚠️ Heads up — Notebooks are not a permanent archive. Close them out at end of cycle (delete or rename), and start a fresh one for the next cycle. The cognitive value is in keeping the working surface clean, not in accumulating an ever-growing pile of “everything I’ve ever worked on”.
5 · Researcher and Analyst — agentic depth on demand
The two standalone agents that are the biggest “thinking partner” unlock for executives in 2026. (Note: these are not Cowork — Cowork is a separate agent that does autonomous multi-app work. See cluster 7 below and the Cowork guide.)
Researcher — the executive’s research analyst
Researcher is a deep-research agent inside Microsoft 365 Copilot. You give it a structured research brief, it goes away for 5-15 minutes and produces a sourced briefing.
For executives, the most useful pattern is pre-board market scans. Before each board meeting, kick off a Researcher task on the state of your sector. Specify the time window, the segments, the questions you want answered. Come back to a structured briefing with citations.
Worked example:
Research the state of the New Zealand logistics sector over the past 6 months. Focus on: (1) major customer wins and losses by the top 5 national operators, (2) any acquisitions, divestments, or trading updates, (3) any moves into AI-enabled service offerings, (4) any regulatory changes or competition commission activity. Give me a 1-page briefing structured for a board pre-read. Cite all sources. Flag anything you’re not confident about.
The output is not a replacement for your Head of Strategy. It’s a co-worker for her — she validates and supplements, rather than doing the gathering work herself.
Analyst — the executive’s scenario modeller
Analyst is a data-analysis agent. You give it a question and a data source. It models the answer, shows its workings, and lets you iterate.
For executives, the most useful pattern is scenario modelling on financial data without queuing for an analyst. Quick what-if questions that used to take a day now take ten minutes — and the workings are visible, so you can hand the output to your CFO for audit.
Worked example:
Using the Group P&L data in the attached financials, model three full-year scenarios using the assumptions on the Scenario sheet: Base, Downside, Upside. For each, show modelled Revenue, Gross Profit, Opex, EBITDA, and EBITDA Margin. Then tell me which scenario breaches our 14% EBITDA covenant floor. Show your workings.
The output is reproducible. The CFO can audit it. You can argue with it. That last point is the most important — Analyst is the cluster where Copilot stops being a writing assistant and becomes something closer to a thinking partner.
💡 Tip — Researcher and Analyst take longer than chat (5-15 minutes vs. seconds). The mental model is different — kick one off, switch to another task, come back to the output. Treat them like email-a-junior-analyst, not like ask-a-chat-window. (Cowork is different again — it does multi-app work autonomously, not single-task deep work. See cluster 7 below.)
6 · Search across M365
The least-flashy executive use case, and possibly the most economically valuable for organisations with sprawled content estates.
What it is
Microsoft 365 Copilot Chat doubles as a permission-aware search box across your email, files, meetings, SharePoint sites, and Teams chats. Anything you have permission to see, Copilot can find and summarise.
Why this matters at the executive level
Executives spend more time than they admit hunting for a document. The most recent draft of a strategy paper, the policy you remember someone circulating last year, the customer email that referenced the contract clause. Copilot turns those hunts into 30-second tasks — with the file or message cited so you can open the source.
Worked example — find and summarise
Find me the latest version of our AI Use Policy. Give me a one-page summary specifically for the executive team: what each accountable function owns, what the leader themselves is responsible for modelling, and what escalation path applies if there’s a suspected breach.
The output should cite the file (with a path you can click) and produce a manager-focused summary that’s different from a generic summary. The framing of who the summary is for is doing most of the work.
Worked example — the critique pattern
Once you have the file:
What does this policy NOT cover that a CEO would expect it to cover? Be specific. Reference the document.
The critique pattern works particularly well on internal policies, strategy documents, and exec papers — documents written by smart people, where the gaps are subtle and worth surfacing.
⚠️ Heads up — Permission-aware search is exactly that — permission-aware. If a document is over-shared on SharePoint, Copilot will surface it to anyone who can technically access it, even if the original author intended a narrower audience. Combined with Notebooks and Cross-File reasoning, over-sharing becomes more discoverable. The SharePoint oversharing controls guide is required reading for any executive responsible for information governance.
7 · Cowork — autonomous multi-app work (Frontier / early-access)
Cowork is the third wave of Copilot — Assistant (2023) → Agent Builder (2025) → Cowork (2026). Where Copilot Chat answers a question and Researcher/Analyst do deep single-task work, Cowork takes an outcome you describe and executes a multi-step plan across your M365 suite, with human-in-the-loop checkpoints at sensitive moments. It is a separate agent, not a label for Researcher and Analyst.
At executive level, three patterns dominate: morning routines (the 20-minute inbox + calendar + Teams scan compressed to 60 seconds), customer / stakeholder preparation (Cowork pulls all threads on a customer across email, Teams, SharePoint and drafts the briefing + confirmation email), and cross-app deliverable creation (email brief → materials gathered → fresh research → deck built → reply drafted, from one prompt). The hard line still holds — checkpoints exist because the editorial judgement that protects your reputation lives there. Cowork requires Frontier tenant enrolment + Anthropic enabled as a subprocessor; if you can’t see it in your Agent Store, that’s a CIO conversation, not a problem to debug.
Read further: Sush’s Microsoft Copilot Cowork — Plain-English Guide is the definitive walkthrough — six high-impact prompts ready to try, the agentic harness explained, worked examples for meeting prep autopilot + weekly executive updates, when NOT to reach for Cowork, and the Frontier enrolment specifics.
Each Copilot feature, called out individually
The clusters above are the why. This section is the what — the actual surfaces inside Microsoft 365 Copilot, one at a time, with what each one is genuinely good at for executives, what to use it for, and where the limits are.
Read the ones relevant to you. Skim the rest. The order roughly follows the frequency that executives actually reach for each feature in their first 90 days.
⚠️ Before you try this — feature availability varies. Not every feature below will be available to every executive immediately. Memory · Scheduled prompts · Researcher · Analyst · Cowork · Notebooks · Teams transcripts · Custom agents (Copilot Studio) all depend on your licensing tier, your admin’s tenant policy, your region’s rollout schedule, and (in some cases) optional connected-experiences settings being enabled. Cowork specifically requires Frontier program enrolment and Anthropic enabled as a subprocessor — that one is the most common reason it’s not visible in NZ tenants yet. If a feature isn’t there for you, ask your IT/CIO contact — it’s usually a configuration question, not a capability gap.
Copilot Chat — the hub
What it is: The general-purpose chat surface at microsoft365.com/chat (or the Copilot icon in the M365 app launcher, or the standalone Copilot app on Windows). The biggest single surface area inside the entire Copilot product.
Why it matters for executives: This is where most of your strategic Copilot work will happen. Multi-source reasoning, document grounding, cross-app questions, the launching pad for Researcher and Analyst, and the home of every prompt that doesn’t sit naturally inside a specific app.
Three patterns that compound for executives:
Always-on grounding via /file or attach. When asking anything about specific content, attach the file or use the slash-command to ground the prompt. Untethered prompts produce untethered answers.
Cross-source comparison. “Compare /Q1 strategy with /board minutes from March — where are we on the commitments we made?” That kind of question used to take a chief of staff a morning. Copilot Chat lands it in 30 seconds.
The follow-up habit. Most executives end conversations after the first response. The strategic value is in the second and third prompt — “make the opposite case”, “what’s missing”, “play devil’s advocate”. The first prompt gets you the brief. The second prompt sharpens your thinking.
Worked example — multi-source briefing:
Pull from /June board paper, /May P&L, and /competitor watch May 2026 — give me a one-page strategic brief on where we’re vulnerable to the predictive logistics threat. Be specific about which competitor, which customers are most exposed, and which of our planned actions reduces or doesn’t reduce that vulnerability.
Limit: Copilot Chat is generalist. For deep data work, hand off to Analyst. For deep research, hand off to Researcher. Don’t try to do everything in chat.
Outlook + Copilot — the inbox surface
What it is: Copilot inside the Outlook web and desktop apps. Three primary modes — Draft, Coach, and Summarise.
Why it matters for executives: Microsoft’s executive enablement material puts typical executive inbox volume at 400+ emails per day — and your day starts with that pile every morning. Outlook + Copilot doesn’t reduce the pile. It changes how fast the pile becomes structured signal.
Five patterns that earn their keep:
Daily triage in 5 minutes. Open Copilot Chat (not in-Outlook — use the broader Chat for this), then:
Triage everything in my inbox from the last 24 hours. Show me only the 6-10 things that actually need a decision or action from me before noon. For each one, show: who, subject, what they need from me, and the deadline. Use a table. Don’t include anything I’ve been cc’d on for awareness only.
This single prompt replaces 20-30 minutes of morning inbox scrolling.
Drafting high-stakes replies. When the email matters and you don’t have time to start from scratch — the board chair email, the customer escalation, the regulator’s preliminary question. Copilot starts you 20 minutes closer to send-ready. You still own the editorial pass.
Tone calibration. Same content, three audiences (board, exec team, all-staff). Same content, three tones (direct, warm, urgent). The variations are cheap; the editorial judgement stays human.
Summarise long threads. A 40-message email thread distils to “decisions made, actions assigned, who’s frustrated with whom” in seconds. Particularly useful for the threads that exploded while you were in back-to-back meetings.
Coach mode. Before sending a draft, ask Copilot’s Coach: “any tone risks here? Anywhere I’m being defensive or evasive without realising it?” Coach is the under-used Outlook feature. It’s an editing pair that’s never tired.
Worked example — the chair email:
For the kind of email that previously triggered six rewrites and 40 minutes of staring at a blank reply:
Draft a reply to this email from the Board Chair. Direct, candid, no defensiveness, no excuses. For her first question on the Energy retail platform payback — acknowledge this is the first formal surfacing of the revised number, explain the two drivers honestly (CAC running hot, two delivery milestones added), and propose a process for surfacing similar timeline changes earlier. For her second question on the Logistics retender probability — admit it wasn’t included, commit to a Tuesday delivery. For her trading update concern — agree, commit to a revised paragraph two by Tuesday close of business. End with a short note acknowledging the trust point she raised in her closing paragraph. Three or four short paragraphs total. Warm but plainspoken.
The first draft is rarely send-ready. It is reliably 20 minutes closer to send-ready than a blank reply box.
Limit: Copilot won’t replace your judgement on relationships. The email is relationship work. Use the time you save to read the original more carefully, not less.
Teams meetings + Copilot — the meeting surface
What it is: Copilot inside Microsoft Teams meetings — covers live in-meeting prompting, the post-meeting recap, transcript-based summarisation, and the Intelligent Recap pane.
Why it matters for executives: Executive calendars are denser than anyone else’s calendar. Microsoft’s published Customer Zero adoption findings consistently show meeting-related use as a top driver of perceived Copilot productivity gain — partly because it’s where the time waste was largest pre-Copilot.
Five patterns:
Pre-meeting brief in 5 minutes. Before any meeting on your calendar — particularly the ones with people you don’t know well or topics you haven’t recently touched — ask Copilot:
I have a meeting in 45 minutes with [name] about [topic]. Pull the recent emails, last meeting notes, files we’ve shared, and any project updates. Give me a one-page brief structured as: who’s coming · what we last left unresolved · what they’re likely to ask me · what I should be prepared to commit to. Plain English.
Recap any meeting in 60 seconds. Recorded Teams meetings now produce structured recaps automatically. The shift is using them — not just letting them sit. Read the recap before you read the chat thread. Pull actions from it. Time saved per week is typically 90 minutes for an executive.
Catch up on a meeting you couldn’t attend. Joined late, missed entirely, or only listened to half. Copilot Chat with the meeting attached as source turns the recording into “what was decided, what was disputed, what was unresolved, what was unsaid” in seconds.
In-meeting Copilot. During the meeting itself, the in-meeting Copilot panel can answer “what have we agreed so far?” or “what did [person] say earlier?” without breaking flow. Useful for back-half meetings where you’ve lost the thread.
The tone observations prompt. This is the executive-specific addition. After any leadership meeting:
Summarise this meeting into: (1) decisions and who carried them, (2) actions assigned with owner and due date, (3) outstanding questions. Then add a fourth section — “tone observations” — anything in the language that suggests under-the-surface tension I should be alert to. Quote the specific lines.
The fourth section is the one that earns the most “huh, I missed that” reactions when an executive first runs it.
Limit: Copilot doesn’t pick up body language, side conversations in the room, or anything someone deliberately didn’t say. It analyses the spoken content. Your in-person read is still essential.
Word + Copilot — the long-form surface
What it is: Copilot inside Microsoft Word — drafting, refining, summarising, restructuring, and the side-by-side Copilot pane.
Why it matters for executives: Executive output skews to Word more than any other app — board papers, strategy memos, customer letters, formal communications, regulator responses. Anywhere the editorial standard is high, Word + Copilot earns its keep.
Four patterns:
Refine, don’t rewrite. Treat Copilot as a refiner of your voice. Give it specific, numbered changes. Vague “improve this” prompts produce vague improvements. Surgical prompts produce surgical changes.
Restructure long documents. When a draft has the right content but the wrong shape:
Restructure this document. The current order doesn’t work for the audience (the board). Move the recommendation to the front, push the analysis behind it, keep the appendices where they are. Tighten any section that runs over 200 words. Preserve every factual claim — don’t add or remove substance.
The board-paper polish prompt. For any document that goes to a board, regulator, or senior audience:
Read this document as if you were the most cynical reader at the board table. Where is the language soft when it should be direct? Where am I claiming success when the evidence is mixed? Where is a hedge masking a real risk? Quote the specific phrases.
Compare versions. Two drafts of the same memo:
Compare these two versions of the strategy memo. What’s better in version A? What’s better in version B? Recommend which structural elements to keep from each.
Limit: Word + Copilot doesn’t know your house style or your unwritten conventions. If your organisation has a Style Guide, paste it in or upload it as a reference each time. Otherwise Copilot will default to generic professional writing.
Excel + Copilot — the numbers surface
What it is: Copilot inside Microsoft Excel — formula assistance, analysis, commentary, chart suggestion, pattern detection.
Why it matters for executives: Most executives are not the people writing Excel formulas. They’re the people reading Excel outputs. Excel + Copilot does the bridging — turning numbers into narrative without a finance analyst in the loop.
Four patterns:
Variance commentary. Numbers turn into board-ready language. Synozur’s Copilot Navigator cites one early CFO adopter who cut a 3-hour reporting cycle to 30 minutes using this pattern.
Analyse this Group P&L sheet. Write variance commentary I can read at the board: the top 5 variances larger than 5% ranked by absolute dollar impact, the most likely business story behind each, and which variances most threaten our forecast. Use the data only — flag anywhere you’re inferring. Plain English. No accounting jargon.
Pattern detection. Ask Copilot to find what you’d miss:
Look across the entire monthly P&L for the past 12 months. What patterns am I missing? Be specific — name three patterns and quote the lines that support each.
Quick scenario calculations. For executive what-ifs that don’t need the full Analyst agent:
If our gross margin compresses by another 1 percentage point in Q3 and Q4, what’s the EBITDA impact, and how much would we need to cut Opex to hold EBITDA flat? Show your working.
Translation for the non-finance audience. When you need to brief a non-finance leadership colleague:
Take this finance dashboard. Translate it for a head of operations who’s brilliant but not finance-trained. Use plain English. Show the three things that should genuinely worry them and the two things they shouldn’t worry about. Cite specific numbers.
Limit: Excel + Copilot is reliable on what’s in the cells. It’s less reliable when you ask it to infer the why behind the numbers — it’ll guess and sometimes guess wrong. Always cross-check the narrative against your own knowledge before using it in a board context.
Important: For genuine multi-scenario modelling with workings shown — the kind that the CFO will audit — use Analyst, not in-Excel Copilot. (See Analyst below.)
PowerPoint + Copilot — the deck surface
What it is: Copilot inside PowerPoint — slide creation, design suggestions, content restructuring, speaker note drafting.
Why it matters for executives: Executives consume more decks than they make. But for the decks you DO make — board updates, town hall material, customer-facing pitches — PowerPoint + Copilot accelerates the worst part of deck work: starting from a blank slide.
Three patterns:
Bullet-to-deck. Take a Word document or set of bullet points and ask Copilot to structure it as slides:
Turn this strategy memo into a 6-slide board update. One slide per section. Title each slide so it reads as a sentence — the audience should know the punchline from the title alone. Speaker notes for me on each slide.
Tighten an existing deck. Long decks that go to the board:
Review this 28-slide deck. Identify slides that are too dense, slides that duplicate each other, and slides that could be cut without losing substance. Suggest a tighter 18-slide version. Tell me which slides to move to an appendix.
Speaker notes for someone else’s deck. When a colleague has built the deck but you’re presenting it:
I’m presenting this deck on Thursday. Draft speaker notes for me — the things I should add verbally that aren’t on the slides. Focus on the why, not the what. The audience is our top-50 customer leadership team.
Limit: PowerPoint + Copilot is good at structure and content. It’s average at visual design — don’t expect it to make your deck visually beautiful. For high-stakes visual work, lean on a real designer.
Researcher — the agent that reads for you
What it is: Researcher is a deep-research agent inside Microsoft 365 Copilot. You give it a structured research brief; it goes away for 5–15 minutes and produces a sourced briefing with citations. It is not part of Cowork — it is its own agent, surfaced under Agents in Copilot Chat and pre-installed for M365 Copilot licensed users (subject to your tenant’s admin controls).
Why it matters for executives: This is the closest thing in M365 Copilot to having a junior strategy analyst on call. Researcher excels at the work executives most often delegate — pre-board market scans, competitor intelligence, sector trend snapshots, regulatory environment summaries.
Three patterns:
Pre-board market scan. Before each board meeting, kick off Researcher on the state of your sector:
Research the state of the New Zealand logistics sector over the past 6 months. Focus on: (1) major customer wins and losses by the top 5 national operators, (2) any acquisitions, divestments, or trading updates, (3) any moves into AI-enabled service offerings, (4) any regulatory changes or competition commission activity. Give me a 1-page briefing structured for a board pre-read. Cite all sources. Flag anything you’re not confident about.
Competitor deep dive. Before a customer pitch where the competitor’s offering matters:
Research [competitor name]’s position in the [sector] market. Their products, pricing model where public, customer wins announced in the last 12 months, leadership team, any reported customer satisfaction or service quality signals, and the most recent published financials or analyst notes if available. 2-page briefing. Cite all sources. Flag what I should NOT rely on without further verification.
Regulatory environment scan. For any executive working in a regulated industry:
Research the regulatory environment for [sector] in New Zealand. Focus on (1) any consultations or draft regulations from the relevant regulators in the past 12 months, (2) any enforcement actions, (3) any policy speeches by relevant ministers signalling forthcoming change, (4) cross-Tasman comparisons where Australian regulators have moved on similar matters. 1-page briefing structured for a board risk committee. Cite all sources.
Limit: Researcher’s coverage of paywalled content and private databases is limited. Don’t expect it to find the proprietary report your strategy consultancy wrote. Use it for the open-web part of the research, then ask your strategy team to fill the gaps.
Analyst — the agent that models for you
What it is: Analyst is a data-analysis agent inside Microsoft 365 Copilot. You give it a question and a data source; it models the answer, shows its workings, and lets you iterate. It is not part of Cowork — it is its own agent, surfaced under Agents in Copilot Chat and pre-installed for M365 Copilot licensed users (subject to your tenant’s admin controls).
Why it matters for executives: Analyst is where Copilot stops being a writing assistant and becomes something closer to a thinking partner. The outputs are reproducible, the workings are visible, the CFO can audit them. This is the cluster where the most under-known executive productivity unlock currently sits.
Four patterns:
Scenario modelling without queuing for an analyst. What-if questions that used to take a day now take 10 minutes:
Using the Group P&L data in the attached financials, model three full-year FY28 scenarios using the assumptions on the Scenario sheet: Base, Downside, Upside. For each scenario, show modelled Revenue, Gross Profit, Opex, EBITDA, and EBITDA Margin. Then tell me which scenario breaches our 14% EBITDA covenant floor. Show your workings.
Sensitivity analysis. When you want to know what matters most:
Now show me the single biggest sensitivity in the Downside scenario. If we could only protect ONE driver to keep us above the covenant, which would do the most? Show the workings.
Comparing two business cases. When two teams have submitted different views:
Two teams have submitted business cases for the same investment — see attached. Compare them across: NPV, payback period, key sensitivities, embedded assumptions. Surface where they fundamentally disagree on inputs, not just outputs. Don’t recommend — I’ll decide.
Trend explanation. When the numbers have moved and you want to know why:
Looking at our monthly NPS data over the last 18 months in the attached file. Find inflection points. For each inflection, propose 3 hypotheses about what might be causing it. Tell me which hypothesis is best supported by the data and what additional data we’d need to test the others.
Limit: Analyst is bounded by the quality of the data you give it. Garbage data produces confident-sounding garbage output. The most common failure mode is feeding Analyst a messy spreadsheet and trusting the output without sanity-checking the inputs.
Cowork — the autonomous multi-app agent (Frontier / early-access)
What it is: Microsoft’s third-wave Copilot agent (Assistant 2023 → Agent Builder 2025 → Cowork 2026). You describe an outcome, Cowork builds a multi-step plan across multiple apps (Outlook · Teams · Word · Excel · SharePoint · OneDrive), executes it autonomously over minutes or hours, and pauses at checkpoints for your approval before doing anything sensitive. You’ll find it in the Agent Store inside Copilot Chat. Available via the Microsoft Frontier program (early access — requires Anthropic enabled as a subprocessor at the tenant level).
Why it matters for executives: This is the agent that changes Copilot from “tool I open to draft something” to “colleague who takes ownership of a multi-step task” — the closest current product to “delegate to an AI staff member”, with the human-in-loop checkpoints that make it safe at executive stakes. “Copilot drafts, you decide” gets the most stress-tested here; the moments where Cowork pauses to ask “should I send this?” are the moments where your editorial judgement protects your reputation.
Read further: Sush’s Microsoft Copilot Cowork — Plain-English Guide covers the five highest-leverage Cowork patterns at executive level (morning triage · customer meeting prep · post-session follow-up · weekly executive update · customer deliverable from email brief), how Cowork actually feels different from regular Copilot, the limits to know, and the Frontier enrolment specifics.
Notebooks — the workspace that grounds everything
What it is: A workspace inside Copilot Chat where you’ve grounded a set of supported source files (Word, Excel, PowerPoint, PDF, Loop, OneNote pages, Copilot Pages). Every prompt you make inside that Notebook is grounded against those sources by default. Notebooks persist until you delete them — you can come back to one next week and pick up where you left off. Notebooks do not browse the general web — for that, hand off to Researcher or use Copilot Chat with web search enabled.
Why it matters for executives: This is the most under-known executive feature in Microsoft 365 Copilot. If you remember nothing else from this guide, set up one Notebook for your next board prep cycle. It will change how you work.
The prototypical executive Notebook is “Board Prep — [Month]” with these sources loaded:
- The latest board paper
- The financials pack
- The risk register
- The competitor watch
- Recent material correspondence (regulator letters, key customer threads)
- Last month’s board minutes
- Any matters arising from prior meetings
Every prompt you make inside that Notebook is grounded against this working set.
Five patterns:
Cross-file board prep questions. Inside the Notebook:
Across all files in this notebook, which of our Top 15 risks are most reinforced by what we’re seeing in competitor activity and Q1 financials? Give me three risks ranked by combined evidence, and for each one, quote the specific lines from each source that supports the ranking.
Pattern hunting. The prompt that occasionally produces “huh, I hadn’t put those together”:
Looking across the board paper, the risk register, and the competitor watch, what story is being told that we haven’t yet explicitly named? Be specific — name the pattern and quote the supporting evidence.
Pre-board sanity check. The night before:
Stress test this board paper. The Chair has flagged that she wants paragraph 2 of the trading update to be more direct. Re-read everything in the notebook and tell me where else my language is softer than the evidence warrants. Quote specific phrases.
Compound memory across cycles. At the end of each board prep cycle:
Summarise everything I should retain from this notebook for next quarter’s board prep. What questions did the board ask this cycle that I should pre-empt next cycle? What did we promise to come back on? Format as a forward-looking note to myself.
Onboarding a new exec. When a new ELT member joins:
Using everything in this Board Prep notebook, write a 2-page primer for a new ELT member on the strategic context, the current state of the business, and the open questions in front of the board. Plain English, candid, no jargon.
Best practice: Close out Notebooks at end of cycle. Start a fresh one for the next cycle. The cognitive value is in keeping the working surface clean, not in accumulating an ever-growing pile. Treat Notebooks like project folders, not archives.
Limit: Notebooks can ground against up to 300 files. When you add a shared location (a SharePoint site or a folder), Copilot selects up to 300 relevant files for grounding. Add the most important files directly rather than relying on relevance selection. If you find yourself wanting genuinely different working surfaces (board prep vs. quarterly planning vs. customer briefings), split them into separate Notebooks — the cognitive value is in keeping each surface focused.
Pages — the live canvas for shared thinking
What it is: Copilot Pages is a live, editable canvas where you and Copilot co-author together. The output of any Copilot Chat response can be sent to a Page, where you can edit, refine, and continue prompting against the live canvas. Pages can be shared with colleagues for collaboration.
Why it matters for executives: Pages takes care of the blank-page problem. It’s not a one-shot generator — it’s a canvas you shape live with Copilot as co-author. Particularly useful for strategy memos, exec offsite preparation, board update drafts, and any document where the iteration is the work.
Three patterns:
One-page strategy memo for the board. Inside a Page (started from a Notebook source for grounding):
Create a one-page strategy memo for the board on the Q1 FY27 strategic response. Sections: (1) Context — 2 sentences. (2) Problem — 3 bullets. (3) Options A / B / C — one short paragraph each. (4) Recommendation from the executive team with reasoning — 3 bullets. (5) Decision required — numbered list. Use the board paper, financials, risk register, and competitor watch in this notebook as source. Keep it under 400 words total. Plain English, no buzzwords.
Then edit the recommendation manually, then prompt in-Page:
Tighten the recommendation section using my edits as the new direction. Keep the reasoning bullets to 12 words each.
Co-authored exec offsite agenda. When the exec team needs to shape an offsite together:
- One leader starts a Page with a draft agenda
- Each ELT member edits live (Page collaboration like a Word document)
- Anyone can prompt the in-Page Copilot for refinements
- The final agenda lives in the Page; no one has to merge versions
Living strategy document. Pages can be longer-lived than meeting decks. The annual plan, the transformation roadmap, the AI adoption roadmap — Pages work better than Word for documents where the working surface needs to stay co-editable across a quarter.
Limit: Pages have less formatting control than Word. For the formal final-version document — the one that goes to board portal — drop the Page back into Word for final layout. Pages are for the doing; Word is for the publishing.
M365 Search via Copilot Chat — the universal find-anything
What it is: Copilot Chat doubles as a permission-aware search box across your email, files, meetings, SharePoint sites, and Teams chats. Anything you have permission to see, Copilot can find and summarise.
Why it matters for executives: Executives spend more time than they admit hunting for a document. The most recent draft of a strategy paper, the policy you remember someone circulating last year, the customer email that referenced a specific contract clause. M365 Search via Copilot Chat turns those hunts into 30-second tasks — with the file or message cited so you can open the source.
Four patterns:
Find and summarise.
Find me the latest version of our AI Use Policy. Give me a one-page summary specifically for the executive team: what each accountable function owns, what the leader themselves is responsible for modelling, and what escalation path applies if there’s a suspected breach.
Trace a thread. When you need to reconstruct a conversation across email and Teams:
Trace the conversation about the predictive logistics MVP across my emails, Teams chats, and meetings from the past 60 days. Show me the timeline of who proposed what, who pushed back, what was agreed, and what’s still open.
Find by description, not by filename. When you can’t remember what you called it:
Find me the document I created in February that had the competitive analysis for the Pacific Freight loss. I think it was a Word document. Quote the opening paragraph so I can confirm it’s the right one.
The critique pattern. Once you have any document:
What does this policy NOT cover that a CEO would expect it to cover? Be specific. Reference the document.
This pattern works especially well on internal policies, strategy documents, and exec papers — documents written by smart people, where the gaps are subtle and worth surfacing.
Limit: Permission-aware search is exactly that — permission-aware. If a document is over-shared on SharePoint, Copilot will surface it to anyone who can technically access it, even if the original author intended a narrower audience. Combined with Notebooks and Cross-File reasoning, over-sharing becomes more discoverable. The SharePoint oversharing controls guide is required reading for any executive responsible for information governance.
Memory — the under-known executive lever
What it is: Copilot Memory (in preview at the time of writing) can save preferences, facts, context, and inferred chat-history details across sessions. Memory entries are stored in your Exchange mailbox and are governed the same way other mailbox content is — your admins can review or remove memory via Microsoft Purview and Microsoft Graph. What gets saved depends on your tenant configuration, your admin controls, and (for explicit saves) your own confirmation.
Why it matters for executives: The re-priming tax is enormous for executives. Every time you start a new Copilot conversation, you give the same context — your role, your industry, your common preferences. Memory removes that. Once installed, your Copilot conversations start from “knows me” rather than “starts cold”.
Four memory entries worth installing in your first week:
Your role and context:
Remember: I’m the CEO of Kauri Pacific Group, a diversified NZ business with Health, Logistics, and Energy divisions. We operate primarily in NZ with limited Australian exposure. We’re an unlisted company with a strong governance board.
Your preference for tone:
Remember: I prefer plain English in all outputs. No corporate buzzwords (“leverage”, “doubling down”, “synergy”). Direct, even when uncomfortable. Avoid hedge words (“perhaps”, “it could be argued”). If you’re uncertain, say uncertain.
Your preferred format:
Remember: I prefer structured outputs — bullets, tables, numbered lists. Maximum 200 words per section unless I ask for depth. Always end with a section called “What would you double-check” so I know where to apply my judgement.
Your common counterparty list:
Remember: My most frequent counterparties are Margaret Chen (Board Chair), Priya Anand (Audit Chair), Ben Hartley (CFO), Mark Robinson (GM Logistics), Tom Walker (GM Energy), Helen Cho (GM Health). When I reference any of them by first name, use this context.
Once these four facts are installed, the typical executive prompt drops from 4 lines to 1 line of intent. The savings compound across hundreds of prompts a month.
Limit: Memory is not infinite. You can install dozens of facts but not hundreds. Prioritise the facts that re-occur in 80% of your prompts. Review memory monthly — delete anything you’ve stopped using.
Important governance note: Memory persists across sessions inside your tenant boundary. It is not shared across users, but it is not private from your IT and compliance teams — saved memories and related mailbox-backed content may be discoverable through Microsoft 365 compliance and eDiscovery tooling, and admin controls over Memory continue to evolve. Confirm current controls with your tenant admin. Treat memory the same way you treat any other email content — useful, governed, not secret.
Custom agents (Copilot Studio) — the most underused executive lever
What it is: Copilot Studio is the low-code platform where you can build custom agents — purpose-built versions of Copilot configured for a specific task, with their own knowledge sources, instructions, tools, and triggers.
Why it matters for executives: This is the layer most executives never reach. They use Copilot for the typing-tax reduction (drafting, summarising) but never get to the agent layer. Custom agents are where Copilot starts doing role-specific multi-step work that’s calibrated to your job, not a generic chat experience. For recurring automated rituals (the weekly briefing, the monthly summary), the right tool is usually a Scheduled prompt (see below) or, for genuinely multi-app autonomous workflows, Cowork. Custom agents are about role fit — Studio agents and Power Automate-backed agents extend Copilot for a specific job; the scheduling/automation layer is a separate concern.
Three executive agent patterns:
The Daily Briefing Agent (Monday morning). A scheduled agent that runs every Monday 06:00 and saves a 4-minute exec briefing to your Drafts:
- Sources: your inbox, your meeting recaps, your KPI dashboard, your competitor watch
- Structure: week ahead · last week’s changes · decisions waiting for you · outstanding commitments · “what I’d flag if I were your Chief of Staff”
- Trigger: scheduled (weekly Monday 06:00)
- Delivery: draft email to your inbox
The Pre-Customer-Meeting Agent. Triggered by a calendar event for any top-20 customer meeting:
- Sources: customer profile, last 12 months of correspondence, last 6 months of meetings, contract status
- Structure: customer context · what they’re likely to raise · open commitments · suggested talking points
- Trigger: 2 hours before any top-20 customer meeting
- Delivery: Teams chat to you
The Board-Prep Agent. Triggered manually 5 days before each board meeting:
- Sources: previous 3 board papers, all board commitments since last meeting, latest financials, latest risk register
- Structure: thematic continuity · open commitments status · risk movements · suggested additional pre-reads to circulate
- Trigger: manual
- Delivery: written brief saved to your OneDrive
The pattern is replicable across the executive team. Each leader can sponsor an agent calibrated to their week. CFO might want a daily financial pulse agent. CRO might want a daily pipeline-health agent. Chief of Staff might want a daily decisions-pending agent. The shape is the same — the source data and the questions change.
Limit: Building agents requires either internal capability or a vendor partner. Most executives won’t build them themselves. The value is in sponsoring and defining them — the IT team or partner builds them to your spec.
Critical: Custom agents must be designed and tested for least-privilege access. Confirm whether each agent action runs with user-delegated permissions, agent/service credentials, or scoped data sources — Copilot Studio supports several patterns. An agent built for the CEO could potentially access what the CEO can access, but the design choices determine actual scope. Test access carefully before turning the agent live.
Scheduled prompts — the executive's overnight assistant
What it is: A Copilot Chat prompt that runs automatically on a recurring schedule (daily, weekly, monthly) and delivers the output to your inbox without you opening Copilot.
Why it matters for executives: This is the most under-used feature in M365 Copilot. Once you’ve set one up, your relationship with Copilot changes — from a tool you open to a recurring workflow that runs without you needing to remember.
Four patterns worth installing in your first month:
Monday morning week-ahead briefing. Every Monday 06:00:
Summarise last week’s emails, meetings, and Teams chats from a project / customer / topic focus. What changed? What’s pending my decision? What did I commit to that I haven’t yet delivered? Email me a 1-page digest before standup.
Friday afternoon plan-ahead. Every Friday 16:00:
Look at next week on my calendar. For each meeting, surface: what’s the latest from each attendee, what we last left unresolved, what I might need to prepare. Email me a Monday-prep brief.
Monthly briefing. First business day of each month — a 7-section monthly executive briefing structured around: the number that matters most · three things going well · three things to be alert to · decisions waiting for you · customer pulse · team pulse · “what I’d flag if I were your Chief of Staff”. Paste it straight into Copilot Chat’s scheduling.
Quarterly board prep nudge. Once each quarter, 5 days before the board meeting:
Review the last three board meeting recaps. List every commitment we made to the board that hasn’t been formally closed out. For each, status, owner, and what to bring forward at next meeting.
The mental shift this enables: Copilot becomes part of your weekly rhythm, not a tool you have to remember to open. The recurring brief arrives in your inbox without you triggering it.
Set up your first scheduled prompt this week. It’s the closest thing to a free productivity gain in the entire Copilot product.
Sensitivity labels — what executives need to know
What it is: Sensitivity labels are a Microsoft Purview feature that classifies content (Public, General, Confidential, Strictly Confidential, etc.) and controls who can access and share it. Copilot respects labels, permissions, and Rights Management protections — confirm in your tenant exactly how generated files, Pages, and emails are labelled, because behaviour varies by surface and configuration.
Why it matters for executives: This is the technical-sounding governance feature that determines whether your AI strategy is safe at scale. Get it right and you can let your organisation use Copilot freely on sensitive data. Get it wrong and Copilot becomes a leakage vector.
What you should ask your CIO:
- Do we have sensitivity labels defined? Most organisations have 3-5 levels.
- What’s the default label for new content? Microsoft’s internal default is
Confidential\Internal Only. Yours should be at least that strict. - Do labels flow through Copilot — and on which surfaces? Labels are inherited where supported (typically Word, Outlook, and other native file outputs). Behaviour for Pages, Notebooks, and Chat-generated content can vary by tenant configuration. Get specifics from your IT team, surface by surface.
- What happens when someone tries to share Strictly Confidential content? There should be technical guardrails, not just policy.
- How do we audit labelled content access? Microsoft Purview gives you the visibility — make sure it’s actually being reviewed.
For your own content:
- Label your inbox-saved drafts, especially anything pre-board or pre-release
- Label any Pages you start with sensitive content
- Label Notebooks for board prep so the cycle’s working surface inherits the right protection
Critical executive behaviour to model:
In your visible Copilot usage in front of the organisation, explicitly call out labels. “I’m using my Board Prep Notebook which is labelled Restricted. Anything I generate from this notebook should inherit that label where the surface supports it — Word documents, Outlook emails, and other native outputs typically do; confirm with your IT team how label inheritance behaves for Pages, Notebooks, and Copilot Chat exports in your tenant.” This is a small thing that sets a big norm.
Reading further: The SharePoint oversharing controls guide is the right next read for any executive responsible for information governance. The content safety controls guide is the deeper technical companion.
C-suite role playbooks
The use-case clusters above apply to all executive roles. This section unpacks what Copilot looks like specifically for each seat at the executive table. Read your own role’s section first. Skim the others to understand what your peers are doing — that helps when you’re modelling adoption across the leadership team.
The patterns are drawn from Microsoft’s public Customer Zero deployment writeup (300,000+ employees and external staff), the Synozur Copilot Navigator C-suite series, Microsoft’s internal executive enablement materials, and direct observation across NZ executive engagements over the past six months.
CEO — Copilot as your strategic sidekick
Your defining context: Time-poor, agenda-overloaded, accountable for the whole. Your most precious resource is thinking time — Copilot’s job is to hand it back to you.
The four highest-impact CEO use cases:
Morning briefing automation. A scheduled prompt that runs Monday 06:00 and produces a 4-minute read covering: week ahead · what changed last week · decisions waiting for you · what your Chief of Staff would flag. This is the single most-compounding exec Copilot pattern. See Scheduled prompts in the features section above.
Board paper brief-down + devil’s advocate. Take any board paper, generate a 90-second brief, then immediately ask Copilot to make the strongest opposite case. The compounding value is in the second prompt — most CEOs stop at the first.
Town hall and all-hands message drafting. Not “write my message”, but “refine my draft” — specific, surgical, with the buzzword list explicitly named. (Pattern 2 below, but the CEO version has higher stakes — every word lands across the entire organisation.)
Scenario rehearsal. Before a high-stakes conversation (board chair, regulator, major customer escalation), ask Copilot to play the counterparty. “You are the Chair. Given this trading update draft, what three sharpest questions would you ask me? Quote the specific lines you’d probe.”
Modelling for the organisation (the CEO’s unique job):
The CEO has more impact on Copilot adoption than any other single factor in the organisation. Three behaviours separate the CEOs who lead successful adoption from those who don’t:
- Visible use. Mention Copilot use in passing during all-hands meetings. “I drafted this with Copilot’s help and edited it myself” beats three change-management workshops.
- Visible failure. Share the time Copilot got something wrong and you caught it. The single most damaging adoption pattern is the perception that the exec team uses it perfectly.
- Visible discipline. Refuse decisions visibly when the chain of reasoning is “Copilot said”. Once a quarter publicly, restore the human chain. The cultural norm sets.
What to NOT do as CEO:
- Don’t outsource your AI strategy to IT or to a Centre of Excellence. The CEO needs to be visibly the AI sponsor — not delegate the visibility.
- Don’t be the AI cheerleader without limits. Teams notice over-claim. Honesty about where it fails is what builds trust.
- Don’t use it for personnel decisions about individuals. Modelling the hard line in your own behaviour is non-negotiable.
Starter pack — your first 10 prompts:
The first 10 prompts to install as a new CEO Copilot user are in the 50+ executive prompt library below — see the “CEO starter pack” group.
CFO — finance insights at lightning speed
Your defining context: Accuracy and compliance are your north stars. Speed without accuracy gets you fired. So Copilot’s role for you is acceleration with a tight audit posture.
The five highest-impact CFO use cases:
Variance commentary at speed. Synozur’s Copilot Navigator cites an early CFO Copilot adopter who cut a 3-hour monthly reporting cycle to 30 minutes using this pattern. Excel + Copilot generates the variance narrative; you and your FP&A leads verify and refine.
Ad-hoc analysis via Analyst. The most powerful CFO Copilot lever is the Analyst agent. Real scenario modelling with workings shown, reproducible outputs the audit committee can ask to see, sensitivity analysis on demand. See Analyst in the features section above.
Anomaly detection across versions. Feed Copilot two versions of a forecast and ask what changed. Particularly useful when teams have submitted updated numbers and you want to know what assumption shifted, not just what figure shifted.
Board pre-read drafting. The financial story for the board, drafted from your reporting outputs. You own the editorial pass, but the first draft compresses dramatically.
Bank and lender comms. When the bank comes back with a covenant question or a stress-test request, Copilot drafts the structured response in your house style. You verify every number, your treasury lead double-checks the working, then it goes out.
The CFO’s audit posture (non-negotiable):
- Always cross-verify critical numbers against source systems. Think of Copilot’s draft as you would a junior accountant’s work — helpful but requiring your sign-off.
- Establish an internal review workflow before any Copilot-assisted finance output goes external. Typically: Copilot drafts → manager reviews → you approve.
- Confirm data permissions with IT. Copilot follows your existing access rules, but it’s wise to verify it’s not picking up sensitive payroll data in a general financial analysis if that’s not intended.
- Audit-trail discipline. When Copilot was meaningfully involved in financial output that lands on the board pack or the regulator’s desk, note it in your working papers. Auditors are asking the question now; have the answer ready.
SOX / IFRS / NZ FRS implications:
The current expectation from auditors globally is that AI-assisted financial work is acceptable provided (a) the AI didn’t make the decision, (b) human review is documented, (c) the data flow is governed, (d) the working papers describe the AI’s role. None of this is contentious — it’s the same posture you’d apply to any other tool. The difference is documenting it.
Starter pack — your first 10 prompts:
See the “CFO starter pack” group in the 50+ executive prompt library below.
COO — operational efficiency without losing the plot
Your defining context: You run the engine. Every gain compounds across thousands of staff and hundreds of processes. Your job is to find the high-impact process improvements and not break what’s working.
The four highest-impact COO use cases:
Supply chain / operations bottleneck summarisation. Pull from Teams, SharePoint reports, vendor correspondence — “Summarise the bottleneck signals reported this month. For each, the data, the affected sites, the proposed mitigation, and who owns it.”
Cross-site comparison. When you have multiple sites running similar operations, Copilot can pull the data and find patterns. “Across our 12 distribution hubs, which sites have the largest variance in cost-per-parcel? What’s the story behind each outlier?”
Action plan drafting with team assignments. Once you know what needs to happen:
Draft an action plan to address the Christchurch hub capacity issue. Sections: immediate (next 7 days), short-term (next 30 days), medium-term (next quarter). For each action, recommended owner, dependency, success criterion. Then turn this into a Teams Planner ready format so I can assign it.
Operations review prep. Before each weekly ops review, a scheduled prompt that pulls KPI movements, incident reports, customer complaints, and surfaces the 3 things that need attention this week.
The COO’s signature blind spot:
Process automation that adds friction without adding value. Copilot can produce more dashboards, more reports, more summaries — but if the org can’t act on them, you’ve added overhead, not capacity. The discipline is to retire the old workflow when you introduce the new one. Add and subtract simultaneously.
CIO / CTO — sponsor of the platform, custodian of the trust
Your defining context: You own the AI strategy at the technology layer. Adoption depends on your governance being sound. The board judges you on whether the platform is safe.
The five highest-impact CIO use cases:
Adoption analytics via Viva Insights. The exec dashboard that shows active users by division, by role, by use case. Use it for two purposes: monthly board update on AI adoption, and quarterly intervention list (“who has licenses but isn’t using them? what’s blocking them?”).
Oversharing detection at scale. Microsoft Purview + Microsoft Graph Data Connect surfaces where sensitive content is over-shared. The Customer Zero deployment guide describes this as “the work you do BEFORE Copilot becomes a leakage vector”. Run it monthly, escalate the patterns.
Sensitivity label governance. The CIO’s responsibility is to ensure labels exist, defaults are set, and labels flow through Copilot’s outputs. See Sensitivity labels in the features section above for the five questions to drive.
Custom agent sponsorship and governance. As executives sponsor custom agents, the CIO owns the framework: who can build, what data they can access, how access is reviewed, how agents get retired. Build the framework before the first agent goes live; retrofitting governance is harder.
Pre-adoption communications strategy. The Customer Zero internal deck flags that most early support requests come from staff outside the initial pilot asking “when do I get access?”. Plan the comms ahead of the licensing waves to manage expectations.
The CIO’s signature governance failure mode:
Treating Copilot rollout as an IT project rather than a business transformation. The technical setup is straightforward — the cultural and behavioural change is where adoption lives or dies. Partner with HR, Comms, and the business leaders from day one. The AI Centre of Excellence (CoE) is the canonical setup for this — see the AI Centre of Excellence pattern in the trust section below.
CHRO — talent, capability, and the hard line
Your defining context: AI is reshaping how work gets done, but the hard line on hiring/performance/termination decisions is yours to enforce. The CHRO is the conscience of AI adoption in most organisations.
The four highest-impact CHRO use cases:
AI Use Policy authorship and enforcement. The single most important document in the organisation right now. Co-authored with CIO and Legal. Reviewed quarterly. Communicated to every leader. Your organisation will have its own AI Use Policy — find it via the Search pattern in the features section, or work with your CIO to draft one if there isn’t one yet.
Workforce planning and capability mapping. Copilot can summarise the skills picture across your organisation by pulling from job descriptions, performance reviews (with appropriate anonymisation), and talent management data. “Across our 600 staff, what’s the spread of AI-readiness based on the skills data we have? Where are the genuine capability gaps that training would close?”
Leadership 1:1 prep. For the CEO’s quarterly 1:1 with each direct report, a prompt that pulls the leader’s recent meeting recaps, key decisions, customer signals, and surfaces what’s worth asking about. The hard line: this is Copilot helping the CEO prepare for a conversation, not Copilot assessing the leader.
Talent review prep — with the line clearly drawn. Copilot can summarise data inputs for a talent review (performance trajectory, team feedback themes, business outcomes). Copilot CANNOT make rating recommendations, succession recommendations, or comparative judgements. The CHRO’s role is to keep this line visible.
The CHRO’s signature responsibility:
When a leader presents a recommendation about an individual and the chain of reasoning includes “Copilot said”, push back visibly and immediately. Restore the human chain of reasoning. This is the single behaviour that protects the organisation from regulatory risk and protects individuals from inappropriate AI involvement in decisions about them.
CMO — creativity and scale with AI
Your defining context: Marketing is half analysis, half creative. Copilot turbo-charges both, but the brand voice is yours to protect.
The four highest-impact CMO use cases:
Content creation acceleration. Marketing teams using Copilot widely report sped-up content creation cycles — Synozur’s Copilot Navigator series surfaces specific case data. Social posts, blog drafts, email copy, campaign briefs — the first-draft cost collapses.
Brainstorming partner. The blank-page solver. “Give me 12 different angles for a 60-second customer testimonial video for the Christchurch hub. Different tones — practical, emotional, contrarian. Don’t repeat themes.”
Customer voice synthesis. Pull from customer survey results, review platforms, support ticket themes — “What are customers saying about feature X? Themes, not anecdotes. Quote the patterns, not the individual quotes.”
Per-segment personalisation at scale. A core message turned into 5 different versions for 5 different customer segments — same substance, calibrated language. Particularly powerful for B2B segmentation.
The CMO’s signature risks:
- Brand voice homogenisation. If everyone uses Copilot, content starts feeling generic. Counter this by feeding Copilot your brand style guide and your highest-performing past content as reference each time. Better still — have it explicitly mimic three specific exemplar pieces of yours.
- Factual claims in AI-generated thought-leadership. Always verify any market stat or claim Copilot inserts. AI can produce plausible-sounding but incorrect facts. The verification cost is small; the reputational cost of getting it wrong is large.
- The over-claim trap. Don’t tell your team Copilot replaces creative judgement. Tell them it shortens the path from idea to draft, so they can spend more time on the strategy and the originality that justifies their seat.
CISO — Purview, audit, and the AI risk register
Your defining context: Your peers are excited about Copilot’s value. Your job is to ensure that value isn’t paid for in security or compliance debt. You’re the constructive friction in the AI rollout.
The five highest-impact CISO use cases:
Microsoft Purview deployment for AI-era governance. Data Loss Prevention, sensitivity labels, and Graph Data Connect form the foundation. The Customer Zero internal documentation describes this as the “establish good defaults” precondition — without it, Copilot’s permission-awareness is undermined by oversharing.
Audit logs for AI usage. Every Copilot prompt and response is in the audit log. Use it for: (a) periodic sampling to spot misuse patterns, (b) incident-response evidence when needed, (c) compliance evidence for regulator interactions. Don’t use it for ambient surveillance of individual users.
Phishing pattern detection. The most common Copilot-adjacent security risk is phishing that targets new Copilot users (e.g., spoofed “AI training material” emails). Brief your security awareness team to add Copilot-relevant phishing patterns to their watch list and training content.
AI risk register entries. Treat Copilot as a tier-one platform risk in your risk register. Categories to cover: data loss via consumer AI tools, oversharing surfaced via Copilot reasoning, prompt injection in document inputs, model behavioural drift, vendor concentration risk on the AI platform.
Incident response runbook updates. Your existing incident response runbook needs an AI-aware section: what to do if a sensitive document is found in a Copilot-generated output, what to do if a custom agent’s permissions are found to be over-scoped, what to do if a vendor-built agent shows unexpected behaviour.
The CISO’s value-add posture:
The temptation for the CISO is to be the “no” function. The high-trust CISOs are the ones who are visibly the “yes, and here’s how” function. Build the framework that lets the business use Copilot freely on data that’s appropriately classified, and your peers will partner with you rather than work around you.
Chief Strategy Officer / Chief Risk Officer
Your defining context: You sit at the intersection of analytical depth and judgement. Both Researcher and Analyst are particularly valuable for your work.
Three highest-impact CSO/CRO use cases:
Pre-board strategic intelligence. A weekly Researcher task that produces a sector intelligence briefing covering competitor moves, regulatory environment, customer trends, and macroeconomic signals relevant to your strategic priorities.
Risk theme detection across the enterprise. Pull from incident reports, customer feedback, employee voice surveys, and operational data — “What are the recurring themes that could be early signals of risks not yet in our register? Be specific. Quote the supporting evidence.”
Strategic options stress-testing. When the executive team is considering a major strategic choice, use Analyst for the modelling and Researcher for the external context. Then ask Copilot to make the strongest case AGAINST your recommended option, using only the evidence in front of you.
The CSO/CRO’s signature opportunity:
Custom agents are particularly valuable in your role. A “Strategic Watch Agent” that monitors named competitor and sector signals daily; a “Risk Pattern Agent” that surfaces correlation patterns across risk register entries; a “Board Continuity Agent” that tracks every commitment made to the board across cycles. Sponsor these agents in your first 90 days.
Board director / non-executive director
Your defining context: You meet quarterly or monthly. You have limited day-to-day fluency with the business. Your job is governance and oversight — and you need to ask sharp questions without operational context.
The four highest-impact director use cases:
(Note: directors typically work in their own M365 tenant or a board portal, not the company’s internal tenant — so the Copilot you use may be more constrained than what executives use.)
Board paper brief-down before reading. Take the board pack, ask Copilot to produce the 90-second brief, read the brief on the way to the meeting, then read the source for any item that needs deeper attention.
Question prep. “Based on this board paper, what are the three sharpest questions a sceptical director would ask management? Be specific. Quote the lines you’d probe.” This is the prompt that earns directors a reputation for prepared, calibrated questioning.
Historical reference search. “Across the last 12 months of board minutes, find every reference to [topic]. What did the board say each time? What did management commit to? Has it been delivered?” This is the pattern that catches the commitments that quietly slip.
External benchmarking. Researcher for the comparable disclosures from peer companies, the sector trend analysis, the regulatory environment scan. Particularly valuable when you sit on multiple boards and want to bring cross-board pattern recognition.
The director’s signature responsibility:
Asking the AI governance questions of management. Three to put on the audit committee agenda every six months: (a) what’s our AI Use Policy and how is compliance measured?, (b) what’s our oversharing detection picture and is it improving?, (c) where in the business has AI involvement crossed into decision-making that should be human-only, and how was it addressed?
Chief of Staff / Executive Assistant
Your defining context: You’re the quiet multiplier. Every executive you support has more time because you do. Copilot amplifies that further.
The five highest-impact Chief of Staff / EA use cases:
Daily executive briefing. The Monday morning briefing agent (see Custom agents in the features section above). You configure it, the executive reads it. Quietly the most-thanked thing you’ll ever do for them.
Inbox triage at scale. The triage prompt referenced in the Outlook section turns the executive’s 400-email morning pile into 6-10 things that need their decision. You run it before they wake; they read it with their first coffee.
Meeting choreography. For every senior meeting on the executive’s calendar, a pre-meeting brief covering who’s coming, what we last left unresolved, what they’re likely to ask, what we should commit to. The agenda is yours; the brief is Copilot-generated and you-edited.
Board paper automation. The Microsoft Copilot Quick Starts Executive Assistant deck covers this in depth — using Copilot to take draft inputs from teams, standardise them to board template, generate executive summaries, and produce the consolidated pack. Cycle times that ran to days can drop to hours.
Speech and message drafting. When the executive needs a town hall message, customer letter, or stakeholder note — your job is to give them a strong starting draft. Copilot accelerates your starting draft. You add the editorial judgement that knows the executive’s voice.
The Chief of Staff / EA’s signature multiplier:
You’re often the first person in the organisation to use Copilot at depth (because you have the time and the broad context). Make this a visible advocacy role. Lead the “Copilot Champions” community for the EA cohort. Share patterns. Build the institutional knowledge that scales beyond your own executive.
Common patterns across all C-suite roles
Six patterns repeat across every executive role, regardless of seat at the table:
- The first month is small wins. Drafting tax reduction, meeting prep, inbox triage. Don’t try to do strategic work in week one — build the muscle on operational work first.
- The second month is compounding. Notebooks for repeating prep cycles, scheduled prompts for recurring rituals, memory installation for cross-session efficiency.
- The third month is compounding. Researcher for things you’d otherwise delegate. Analyst for things you’d otherwise commission. The shift from typing-tax assistant to thinking partner.
- The sixth month is agents. Custom agents for your unique recurring patterns. This is the executive-grade Copilot move that most leaders never reach.
- The hard line never moves. Copilot drafts; you decide. Forever. In every role.
- The most adoption-positive behaviour is visible failure-sharing. Every executive who built a strong adoption culture in their division did this. The ones who tried to perform perfectly with Copilot left their teams quietly wondering why their own usage felt clunkier.
👥 You are also a people leader (probably)
Most executives don’t ONLY do executive work. You almost certainly have 4-15 direct reports who are themselves managers, and you almost certainly do 1:1s, recognition, hiring, performance check-ins, and skip-level conversations as part of your week. The patterns in the Copilot for People Leaders Field Guide all apply — but here are 3 of the highest-leverage PL scenarios calibrated for the manager-of-managers level. The full playbook is the companion guide.
1:1 with a manager direct report
The PL field guide covers the 1:1 prep flow. The exec twist: you’re not asking “how is your team doing” (that’s their job to know), you’re asking “what’s developing your leaders”. Reframe the Copilot prompt accordingly.
“My 1:1 with [manager’s name] is tomorrow. Look at their team’s outputs this fortnight (status updates, project shipments, any wins they’ve shared), the team-health signals from their last 1:1 with me, and the 2-3 things I’ve been asking them to develop. Give me a structured 30-min agenda focused on: (1) what’s the highest-leverage stretch I’m under-asking from them, (2) where might they be over-protecting their team from useful pressure, (3) what’s the one feedback they’d benefit most from hearing from me. Don’t tell me to do or say anything — just surface the picture.”
This is where Copilot’s value compounds most for execs — your direct reports are themselves time-constrained leaders, and your 30 minutes a fortnight is the highest-leverage development you give them. Don’t outsource the conversation; do use Copilot to make sure you walk in already noticing what they’d be working hardest to articulate themselves.
Recognition for a leader’s team win
When a leader on your team has shipped something significant, the standard recognition is “congrats to the team”. The recognition that actually develops the leader is recognition of HOW they set their team up to win — what they delegated and to whom, what they protected, what they pushed back on. Copilot is built for this kind of synthesis.
"[Leader’s name] just shipped [project / milestone]. Look at the team’s contributions across SharePoint and Teams over the past quarter, and the patterns of how [leader’s name] has been delegating, recognising, and removing blockers. Draft a 4-sentence Teams DM to them that names what they DID specifically as a leader (not what the team delivered). Warm but specific. No clichés (no ‘crushing it’, no ’leveraged’, no ‘doubling down’). Include one observation about a leadership choice they made that I want them to keep doing."
The output is rarely send-as-is. The structured noticing it forces — what did this leader actually do that made the team’s work possible — is half the value, even before you edit it into your voice.
Skip-level prep
Skip-levels are the highest-leverage cultural-health signal an exec has, AND they’re the hardest to prep — because the patterns that matter are the ones that DON’T appear in your direct reports’ status updates. Copilot’s synthesis is genuinely useful here, pulling threads across multiple skip-level signals to surface the “what’s the pattern” question for you.
“I have skip-level conversations with [team A, B, C] this month. Look at the recent meeting summaries, project updates, and any Teams chats my direct reports have in those team channels. Don’t tell me who’s struggling or who’s leading. Show me: (1) which themes are being raised at the team layer that haven’t surfaced in my 1:1s with their managers, (2) which questions team members are asking that suggest they don’t have full context from their manager, (3) where the leader’s voice is consistently positive while the team’s signals are mixed. Patterns only, no recommendations about individuals.”
The hard discipline is the same as elsewhere in this guide — Copilot surfaces the picture, you decide what to do with it. Skip-levels are where that discipline matters most because the conversation is one-on-one with a junior team member who has no idea you’ve been doing Copilot synthesis on their team’s signals. They deserve your full presence in that conversation, not a recital of what Copilot told you about their reality.
📖 Want the full PL playbook? Sush’s Copilot for People Leaders Field Guide is the companion piece — 16 features calibrated for managers, the People Leader role playbook, 13 named PL scenarios (1:1 prep · team recap · performance check-in · recognition · feedback · hiring · coaching · wellbeing · status update · onboarding · career · workload · OKRs), 18 PL prompts (now including calendar audit · 1:1 cadence drift · comms audit), and a first-90-days starter for new managers.
Scenario library — 20 named executive scenarios
The patterns above give you the how. This section gives you the when — twenty named scenarios that recur in executive work, with the prompt scaffolding that lands first time. Bookmark this section; the patterns repeat.
1 · Board pre-read briefing
Trigger: Board pack arrives 5-7 days before meeting. You have an hour now and 30 minutes the day before to read it.
Prompt:
Summarise this board paper into a 90-second briefing for me. Use four sections: (1) bottom line in one sentence, (2) the three options or recommendations on the table with one-line trade-offs, (3) the top 3 risks I should be alert to, (4) the specific decisions I’m being asked to make. Then add a fifth section — three sharpest questions a sceptical director would ask. Quote the lines they’d probe.
Why it works: Reads on the way to the meeting, primes you for the harder questions. The fifth section is the executive-specific addition.
2 · Crisis response — cyber incident
Trigger: Incident detected overnight. You have until 14:00 to decide on disclosure approach.
Setup: Open Copilot Chat. Attach the incident brief from your security team.
Prompt:
Read this incident brief. Help me think through the disclosure decision. Structure your response as: (1) the facts as we know them, in plain language, (2) the case FOR proactive customer disclosure, (3) the case AGAINST proactive customer disclosure, (4) the threshold that would convert me from one to the other, (5) the holding statement I should have ready in case the incident becomes public via another route. Don’t recommend — I’ll decide.
Why it works: Forces structured thinking under time pressure. The “don’t recommend” clause keeps you in the decision seat.
3 · Quarterly Business Review prep
Trigger: Division QBR in 3 days. You’ve received the KPI dashboard, the division performance report, and a customer health summary.
Setup: Set up a Notebook called “Logistics QBR — June” and add all three documents.
Prompt:
Across all files in this notebook, prepare my QBR prep brief. Structure: (1) what’s the headline story Q1 told us about this division — 2 sentences, (2) the three numbers that most need explaining, with the most likely story behind each, (3) the three customers I should ask about by name, (4) the three “actions in flight from last QBR” status checks I need to do, (5) the one decision I want to come out of this QBR with. Plain English.
Why it works: Walks you into the room with a clear point of view, not a clean head.
4 · Competitive response in a day
Trigger: A competitor announces a move this morning. The market is asking how you’ll respond. You have until close of business.
Prompt sequence — three prompts in sequence:
Prompt A (Researcher, kicked off first because it takes 10-15 min):
Research the [competitor name] announcement made today regarding [specifics]. What exactly did they announce? What’s the market reaction so far — press, analyst notes, social? What’s the strategic implication for [your sector]? 1-page briefing, cite all sources.
Prompt B (Copilot Chat, while Researcher runs):
Drawing on /our strategy paper and /our competitor watch, what’s our planned response to the kind of move [competitor] just made? Are we ready? Where are we under-prepared?
Prompt C (after Researcher returns):
Combining your earlier briefing and the Researcher’s report, draft three response options for the leadership team: (1) hold and observe, (2) public competitive response within 48 hours, (3) accelerate our pre-existing differentiator. For each, the pro, the con, the cost, and the time-to-execute. Don’t recommend.
Why it works: Parallel prep — research and analysis happening in different surfaces simultaneously. By the time you walk into the noon leadership meeting, you have all three layers.
5 · M&A pre-screen
Trigger: Banker brings you a target. You want a 24-hour view on whether it’s worth pursuing further work.
Prompt:
I have information on a potential acquisition target — see attached. Help me build a pre-screen view. Structure: (1) strategic fit — how this would change our shape and what we’d gain, (2) financial sanity check — what jumps out as either attractive or worrying based on the headline figures, (3) integration complexity — what cultural and operational integration challenges would matter most, (4) my three sharpest questions to take back to the banker before any further work, (5) compare three paths — dig deeper / decline politely / commission diligence — across evidence quality, risk, missing facts, and the next validation step needed. Don’t recommend — I’ll decide.
Why it works: Compresses the 1-2 day analyst pre-screen into a 1-hour executive review. Real diligence still has to happen, but the go/no-go on commissioning diligence becomes faster.
6 · Regulator response drafting
Trigger: Regulator has asked for a written response to a specific event. Legal has drafted; you need to sign off.
Setup: Have the legal draft, the relevant correspondence chain, and the underlying facts.
Prompt:
Read this draft regulator response that legal has prepared. Then assess: (1) where is the tone lawyered when it should be CEO-on-the-record, (2) where does the language hedge in a way that might invite a follow-up question we don’t want, (3) where could a phrase be misread by a journalist if this letter became public, (4) is anything missing that the regulator’s office is likely to expect us to volunteer. Quote specific phrases. Then propose a rewrite of the three highest-priority changes.
Why it works: Brings an executive editorial eye to legal-authored content. The fourth question is the one that prevents the follow-up letter you didn’t want.
7 · Investor relations / analyst day prep
Trigger: Analyst day in 2 weeks. The IR team is preparing the materials and asking for your input.
Setup: Notebook with the IR pack, last analyst day Q&A transcript, recent broker notes, current consensus.
Prompt:
Across all files in this notebook, help me prepare for the analyst day. Structure: (1) the three themes analysts will most want to hear addressed based on the consensus and recent notes, (2) the three questions I should expect to be asked that I’d rather not, with my best preparation for each, (3) where my draft narrative is strong and where it sounds defensive, (4) the one number or commitment I should NOT volunteer if not asked. Quote the specific lines you’re drawing from.
Why it works: The fourth question is the most-thanked addition from CEOs prepping for these days. The “don’t volunteer if not asked” discipline matters in IR.
8 · Annual planning / strategy refresh
Trigger: Annual planning cycle starts. Each ELT member has submitted draft strategy documents for their function.
Setup: Notebook with all ELT strategy submissions plus the previous year’s plan plus the latest financials.
Prompt:
Across all functional strategies in this notebook, identify: (1) the synergies — where two or more functions are doing similar things that could be combined, (2) the gaps — where no function is owning something the overall strategy needs, (3) the conflicts — where two functions have contradictory assumptions or commitments, (4) the over-commitments — where the sum of functional asks exceeds plausible capacity. Be specific. Quote the lines you’re drawing from.
Why it works: Surfaces the integration work that’s normally left to a strategy team retreat. Doesn’t replace the retreat, but pre-empts the easy findings.
9 · Exec offsite design
Trigger: Annual exec offsite in 6 weeks. You’re chairing.
Setup: Co-author the agenda live in a Page with the ELT.
Prompt:
Draft an exec offsite agenda for 2 days. Outcomes I want: (1) shared view of where we are on the FY27 plan, (2) decision on the predictive logistics pull-forward, (3) honest exchange on where the team isn’t operating well, (4) reset of how we handle the 6 most contentious decisions ahead of us. Format: time blocks, intended outcome per block, suggested facilitator per block. Build in 2 hours of unstructured time on each day. Be specific about what we’d discuss, not just topics.
Why it works: Pages collaboration means everyone can edit live; you avoid the version-merging hell of agenda drafting via email.
10 · Town hall messaging
Trigger: Quarterly all-hands in 2 weeks. You need to message a difficult quarter.
Setup: Have your rough draft of the town hall message ready.
Prompt:
Refine this town hall message for ~600 staff. Specifically: (1) cut to under 200 words, (2) replace every buzzword (“doubling down”, “crushing it”, “leverage”, “values-led”) with plain English, (3) add a one-sentence acknowledgement of the Logistics softness without being defensive, (4) end with a single specific ask of staff for this month, (5) keep the warmth, lose the corporate tone.
Then immediately:
Re-read this draft as if you were a sceptical staff member in Logistics who’s been navigating the softness directly. What lands? What feels hollow? Quote the specific phrases that would land either way.
Why it works: Two-step pattern — refine first, then sceptical-audience check. The second prompt is where most rough edges get sanded.
11 · CEO-level customer escalation
Trigger: A top-10 customer has escalated to your office. You need to call their CEO in 24 hours.
Setup: Notebook with the customer relationship history, recent contract activity, any incident reports, sales team notes.
Prompt:
Across the files in this notebook, help me prepare for tomorrow’s call with [customer CEO]. Structure: (1) the customer’s view of what’s gone wrong — what would they say if I asked them directly, (2) our view of what’s gone wrong — and where we’re not in agreement with their view, (3) the three concessions we’ve already made (so I don’t make them again unknowingly), (4) the three things I could offer that would land well but cost us little, (5) the one thing they’re most likely to ask for that I should NOT commit to in this call. Quote the relevant evidence.
Why it works: The fifth question is the executive-specific one. CEO-to-CEO calls have a momentum of their own; knowing what to NOT commit to is the discipline.
12 · Audit committee prep
Trigger: Audit committee in 5 days. You’re presenting the financial controls update.
Setup: Notebook with the prior committee minutes, latest internal audit reports, the management letter from the external auditor, any open compliance items.
Prompt:
Across the files in this notebook, prepare my audit committee briefing. Structure: (1) status of every open commitment from the previous meeting, (2) the new material findings, with my honest assessment of severity, (3) the three areas where the committee is most likely to want more depth, with the answer ready, (4) the one thing I’d rather not bring up but suspect I should. Plain English.
Why it works: Audit committees reward candour. The fourth question forces the discipline.
13 · Risk committee prep
Trigger: Risk committee tomorrow.
Setup: Notebook with the risk register, recent incident reports, the prior committee minutes.
Prompt:
Help me brief the risk committee tomorrow. Structure: (1) what’s changed materially in the risk register since last meeting — additions, escalations, closures, (2) the three risks where the committee should be putting most of its time, with why each, (3) the risk I’d most want the committee’s perspective on (something I haven’t worked out yet), (4) any patterns across multiple risks that suggest a deeper structural issue we haven’t yet named. Quote evidence.
Why it works: Treats the risk committee as a thinking partner, not a reporting venue. Best risk committees say afterwards “that was a real conversation, not a presentation”.
14 · ESG / sustainability board update
Trigger: Quarterly sustainability update at the next board meeting.
Prompt:
Draft my quarterly ESG board update. Sections: (1) progress against our published commitments — be specific about which are on track, which are slipping, which are off-track, (2) any new material disclosure obligations that have come into effect, (3) the three areas where stakeholder expectations have moved faster than our planned response, (4) any genuine progress worth celebrating without overclaiming. Tone: serious, specific, non-promotional. The board is increasingly cynical about ESG narrative and rewards directness.
Why it works: The “non-promotional” instruction matters. ESG content has a strong default tone Copilot will land on; you have to actively push against it.
15 · Transformation programme update
Trigger: Quarterly transformation programme update.
Setup: Notebook with the programme charter, latest status reports, the original business case, recent steering committee minutes.
Prompt:
Across the files in this notebook, prepare my transformation programme update for the board. Structure: (1) where we are vs. the original commitment — specifically, not narratively, (2) where the timeline has shifted and the honest cause of each shift (was it scope, was it capacity, was it complexity we underestimated), (3) what the team needs from the board to keep moving, (4) the uncomfortable truth I should name explicitly if I want to keep the board’s trust. Plain English.
Why it works: Transformation programmes have a defensive default narrative. The fourth question forces the discipline to name what’s hard.
16 · Post-merger integration leadership
Trigger: 90 days into a merger. Monthly leadership update due.
Setup: Notebook with the integration playbook, the latest tracking, the people sentiment data, customer retention data.
Prompt:
Across the files in this notebook, prepare my 90-day integration update. Structure: (1) where the integration is genuinely working — be specific, name people, (2) where the integration is harder than planned — be specific, name the root cause, not the symptom, (3) the three people decisions still pending and the consequence of further delay, (4) the customer relationship temperature — overall and by top-10, (5) compare the three options — accelerate / hold / de-scope — across what we’d gain, what we’d lose, and the second-order consequences. Don’t recommend — I’ll decide.
Why it works: Integration leadership rewards honesty. The fifth question forces a structured comparison rather than a flat status report.
17 · Crisis comms — public criticism
Trigger: A high-profile critic has published a piece criticising the company. Media calls are coming in.
Setup: Have the original criticism piece, any internal data that’s relevant, and the prior holding statements.
Prompt sequence:
Prompt A:
Read this criticism piece. Identify (1) the specific factual claims that are accurate, (2) the specific factual claims that are inaccurate, (3) the specific opinions framed as facts, (4) the most likely underlying motivation for the piece based on tone and emphasis. Be careful and specific.
Prompt B:
Now draft three response options: (a) no public response, internal-only message to staff, (b) brief on-record correction of the factual inaccuracies only, (c) substantive response engaging the substance. For each: the audience reaction it’s most likely to produce, the second-order risks, the time-to-publish.
Prompt C:
I’ve decided on option (b). Draft the response. Tone: direct, specific, non-defensive, no personal criticism of the author. 150 words maximum. Include the specific factual corrections.
Why it works: Three-step decision process under media pressure. The structure prevents the rush to publish that usually makes a crisis worse.
18 · Performance conversation prep with direct reports
Trigger: Quarterly 1:1 with each ELT direct report. You want to have a real conversation, not a report-out.
Setup: For each direct report, ask Copilot:
Prompt:
I have a quarterly 1:1 with [name] tomorrow. Pull from their recent Teams meetings I’ve attended, their emails, any project status reports they’ve owned. Help me prepare. Structure: (1) what they’re most likely to want to discuss, (2) what I should be alert to that they might not bring up directly, (3) what I should ask them to think harder about, (4) the one thing I should explicitly acknowledge they’ve done well. Don’t summarise their performance — that’s my job. Help me prepare to have the conversation.
Why it works: Helps you walk into the 1:1 calibrated, not cold. Critically — explicitly NOT a performance summary. Copilot helps you prepare for the conversation; you have the conversation.
Hard line: Do NOT use Copilot to “rate” a direct report or to recommend who to promote / let go / move. That’s the line in The hard line section.
19 · Succession / talent review prep
Trigger: Annual talent review with CHRO and CEO peer.
Setup: Have your input on each succession-pipeline name from your area. CHRO has the cross-functional view.
Prompt:
I’m preparing for tomorrow’s talent review with the CHRO and CEO. Help me prepare my contributions. For each name I’m bringing forward, structure: (1) what’s their distinctive strength I want to call out, (2) what’s the development gap I want to acknowledge candidly, (3) what’s their next plausible role and the typical 18-month preparation for it. Be specific. Don’t rate or compare them — I’ll do that with the CHRO in the room. Help me ARRIVE PREPARED, not arrive with conclusions.
Why it works: Same as #18 — Copilot helps prepare for the conversation, not pre-judge the conversation. The instruction “don’t rate or compare” is the hard-line in practice.
20 · CEO transition / first 90 days
Trigger: New CEO arriving in 4 weeks. Outgoing CEO is preparing the handover.
Prompt for the outgoing CEO:
Help me prepare a 90-day arrival pack for my successor. Structure: (1) the three meetings I’d put in their first week — who and why, (2) the three decisions they’ll be asked to make in their first month — context and our recent thinking on each, (3) the three relationships they need to invest in early — who, why, and the recent state of each, (4) the three things I’d leave alone for 90 days — let them form their own view, (5) the one thing I’d quietly warn them about — based on what I’ve seen but never formally surfaced.
Prompt for the incoming CEO (run early in week 1):
I started this week. Help me build a calibration brief. Pull from the inbox I’ve inherited, the org chart, the recent board minutes, and any leadership team meetings on my calendar from the last 60 days. Structure: (1) who matters most to know in my first month, (2) what’s the current state of the business in plain English, (3) what’s the unspoken thing that everyone seems to be navigating around, (4) where I’d most expect to be tested early.
Why it works: A 4th-quarter retiring CEO and a fresh-arrival CEO are both information-overloaded. These two prompts compress hours of one-to-ones into a calibrated starting point. The handover one ALSO gives the outgoing CEO a structure to be useful without being intrusive.
60+ executive prompt library
A copy-paste library of prompts that have landed well in real executive sessions. Grouped by use. Bookmark this section; the structure is what you’ll come back to.
CEO starter pack (10 prompts)
- “Summarise this board paper into a 90-second briefing structured as bottom line · options · risks · decisions required.”
- “Make the strongest possible case for [the option I didn't recommend], using only the evidence in this paper.”
- “Triage everything in my inbox from the last 24 hours. Show me only the 6-10 things that need my decision before noon.”
- “Refine this town hall message — cut to under 200 words, replace every buzzword, add an acknowledgement, end with a specific ask.”
- “Re-read this draft as if you were a sceptical [audience]. What lands? What feels hollow? Quote specific phrases.”
- “I have a meeting in 45 minutes with [name] about [topic]. Pull the recent emails, files, and meeting notes. Give me a one-page brief.”
- “Summarise this meeting into decisions · actions with owner and date · outstanding questions. Then add a fourth section — tone observations — anything that suggests under-the-surface tension.”
- “Across the files in this notebook, what story is being told that we haven't yet explicitly named? Quote the supporting evidence.”
- “What does this policy NOT cover that a CEO would expect it to cover? Be specific.”
- “Set up a scheduled prompt: every Monday 06:00, email me a 1-page week-ahead briefing structured as [my preferred structure]. Save to drafts so I can edit before any onward send.”
CFO starter pack (10 prompts)
- “Analyse this Group P&L sheet. Write variance commentary for the board: top 5 variances over 5% by absolute impact, the story behind each, which most threaten our forecast. Plain English.”
- “Compare these two versions of the forecast. What changed in assumption, not just figure?”
- “Model three scenarios — Base, Downside, Upside — using these assumptions. Show: Revenue, GP, Opex, EBITDA, EBITDA Margin. Which breaches the covenant floor? Show workings.” [→ Analyst]
- “What's the single biggest sensitivity in the Downside scenario? If I could only protect ONE driver, which?” [→ Analyst]
- “Draft my CFO commentary for the trading update — paragraph 2 specifically. Direct about the EBITDA miss. No hedging. 80 words.”
- “Compare these two investment business cases. Surface where they fundamentally disagree on inputs, not just outputs. Don't recommend.” [→ Analyst]
- “Draft the response to the bank's covenant inquiry. Acknowledge the breach risk in Downside, explain the mitigation plan, propose a quarterly review cadence. House style: direct.”
- “Pull the latest from FP&A on operating cash flow. Tell me where the working capital movements are most likely to surprise the board.”
- “Read this draft regulator response from legal. Where is the tone lawyered when it should be CFO-on-the-record?”
- “Audit-trail summary — for any output above where I used Copilot meaningfully, document the source data, the prompt, the human review step, and the sign-off. Format for working papers.”
COO starter pack (10 prompts)
- “Summarise all bottleneck reports across our 12 hubs this month. For each, the data, the affected site, the proposed mitigation, the owner.”
- “Across our 12 hubs, which has the largest variance in cost-per-parcel? What's the story behind each outlier?”
- “Draft an action plan for the Christchurch capacity issue. Immediate (7 days), short-term (30 days), medium-term (next quarter). Owner, dependency, success criterion for each.”
- “Turn that action plan into a Teams Planner-ready format I can assign.”
- “Pull from this week's ops review minutes. List every action that was assigned and is now overdue. Who, what, when, status.”
- “Compare the safety incident reports from the last 12 months. Are there patterns — by site, by time of day, by shift handover? Quote specific incidents.”
- “Looking at our supplier scorecard data, which suppliers have shown the largest service-level slippage this quarter? Story behind each.”
- “Predictive logistics MVP — across the engineering updates, customer feedback, and competitor watch, what's the highest-confidence go/no-go signal for the August launch?”
- “Summarise the customer escalations that came through this week. By urgency, by customer, by the action needed from me.”
- “Pull from my calendar next week. For each operations meeting, what should I be most prepared for? Surface anything from the last week's signals.”
CIO / CISO starter pack (10 prompts)
- “From Viva Insights, who has Copilot licenses but no active use? Group by division and by role. Recommended outreach approach for each group.”
- “From the Purview oversharing report, which SharePoint sites have the largest cross-site sharing footprint that's inconsistent with their sensitivity? Top 10.”
- “From the audit log, identify any Copilot prompts from the last 30 days that may have crossed our AI Use Policy guidance. Group by pattern. Don't name individuals — name patterns.”
- “Brief the board on this quarter's Copilot adoption. Active users %, top-3 use cases by division, top-3 blockers we know about, top-3 actions for next quarter.”
- “Draft the executive comms for the upcoming Copilot Studio agent governance framework. Plain English, frame as enablement not control.”
- “For each of our 10 custom agents already live, check: who owns it, when it was last reviewed, what data it accesses, whether the access scope is still right.”
- “Pull the latest from Microsoft Defender XDR on phishing patterns targeting our staff. Are any specifically targeting Copilot users? Patterns to watch?”
- “Draft the AI risk register update for risk committee. Include: data loss via consumer AI tools, oversharing surfaced via Copilot reasoning, prompt injection via document inputs, vendor concentration risk. Severity, mitigation, owner.”
- “Review our incident response runbook. Where does it need AI-aware additions? Be specific — clauses, not principles.”
- “Set up a scheduled prompt: monthly first business day, summarise our Copilot governance health — adoption, oversharing, audit log patterns, open governance actions. Email me a 1-page digest.”
Leadership communication pack (10 prompts)
- “Refine this town hall message: cut to <200 words, replace every buzzword, add a one-sentence acknowledgement of [the difficult thing], end with a specific ask.”
- “Same message, more direct tone — the kind a CEO would use when they want the leadership team to read and act.”
- “Same message, warmer tone — the kind a CEO would use when the audience needs to feel acknowledged before they hear the ask.”
- “Draft a reply to this email from [counterparty]. Direct, candid, no defensiveness, no excuses. [Specific points to address]. End with a short acknowledgement of [tone point]. 3-4 short paragraphs.”
- “Coach mode: read this draft I've prepared. Where am I being defensive or evasive without realising it? Where is a phrase soft when it should be direct? Quote specific phrases.”
- “Draft the company-wide email announcing [the change]. Sections: what · why · what it means for you · what to do next · who to contact. Maximum 250 words. Plain English.”
- “Draft three subject lines for the email above. One direct, one curiosity-driven, one neutral. Which is most likely to be opened?”
- “Draft my LinkedIn post on [topic]. Short. First-person. Avoid 'I'm thrilled to announce' / 'humbled to share' opening. Open with the substance, not the framing.”
- “Read my draft customer letter. Where would a sceptical customer find the language soft or evasive? Quote specific phrases.”
- “Draft my closing comments for [tomorrow's event]. 3 minutes spoken. One memorable line. No clichés.”
Thinking-partner pack (10 prompts)
- “Play devil's advocate. Make the strongest possible case against [my recommendation], using only the evidence I've shared with you.”
- “What am I most likely to be missing in this analysis? Be specific.”
- “What's the second-order consequence of [the decision I'm considering] that I might not have thought about?”
- “Steelman [counterparty's position] for me. Make the strongest version of their argument, even if you disagree.”
- “What's the pattern across all of these [emails / meetings / reports] that I might not be naming?”
- “Compare [Option A] and [Option B] across [dimensions]. Don't recommend. I'll decide.”
- “If I'm wrong about [this assumption], what would the world look like in 6 months? Be specific.”
- “What's the question I should be asking that I'm not asking?”
- “Quote me back the three lines from this document that I most need to take seriously, even if I'd rather not.”
- “Summarise where my thinking has changed across this conversation. Where am I now compared to where I started?”
Trust, governance, accountability — the deeper picture
The Trust section covers the essentials. This section unpacks the deeper picture for executives who are leading the governance conversation in their organisation — and that’s most CEOs and CIOs at this point in the adoption curve.
The AI Centre of Excellence pattern
Microsoft’s enterprise-wide deployment (300,000+ employees and external staff) centred on an internal AI Centre of Excellence (CoE) bringing together IT, HR, Legal, Security, Communications, and senior business representation. This is the canonical pattern for organisations above ~500 staff. Smaller organisations can adopt a lighter version — a virtual team with monthly cadence and one named accountable executive.
The CoE’s job is to be the connective tissue between:
- The technical platform (governed by IT/security)
- The behavioural rollout (driven by HR, Comms, business)
- The risk posture (curated by Legal, Compliance, Risk)
- The use-case acceleration (sponsored by business leaders)
Without a CoE, these conversations happen in separate rooms and the gaps are where adoption friction or governance failure lives.
The five governance questions every executive should be asking quarterly
These are the questions to put on the executive team agenda once a quarter, regardless of who’s the formal owner:
- Adoption health. What % of licensed users are active? Where are the dead pockets and what’s the intervention plan?
- Use-case quality. What are the top 5 use cases by reported value, and what’s the next 5 we’re investing in?
- Governance health. What did the audit log surface this quarter? Any patterns that suggest policy refresh is needed?
- Risk posture. What’s changed in the risk register? Where is the AI risk profile trending — better or worse?
- Investment efficiency. Are we spending appropriately on Copilot licenses vs. realised value? Are there agent investments we should make next quarter?
Five questions. Quarterly. Same five every time. The discipline of asking them consistently is the discipline. The answers will improve over time; the consistency of asking is what builds the muscle.
What the Microsoft Customer Zero deployment learned (and what to lift)
Microsoft’s internal Customer Zero deployment ran in four phases (engineers → sales/marketing → support/HR/legal/security → all-staff). The lessons worth lifting for any organisation:
- Pre-adoption comms strategy is the most underrated work. Most early support requests are “when do I get access?” Plan for this; pre-write the responses.
- Top-down sensitivity label defaults. Default everything to “Confidential\Internal Only” or stricter. It’s the foundation everything else stands on.
- Group-based licensing. Don’t license user-by-user; license by group. Keeps the licensing aligned with business intent, makes scaling cheap, lets you adjust quickly.
- Works councils and regional regulators are not afterthoughts. Engage them early — particularly in Europe — to avoid late-stage rollout friction.
- The CEO and CIO are seen as accountable. Even if delegated operationally, the visible accountability has to be at the top.
When NOT to use Copilot — the executive-level list
The hard line is the foundational rule. Beyond it, three categories where the risk-reward is unfavourable enough that the discipline is “default to NOT using Copilot”:
- Disciplinary or grievance proceedings. AI in the loop on an individual employee matter creates a defensibility problem. Use Copilot for general background reading only.
- Market-sensitive timing decisions. Trading update timing, M&A announcements, results day. The marginal value of AI is small; the risk if a prompt is later subpoenaed is real.
- Anything you wouldn’t want a transcript of your reasoning in a regulatory submission. Copilot prompts are stored. If you’d be uncomfortable with the transcript being read back later, the conversation should happen elsewhere.
The single most damaging governance failure pattern
Most governance failures in Copilot deployments don’t come from technical leakage — Microsoft’s platform is well-engineered for that. They come from cultural drift:
- Staff start treating Copilot’s outputs as decisions rather than drafts.
- Leaders stop reviewing AI-assisted work as carefully as they used to.
- “Copilot said” becomes a perceived basis for action.
This is the pattern to watch for and counter. The behaviours that prevent it are in the What executives must model section of this guide.
Common failure patterns — and what to do about each
Six failure patterns repeat across executive Copilot adoption. Knowing them in advance is half the immune system.
Pattern 1 — The Over-Enthusiast
What it looks like: Executive becomes a vocal Copilot champion, uses it visibly, but stops applying editorial discipline. AI-generated content starts going out under their name with minimal review.
What it costs: Reputation damage when AI-shaped errors surface — a wrong customer name, a fabricated stat, an off-tone phrase that lands badly. Once the team perceives “they’re not really reading what they sign”, trust drops.
The fix: A personal commitment to editorial discipline that the executive can verbalise. “I always edit. Always. Even when I’m tired.” Make the commitment visible to your team. They’ll calibrate.
Pattern 2 — The Silent Sceptic
What it looks like: Executive privately uses Copilot but never speaks of it. Their team senses they don’t endorse it, even though they technically permit it.
What it costs: Their team’s adoption flat-lines. Without visible executive endorsement, middle managers err on the side of caution and don’t push their teams either.
The fix: Pick one weekly all-hands or leadership meeting to share one specific Copilot use. Make it a habit. Even three minutes of “here’s what I tried this week” shifts the cultural ground.
Pattern 3 — The Over-Delegator
What it looks like: Executive treats Copilot as a junior they can outsource thinking to. “Copilot, what should we do about [strategic question]?” Then takes the answer as input to a decision.
What it costs: Decisions made with shallower reasoning than the executive normally applies. Over time, the executive’s thinking quality degrades because they’re not exercising the muscle.
The fix: Discipline of always asking Copilot for structured analysis, never for recommendation. “Compare for me, don’t tell me.” Restore the executive judgement as the place decisions happen.
Pattern 4 — The Under-Discloser
What it looks like: Executive uses Copilot meaningfully for high-stakes work (board papers, regulator letters, customer responses) but doesn’t disclose AI involvement when asked. Or worse, denies it.
What it costs: When the AI involvement surfaces later (which it often does — colleagues, journalists, regulators ask), trust drops. The non-disclosure is the issue, not the use.
The fix: Default to transparency. “Yes, Copilot helped with the first draft; I edited it and own the final.” This is the modelling that protects you and the organisation. Hiding AI use is the failure mode, not using AI.
Pattern 5 — The Experimenter-Without-Discipline
What it looks like: Executive tries lots of Copilot things, doesn’t stick with any. Three months in, they don’t have habits, just dabbling.
What it costs: Plateau without compounding. The 30-day rhythm and the habit-building never lock in.
The fix: Pick three Copilot use cases. Run them weekly for a month before adding anything else. Build the routine before pursuing the range. The 30-day rhythm in this guide is calibrated for exactly this.
Pattern 6 — The IT-Project Treator
What it looks like: Executive treats Copilot rollout as an IT initiative. Delegates fully to the CIO. Doesn’t visibly engage. Doesn’t participate in shaping the AI Use Policy or the governance approach.
What it costs: Adoption stays operationally-driven, never gets the cultural lift that executive sponsorship provides. The CIO has to fight for engagement that should have been freely given.
The fix: Executive sponsorship requires visible participation. Not “I support this” in a town hall — “I am personally involved in shaping how we use this safely and well, here’s what I’m thinking, here’s what I’m asking the team.”
First 90 days for a new executive — Copilot starter pack
For an executive arriving fresh into a new role, here’s the calibrated 90-day Copilot starter pack. Skip nothing in the first month; you’ll thank yourself in the third.
Week 1 — Set up
- Day 1: Log into Microsoft 365 Copilot Chat. Try one prompt. (Aim for “what did I miss in my new inbox this morning, sorted by urgency.”)
- Day 2-3: Install your four memory entries (role context · tone preference · format preference · counterparty list).
- Day 4-5: Run the “find me the latest version of [each major strategy document]” prompt for each of your area’s foundational documents. Read each.
Week 2 — Calibrate
- Set up your first Notebook. Topic: whichever ongoing prep cycle is most active for you right now (board prep / customer review / strategy refresh).
- Try one Refine-this prompt on a real email you would otherwise have struggled with.
- Try one pre-meeting brief for a meeting with someone you don’t know well.
- Have a 30-minute conversation with your CIO about your tenant’s Copilot governance posture. Use the five questions from the trust section above.
Week 3 — Compound
- Set up your first scheduled prompt. Recommended: Monday morning week-ahead briefing.
- Try Researcher once. Pick a topic you’d otherwise delegate to a junior analyst.
- Try Analyst once. Pick a spreadsheet you usually rely on someone else to model.
Week 4 — Reflect
- Review what stuck. What did you keep doing? What did you abandon?
- Save your three most-used prompts to the Prompt Gallery (or a OneNote section).
- Block 30 minutes a week going forward to try one new pattern.
Month 2 — Build compounding habits
- Sponsor your first custom agent. Recommended: the Daily Briefing Agent. Brief your CIO or partner on the spec.
- Try a Pages-based co-authored document with your ELT.
- Set up your monthly briefing scheduled prompt.
Month 3 — Embed
- First custom agent goes live. Begin tuning based on actual use.
- Run a quarterly governance check with your CIO using the five questions.
- Share one specific Copilot use in an all-hands or leadership meeting. Model the behaviour.
Three things to NOT do in your first 90 days
- Don’t try to learn everything in one weekend. The judgement compounds over time, not in a sprint.
- Don’t use Copilot for any personnel decision about an individual. The hard line is non-negotiable from day one.
- Don’t outsource Copilot adoption to IT. Your visible sponsorship is the most powerful adoption lever you have.
What changes after 90 days
If you’ve worked through the above, by day 91:
- You’ll have at least one scheduled prompt landing in your inbox automatically.
- You’ll have at least one Notebook for an ongoing prep cycle.
- You’ll have one custom agent in production (or in build).
- Your team will have seen you use Copilot visibly and they’ll have started.
- Your inbox-to-decision time will be measurably shorter.
- You’ll have an opinion on what’s next (and a CIO/partner conversation about how to get there).
That’s the compounding. The work is in the first 90 days. The payoff starts on day 91.
Three prompt patterns for executives
There are a hundred different prompt frameworks online. For executives, three patterns will cover most of what you need. Memorise these. The others are optional refinements; these three cover most executive work.
Pattern 1 — Brief me
Summarise [source] into [number]-[unit] briefing for [audience] who [context]. Use [N] sections: [list of sections]. [Format constraint].
Why it works: It specifies audience, time budget, structure, and format. Vague brief-me prompts produce vague briefs. Specific brief-me prompts produce briefs you can read on the way to a meeting.
Use it for: Board paper digests, briefing notes, pre-meeting reads, “explain this regulatory change to me” requests, customer email triage.
Pattern 2 — Refine this
Refine [content] for [audience]. Specifically: (1) [structural change], (2) [tone change], (3) [content addition or removal], (4) [length constraint], (5) [voice constraint].
Why it works: It treats Copilot as a refiner of your voice, not a replacement for it. The numbered list of specific changes is what separates “refine” from “rewrite”. Refinement preserves your judgement; rewriting deletes it.
Use it for: Town hall messages, leadership emails, board commentary, regulatory disclosures, customer responses.
Pattern 3 — Compare options
Compare [Option A], [Option B], and [Option C] across [dimensions]. Use [format]. Don’t recommend — I’ll decide.
Why it works: It explicitly excludes the temptation for Copilot to make the recommendation, which keeps you in the decision seat. The “don’t recommend” clause sounds optional. It isn’t — without it, Copilot will default to making a recommendation, and that recommendation will subtly anchor your thinking.
Use it for: Strategy options, vendor selection, hiring trade-offs, organisational structure choices, capital allocation decisions.
💡 Tip — Save your best version of each of these three prompts to the Prompt Gallery in Copilot Chat (or to a OneNote section called “My Copilot Prompts”). The third version of a great prompt is usually 10x better than the first — saving it means tomorrow starts from “good”, not blank.
Trust, governance, accountability — the essentials
For the deeper governance picture (AI Centre of Excellence pattern, five quarterly governance questions, Microsoft Customer Zero lessons, when NOT to use Copilot), see the Trust deep-dive section.
The conversation every executive needs to have with their CIO, and the conversation every CIO is glad when their CEO initiates rather than waits for.
What to ask your CIO
Five questions are the start of every governance conversation that matters:
- Where does our Copilot data live? Data residency for prompts, responses, and grounded data. Confirm regional storage if that matters in your sector.
- Who can see my prompts? Compliance team, IT, legal — under what circumstances. The answer should be “for legitimate purposes under documented governance, not casually browsed”.
- What’s our AI Use Policy and how was it socialised? Every organisation needs one. Not having one is now a board-level risk.
- What sensitivity labels are flowing through Copilot, and what happens when Copilot generates output from labelled content? Sensitivity labels should propagate to Copilot-generated outputs. If they don’t, you have a leakage risk.
- How are we monitoring for misuse? Detection of consumer AI tools used with company data, detection of prohibited use cases (hiring decisions etc.), detection of oversharing. Not punitive — culture-setting.
What stays human
The hard line again, said differently: any decision that would land on a leader’s desk for sign-off without AI involvement should still land on a leader’s desk for sign-off with AI involvement. Copilot in the loop changes the time-to-draft. It does not change the accountability.
Specifically, none of the following can be delegated to Copilot:
- Hiring, performance, promotion, termination decisions about individuals.
- Financial commitments to the board, regulator, market, customer.
- Safety decisions in operational contexts.
- Anything a regulator would expect human reasoning behind.
When NOT to use Copilot
Three categories where Copilot adds risk without adding value:
1. Disciplinary or grievance proceedings. AI in the loop on an individual employee matter creates a defensibility problem. Use Copilot for general background reading. Do not use it for analysis of the specific case.
2. Market-sensitive timing decisions. Trading update timing, results day announcements, M&A disclosures. The marginal value of AI assistance is small. The risk if a prompt or output is later subpoenaed is real. Default to human-only handling.
3. Anything where you wouldn’t want a transcript of your reasoning in a regulatory submission. Copilot prompts and responses are stored. If you’d be uncomfortable with the transcript being read back later, that’s a sign the conversation should happen elsewhere.
⚠️ Heads up — The convenience of Copilot makes it tempting to use for situations where the risk-reward is wrong. Discipline yourself out of the temptation. The whole field guide is calibrated for use cases where Copilot creates value without creating exposure. Stick to those.
What executives must model for the organisation
The single biggest driver of Copilot adoption success across organisations I’ve worked with is not training budget, change management plans, or technical readiness. It is the visible behaviour of the executive team.
What to model — five behaviours
1. Use it visibly. In all-hands meetings, in leadership team meetings, in the way you talk about your week. “I used Copilot to…” mentioned twice a week, casually, does more for adoption than three change-management workshops.
2. Talk about your failures. When a Copilot output got it wrong and you caught it, share that openly. The single most damaging adoption pattern is the perception that the executive team uses Copilot perfectly. Most people learn it’s safe to try things imperfectly only when they see imperfection from the top.
3. Adopt the language deliberately. “Drafts” not “writes”. “Helps me think” not “thinks for me”. “Citations” and “sources” mentioned often. Language carries norms.
4. Refuse decisions that should be human-only. When a team member presents a recommendation and the chain of reasoning is “Copilot said…”, push back visibly. Restore the human chain of reasoning. Do this once a quarter publicly and the cultural norm sets.
5. Acknowledge the people Copilot does NOT replace. Your CFO is more valuable in a Copilot-enabled organisation, not less. Your exec assistant is more valuable, not less. Your Head of Strategy is more valuable, not less. Say it out loud. Often.
What to NOT model
1. AI cheerleader without limits. The executives who land worst with their teams are the ones who present Copilot as the answer to everything. Teams notice the over-claim. Trust erodes.
2. AI sceptic without engagement. The executives who leave their organisations exposed are the ones who say “I prefer the old way” without engaging. The organisation will adopt with or without you. Without you, the adoption pattern will be uneven, ungoverned, and culturally undirected.
3. Quiet adoption. Executives who use Copilot privately but never speak of it leave a vacuum. The vacuum gets filled by middle managers winging it. Speak of it.
💡 Tip — If you’re new to Copilot yourself, the most powerful single move you can make is to set up a recurring 30-minute weekly “what I’m trying” session with your exec team. Each leader brings one prompt they tried that week — what worked, what didn’t. Twelve weeks of that builds genuine fluency across the leadership layer.
30-day rhythm for executives
Most adoption advice for Copilot is calibrated for general users. Here is what works specifically for executives, in 30 days.
| Day(s) | Practice |
|---|---|
| 1-3 | Open Microsoft 365 Copilot Chat at start of day. Try one Brief-me prompt on whatever’s on top of your inbox. No goal beyond reps. |
| 4-7 | Add the Refine-this pattern. Use it on one email, one Word doc, one Teams message you would normally have agonised over. |
| 8-14 | Set up your first Notebook. Use it for the next thing on your calendar that has 3+ source documents (board prep, exec offsite, customer review). |
| 15-21 | Try Researcher once. Pick a topic you’d normally delegate to a junior analyst. Give it a structured brief. Read the output. Validate two sources by hand. |
| 22-28 | Try Analyst once. Pick a spreadsheet you usually rely on someone else to model. Ask it a scenario question. Show the output to that someone else — get them to audit your workings. |
| 29-30 | Reflect on what stuck. Save your three most-used prompts. Block 30 minutes a week going forward to try one new pattern. |
Most executives I coach are noticeably faster by day 14 and habitually faster by day 30. Skip the 30-day arc — try to “learn it all in a weekend” — and you’ll learn the apps without building the judgement. The judgement is the bit that matters.
⚠️ Heads up — The single most common 30-day failure mode is using Copilot only inside Outlook or only inside Teams meetings. Both are useful, but neither captures the strategic value. Force yourself to spend the first week in Copilot Chat with grounded files. That’s where executive use diverges from individual-contributor use.
Where to next
You’ve made it to the end. A few suggestions for what to do this week.
Read in this order if you want depth:
- The Prompt Engineering Field Guide — for the four-block framework that underpins every prompt in this guide. 25 minutes well spent.
- The Persona Playbook — for the role-specific patterns your direct reports (or your team) will be reaching for. Helps you coach them better.
- The Cowork guide — for the new autonomous multi-app Copilot agent (separate from Researcher and Analyst). Includes six ready-to-try Cowork prompts and the Frontier enrolment specifics.
- The SharePoint oversharing controls guide — for the conversation with your CIO about information governance in a Copilot-enabled tenant.
- The Copilot for People Leaders Field Guide — companion piece for the managers in your organisation. Send your direct reports (and their direct reports) the link.
Try this week:
- Pick one upcoming board paper or strategy document. Run the Brief-me prompt against it. Compare to your own read after the fact. Calibrate.
- Set up a Notebook for your next significant prep cycle.
- Schedule a 15-minute conversation with your CIO using the five governance questions above as the agenda.
- Tell your exec team you’ve read this. Ask them to read it. Compare notes at the next leadership meeting.
Block 30 minutes a week. Forever. The leaders who get the most out of Copilot are not the ones who took the longest course. They are the ones who blocked 30 minutes a week to try one new thing, and kept doing that for six months.
Field guide v4 · 2 June 2026 (executive edition after split from combined people-leader guide; SME corrections applied across both posts). Microsoft 365 Copilot ships changes monthly — patterns hold, feature names may shift. Spotted something off? Let me know and I’ll update.
Frequently asked questions
The most common questions I get from executives when I sit down with them for their first Copilot conversation.