Choose one update you can support
Pick a product change, lesson or other point you can explain from this week’s work. Use only material you can share and identify any screen detail or name that needs review before publication. The requests below are instructional examples to adapt to your available footage, not tested recipes. Upload the source first, replace the placeholders, and review every change. The editing CTA opens editor Home; copy the request into your project after setup.
Prepare the explanation and its supporting evidence
Record the point, one factual example and the closing. If a screen demonstration helps, record the actual result and keep it available in the project. The evidence should support what you say; a diagram or screenshot is not a substitute for an unsupported outcome.
Reuse a written brief, then supply this week’s details
Keep a written brief with these fields: topic [actual topic], supporting example [recorded passage or screen action], names [correct spelling], caption preference [desired style], and destination [intended viewing size]. Reuse it outside Cubix, then adapt it to this recording. This is a written process, not an account-level saved-template promise.
Replace the topic and source-word placeholders with this recording’s details. Check that the supporting explanation remains, captions are restrained as intended, and names and pauses are correct.
Keep a supporting screen demonstration readable
Upload the screen recording. Replace [actual source words] with its narration and [specific visible result] with the control or result viewers need to see. Choose framing from the source and intended screen size.
Copy and adapt this request after uploading the relevant footage.
Check the entire demonstration at the intended viewing size. Use the available crop/zoom controls for a correction if needed; keep a wider view when a crop hides context.
Review the exceptions in this recording
A recurring brief should not remove a necessary thinking pause or cut through a technical term. Review the first pass and make a bounded follow-up correction where needed. Check any number or claim against the evidence you used.
Keep a simple recording and review ledger
Use a separate note or sheet to record the topic, available evidence, recording needed, editing exception and review status. The two sample rows are fictional; their timings are examples, not a recommended duration for every update.
| Week/topic | Available evidence | Recording needed | Editing exception | Review status |
|---|---|---|---|---|
| Week 1: product walkthrough | A permitted recording of the actual UI | Founder explanation plus screen action | Keep the required control readable | Pending playback and claim review |
| Week 2: lesson learned | The example the founder can describe accurately | A spoken reflection | Preserve a pause that separates the explanation | Pending review of the example and captions |
| [Week/topic] | [Supporting source] | [Recording needed] | [Exception to the brief] | [Reviewer / unresolved issue / status] |
- Name the actual exported file and record its destination.
- Watch it with sound and check names, captions and screen details.
- Record which version was reviewed; rewatch a changed export.
- Upload or publish separately after your review.
✖ Covering multiple unrelated topics in a single weekly founder video.
Why it fails: Diffuse topics reduce viewer engagement and weaken narrative clarity.
✔ Better approach: Focus each weekly video update on a single substantiated core topic.
✖ Over-editing speech pauses, making founder delivery sound rushed or robotic.
Why it fails: Eliminating all silence removes authentic executive tone and cadence.
✔ Better approach: Instruct edit prompts to preserve natural thinking pauses around key statements.
✖ Publishing unverified metrics or financial projections in video updates.
Why it fails: Unchecked claims create compliance risks and damage company trust.
✔ Better approach: Audit all spoken numbers and timeline claims against internal company data.
Start this editing workflow in Cubix
Adapt a written brief to this week’s footage, review the exceptions, and finish your founder update.
Editing workflows in Cubix
Frequently Asked Questions
Common questions around this editing workflow.