Why we don't collect demographics
The app stores almost nothing about a participant. When someone joins a workspace they are recorded as a display name they choose, the team they joined, and a few timestamps. There is no tenure field, no department field, no role level, no gender, no age, no ethnicity, no location, no manager. The same is true of every frustration they submit — it carries the text, a team link, and a timestamp.
That is a design choice, not an oversight. The book's argument is that the cause of disengagement is structural, not demographic. Slicing frustrations by “engineering vs sales” or “under-two-years vs over-ten” tends to teach a facilitator that the problem is one of those groups, and to lead them away from the architecture that is actually generating the pattern. We would rather the dashboard make the structural read obvious and refuse to make the demographic one available.
When a facilitator does need contextual intake — a CEO's own words before an operating review, a non-family executive's named reversals, an operating partner's intervention log — the book ships printable templates for exactly that. They live on paper, outside the app, under the facilitator's control.