Copilot for Executive Assistants
Introduction
In a previous article (A role-based approach to learning to use Microsoft Copilot), we explored what role-based Copilot learning would look like. We used the role of Executives as an example and while every role needs AI skills, not everyone needs the same ones. The work is different. The pressure is different. The risks are different.
And there’s a deeper truth here: knowing how to use a tool isn’t the same as building real capability. That only happens when AI is combined with human judgment, curiosity, and context. That’s what turns speed into something genuinely useful.
Since publishing that edition of the newsletter, my team and I have been building role-based learning journeys for Copilot. Most recently, we have focused on Executive Assistants (EAs). They’re a great example because their work is practical, fast-moving, and often invisible, and it’s where the gap between AI in theory and AI in daily work becomes obvious.
What we keep hearing is this: once people understand the basics (prompting, responsible use, ethical AI) the next question comes quickly:
How does this actually help me in my day-to-day work?
That’s where role-based learning matters. It removes the guesswork. Instead of experimenting endlessly, people can see how AI fits into the work they already own, with constraints and all.
The EA world of work
Stepping into a world of work that you’ve never personally done is humbling. That’s been true for me as I’ve learned more about Executive Assistants (EAs).
What I have discovered is that EAs operate at the centre of communication, scheduling, and decision flow. They help Executives stay focused while everything around them keeps moving.
But their reality also exposes some of AI’s current limits. Many work in delegated inboxes and calendars, where tools like Copilot don’t always carry over seamlessly.
That matters. When an EA writes on behalf of an Executive, tone isn’t optional, it’s risk management. So, EAs try to find the way around technology. Some use tone-of-voice guides to help Copilot draft more accurately. Others align personalization settings, where possible, to reflect the Executive rather than the EA.
Meeting coordination is another example. Copilot and Teams features can be powerful, but only if meetings are set up in the right way. That means role-based learning needs to include not just how to use the tool, but how to prepare the environment so it works.
One area where AI already adds clear value is meeting follow-through. For example:
- Using structured templates to turn AI-generated notes into polished outputs
- Capturing suggested follow-ups and tracking them in a standing Planner plan of the team
- Bringing clear status updates back into leadership discussions
EAs are also starting to use Copilot agents for repeatable workflows like coordination, admin tasks, or event planning. Instead of starting from scratch, they can rely on structured processes and focus on oversight and decision-making.
And that’s the point. In high-pressure moments, like coordinating a senior visit, AI isn’t there to make things look better. It’s there to keep things clear, timely, and under control.
Final remarks
Role-based learningisn’t just a nicer way to train people: it’s what makes AI usable in real work.
The human brain needs context so when learning reflects people’s actual day-to-day, they don’t have to translate generic features into high-stakes situations on their own.
Relevance is very important and is what makes adoption sustainable. For roles like EAs, that difference is critical. So, if you’re building Copilot capability, don’t just learn features. Focus on real moments of work.
Let me close with this question:
Where, in the work you already do, can AI create more clarity, more steadiness, and less mental load?
And if you are an EA yourself and are interested in some inspiration for finding answers to that question, I can share some in-depth Copilot scenarios for EAs that I’ve helped map out. Let me know in the comments and I’ll share the links. 😊
About the author
Magnus Fälth
Copilot Coach
M, Fälth (06/05/2026) Copilot for Executive Assistants. (2) Copilot for Executive Assistants | LinkedIn
