Future-Proofing Your Support Visuals
summary
Support visuals use concrete recipes: save six files per video — thumbnail, captions, editable ScreenFlow project, separate audio, script, and exported video — so only the broken piece gets remade. Mobile capture uses BrowserStack App Live and screenshots and GIFs come from CloudApp. Measure work: 37 videos × ~6 hours ≈ 222 staff hours, six visualizers → ~40 hours each, planned with Airtable database and evidence-based scheduling. Style guide locks two fonts and five colors to cut churn.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:24YNAB's Four Rules
- 4:13Tools We Use
- 6:536 Files for Every Video
- 7:56Scripts
- 9:142 Files for a GIF
- 10:11Maximize Your Time
- 11:05Modular
- 11:46How Long Does it Take?
- 12:57Staffing the Releases
- 14:18Does This Need to Be Remade?
- 17:55Elastic
- 18:33Hurricane Sally
- 22:47Example Staffing Plan
- 26:11Style Guide: Visuals
- 28:07Style Guide: Language
- 29:17Style Guide: Distribution
- 29:33Your Team is Your Audience
related talks
45mDesign Tools and Handoffs*
40mGraphic Relief: Beyond Flowcharts and Screenshots
46mMastering AI Video Creation: Simplifying Complex Products for Business Success
49mDesign Tools - Closing the Gap Between Design and Development
33mVisual thinking - simplify complex
19mBehind the system: A showcase of files that inspire us
36mDesign Develop Deploy!
40mCreating illustration Systems that Work for Everyone