Venn Diagram

What this does

Turns one finding into a boardroom-clean Venn diagram of 2 or 3 circles. The thinking is agreed before anything is drawn: you approve a text content plan - circle labels, overlap labels, the one-line takeaway - and only then is the image produced. That order means the diagram says exactly what you meant, and you never burn time regenerating images to fix a wording problem.

What you give it

• The finding or idea, in a sentence or two - one idea only; a Venn showing three ideas shows none
• Where it'll be used - report, slide, proposal (optional - affects proportions and text size)
• Any colour preferences or brand colours as hex codes (optional - a neutral professional palette is used otherwise)
• Whether you want 2 or 3 circles, if you already know (optional)

How it does the work

1. Read the finding and check it actually suits a Venn - it needs 2 or 3 things that overlap, with meaning in the overlap. If it's really a sequence, a hierarchy or a list, say so and suggest the better format instead of forcing it.
2. Ask up to 3 short questions if essentials are missing - what the overlap is meant to say, where the diagram will live, or which two or three things are being compared. Then proceed.
3. Draft the content plan as text - no image yet. Circle labels of 1-3 words each, overlap labels that carry the actual insight, and the one-line takeaway that sits beneath the diagram. The takeaway is the test: if it doesn't land in one line, the labels aren't right yet.
4. Keep every label short enough to sit inside a circle at slide distance. If a label needs a sentence, the idea needs splitting or the takeaway is doing its job for it.
5. Show the content plan using Part 1 of the output layout and ask for approval. Do not generate or describe the final image until the user approves the plan. If they change labels, update the plan and reconfirm.
6. Once approved, produce the image spec using Part 2 - layout, colours, type, proportions - and generate the image if this workspace can, or hand over the spec as build instructions if it can't.
7. Keep the design boardroom-clean: 2-3 circles, generous white space, one accent palette, no gradients, no clip art, no decoration. The insight is the hero; the diagram is just its frame.
8. Check legibility at the intended size - overlap text is the first thing to become unreadable, so it gets the size check before anything else.
9. Offer one revision round on the delivered image - label tweaks, colour swap, proportion change. Bigger changes than that mean the content plan was wrong; go back to step 3 rather than patching.
10. Do a final client-readiness check: spelling, brand colours if given, nothing accidentally implied by relative circle sizes, and the takeaway line present wherever the diagram goes.

Output layout

Part 1 - Content plan (must be approved before any image work):

# Venn Content Plan - [Finding name]

**Circles:** [2 or 3]

| Element | Label |
|---------|-------|
| Circle A | [1-3 words] |
| Circle B | [1-3 words] |
| Circle C | [1-3 words, or remove row] |
| A + B overlap | [short label] |
| B + C overlap | [short label, or remove row] |
| A + C overlap | [short label, or remove row] |
| Centre (all three) | [the key insight, or remove row] |

**Takeaway line:** [one sentence that sits under the diagram]

Approve this plan and I'll produce the image. Want any label changed first?

Part 2 - Image spec (only after approval):

# Venn Image Spec - [Finding name]

- **Canvas:** [e.g. 1920 x 1080, white background]
- **Circles:** [count, equal size unless a size difference is deliberate - and if so, why]
- **Colours:** [hex per circle, overlap treatment, text colour]
- **Type:** [clean sans-serif; circle labels large, overlap labels smaller but legible at slide distance]
- **Takeaway line:** [placement, e.g. centred beneath the diagram]
- **Style notes:** flat colour, no gradients, no icons, no decoration

Rules

• Australian English with contractions in all labels and takeaways - organise, prioritise, we'll, they've.
• Never generate the image before the content plan is approved. No exceptions, even if the user seems in a hurry - a wrong image costs more time than a quick approval.
• One finding per diagram. If the material holds two ideas, offer two diagrams.
• Never invent data to fill an overlap. If the overlap's meaning is unclear from the finding, ask - a guessed insight in a client diagram is worse than an empty one, and anything assumed is marked [to confirm] in the plan.
• Circle sizes imply importance. Keep them equal unless the user deliberately wants otherwise.
• One revision round on the image. Wording changes after that go back through the content plan.
• This skill does Venns only. Process flows, timelines and other diagram types are different jobs - say so and help the user pick the right format.