Scott Brant's tutorial demonstrates how Microsoft 365 Copilot transforms Outlook from a passive email client into an active executive assistant.

The scheduled prompt feature is the bridge from one-time query to persistent assistant. Without scheduling, you must remember to ask Copilot every morning. With scheduling, Copilot proactively sends you a priority email summary before you even open Outlook. This is the difference between using Copilot as a tool and building Copilot as a system.

This eliminates the need to teach users Outlook's multi-step Rules wizard. The natural language approach means any knowledge worker can set up sophisticated inbox automation without knowing where the rules menu is. The key teaching point is that Copilot-created rules are real Outlook rules—they persist, they're visible in Settings, and they work even when Copilot isn't open.

Calendar rules represent a shift from reactive calendar management to proactive boundary-setting. The teaching emphasis should be on identifying which recurring commitments need protection (family time, deep work blocks, specific meeting-free zones) and codifying them as rules rather than relying on manual declination each time. This is particularly valuable for managers and executives who receive many meeting invitations.

Focus time booking addresses the universal problem of calendars filled with meetings leaving no time for actual work. The teaching point is that focus time should be treated with the same priority as meetings—it's a calendar event that protects deep work. Copilot makes this frictionless because you don't need to navigate Outlook's recurrence dialog or set up a manual recurring appointment.

The Work IQ tab is the bridge between Outlook and the rest of the Microsoft 365 ecosystem. It means knowledge workers don't need to context-switch between SharePoint, Teams, and Outlook to compile a status update. The teaching emphasis should be on the workflow: query first, then transform—ask Copilot for the status, then ask it to format the output for the specific communication channel (email, meeting agenda, chat message).

This is the most compound skill in the tutorial—it chains project summarisation, email drafting, and meeting scheduling into a single workflow. The teaching emphasis should be on the natural language chaining: each Copilot response can be the input to the next request. You don't need to re-explain context; Copilot carries the conversation forward. This is where the "executive assistant" framing becomes most concrete.

This is the most "set it and forget it" skill in the tutorial. Unlike prompt-based prioritisation (which requires you to ask), native AI prioritisation runs continuously in the background. The teaching emphasis should be on the customisation step—users should invest time upfront defining their priority criteria, as this determines the quality of sorting going forward. Note the important limitation: this only applies to future emails, not retroactively to the existing inbox.