Planning engagement
Naming Workshop
Click, tap, submit, and success are not events. In four hours we practise renaming the messy list you already have, then write the rule you will use on the next feature.
Who it is for
Squads about to instrument a feature, or analytics partners who keep receiving three names for the same tap.
What you leave with
A one-page naming convention, a starter inventory for one feature area, and a list of words the team has agreed never to use as event names.
In scope
- Convention: object_action, tense, and locale
- When a screen view is enough and an event is waste
- Properties that belong on the user versus on the event
- A live rewrite of one feature’s current names
Included
- Facilitation for up to eight people
- Printed worksheets and a shared recap document
- The banned-word list the room agreed
Not included
- A complete app-wide dictionary (book Schema Planning)
- Follow-up coaching unless scheduled separately
How the work proceeds
-
Bring the messy list
You arrive with the current names for one feature, however inconsistent.
-
Rewrite in the room
We do not lecture for four hours. Most of the time is spent renaming rows together.
-
Leave with the rule
The recap is the convention plus the starter inventory, not a transcript.
Preparation
Print or share the current event names for one feature. Nominate one person who can settle disputes in the room.
Constraints
Eight people. Observers beyond that dilute the rewriting. Bahasa Malaysia discussion is welcome; the dictionary we write is in English unless you ask otherwise.
Next step
Propose two morning dates. We confirm room or travel within Klang Valley.