How to fix a generated diagram that came back too cluttered to read
Tell Vizard Agent the graphic does not read, and let it retry with a simpler brief rather than a more detailed one. It generates a stripped-back version, previews both, compares them against how long the shot actually lasts, keeps the one that reads on a phone, then measures the result so it sits centred instead of drifting off to one side.
What is the short version?
A generated diagram that is hard to read almost never has too little instruction. It has too much — four labels, a legend, an arrow and a title in a shot that is on screen for three seconds.
- Go to Vizard Agent with the shot.
- Say it does not read, and how long it is on screen.
- Ask for a simpler version to compare against.
What do you need before you start?
The shot and its duration. That second number is what turns this from taste into arithmetic, because a diagram that needs six seconds of reading in a three-second shot is not a design problem that Vizard Agent can style its way out of.
- The graphic as it stands. The version that failed.
- How long it is on screen. The real constraint.
- The one thing it must say. Usually there is only one.
- Where it sits in the frame. Over footage, or full screen.
- Whether it animates. Motion eats reading time.
What do you type into Vizard Agent?
Tell Vizard Agent what is wrong with the graphic rather than what to add to it. The temptation at this point is to write a longer and more precise specification, and a longer specification is very often exactly what produced the crowded version in the first place.
Prompt
Variants worth knowing:
- "A much simpler brief." The instruction that works.
- "Show me both." Comparison beats description.
- "Measure it and centre it." Placement is separate.
What does Vizard Agent actually do?
Here is the sequence on a real talking-head edit with an animated flight-route graphic that came back unreadable. Note that the second attempt asks for less, not more, and that the choice between them is made by looking rather than by arguing.
- Watches the render and confirms the graphic does not read.
- Regenerates it larger as a first attempt.
- Finds size alone did not fix it.
- Retries with a deliberately simpler brief.
- Previews the new version on its own.
- Puts the two side by side.
- Chooses the one that reads at the shot's real length.
- Measures the chosen graphic's dimensions.
- Centres it in the frame from that measurement.
- Re-renders and checks the animation end to end.
Step three is worth dwelling on because it is the step everybody skips. Making a crowded diagram bigger makes a crowded diagram bigger; if four things are competing for attention, scaling all four up changes nothing about which one the viewer looks at first.
Step six is how the decision gets made without a debate. Two versions in front of you settle in five seconds what a paragraph of adjectives will not settle at all, so Vizard Agent generates rather than argues.
Step seven is where the shot length finally enters the argument. A graphic is not legible or illegible in the abstract; it is legible in the number of seconds it is actually on screen, and Vizard Agent judges the two candidates against that number rather than against each other alone.
Step eight is a small thing that spoils a lot of shots. A graphic that was never measured sits wherever it landed, and a diagram two-thirds of the way to the left reads as an accident even when it is perfectly legible.
What does the result look like?
A graphic with fewer things in it, larger, sitting centred in the frame, that a viewer takes in without having to pause the video. It usually carries less information than the first attempt did and manages to communicate more of it.
If the shot genuinely needs all that detail, the honest fix is a longer shot rather than a denser graphic, and Vizard Agent will tell you that rather than trying again.
When does this not work well?
Simplifying has a floor, and Vizard Agent will reach it eventually. Some diagrams genuinely need every element they have, and at that point the binding constraint is the length of the shot rather than the design of the graphic — no amount of regeneration makes six labels readable in two seconds.
- Genuinely complex information. Give it more time instead.
- Regulatory or required text. It cannot be dropped.
- Data with many series. Split it across shots.
- Very small formats. A phone limits what fits at all.
- Graphics over busy footage. The background is the problem.
How do you fix a result that came back wrong?
Say which of the two versions you preferred and what is still wrong with that one. Because Vizard Agent kept both of them rather than overwriting the first, the next attempt starts from a known-better graphic instead of going back to a blank page.
- "The second one, but bigger." A scale change only.
- "Still too busy." Vizard Agent strips another element.
- "It is off to the left." Re-measured and centred.
- "It needs the numbers." Then the shot gets longer.
How does Vizard Agent compare to doing it yourself?
By hand the fix for an unreadable graphic is usually another round of instructions, which adds elements. Then it gets scaled up, which makes the collision worse. Vizard Agent treats "does not read" as a signal to remove things and to compare, not to specify harder.
| By hand | Vizard Agent | |
|---|---|---|
| First instinct | Add instruction | Remove elements |
| Second attempt | Scale it up | Simplify the brief |
| Choosing | Argue about it | Two versions, side by side |
| Placement | Eyeballed | Measured and centred |
| The real constraint | Ignored | Checked against shot length |
Common questions
Why simplify instead of specifying more? Because crowding, not vagueness, is what usually makes it unreadable.
Will it lose information? Some. Vizard Agent will tell you what it dropped.
Can I keep both versions? Yes. Ask Vizard Agent to hold them for comparison.
Does bigger ever work? Sometimes, on a single-element graphic. Rarely on a busy one.
How long does a diagram need on screen? Longer than you think. Vizard Agent checks it against the shot.
Can it lengthen the shot instead? Yes, if the edit allows. Ask Vizard Agent which is cheaper.
Will it centre it automatically? It measures and places it. Say if you want it off-centre.
What about animated diagrams? Motion costs reading time, so Vizard Agent accounts for it.
Can it match my brand colours? Yes, but ask separately so legibility is settled first.
Does this apply to charts? Yes. Fewer series read better than more.
What if it must show everything? Then Vizard Agent will suggest splitting it across shots.
Can I give it a reference? Yes, a diagram you like helps Vizard Agent more than adjectives.
Will re-generating cost much? One graphic. It is far cheaper than a re-edit later.
Why did the first one look fine to me? Because you knew what it said before you looked at it.