The recipe approach to writing labels

When writing labels for productivity software, labels should be clear, concise, and neutral. The goal is to help the user complete a task, not influence them toward your own goals. When writing for such experiences, I think about the process of following a recipe.

In both software and a recipe, someone is focused on achieving a specific goal that has multiple steps. Some folks will have memorized (or will ignore) all the steps and can find their way around by feel alone. Others will read every instruction twice.

Language in a user experience guides users through the steps they need to take to complete a task. There are two broad categories of language in a UX: instruction and information. Instructions can be complex and narrative. They bring the user from one mental state to another.

Information is perhaps less complex, but still challenging to write. Especially labels. Labels are signposts that inform users what they are looking at and provide clues as to how it will work.

How not to write labels

Just like in a recipe, labels should be clear, concise, and neutral. Neutral means the labels don’t make assumptions about what the user values or what they are trying to do. Users could be using your software for all sorts of unexpected uses. Well-designed software enables all kinds of unforeseen use cases. (This is kind of what folks mean by timeless” design.)

Users don’t need branded terms in labels. They are distracting and they can imply a specificity that isn’t necessarily required. Consider a recipe that looks like this:

Branded labels


  • Franklin Farms Eggs
  • Lucerne 2% Milk
  • King Arthur All Purpose Flour

It’s too specific. It also feels a little smarmy, but we see this in software products all the time.

Users also don’t need buzzwordy value-props. These are appropriate in marketing copy to differentiate features. Within the product, however they are distracting and often disconnected from the user’s immediate goals:

Value-prop labels


  • Farm-fresh cage-free eggs
  • Ultra-filtered 2% milk
  • 100% employee-owned King Arthur all purpose flour

Users don’t need all technical details or capabilities either. Remember that when the user is engaged in the task, they are not ready to learn complex concepts. Technical details are appropriate for instruction before a user gets started or in documentation when a user is stuck.

Here’s what a too technical recipe looks like:

Overly-technical labels


  • Grade AA, CA SEFS compliant eggs
  • 2% grade A, pasteurized, and from cows not treated with rBST milk
  • Enriched, bleached, prestified all purpose flour

Of course, if detailed specifications are critical for success, include them early in the experience (in recipes, the ingredient deck is appropriate), but make sure to use simpler versions through the experience.

Less is more

The best labels are clear, concise, and neutral. A user baking a cake needs to know the basics.

Clear and simple labels


  • Eggs
  • 2% Milk
  • All purpose flour

The shorter the better since these labels will be used in the method too. In the method, you can remove modifiers (like 2% or all purpose) to keep it short and scannable.

Separate eggs, then add to the flour. Add milk.”

Compare this to:

Separate Grade AA, CA SEFS compliant eggs, then add to the dry ingredients. Grade AA, CA SEFS compliant eggs should be added one at a time.”

But business software does this all the time:

To enable Omnibuzzword Filtering go to Omnibuzzword Filtering Power Settings > Omnibuzzword Filtering and choose Activate Omnibuzzword Filtering.

They’d probably jam a damn trademark sign in there if you let them. Gross.

Keep labels simple. When in doubt, think cake.

Up next Sorry no pizza Content design vs visual design
Latest posts A Smallish Book about content design How to make Confluence less horrible I am a writer designer Are SLCs the new MVPs Work is like a hill Badge of dishonor Ceci n'est pas un poubelle This sign is a crime Beware the lure of consistency Do not water Never, ever use the term microcopy You need three things to design content Permanently fixed Assembly instructions for a side table Extraneous labels, ignored conventions The double diamond model Don't have an emergency here Product tours that don't suck Quickly edit text on the web How content designers can get the most out user interviews Let's be reasonable How to derisk trial experiences Turn around, bright eyes We could be zeroes Content design vs visual design The recipe approach to writing labels Sorry no pizza 6 truths for first-time public speakers Do not enter, exit only What the %&@! is content design Content design has a nomenclature problem