Form
Cleaned-up Venn diagram with three labeled circles, all items in the seven areas, evaluation table (finding and implication per area), and list of three to seven next actions with owner and date.
RunsheetFacilitation
3-Circle Venn Diagram
ComplexityLow
Time15-45 min
Participants2-8
FormatWorkshop + async
MaturityCanonical
01
Preparation
What needs to be ready before start
Materials
Whiteboard, A3 sheet, or Miro with three overlapping circles; stickies in different colors per circle; timer; list of items to classify.
People / roles
One facilitator; two to eight thinkers with context on the three perspectives; one scribe for evaluation of overlap and exclusive areas.
Pre-read
Three clearly defined perspectives, sets, or options with short description; prepared item list (for example skills, requirements, features); purpose of the analysis (for example sweet spot, differentiation, conflict clarification).
Time needed
15-45 min
Setup
Three circles with clear labels. Seven areas emerge: three exclusive, three pairwise overlaps, one triple intersection. Rule: each item belongs in exactly one area.
02
Core question
The one question this method answers
Which items sit in which intersections of the three perspectives, and what implications follow for next decisions?
03
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-5 min | 5 min | Sharpen the three perspectives. For each circle, define a one-sentence criterion: what counts for this circle. Put examples for each circle at the edge. | Unclear circle definitions lead to arbitrary sorting. If an item could fit everywhere, criteria are too soft. |
25-25 min | 20 min | Sort items silently. Discuss conflicts openly. Each item gets exactly one area; if unclear, put it in the triple intersection or the most fitting overlap. | The common trap: items are wished into the central sweet spot although they do not belong there. Discipline: does the item match all three criteria, or is one missing? |
325-35 min | 10 min | Evaluate per area: what does a full triple intersection, empty overlaps, or one-sided accumulation mean? Derive conclusions for the guiding question. | An empty triple intersection is an important finding (no sweet spot), not a failure. A fuller overlap in one pair shows a specific axis as dominant. |
435-45 min | 10 min | Next steps: define one action with owner and date per relevant finding. At least three actions, otherwise the diagram remains diagnosis without effect. | Venn diagrams tempt pure visualization. Workshop ends with actions, not with a pretty picture. |
04
Artifact
What comes out at the end
Versioning / ownership
One entry per analysis with date and guiding question in the title. Create follow-up iterations as version 2 and keep previous sorting for comparison.
Tool alternatives
- Miro or FigJam with Venn template
- Lucidchart or draw.io for persistent diagrams
- Whiteboard photo plus Markdown table
- Notion page with three columns as approximation
three-circle-venn-diagram-working-template.md
Compact working template for 3-Circle Venn Diagram with context, input, output artifacts, and next step.
3-Circle Venn Diagram Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Venn Diagram:
- Overlap Notes:
- Differentiators:
Open questions
- ...
Next step
Owner, date, success signal.
05
Example output
Concrete filled scenario, fictional example
three-circle-venn-diagram-beispiel.md
Concrete filled scenario, fictional example
Venn - Hiring profile Senior Platform Engineer (2026-05-15)
Three circles: (A) Kubernetes operations depth, (B) Go codebase experience, (C) developer-experience mindset.
Triple intersection (sweet spot): 2 candidates in the current pipeline.
A intersection B (without C): 7 candidates. Finding: strong engineering, but DX mindset missing. Implication: onboarding risk, senior mentoring required.
B intersection C (without A): 5 candidates. Finding: would fit the team well, but operations-light, risk in cluster incidents.
A intersection C (without B): 3 candidates. Finding: Go learning curve, 4-6 weeks.
Only A: 14 candidates. Only B: 9. Only C: 11.
Implications:
- Sweet-spot pool is too small, activate more sources (Owner: @anna, by 2026-05-25).
- Consider B-intersection-C as next-best option, with dedicated K8s buddy in the first 90 days (Owner: @ben).
- Recalibrate hiring criteria: weighted profile instead of absolute sweet-spot requirement (Owner: @lisa, by 2026-05-30).
06
Pitfalls
Recognize symptoms and steer against them
Trap
Circles defined too vaguely
Symptom
Participants interpret criteria differently, sorting becomes arbitrary.
What to do
Write down circle criteria as one-sentence definitions with 2-3 examples before sorting. In conflict, sharpen definitions instead of moving the item.
Trap
Sweet spot as wishful thinking
Symptom
Items are pushed into the triple intersection although they fulfill only two criteria.
What to do
Explicitly check per item whether it fulfills all three circle criteria. If not, put it in the matching pair overlap.
Trap
No action
Symptom
Diagram hangs on the wall, but no decision follows.
What to do
Reserve the last 10 min for actions. At least one implication per area, three to seven actions overall with owner.
Trap
Items too generic
Symptom
Items such as "innovation" or "efficiency" cannot be sorted.
What to do
Break items into operationalizations before sorting starts. Use generic terms as cluster headers, not as items.
Trap
Statistics instead of analysis
Symptom
Workshop only counts items per area without drawing implications.
What to do
Ask two questions per area: what does the accumulation or emptiness mean for the guiding question? Which decision does this support?
07
Stop criteria
Done signals checkable in under a minute
More than three perspectives are actually relevant; Venn is not the right format.
Items cannot be sorted clearly, criteria are not selective enough.
Purpose of the analysis is unclear, visualization remains without consequence.
Group has no context on the perspectives, sorting becomes hearsay.
All items are expected in the same intersection, diagram creates no insight.
Visualization is expected only decoratively, without actions; effort does not fit.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.