<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tany Holzworth on Medium]]></title>
        <description><![CDATA[Stories by Tany Holzworth on Medium]]></description>
        <link>https://medium.com/@tanyholzworth?source=rss-942c01c7d40c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gvkJVO2RQ1LNh9sX2-1PQg.jpeg</url>
            <title>Stories by Tany Holzworth on Medium</title>
            <link>https://medium.com/@tanyholzworth?source=rss-942c01c7d40c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:07:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanyholzworth/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The “Bird Names for Birds” Movement: A Crash Course in Content Design]]></title>
            <link>https://codewords.tech/the-bird-names-for-birds-movement-a-crash-course-in-content-design-0288e7cdc60b?source=rss-942c01c7d40c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0288e7cdc60b</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[birding]]></category>
            <category><![CDATA[bird-watching]]></category>
            <dc:creator><![CDATA[Tany Holzworth]]></dc:creator>
            <pubDate>Tue, 24 Feb 2026 14:46:00 GMT</pubDate>
            <atom:updated>2026-02-26T16:10:57.840Z</atom:updated>
            <content:encoded><![CDATA[<p>In the tech world there’s a common quip, “There are only two hard things in computer science: cache invalidation and naming things.”</p><p>Content designers know. You spend hours considering whether a button should say “Submit,” “Send,” or “Post.” You get eye rolls for insisting on consistent phrasing…again. You’re asked to use 30 characters to label a feature that does 6 (very distinct) things.</p><p>But if you think tech has a naming problem, look at ornithology.</p><figure><img alt="Merlin app’s yellow-billed tit-tyrant. includes a photo of a small bird with a yellow breast striped with black and white streaks and horn like feathers sprouting from between it’s eyes and the supporting copy “Active little bird of scrubby and brushy habitats in drier regions of the andes and locally in the lowlands of argentina. Often in pairs, hopping in bushes and weeds and can be difficult to see well. Best identified by bold blackish striping on breast and wispy black crest." src="https://cdn-images-1.medium.com/max/768/1*4xykXm94GYp2CGRQTpPt0g.png" /><figcaption>Screenshot from the Merlin Bird ID app.</figcaption></figure><p>Looking past the unhinged nature of many bird names (that’s another article I’m not sure I’m funny enough to write) content designers will recognize the poor UX of having to use a block of text to explain a nonsensical feature name. Rife with obscure jargon, misleading labels, and exclusionary language, ornithology is a prime example of bad UX.</p><p>Like the tech world, ornithology has a long history of being led by a homogeneous group (white men) and following legacy patterns. As both the tech and birding universes become more diverse, and recognize the virtuous cycle of increased diversity improving their experience and expanding their audience, naming conventions stand out as an area of opportunity.</p><p>Recently, a movement called<a href="https://birdnamesforbirds.wordpress.com/"><strong> Bird Names for Birds</strong></a> has pushed for an overhaul of naming conventions from the lens of social justice. The goal is to reduce barriers to participation in birding that arise from racist associations that can result from birds being named after their “discoverer” and rename the birds using identifiers that refer to the species itself. <a href="https://americanornithology.org/american-ornithological-society-will-change-the-english-names-of-bird-species-named-after-people/"><strong>The American Ornithological Society has committed to this effort</strong></a>, and is working with scientists and communities to start the renaming process.</p><p>While the Bird Names for Birds movement is rooted in anti-racism, the reworking of bird names more generally presents an excellent case study for applied content design. When we look at why bird names fail, we can see some of the basic patterns that help product copy succeed. If you’re new to the discipline, needing a refresher, or looking for a shred of hope to hold onto (change is possible) take a peep.</p><h3>1. Write for accuracy: Goatsuckers</h3><p>For centuries, the <em>Caprimulgiformes</em> family of birds, now mostly known as nightjars or whip-poor-wills, was officially classified as “Goatsuckers.”</p><p>Why? Because of an ancient folk myth that these small, nocturnal birds flew into barns at night and sucked milk from the udders of goats.</p><p>They don’t do that. They eat moths.</p><p>But the name stuck. It was “legacy.” To change it would require updating the books, the museums, and the collective knowledge of the “users” (birders). So, for generations, if you wanted to learn about this bird, you had to learn a lie first.</p><p>In UX, we do this all the time.</p><ul><li><strong>“Breadcrumbs”:</strong> We rely on a specific European fairy tale (Hansel &amp; Gretel) to explain site hierarchy.</li><li><strong>“Toast”:</strong> We use a developer’s inside joke (“it pops up like toast!”) to describe a temporary alert.</li></ul><p><strong>The lesson:</strong> The first job of a label is to be true. If a bird eats moths, don’t call it a goatsucker. If a button saves a draft, don’t label it “Submit.” If your user needs a degree in folklore to understand your navigation, your design has failed the accuracy test.</p><p><strong>See also:</strong> Ring-necked Duck, Yellow-billed Tit-tyrant</p><h3>2. Match user mental models: Ring-necked Duck</h3><p>Consider the <strong>Ring-necked Duck</strong>. If you look at this bird in the wild, you will see a black back, a grey side, and a very distinct white ring around its <em>bill</em>.</p><p>You will not see a ring around its neck. The “ring” is a faint chestnut band that is barely visible even when you are holding the bird in your hand.</p><p>So why is it called the Ring-necked Duck? Because the 19th-century taxonomists who named it were looking at dead specimens in a drawer, not living birds on a lake. They named the bird based on the “backend” data (the specimen), not the “frontend” user experience (the field mark).</p><p>When we as designers and builders of things get too familiar with internal jargon and systems, we forget that the user is a beginner.</p><ul><li><strong>The system model:</strong> How the experience is built. (e.g., “Directory / Sub-directory / File”).</li><li><strong>The mental model:</strong> How the user thinks. (e.g., “Photos / 2024 / Vacation”).</li></ul><p>When we name features based on how engineering built them (“sanitized_input_check”) rather than what the user needs (“security check”), we are creating Ring-necked Ducks. While the information we’re giving them may technically be correct, it doesn’t match the beginner’s mental model and adds friction.</p><p><strong>The lesson: </strong>Name things based on the information the audience has, not the information available to the team that built it. Ring-<em>billed</em> Duck makes sense to everyone, not just the scientists with specimens.</p><figure><img alt="A black-backed duck with grey sides and stomach swimming in water that’s reflecting green foliage. The duck has yellow eyes and a grey bill with a distinct white ring around the tip." src="https://cdn-images-1.medium.com/max/768/1*FiLkbPIKGqvJr48GTr2r1w.png" /><figcaption>Screenshot from Merlin Bird ID app.</figcaption></figure><h3>3. Reduce cognitive load: Wilson’s Warbler</h3><p>In birding, an “eponym” is a bird named after a person: <em>Wilson’s Warbler, Cooper’s Hawk, Baird’s Sandpiper.</em></p><p>These names are functionally useless. The name “Wilson” tells you nothing about the bird. It doesn’t tell you it’s yellow, or that it has a black cap, or that it lives in willows. To identify a Wilson’s Warbler, you must rely entirely on rote memorization. You have to memorize that <em>Wilson = yellow bird. </em>Not only that, but some people have several different species of birds named after them. Take the Swainson’s Hawk, Swainson’s Flycatcher, Swainson’s Thrush, and Swainson’s Warbler, for example.</p><p>Compare that to the <strong>Yellow-rumped Warbler</strong>. The name gives you the answer. Adding it to your birding vocabulary is easy, the name is memorable because it reflects a key detail of the bird’s appearance.</p><p>In UX, eponyms are the equivalent of vanity project names.</p><ul><li><em>Bad UX:</em> “Welcome to <strong>Project Titan</strong>.” (Requires memorization)</li><li><em>Good UX:</em> “Welcome to <strong>Advanced Search</strong>.” (Self-explanatory)</li></ul><p>Every time you force a user to memorize a term that doesn’t describe the function, you are adding to their cognitive load. You are taxing their brain before they have even started the task.</p><p><strong>The lesson:</strong> Skip fancy names in favor of descriptive ones.</p><figure><img alt="A small yellow bird with black feathers mimicking a cap on top of it’s head sits on a branch. It has black eyes and a short, triangular beak." src="https://cdn-images-1.medium.com/max/768/1*zCiNwlPEX8e4tWU002Timw.png" /><figcaption>Screenshot from Merlin Bird ID app.</figcaption></figure><h3>4. Inclusive language: McCown’s Longspur</h3><p>As we’ve seen, there’s lots of usability reasons to rename birds. Accurate, memorable names help make birding (and app navigation) more accessible and easier to onboard to. But the “Bird Names for Birds” movement isn’t just about usability, but ethics — and it turns out they are one and the same.</p><p>Until 2020, a small prairie bird was known as <strong>McCown’s Longspur</strong>. It was named after John P. McCown, a Confederate General.</p><p>For Black birders, a name like this isn’t neutral. It’s a micro-aggression and a symbol of their historical exclusion from the scientific and birding communities.</p><p>The movement successfully campaigned to rename the bird. It is now called the <strong>Thick-billed Longspur</strong>.</p><p>Notice what happened here.</p><ol><li><strong>The ethical win:</strong> The racist barrier was removed.</li><li><strong>The usability win:</strong> The new name — <em>Thick-billed</em> — is descriptively accurate. It helps <em>everyone</em> identify the bird faster.</li></ol><p>This is the <a href="https://en.wikipedia.org/wiki/Curb_cut_effect"><strong>curb cut effect</strong></a> in action. When you add a ramp to the sidewalk, it’s not just wheelchairs that benefit, but strollers, wagons, bikes, and rolly-suitcases. When you design for the most marginalized user (removing the exclusionary term), other users almost always benefit too.</p><p>When we replace tech terms like “master/slave,” “whitelist,” or “sanity check,” we aren’t just being politically correct. We are replacing obscure, violent, or ableist metaphors with precise, descriptive language like “original/copy,” “allowlist,” and “logic review.”</p><p><strong>Lesson: </strong>Inclusive language isn’t an extra demand, it’s a worthwhile investment.</p><figure><img alt="A greyish bird with rusty shoulder patches, black breast, and black cap stands in the grass. It has a dark, thick bill, probably for eating seeds." src="https://cdn-images-1.medium.com/max/1024/1*3tW8mpJK4TXnQFEXIfQrVw.png" /></figure><h3>But change is hard!</h3><p>Don’t we know it. The real challenge of my content design career is convincing stakeholders that the effort is worth it. But if a centuries-old, deeply-entrenched system like ornithology can change, surely we can be hopeful for our content decisions. Code is easier to update than guidebooks.</p><p>With so many bird species in decline, and conservation becoming more and more central to the birding community (as opposed to an ego-driven “imma-name-this-bird-after-myself” competition) bird organizations have recognized that reaching a large audience is vital to the goal. As tools like the (free!) <a href="https://merlin.allaboutbirds.org/"><strong>Merlin Bird ID app</strong></a> help remove barriers to joining the birding community, inclusive language adds to the flywheel that welcomes more people to care about conservation.</p><p>Obviously, as product designers, we can relate to wanting to expand our product’s usage!</p><p>The ecosystem is changing. The birds need our conservation efforts. The birding community needs diverse voices. It took a lot of advocacy, but the field guides are being reprinted. The sky didn’t fall when the names changed — the view just got clearer.</p><p>It’s time for our style guides to catch up. Armed with some hope, content designers can help.</p><p><em>code:words is a collective effort focused on elevating and amplifying every aspect of writing in the tech industry. This curated publication requires community contribution in order to learn, grow, and connect with other writers. To submit an article, </em><a href="https://medium.com/words-in-tech/how-to-publish-with-code-words-9ef83ac38745"><em>start here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0288e7cdc60b" width="1" height="1" alt=""><hr><p><a href="https://codewords.tech/the-bird-names-for-birds-movement-a-crash-course-in-content-design-0288e7cdc60b">The “Bird Names for Birds” Movement: A Crash Course in Content Design</a> was originally published in <a href="https://codewords.tech/">code:words</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>