pre-production

Install the tool in a sandbox directory and run four escalating tests: sanity, stress, self-healing, and a real-workflow test matching your actual use case. Document which tests pass, where the demo-worthy moments are, and make a go/no-go decision before recording.

Define the end outcome first, explore freely with trial and error, then strip everything down to the minimal steps a fresh user needs. Write each step with a plain-language WHY, then verify the guide reproduces cleanly multiple times on a fresh setup.

Yes. Test on the exact setup used for recording, such as a Hostinger VPS for VPS videos or localhost for Mac recordings. Steps verified in one environment can fail in another, causing on-camera surprises.

Open with the payoff in the first 15 seconds, state the problem and agenda, crush objections early, then walk through setup and the main demo with the WHY behind each step. Weave sponsors natively into the workflow and end with a recap and call to action.

Skip vetting only for pure build or use-case videos where the tool is already proven. For any tool, repo, or product video, the four-test check is essential because the self-healing test usually reveals the key differentiator or a dealbreaker.