How I Use Microsoft Copilot as a Manager (Without Letting AI Do the Managing)

Some meetings arrive with a beautifully prepared agenda.

Others arrive as seven messages, three half-finished thoughts and the knowledge that there is one subject everybody is carefully avoiding.

Before a meeting, I can use AI to help turn that mental pile into structure.

I might give it my non-sensitive notes and ask it to identify the themes, separate decisions from discussion points and suggest questions that would help us get underneath the issue rather than simply talk around it.

The output is not the agenda. It is material for me to challenge.

What is missing? Which question is too generic? What does this group actually need from me? Where am I making an assumption?

That last human pass is the important one.

Useful prompt shape: “Here are my notes for a meeting. Group them into themes, identify what appears to require a decision, and suggest five questions that would help the group move from describing the issue to understanding it. Do not invent facts that are not in my notes.”

Meeting notes are only useful if something happens because of them.

After a meeting, AI is good at helping me separate the conversation into a few practical categories: What did we decide? What still needs a decision? Who appears to own the next action? What needs communicating elsewhere? What is still ambiguous?

The last question is often more valuable than the action list.

A polished summary can create the illusion that a messy meeting was clearer than it really was.

So I specifically want AI to surface uncertainty rather than quietly smooth it away.

Then I check the output against my own notes before anything is shared.

Managers spend a surprising amount of time holding several versions of the same problem in their heads.

There is the process version. The people version. The deadline version. The political version. And usually the version somebody believes is “just a quick change”.

This is one of my favourite uses of AI: asking it to help me look at the same information through different structures.

What are the decisions, dependencies and risks? Which parts affect people directly? What questions remain unanswered? What would this look like as a sequence rather than a list? Where are two pieces of information contradicting each other?

It does not remove complexity.

It makes the complexity easier to see. That is a very different thing.

I do not particularly need AI to make my emails sound more impressive.

I do find it useful for testing whether communication will land the way I intend.

Before sending something important, I can ask: What could be misunderstood here? Which sentence contains an assumption? What questions is a reader likely to have after reading this? Does the action I am asking for appear early enough? Rewrite this in plain language without making it colder.

That is much more useful to me than “make this professional”.

Management communication often fails because the sender knows too much. You unconsciously fill in context that the reader does not have.

AI can be a surprisingly useful first reader.

I still decide what I want to say.

Change is where I am particularly careful about the boundary.

AI can help me prepare. It cannot have the conversation for me.

If a change is likely to create questions or resistance, I can use a fictionalised or non-sensitive description of the situation to explore what someone might need to understand.

What could create uncertainty? Which questions are likely to be practical and which are really about trust? What information would support awareness of why the change is happening? What might someone need before they are ready to discuss how?

That can help me prepare better questions.

But I would never want to walk into a real conversation holding an AI-written script and simply perform it.

People notice when you are not actually listening.

I do not think managers need an enormous prompt library.

I think we need a repeatable way of giving AI enough context to be useful.

Mine is essentially: Context (what is happening?), Role (what perspective should the AI take?), Task (what exactly do I want it to do?), Boundaries (what must it not assume, invent or change?) and Output (what form would make the result easiest for me to review?).

The example below shows how that sounds in practice. It is far more reusable than memorising a clever sentence somebody posted on LinkedIn.

This matters more than the workflows.

I do not ask AI to decide whether somebody is performing well.

I do not ask it to tell me what an employee “really means”.

I do not put sensitive HR situations into it simply because summarising them would be convenient.

I do not outsource difficult feedback.

I do not let an AI-generated summary become the official truth when I was in the room and know the conversation was more nuanced.

And I do not confuse a plausible answer with a correct one.

The manager remains responsible.

That is not an unfortunate limitation of AI. It is the job.

The test I keep coming back to is simple: did using AI give me more capacity for the part of the work that actually needed me?

If it saved fifteen minutes and I used those fifteen minutes to read another AI-generated summary I did not need, probably not.

If it helped me walk into a meeting with a clearer question, notice an unresolved issue earlier or spend less time staring at a blank document before writing something difficult, yes.

That is the version of AI at work I am interested in.

Not artificial management. Better-supported managers.