Use consistent emoji vocabulary
making titles and headings more browsable 2024-10-22 #collaboration
- Emoji vocabulary β
- Reaction emoji
When you use contemporary collaboration tools like Slack and Notion, you have a choice. You can either complain about the emoji and call them unprofessional, in which case you need help, or you can develop and use a consistent emoji vocabulary that makes document titles and section headings easier to browse.
If you donβt stop there, you also end up with an #emoji-language
Slack channel,
for questions and answers about correct emoji usage, and their rules, exceptions and dialects.
And if it escalates, you go beyond the standardised Unicode emoji,
and start adopting slang, in the form of
Slack custom emoji.
In the following vocabulary, each entry has an example of a title or heading that each emoji can introduce, to categorise it, group it with similar items, or add visual structure to a document outline. You can develop your own similar vocabulary, focused on whatever you write about.
Note that you donβt need to remember what each emoji means. Instead, their value comes from making the content they proceed more recognisable. But if you use them consistently, it wonβt take long before you can read them
A-C
π€ agreement - something you agreed to, in a meeting write-up
βοΈ assumption - an unresolved issue, in discovery and design documentation
π€ automation - a software development task, in a work tracker
π bug - software development work, in a work tracker
πΌοΈ canvas - a virtual whiteboard link in a calendar invitation
π context - a document introduction section
π§βπΌ customer - a (B2B) customer name
D-E
π delivery - a product delivery to a customer
π¨ design - a work type, or team
πΉ discount - a discount code or percentage
π¬ discussion - a calendar event
π documentation - a document type
π§ email - a document/message type
π¨ emergency - an issue priority
F-I
π feature - software feature documentation
π© feature flag - a software release toggle
π―οΈ feedback - received customer feedback
π― goal - a business objective
ποΈ holiday - a day off in a calendar
π‘ idea - something to think about
β‘οΈ integration - software integration or an API
M-Q
π£ marketing - a work type, or team
π metrics - product data
π± needs - customer needs, in discovery work
π new product/feature - software development work, in a work tracker
π notes - a document type
ποΈ notification - a document/message type
P-R
ποΈ performance - a non-functional requirement
π¦ product - a catalogue entry
β question - an unresolved issue, in discovery and design documentation
π§βπ¬ research - a work type
π review - a work type
S
π schedule - a planned event
π search - a software feature type
π’ shipped - a software release announcement
πͺ shop - a web shop
πΌ spring - a season
π strategy - a business work type, e.g. product strategy
T-Z
π¨ task - a work type
π§Ή technical debt - a software development (clean-up) work type
π§ͺ testing - a software development work type
π vision - a business work type, e.g. product vision