Monica Cordoba | Learning Design & Program Operations Portfolio

Step by Step Toolkit

A facilitation manual for running polished, highly interactive sessions in Microsoft Teams.

Something about yourself

Facilitating Effectively with Teams Toolkit

The idea

Virtual facilitation loses something the moment you can't read a room's body language. I built this manual to close that gap: a step-by-step reference covering everything from webcam setup and engagement techniques to the exact clicks needed to run breakout rooms, Whiteboard, live polls, and Mentimeter inside a Teams meeting.

It's the kind of document a facilitator opens the night before a big session, and a new team member uses to get fully up to speed without needing to shadow anyone.

What's inside

• Facilitation best practices: how to maintain

engagement, read the room, and set expectations with

participants when body language isn't available

• Professional setup: camera placement, lighting, framing,

and audio, so every session looks and sounds polished

• In-meeting mechanics: screen sharing,

presenter/participant roles, and troubleshooting, all

illustrated with annotated screenshots

• Interactive tools, step by step: pre-building and

launching Whiteboards, Polls, and Mentimeter activities,

exactly as they're used in a live session

Why these two sections

This is a working internal document, so what's shown below is a curated excerpt rather than the full manual. I chose two sections that show different sides of the work.

If a client wants the full toolkit for their own team, I build a fresh, client-specific version as part of an engagement.

Maintaining Engagement — Is the facilitation philosophy behind the toolkit: how to read a room and hold attention when body language isn't available. It's the thinking, not the clicks.

Pre-making and securing a Whiteboard — Is the operational side: building a reusable asset ahead of time, then locking down exactly who can access and edit it before a session goes live. It's the same instinct that shows up in how I structure any recurring program: build it once, make it safe to reuse.