4 exercises — agenda-driven Loom openings, pre-meeting watch messages, async follow-ups after recordings, and time management in live online presentations.
0 / 4 completed
1 / 4
You're recording a Loom video to update your team on a migration project. You have 3 main areas to cover: progress, blockers, and next steps. Which opening is best for an async video?
Option B is a proper agenda-driven async video opening:
1. Timestamp the recording: "Tuesday at 2pm" — so viewers know how fresh the information is when they watch later 2. Named sections with timestamps: "migration progress at 0:30", "blockers at 1:15", "next week at 2:00" — makes the video skimmable and respects async viewers' time 3. Total runtime upfront: "about 3 minutes" — the viewer can decide if they have time to watch now or later 4. Explicit permission to skip: "Jump to the section you need" — this is what makes async communication different from sync; engineers will thank you
Why A fails: "Quick update on things" — vague, no structure, no way to navigate
Why C fails: "A lot to cover, let me start from the beginning" — an async video that starts at the beginning with no navigation cues forces everyone to watch the entire recording
Why D fails: "Let me share my screen and we'll go through everything" — no agenda, no timestamps, no runtime estimate
Async video formula: Hi + recording time + [section name at timestamp] × N + total runtime + invitation to skip
2 / 4
You recorded a 15-minute technical overview that stakeholders should watch before Thursday's meeting. Which "watch before meeting" message is most effective?
Option C demonstrates a meeting-prep async message with full context:
1. Specifies runtime upfront: "15-minute overview" — viewers can plan their schedule 2. Connects the video to the meeting action: "the decision you'll be asked to make at 9am is whether to approve the Redis migration" — now the video isn't just "useful content", it's preparation for a specific yes/no decision 3. Provides a minimum viable section for busy stakeholders: "7:00–11:00 (the Redis comparison)" — respects that not everyone has 15 minutes but everyone has 4 minutes 4. Creates a feedback channel: "#arch-review" — gives viewers a venue to ask questions before the meeting, preventing the meeting from being derailed by basic questions
Why A and B fail: "Please watch the Loom" without context — why should the viewer watch? What decision will they make?
Why D fails: "for context" is vague — context for what? A viewer who doesn't watch misses preparation for an important decision
Pre-meeting message formula: Watch this [runtime] [topic] before [meeting time]. You'll be asked to [specific decision]. Skip ahead to [timestamp] if time is short. Questions → [channel].
3 / 4
You gave a recorded presentation for an async audience three days ago. Several people have now watched it. Which follow-up message is most professional?
Option C is a professional async follow-up to a recorded presentation:
1. Addresses both groups separately: "for those who've watched" and "for those who haven't had time" — respects the two different states your audience is in 2. Makes the ask specific and low-friction: "thumbs up/down in the thread or a longer comment" — reduces decision fatigue; people know exactly what action is needed 3. Provides a TL;DR for the unwatched: "replacing Memcached with Redis for the session cache" — a one-sentence summary that lets someone contribute even without watching 4. Sets a collection deadline: "decision summary by Friday" — creates accountability and signals the discussion has a close date
Why A fails: "Did you all watch?" is a passive guilt message without an action request
Why B fails: "Let me know if you have feedback" is so open-ended that most people won't respond — too much cognitive effort required
Why D fails: "Please watch before the deadline" without a TL;DR forces everyone to spend the full runtime regardless of their schedule
Async follow-up formula: For [watched] → specific ask. For [not watched] → TL;DR + timestamp. I'll [synthesise/decide] by [date].
4 / 4
You're presenting a technical demo in a live online meeting and are approaching the 30-minute mark with 10 minutes of content remaining. Which phrase most professionally manages time pressure?
Option C uses the time check → content value → ask → alternative technique:
1. Transparent time check: "We're at 30 minutes — I have 10 minutes left" — names the situation factually without apologising excessively 2. Explains why the remaining content matters: "the security section directly affects Thursday's approval" — gives the group a reason to agree to 10 more minutes 3. Asks for permission rather than assuming: "With the group's permission, could we take it to 40?" — respects the audience's calendars 4. Offers an alternative: "I can send the deployment section in writing" — shows you've thought about both outcomes and aren't demanding more time
Why A fails: "Sorry I'm running over" with no plan — leaves the audience in an awkward position
Why B fails: "Speed through quickly" is the worst outcome — you skip the detail everyone needs, and the content becomes useless
Why D fails: "Skip some slides" without naming which ones creates uncertainty — the audience doesn't know what they're missing
Time management formula: State time status → explain why remaining matters → ask for permission → offer alternative if declined