Chart · venn

Overlap between three workspace roles

Builders, reviewers and operators are not disjoint audiences. 660 accounts do all three jobs — the group every workflow change hits three times.

Overlap between three workspace roles Illustrative dataset, not a real account census. Three overlapping user segments: 5,400 builders, 4,800 reviewers and 3,900 operators. Seven regions are labelled — builders only 3,180, reviewers only 2,760, operators only 2,180, builders and reviewers 940, builders and operators 620, reviewers and operators 440, and all three 660, the focal region. Region areas are schematic and carry no magnitude: the circle radii and centre distances were not computed from the counts, so every quantity is read from its printed label and never from an area. The three circles are equal in radius because the three sets are comparable in size. Each set fills its own design-token colour at one shared fill-opacity of 0.16; overlaps read darker because those fills compound, not because a new colour was introduced. Builders 5,400 accounts Reviewers 4,800 accounts Operators 3,900 accounts Builders only 3,180 Reviewers only 2,760 Operators only 2,180 Builders + Reviewers 940 Builders + Operators 620 Reviewers + Operators 440 All three roles 660

Illustrative dataset — the segment counts are invented to demonstrate the venn grammar and describe no real user base. Region areas are schematic. The radii and centre distances were not derived from the counts, so no area on this canvas encodes a quantity; every number is printed in its region's own label. Each set fills one design-token colour at a shared fill-opacity of 0.16, and the overlaps darken because those fills compound. Every region carries a direct label, so identity never rests on a compounded tint. A venn has no value scale, so data-baseline is not-applicable. Colour resolves through design-system tokens; where no project tokens are compiled the page falls back to the documented neutral palette declared in :root. Static, script-free, and offline.