What is the best way to record an SME performing a complex software task?
The best way to record an SME performing a complex software task is to use a workflow capture tool that runs silently in the background while they work normally. Glyde captures browser actions — clicks, navigation, text input — and generate a structured step-by-step guide automatically. The SME spends zero extra time beyond performing the task itself.
What methods are available for recording SME workflows?
| Method | SME Effort | Output Quality | Best For |
|---|---|---|---|
| Workflow capture tool | None — just perform the task | High — structured steps with screenshots | Browser-based processes |
| Loom recording | Low — hit record and narrate | Medium — requires post-processing | Context-heavy explanations |
| Live shadowing | Medium — needs to schedule and explain | Low — relies on observer's notes | Physical or multi-tool processes |
| Written documentation | High — must write from scratch | Variable — depends on writing skill | Architecture decisions, policies |
How do you set up a recording session with a busy SME?
The key is making the process invisible to the SME's workflow:
- Install the tool beforehand — Have IT or the documentation lead set up the Chrome extension on the SME's browser
- Pick a real task — Don't ask them to simulate. Wait for the next time they need to perform the actual process
- Hit record, then get out of the way — The SME performs the task exactly as they normally would
- Review the output — The tool generates a draft SOP. Have someone else review it for completeness and add context
- SME validates — A 5-minute review of the generated guide, correcting any misinterpretations
For complex tasks that span multiple tools (browser, terminal, desktop apps), combine a workflow capture tool for the browser portion with Loom for the rest. Stitch the outputs together in a single Notion or Confluence page.
The fundamental principle: capture during work, not about work. SMEs are willing to be recorded doing their job. They're not willing to sit down and write about it.
This answer is part of our guide to capturing and preserving team knowledge.