Using feedback after a Microsoft Teams meeting

You can add Pascal to a Microsoft Teams meeting, and he will join you and provide feedback afterward. That makes an everyday meeting a concrete starting point for reflection, with a manager considering what happened during the conversation and deciding what to practice when a similar situation comes up again.

Make an everyday meeting the starting point

A manager's regular meetings contain the conversations that shape everyday leadership. A discussion about priorities, a project update or a conversation about expectations can each offer material for reflection. Choose a meeting that connects to a leadership behavior you want to understand through practice.

Pascal is an AI coach for every manager: a leadership companion who accompanies them in their meetings and work, and coaches from what actually happened. With coaching in Microsoft Teams meetings, you can add Pascal so he joins the conversation and provides feedback afterward.

Before the discussion, write down what you hope to accomplish with the people attending. That note might describe an agreement you want to reach or an issue you hope to clarify. Treat the note as your own preparation, and use the meeting itself as the shared event you can reflect on later.

This approach gives your reflection a specific setting and purpose. You can think about the subject under discussion, the decisions involved and your own part in the conversation. Those details help you connect a broad development intention to something you remember doing.

Give the feedback a focused reading

After the meeting, make space to read the feedback and consider the conversation it concerns. Start by recalling the meeting's purpose and the moments that seemed important to you. Then look for a connection between the feedback and a behavior you can describe in everyday language.

A useful personal reflection records the situation, your own action and a possible adjustment. For example, a manager might consider how clearly they explained a request or how they invited questions. These are suggested reflection prompts that a manager can use when considering feedback from a real meeting.

Keep your notes anchored in the conversation you remember attending. Include enough detail to recognize the moment and explain why it matters to your work. If a point calls for further thought, turn it into a question you can revisit in your own reflection.

The aim of this reading is a specific practice intention. A manager might decide to state the purpose of a discussion earlier or leave space for a colleague's explanation. Choose wording that describes an action you can recognize during another conversation.

Carry a practice intention into the next conversation

Select a forthcoming discussion where the same behavior would be relevant. Write a short preparation note describing what you intend to do and when it would help. This keeps the connection between feedback and practice visible in your own working notes.

During preparation, picture the part of the conversation where you could use that behavior. You might prepare language for explaining an expectation or a question that invites a fuller response. These are actions a manager can plan independently while deciding how to apply feedback.

After that discussion, reflect on what you tried and what you noticed about your own contribution. Consider whether your preparation helped you act as intended, and describe the circumstances that affected your choice. Keep the next practice intention connected to a situation you expect to encounter again.

This reflection cycle can sit alongside a manager's normal preparation habits. A brief note before the meeting and a considered review afterward give the practice a place in everyday work. The relevant product capability remains straightforward: Pascal can join a Teams meeting and provide feedback after the conversation.

Explain the coaching privacy boundary

Each person's coaching conversations with Pascal stay private. HR and executives see aggregated, anonymized insights, and only for groups large enough to protect anonymity.

Use that wording when explaining coaching to the people involved. A clear introduction helps participants understand the stated boundary around coaching conversations and organizational insights. Keep any further implementation questions together for discussion with the people responsible for the setup.

Key takeaways

• Add Pascal to a Microsoft Teams meeting so he can join and provide feedback afterward.
• Choose an everyday discussion connected to a leadership behavior you want to practice.
• Read the feedback alongside your recollection of the meeting's purpose and important moments.
• Turn your reflection into a concrete action for a relevant forthcoming conversation.
• Explain the coaching privacy boundary using clear and consistent wording.