The Loom-Based SOP Library: Training Teams Without Writing Documentation

Written SOPs are almost never used. I have spent enough time in operations to say this with reasonable confidence. Teams write them during onboarding pushes, often under pressure from a process audit or a new hire. They sit in Notion or a Google Drive folder. They go out of date within 60 days because the tool changed or the process changed or someone found a faster way to do it and updated their personal practice without updating the document. When a new hire looks for guidance on how to do a task, the written SOP either does not exist or describes a process that no longer matches what actually happens.

The approach here was different from the start, and partly accidental. The team was distributed and remote, so synchronous training was impractical. When someone needed to learn a task, the trainer recorded a Loom while actually doing it. Not a prepared, scripted walkthrough, but the real task in real time, with narration explaining the decisions as they came up.

The recording became the SOP, and the pile of recordings became the library.

How the library works in practice

Every Loom gets a name that includes three things: the client or context, the task, and the date. Not “FBA Transfer” but “FBA Transfer Thought Process - 2021-08-30.” Not “Buy Box” but “BB% Explained - a brand - 2021-05-17.”

The naming convention matters more than it sounds. After three years of consistent recording, the library has hundreds of videos. The only way to find a specific one without watching everything is to search by a recognizable name. Generic names leave you with an archive nobody can search. Specific ones are the reason the library is usable at all.

Videos addressed to a specific person work better than generic training recordings. “For the teammate: Remote Fulfillment in California” tells the teammate this one is for her. She is more likely to watch it closely, and more likely to ask follow-up questions, than if it were addressed to no one in particular. Naming her also ties the video to a real context. Her situation will not be identical to the next person who has to learn remote fulfillment, but the video works through the decisions in her actual account, which makes it more useful than a generic overview.

The trigger for making a Loom

Any task a team member asks about more than once gets a Loom. The rule is that simple. The first time someone asks, you answer the question. The second time, you record a Loom while you answer. The third time, you send them the Loom.

This sounds like a low bar, and it is. It means the library grows out of actual pain points instead of someone’s idea of what should be documented. The tasks that get recorded are the ones people genuinely get confused about. The ones that never get recorded are either simple enough that nobody asks twice or so rare that the confusion never comes back around. Both are fine.

What the library looks like after three years

After three years of consistent use, the Loom library covers most of what an Amazon FBA management team actually does: metrics posting, buy box management, FBA transfer thought process, inventory planner walkthroughs in multiple parts, boat shipment forecasting, flat file uploads, coupon creation, IPI report sharing, BFCM planning. It also covers judgment tasks that are hard to encode in a written SOP: how to think about a purchase order decision when sales velocity is changing, how to prioritize between two out-of-stock SKUs when you cannot restock both immediately.

The thought process recordings are the most valuable ones. A step-by-step SOP for creating an FBA shipment is useful but becomes obsolete when Amazon changes the shipment creation workflow, which it does several times a year. A recording of someone working through the decision of how much inventory to send, reasoning out loud about sell-through rate and supply limits and warehouse capacity, remains useful even when the interface changes because the decision logic does not change.

Where the library has gaps

The library’s weakness is searchability. Loom’s search works on video names and descriptions, not on transcripts, at least in the standard plan. A video about the FBA transfer thought process may be exactly what someone needs, but if they search for “how much to send to Amazon” they may not find it.

The gap worth closing: pair each significant Loom with a short written checklist in Asana or Notion. Not a full rewrite of the video, just the five to ten steps it covers, with the Loom linked at the top. The checklist gives you something searchable, and the Loom holds the depth. Someone can use the checklist to confirm they followed the process, then watch the Loom if they hit something they do not understand.

After the first year, repeated questions from the same team members dropped off noticeably. Not because anyone got smarter, but because the answers now existed, were findable, and actually matched how the work was currently done.