How do I embed process documentation directly into our team's daily workflows?
Embed documentation into daily workflows by placing SOPs where the work happens — pinned in Slack channels, linked in project management tools, bookmarked in browsers, and integrated into onboarding checklists. Documentation that requires searching through a wiki will not be used. Documentation that appears at the point of need will.
Where should you embed documentation?
| Where Work Happens | How to Embed Documentation |
|---|---|
| Slack channels | Pin the relevant SOP in each team channel |
| Project management (Asana, Monday) | Link SOPs in task descriptions and templates |
| CRM (HubSpot, Salesforce) | Add SOP links to deal stages and workflow automations |
| Support tools (Zendesk, Intercom) | Link guides in macro templates and internal notes |
| Browser bookmarks | Create a shared bookmark folder with critical SOPs |
| Onboarding checklists | Each checklist item links to the relevant SOP |
| Email signatures | Internal signatures with links to team knowledge base |
What is just-in-time documentation?
Just-in-time documentation surfaces the right information at the right moment — when someone needs it, not before. Three implementation approaches:
-
Contextual links — When an agent opens a refund ticket, the macro template includes a link to the refund SOP. They do not search for it; it appears in context.
-
Slack bot responses — Configure a documentation bot (Guru, Tettra) to detect common questions and automatically reply with the relevant SOP link.
-
Tool integrations — Glyde guides can be shared as links that work in any context — Slack messages, task descriptions, email threads, or bookmark bars.
The principle: reduce the distance between "I need to know how to do this" and "here are the steps." Every additional click or search query between those two moments increases the chance the person will skip the documentation and guess instead.
This answer is part of our guide to process documentation.