Just like developing an app – recording a public video is easier when you get incremental feedback along the way.
Good coaching helps you improve the message, delivery, and final edit before too much time is spent recording the wrong thing.
Many people record a full video first, then ask for feedback after.
That often means the issues are found too late:
When recording an important video, use these 4 coaching tips.
Do not record alone if the content matters.
Get someone technical, or someone who understands the topic, to watch and coach you. They can help you check whether the content is correct, clear, and useful.
This is especially important before recording public videos.
Consider writing up a draft script first and sending it to your coach for initial feedback.
For your first version, do not wait until the end to get feedback.
Ask your coach to interrupt you as you go. This helps you improve the video while the ideas are fresh.
They can stop you when:
This feels less natural at first, but it saves time and makes the final video much stronger.
In a perfect world, you'd deliver everything in one clean take. But if you make a few mistakes, you don't want those hiccups to spoil your flow or force you to restart the entire recording.
Instead, mark each mistake with a quick clap. The clap creates a visible spike in the audio waveform, making it easy to find the mistake later when editing in software such as Adobe Premiere Pro.
Without these markers, it's surprisingly easy to miss those moments during the editing process.
After clapping, pause briefly, reset your posture, make eye contact with the camera, and restart the sentence or section.
Do not go straight from raw footage to a polished video.
Once the footage is roughly cut together, share the rough edit with a Subject Matter Expert (SME) - ideally the same person who coached you. Watch it together on a call so they react to and can give you the feedback.
They can catch:
Changes are cheap while the edit is rough. Once the music, captions, and other edits are done, every fix costs the editor real time. This is the video version of a Test Please.
✅ Figure: Good example - Sharing the rough edit with an SME on a Teams call and getting feedback before the final edit.