Journal · 2 February 2026
Mapping workspace events without drowning in properties
Event streams rot when every stakeholder adds a property “just in case”. Engagement Segmentation Analytics then becomes an archaeology project. Give the stream a budget: a small set of object ids, a role, a workspace id, and a boolean that says whether the action completed a job.
Source, campaign, and experiment flags belong in a join, not on every click. They are political fields — they exist so someone can prove a channel worked. If they leak into segment definitions, your lattice starts describing last quarter’s ads, not how people work.
Event Grammar for Product Desks uses a one-page contract: object, action, required properties, forbidden properties, owner, retirement rule. If a property cannot name an owner, it does not ship.
The uncomfortable part is deleting. Teams fear breaking a dashboard. Write the break as a date. Segments that depended on a junk property should fail loudly rather than silently fill with nulls.