Production workflow
Plan a diagram before you animate or record it
You do not need a complicated animation plan. You need a clear start, a meaningful change, and a final canvas worth keeping.
· Diagram Studio Editorial
Direct answer
Plan a diagram animation in four beats: orient the viewer, make one meaningful change, confirm its consequence, and finish on a reusable final canvas. Use a preset to reveal an existing diagram and Free flow to record canvas-state changes while you edit.
Choose the right production mode first
Diagram Studio supports two different ways to create motion. Preset styles animate a diagram that already exists. Free flow records your live canvas edits. Confusing the two leads to unnecessary work.
Use Arrow motion, Sketch draw, Build parts, Soft wiggle, or Focus selected when the diagram is already correct and you want to guide attention. Use Free flow when the transformation itself is useful: drawing a system, rearranging ownership, replacing a weak step, or turning a rough idea into a clearer model.
- Existing route needs a reveal: choose Arrow motion.
- Arranged groups need a reading-order reveal: choose Build parts.
- Only selected objects need emphasis: choose Focus selected.
- The live edit is the lesson: choose Free flow.
Write a four-beat plan
A short recording needs only four beats. Orient: show the starting canvas and name the question. Change: make the one edit that matters. Confirm: point to the consequence of that edit. Final canvas: stop with a clear diagram the viewer can inspect.
For example, imagine a support workflow where every ticket goes directly to an agent. In the recording, orient the viewer to the current queue, add a classification step, route urgent requests to a priority lane, then finish on the new complete workflow. The meaningful event is not the drawing motion; it is the new routing decision.
| Beat | Canvas change | Viewer should understand |
|---|---|---|
| Orient | Show Customer request → General queue → Agent. | Every request currently enters the same queue. |
| Change | Insert “Classify urgency” between request and queue. | A routing decision now happens before assignment. |
| Confirm | Connect urgent requests to Priority queue; leave normal requests on the original route. | Urgent work receives a different path without hiding the normal path. |
| Final canvas | Show both labeled routes and their owners. | The completed workflow remains useful after playback ends. |
Keep supporting edits outside the recording when possible. Rename labels, fix spacing, and prepare reusable objects before pressing Record. The final take should contain the explanation, not housekeeping.
Record a Free flow explanation
Open Animate, choose Free flow, and press Record. Draw, move, edit, or arrange canvas objects in the order you planned. Press Stop as soon as the final canvas is complete. Diagram Studio captures sampled element states—not the pointer or editor chrome—and keeps up to 72 recent frames for Replay and GIF export.
The take lives in the current session, so export it before reloading the page or clearing the recording. If an accidental canvas change obscures the transformation, clear the take and record it again.
Replay for meaning, not performance
Use Replay and ask whether a viewer can name the starting state, the change, and the result. Watch once without narration. If the point disappears, add a concise label or simplify the change rather than relying on a longer explanation.
Check the end carefully. The captured canvas should settle on the state you want people to remember, with complete labels and no accidental element changes. The final frame is part of the recording, not an afterthought.
A clean take does not need to look rehearsed to perfection. It needs to remove accidental movement and preserve the reasoning. Natural drawing can help; hesitation that obscures the change does not.
Export the version the audience can use
Export the GIF when the transformation itself is useful. Export a PNG of the final canvas when the audience needs a reference, a review artifact, or a reduced-motion alternative. Add a short written explanation wherever the animation appears without narration.
For a presentation, test the GIF on the actual slide. For documentation, place the PNG near the animated version so readers can inspect it at their own pace. For async review, include the question the recording answers.
Planning stays deliberately simple: one question, four beats, one replay, and two possible outputs. That constraint is what keeps the result easy to follow.
Use the product-story editing guide when the starting canvas is too crowded. Use the founder demo guide when the recording will support a sales conversation.