Start with the source’s visual language
A chart already has axes, colors, categories, and a scale. A diagram already has objects and connections. Before adding anything, identify which of those elements carry meaning. Drawing a second legend over the first or assigning a new meaning to an existing color can make the explanation harder to follow. Pointing at a visible label may be enough.
For example, suppose a process diagram contains four stages but only one path is relevant to a delay. Trace that path and identify the blocked transition. There is no need to redraw every stage in a separate box. Keeping the original structure intact lets the person compare the explanation with the evidence, including branches that are not being discussed yet.
Match the mark to the relationship
A highlight is useful for an area or a phrase. An arrow is useful for a direction, a dependency, or a connection. A bracket can group items that belong together. A short label can supply a missing term, but it should not become a paragraph floating over the source. Choosing the right mark reduces the amount of visual explanation you need.
Try to avoid using the same shape for several different meanings in one scene. If a circle first means “look here” and later means “this is wrong,” the viewer has to infer the change. State the intended meaning when it matters. For dense material, one mark that moves between examples is often easier to follow than a growing collection of permanent circles.
A question to try“Use the diagram already on screen to explain the path that matters here.”
Leave room for comparison and correction
An annotation should not hide the value it is explaining. Keep labels near the relevant item without covering the number, button text, or boundary. When the source is crowded, it may be better to point briefly and use a nearby empty area for one small supporting example. The example should reuse the source’s terms so the connection stays obvious.
If the explanation highlights the wrong feature, correct that before more marks accumulate. Ask to return to the original view or explain only one branch. Rayito can add screen annotations while discussing visible content, but a clear correction from you is still important when the intended target is ambiguous.
Clear the scene when the question changes
Marks that helped answer the previous question can distract from the next one. Treat the overlay as a working explanation rather than permanent documentation of the underlying app. Keep the useful idea in conversation history if you want to revisit it, and start the next topic with only the context it needs. Replaying a saved explanation is different from editing or exporting the original document; check the actual document when you need a durable change.