Field note · 28 July 2026
A practical vocabulary for workspace events
Consistent event language lets analysts, designers and operational teams ask the same question of the data.
Name the behaviour, not the interface
Interface labels change. The intent behind a meaningful action is usually more stable. An event called review_completed carries more analytical value than green_button_clicked because it describes a recognised point in the work.
A useful definition states who can perform the action, when it fires, which object is involved and what properties are reliable. Examples and exclusions prevent teams from quietly developing different meanings for the same term.
Give the vocabulary an owner
A taxonomy remains trustworthy only when changes are reviewed. Assign ownership, include analytics in release checks and deprecate old events explicitly. Treat the vocabulary as part of the product, not incidental plumbing.