The product manager video workflow has a third person in it, and nobody schedules them
Quick Answer
A product manager video workflow is the path an enablement team uses to turn a product manager's explanation into a finished video: the PM records what the feature does, someone adds a voiceover, and a third person merges the two. The merge is where most of the calendar time goes.
What does a product manager video workflow look like inside an enablement team?
It has an owner, and the owner does not sit on the enablement team. An enablement lead at a B2B IT asset management company described hers to me:
"people who create videos, who are the owners, like product managers, or POS who create videos and they describe what it is, and we often do a voiceover just to give an example. Well, and then somebody needs to merge those two."
an enablement lead at a B2B IT asset management company
"Somebody needs to merge those two" is a job with no name attached, no slot on a calendar, and no deadline of its own. It inherits whatever deadline the video had.
The first two steps are cheap. The third needs software, a license for that software, and a person who knows where the files went.
Why does the merge step decide when an enablement video ships?
Because it cannot start until both of the other steps finish. The PM can record on Monday and the voiceover can happen Tuesday, and neither of them can finish the video. The person who can is working from a queue that holds other people's videos too.
The same shape shows up whenever the person with the knowledge and the person with the tools are different people. We wrote about the training side of it in when the subject matter expert becomes the bottleneck. Here the expert is available and the editor is the constraint.
Who is waiting on whom in a product manager video workflow?
Five steps, and the person who understands the product owns exactly one of them.
| Step | Who owns it | What comes out | What it waits on |
|---|---|---|---|
| Record the explanation | Product manager or PO | A recorded description of what the feature is | The PM's calendar |
| Record the voiceover | Enablement team | A spoken example over the same material | The explanation existing |
| Merge the two | Whoever holds the editing tool | One video file | Both steps above, plus that person's queue |
| Review | Product and enablement together | Approval or notes | The merged file |
| Publish | Enablement team | A video the field can find | Approval |
What happens to a lecture series when the tooling is old school?
The merge cost repeats. The same enablement lead:
"We use quite old school video tooling and. We created a lecture series as an enablement team"
an enablement lead at a B2B IT asset management company
A lecture series is a format, so every episode runs the same route and pays the merge cost again. Old school tooling makes that a cost per episode instead of a setup cost, because nothing carries from the first episode to the second except the files.
Take one episode. The PM records the explanation and moves on to their actual job. The enablement team adds the voiceover the next day. The episode is complete as content and unfinished as a file, so it joins the queue of the one person who can combine them. When it comes back, the PM hears a sentence they got wrong, and the whole route runs again at full price.
How do you rebuild a product manager video workflow so the merge disappears?
Put both recordings in the same place and make that place the video. When the PM's explanation and the voiceover live in one browser based project built on a brand locked template, there is no file to hand off. The merge stops being a step and becomes the resting state of the project.
That is what Capsule's published numbers describe: 93% lower cost per video, 10x more videos, 8x faster production. Around 30% of creative time goes to tedious tasks, and stitching two takes of the same explanation is exactly that kind of task.
If you are still deciding what the PM should record, start with the types of demo video a product team actually needs, then look at how teams run product demo video in Capsule to see the same route with the handoff taken out.
Count handoffs while you are at it. Every time a video changes hands it enters someone else's queue, and queue time never appears in a production estimate because nobody logs it. The handoff between the PM and the enablement team is real. The handoff to a third person with editing software exists because the first two cannot finish what they started, and that is a tooling decision you can reverse.
FAQ
Who should record a product demo video, the product manager or the video team? Whoever can explain the feature, usually the product manager. The argument worth having is over who finishes the video, because that step sets the ship date.
Why do internal enablement videos take so long to produce? The recorded pieces sit in a queue waiting for the one person with editing software, and that wait never appears in an estimate built from working hours.
Do product managers need video editing skills to make enablement videos? No, and asking them to learn is how the video never gets made. Take the editing step out of the route instead of spreading it to more people.
How do you add a voiceover to a product manager's recording without a separate merge step? Record both into the same project instead of into two files. If the explanation and the voiceover are already in one place, there is nothing to merge and nobody to hand it to.