โ† Operator Hour
Season 1 ยท Episode 3 ยท Public recap

Reclaim your morning.

The first hour of the day should not disappear into sorting messages. We tested a routine that reads the noise first and gives you a short brief instead.

Recap

The live session used a sanitised inbox and calendar inside a controlled Microsoft environment. The task will be familiar: find what genuinely needs attention, leave uncertain items alone, and prepare a brief before the day starts.

Rules can move messages around. A routine can explain why something matters, but only if its judgement has clear boundaries. We made the safety instructions simple enough to read in one breath.

The safety ruleDraft freely. Send nothing. If confidence is low, leave the item where a person will see it.

The result was a short morning brief showing what had changed overnight and what needed action. It flagged the meeting that required preparation and the reply still waiting. Easy responses were drafted, then held for review.

Scout has moved on since the session. It was internal when this episode ran. Microsoft now documents Scout as a preview available through the Microsoft 365 Frontier program. It can work across local files, browser tasks, and Microsoft 365 data, with approval before sensitive actions. Preview capabilities can change. Read the current overview.

Operator move: pick the inbox, calendar, or project feed that takes over your first hour. Ask for one brief before automating anything. Then read it carefully and see what the agent gets wrong.

Take it home

Start with a read-only routine.

Ask the agent to summarise and prioritise. Keep every external action behind your approval until you have seen enough to trust the routine.

Do the exercise

Build a read-only morning brief

Use the synthetic file below, or use your own connected mail and calendar only when the assistant is approved for that data.

15 minutesRead-only first
Download synthetic morning input
  1. Download the sample into an empty folder as sample-morning-input.md.
  2. Open your assistant in that folder and paste the prompt below.
  3. Check whether it separates urgent work from automated noise.
  4. Change one rule, run it again, and compare the brief.
Morning brief prompt
Read sample-morning-input.md.

Create a morning brief with:
- What changed since yesterday
- The meeting that needs preparation
- Replies or decisions waiting on me
- The two things I should do first

Separate human requests from newsletters, system alerts, and broad invitations.

For simple replies, draft text for my review. Do not send, move, delete, accept, or decline anything.

End with:
1. What you were unsure about
2. Which rule you used for each priority
3. One change that would make tomorrow's brief better
You are done when: the brief names the customer preparation and approval request, while the newsletter and system alert stay out of the priority list.
Keep it safe: begin with read-only access. Sending, moving mail, or changing calendar items should stay behind explicit review.
Resources
๐ŸŽž๏ธ

Public slide deck

The read-only morning routine, fictional example, and safety boundary in seven slides.

open slides
๐ŸŽฌ

Full recording

Microsoft employees can watch the connected inbox and morning brief demo after corporate sign-in.

Microsoft employees
๐Ÿ”Œ

Connected tools lesson

Learn how tool connections change what an assistant can read and do.

public lesson
๐Ÿ”ญ

Microsoft Scout preview

Current public documentation for the preview through the Microsoft 365 Frontier program.

official docs
๐ŸŽฏ

Find your routine

Use the interview to identify which repeated feed is worth fixing first.

Still not a developer. I just stopped letting the inbox decide how my day begins.