Welcome back; this article is part of the series called DaS™ — Naming convention.
The previous article explored the history and mental models behind sorting information in digital space. This article aims to discuss the naming convention of our files spread across drives or remote places.
The remote world eventually moved our internal naming convention from local hard drives to a public space. You name it — Miro, Slack, Google, Microsoft or Figma (or Sketch). Every boss, product owner, human resources or developer knows what we are and how we orchestrate our designs in the company we work for.
“The messy team equals messy structure, resolving in a messy product or service, period — there is no science about it.”
–Jiri Mcc, Greenwich
The good thing is if you are really organised, the impact is imminent. Upon gaining the respect, you also broaden your influence that could easily expand from design to business and development.
There is a silver lining between imposed file naming convention and a carefully crafted one. Do make sure you work with your development team first to align on the basics of how the names work in their specific world and how we can make them more prominent in our designs.
The red flag goes with making everything an acronym or abbreviation –
even though it can be very efficient once embedded. It also has to be digestible to a broader audience. So if your team serves cat food in your company, you don’t have to call it “CFC — Cat Food Company”.
The challenge with some acronyms comes with an ambiguity of the meaning. Once, on a project, we had the acronym CWA. It meant four different things — you most certainly want to avoid that.