By now the deck's structure holds. What's left is detail: a logo slightly too large, a label that needs rewording, a chart that's cramped, a group of elements sitting a little high.
None of that is worth regenerating a slide for. OpenDesign gives you three tools at three different precisions.
This logo is too big; this label needs a different word; this chart needs more air
Mark
A visual region — easier to show than describe
This group sits too high; this should align with the title; this header lacks contrast
Edit
You already know the exact change
One word, one type size, one colour
Choosing the wrong tool costs you time. Describing a position in prose ("the bit slightly left of centre, just under the second line") loses badly to circling it.
Use it when the problem belongs to a specific object. The comment attaches there, so the next agent pass knows which part to touch and doesn't wander into the rest of the slide.
Good for:
Assets: this should be the horizontal lockup
Copy: this sentence is too long to say out loud
Spacing: this chart is too close to the title
Verification: is this number right
When writing one, saying what you want beats saying what you don't:
Weak: "this is too big"
Better: "halve this logo and align it with the one on the right"
Step 9 · Comment, Mark, Edit
By now the deck's structure holds. What's left is detail: a logo slightly too large, a label that needs rewording, a chart that's cramped, a group of elements sitting a little high.
None of that is worth regenerating a slide for. OpenDesign gives you three tools at three different precisions.
Three tools, three occasions
Choosing the wrong tool costs you time. Describing a position in prose ("the bit slightly left of centre, just under the second line") loses badly to circling it.
Comment: pin feedback to the element
Use it when the problem belongs to a specific object. The comment attaches there, so the next agent pass knows which part to touch and doesn't wander into the rest of the slide.
Good for:
When writing one, saying what you want beats saying what you don't:
Mark: circling beats describing
Use it for layout and position problems. Some faults are obvious on sight and take three sentences to explain. Circle it, add a line, done.
Good for:
Edit: when you know the answer
When the change is already decided, don't spend an agent pass on it. Select the element, change the text or the style property, save.
Good for:
It's the fastest path in the workflow. In the last half hour before a deck ships, most changes should happen here.
An order that avoids rework
Coarse to fine, one precision per pass:
Reverse it and you'll redo work: fix the typos, then have one re-layout pass wash them away.
The last pass before you present
Whatever tools you used, run this before it ships:
[TOPIC], "TBD")That last line has no substitute. Colour shifts, dropped frames, and type that's too small only show up in the room.
Where it goes wrong
Next
Step 10 · Presentation flow and export — the last step, and the one you must not do early.