TL;DR — Written documentation is still the right home for anything that needs to be precise, searchable and version-controlled. But a lot of useful knowledge — how someone actually approaches a tricky client call, a trick for a tool nobody wrote down, context behind a decision — never gets documented because writing it up feels like too much effort. A 60-90 second video, recorded once and shared with one link, captures that knowledge at a fraction of the effort of writing it, and often communicates it better.
- Short video is best for tacit, hard-to-write-down knowledge — not a replacement for proper documentation.
- A specific prompt ("show how you do X") produces more usable knowledge-sharing clips than an open request.
- Compiling a short library of these clips by topic turns them into a lightweight, searchable resource over time.
- This works especially well for onboarding new hires into undocumented team habits.
On this page
The gap between what is documented and what people actually know
Every team has a layer of knowledge that never makes it into a wiki: the reason a particular client always gets handled a certain way, the shortcut someone found in a tool three years ago, the judgment calls a senior person makes without being able to fully articulate the rule behind them. This is sometimes called tacit knowledge, and it typically does not survive someone leaving the team, because it was never written down in the first place.
The reason it never gets written down is usually effort, not unwillingness — explaining a nuanced process in prose, with the right caveats, takes real time to do well. Saying the same thing out loud while demonstrating it takes a fraction of that time.
Where short video knowledge-sharing works best
- A specific how-to: "show how you handle a difficult client call" or "walk through how you debug this type of issue".
- Decision context: "explain why we do X this way instead of the more obvious Y".
- A tool trick: a 30-second screen-recorded tip for software the team uses daily.
- Cross-team context: someone from another department explaining what they actually need from a handoff, in their own words.
- Pre-mortem or retro insight: one specific lesson from a project, recorded while it is still fresh rather than written up weeks later.
Why this also improves collaboration, not just documentation
A side effect of asking people to explain their own work out loud is that other teams get to see and hear how a colleague actually thinks, not just what they produce. That visibility tends to improve cross-team collaboration on its own — people are more willing to ask a follow-up question of someone they have "met" via a video clip than a name on a wiki page.
Keeping it from becoming clutter
The failure mode for any knowledge-sharing format is a growing pile of clips nobody can find again. Tag or title each clip by topic from the start, and treat genuinely durable knowledge as a prompt to also write it up properly later — video is a fast way to capture and share something, not a long-term replacement for structured documentation where precision matters.
Doing this in Whoosh
Set up an open-ended campaign for the team with a rotating prompt ("this month: share one trick that saves you time"), and let people contribute whenever something comes up worth sharing, rather than only on a fixed schedule.
Start freeFrequently asked questions
Does this replace our documentation or wiki?
No. Use video for things that are hard to write down well or that nobody has gotten around to documenting — keep formal documentation for anything that needs to be precise and searchable long-term.
How long should a knowledge-sharing clip be?
60-90 seconds is usually enough. If an explanation needs longer than that, it is probably better suited to a written doc with screenshots.
Who should be asked to contribute?
Anyone with a specific piece of knowledge worth sharing, not just senior staff — some of the most useful tips come from people closest to the day-to-day work.