How can a remote team lead document a new software rollout without hosting a mandatory live training?
Record yourself performing key workflows in the new software using a workflow capture tool. Create a guide for each task the team needs to learn. Share the guides in Slack or your wiki with a checklist: "Complete these 5 guides this week." Team members follow the visual steps at their own pace, in their own time zone. No mandatory Zoom call needed.
How does async training compare to live training?
| Factor | Live Zoom Training | Async Guide-Based Training |
|---|---|---|
| Scheduling | Must find time that works for all time zones | Team completes on their own schedule |
| Attention | Participants multitask during the call | Self-paced — higher engagement |
| Retention | Forget details within 24 hours | Reference the guide whenever needed |
| Absent team members | Miss the training entirely | Access the same materials anytime |
| Update process | Re-host the training session | Update the guide |
| Preparation time | Build slides, rehearse | Record the workflow in real time |
What is the rollout workflow?
- Identify the 5-10 key workflows in the new software
- Record each workflow with Glyde — takes 5 minutes per task
- Organize guides in a Notion page or Confluence space titled "New Tool Training"
- Share in Slack with a message: "We're switching to [Tool]. Complete these guides by Friday."
- Add a completion checklist — Team members check off each guide as they finish
- Hold a 15-minute Q&A after the deadline — Address questions only, no re-demonstration
How do you handle questions?
- Create a #new-tool-questions Slack channel — Team posts questions as they follow the guides
- Add answers to the guides — If multiple people ask the same question, add a callout to the relevant step
- Record additional guides for edge cases that come up during the rollout
This approach scales to any team size. Whether you have 5 people or 50, the same set of guides works for everyone.
This answer is part of our guide to screen recording to documentation.