Harder than creating video manuals is embedding them on the floor. Especially when starting from zero, a mistake can turn it into "unwatched video collection". Video manuals are not "materials" but "systems".

Here are Tips for embedding them, in practical order.

① Don't aim for perfection at first (start with 3 videos)

If you try to systematize from the start, you'll get stuck. First, create just 3 from "easy to adopt" ones like these.

• Top 3 frequently asked work tasks
• Tasks where new staff always stumble
• Tasks with frequent mistakes

At first, think of it as an "experiment" - that's OK.

② Gather "what to create" from frontline voices

There's no need for the admin to handle alone "which SOP to create next". You don't need to start with heavy work like Skills inventory.

Using Dive's "Desired procedures", staff themselves can post "I want this kind of SOP" and "I had trouble here". Everyone including new staff, View-only users, and Guest members can post, and those who want the same thing can show support by marking "Want".

• Post what you want or what you struggled with seeing, right where it happens
• "Want" votes collected in order = you can decide which SOP to create in the order truly needed
• When you Link the Completed SOP to the request, the person who posted gets a "Responded" Notification

Starting from frontline "want/struggled" reduces unused SOPs. See How to use Desired procedures (Idea notebook) for details.

③ First create one success story

If you try to expand to everyone at once, you'll fail. First, have one person (honest type, young staff, growth-minded) thoroughly use it.

"When I watched the Video, I learned fast" — this success story becomes the best spreading power.

④ Don't have just one creator (build a creation culture)

At first, the implementer can Create - that's OK. But if just one person keeps doing it, you'll get stuck. The ideal state is this.

• Department staff Capture themselves
• "If there's Improvement, Capture again" culture
• Common understanding that "Video = asset"

Tips: "Lower the capture barrier to the extreme (smartphone, screen recording is enough)" and "just Upload after Capturing - that's OK".

⑤ Integrate into work workflow (create "you lose if you don't watch" state)

The biggest reason for non-embedding is "doesn't matter if I don't watch".

❌ "Watch the Video if you don't understand" → doesn't watch

⭕ "Confirm the Video before asking"
⭕ "Training assumes Video viewing"
⭕ "Practice after Video viewing"

That is, it's essential that Video becomes part of the work workflow.

In Dive especially, AI can be used to reduce capture load and editing time. Even if you don't Capture or prepare Videos in detail, if you prepare one continuous Video, Analysis of explanation content and people's movements splits the Video by step. Based on explanation content, it also Create titles and Description. Please try it.