<?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 Sam Pierce on Medium]]></title>
        <description><![CDATA[Stories by Sam Pierce on Medium]]></description>
        <link>https://medium.com/@sampierce_75702?source=rss-3527e622e43a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HVWKGXGM_UQY_5ZmgMf1UQ.png</url>
            <title>Stories by Sam Pierce on Medium</title>
            <link>https://medium.com/@sampierce_75702?source=rss-3527e622e43a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:39:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sampierce_75702/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 Hidden Cost of Context-Shifting Menus: A Quick UX Teardown of Medium’s “Unlist” Feature]]></title>
            <link>https://medium.com/@sampierce_75702/the-hidden-cost-of-context-shifting-menus-a-quick-ux-teardown-of-mediums-unlist-feature-f07cfc7312a9?source=rss-3527e622e43a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f07cfc7312a9</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[discoverability]]></category>
            <dc:creator><![CDATA[Sam Pierce]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 14:15:02 GMT</pubDate>
            <atom:updated>2026-08-30T14:15:02.101Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently decided to clean up my Medium profile. Like many practitioners evolving their focus, I wanted to archive early-career articles that no longer reflected my current work. Medium doesn’t offer a traditional “revert to draft” feature, but it does allow you to <strong>unlist</strong> a story — keeping the URL alive while removing it from public feeds and your profile.</p><p>It sounded simple enough. Finding where that setting lived turned into a case study in broken information architecture and hidden actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*jnOhxFC8pUU9NNQTi3oOMA.png" /></figure><h3>The Hunt for a Status Toggle</h3><p>Managing a story’s publication status is metadata management, not content editing. Naturally, I started where stories are managed:</p><ol><li><strong>The Stories Dashboard:</strong> Next to each story is a standard three-dot action menu. It offers options like <em>Edit story</em>, <em>Submit to publication</em>, <em>View stats</em>, <em>View settings</em>, and <em>Delete story</em>. No “Unlist” option.</li><li><strong>The Published Story View:</strong> Navigating directly to the article header presents another three-dot menu. It looks nearly identical to the dashboard menu and includes the same high-level options. Still no “Unlist.”</li><li><strong>The Dedicated Settings Page:</strong> Assuming story visibility was an administrative setting, I clicked <em>View settings</em>. I was met with SEO metadata, custom canonical URLs, and audience controls — but no toggle for unlisting.</li></ol><p>To actually unlist a published story, you must enter <strong>Edit story mode</strong>, click the three-dot menu <em>within the editor</em>, and select <strong>“Manage unlisted setting.”</strong></p><h3>Where the UX breaks down</h3><pre>[Dashboard List View]      →  Action Menu: High-level management (No &quot;Unlist&quot;)<br>[Published Story View]     →  Action Menu: High-level management (No &quot;Unlist&quot;)<br>[Story Settings Page]      →  Metadata &amp; SEO configurations (No &quot;Unlist&quot;)<br>[Editor Mode]              →  Action Menu: Suddenly reveals &quot;Manage unlisted setting&quot;</pre><p>This interaction model introduces three distinct usability friction points:</p><h4>1. Violating the Mental Model of “Editing”</h4><p>Entering edit mode implies an intent to alter content: fix a typo, rewrite a paragraph, or replace an image. Changing publication state (published vs. unlisted vs. draft) is an administrative action on the object itself. Forcing users to enter an active editing canvas to access visibility settings conflates content manipulation with state management.</p><h4>2. Inconsistent Contextual Menus</h4><p>Dynamic action menus make sense when the available actions strictly relate to the active environment (e.g., formatting options that only exist inside a text editor). However, Medium’s editor menu houses general distribution and metadata actions — such as <em>Change topics</em>, <em>Change display title / subtitle</em>, and <em>Manage unlisted setting</em> — that are equally relevant from the dashboard list view or the dedicated settings screen.</p><p>When users see a three-dot menu on an item in a list, they expect it to contain all primary actions for that entity. Stripping critical management features from the list menu and only revealing them in editor mode destroys discoverability.</p><h4>3. Redundant and Fragmented Settings</h4><p>Having both a standalone <strong>View settings</strong> page and an in-editor menu with options like <em>More settings</em> and <em>Manage unlisted setting</em> fragments the information architecture. Users shouldn’t need to guess which bucket of settings contains visibility toggles versus SEO tags.</p><h3>How to Fix It</h3><ul><li><strong>Promote State Controls to the Story Management Menu:</strong> Add status controls (<em>Unlist</em>, <em>Make Public</em>, <em>Archive</em>) directly into the three-dot menu on the Stories dashboard and published view.</li><li><strong>Consolidate Administrative Options into Story Settings:</strong> If an action alters how a story is distributed or discovered, it belongs on the story’s dedicated settings page.</li><li><strong>Keep Editor Menus Context-Specific:</strong> Reserve editor-level menus for actions pertinent to drafting and revision (e.g., <em>Revision history</em>, <em>Keyboard shortcuts</em>, <em>Draft sharing</em>).</li></ul><p>Action menus should reflect user intent, not arbitrary layout states. When administrative controls are tied to content-editing modes, users spend less time creating and more time hunting through the UI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f07cfc7312a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Illusion of Scannability: A Tale of Two Identical Icons]]></title>
            <link>https://medium.com/@sampierce_75702/the-illusion-of-scannability-a-tale-of-two-identical-icons-837b80da554d?source=rss-3527e622e43a------2</link>
            <guid isPermaLink="false">https://medium.com/p/837b80da554d</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Sam Pierce]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 23:19:53 GMT</pubDate>
            <atom:updated>2026-08-29T23:19:53.927Z</atom:updated>
            <content:encoded><![CDATA[<p>I was browsing UI kits the other day, comparing pricing tiers like any designer trying to evaluate tooling. I landed on a pricing matrix — clean layout, sharp typography, modern minimalist aesthetic. Exactly what you’d expect from a product built <em>for</em> designers and developers.</p><p>Then I tried to actually compare the plans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rmFOAYo7rCgI9EDWg_sj7g.png" /><figcaption>shadcn product pricing module</figcaption></figure><p>At a glance, everything looks balanced. But when you try to scan across the tiers to figure out what you’re actually paying for, your eyes hit a wall.</p><h3>The Problem: When Visual Differentiation Disappears</h3><p>Pricing matrices exist to do one job: <strong>accelerate decision-making through rapid visual comparison.</strong></p><p>We rely on three primary visual signals to parse these tables in seconds:</p><ol><li><strong>Icon shape</strong> (Checkmark vs. Minus/X)</li><li><strong>Color coding</strong> (Positive state vs. Negative/Disabled state)</li><li><strong>Typography &amp; Contrast</strong> (Active feature vs. Muted/Disabled text)</li></ol><p>In this interface, two critical breakdowns occur:</p><ul><li><strong>Hue &amp; Luminosity Collapse:</strong> The green used for the included checkmarks is muted and pale. The gray used for the “Not included” minus icons is nearly identical in visual weight and lightness. Unless you lean in and inspect the individual glyph, the entire column looks like a uniform wash of low-contrast circles.</li><li><strong>Copy Overload in Place of State:</strong> Instead of disabling or dimming the row when a feature isn’t present, the table relies on explicit text like “Not included” alongside custom descriptors like “Official set only” or “React (Site only).” Because every cell contains an icon and a string of text with identical visual hierarchy, the brain is forced to read every single line sequentially rather than scanning down the column.</li></ul><h3>Why This Matters</h3><p>Design systems and component libraries often fall into the trap of prioritizing <strong>aesthetic uniformity over functional hierarchy</strong>.</p><p>When a design leans too hard into low-contrast, ultra-subtle palettes, it strips away the affordances that make tabular data usable:</p><ul><li><strong>Higher Cognitive Load:</strong> Users shouldn’t have to read four different cells to confirm whether a basic tier includes components. A quick vertical scan should reveal the “density” of value immediately.</li><li><strong>Accessibility Breakdown:</strong> If someone with standard vision has to squint to tell a pale green check from a pale gray minus, anyone with low vision or color vision deficiency has zero chance of parsing this table efficiently without assistive tech.</li></ul><h3>How to Fix It Without Ruining the Aesthetic</h3><p>Fixing this doesn’t mean slapping garish red X’s all over a clean interface. Subtle, functional hierarchy can be achieved cleanly:</p><ul><li><strong>Mute the Disabled State Entirely:</strong> If a tier lacks a feature, gray out both the icon and the text label. The contrast between active rows and disabled rows does the heavy lifting instantly.</li><li><strong>Differentiate Icon Geometries:</strong> A checkmark inside a filled or distinctively colored circle contrasts sharply against a simple, unfilled strike or hyphen.</li><li><strong>Let Absence Speak:</strong> Often, an empty dash ( — ) or an empty cell communicates “not included” far faster than a dedicated icon paired with the phrase “Not included.”</li></ul><p>When designing for developers and designers, polish is great — but clarity always wins. If your users have to read every word of a comparison matrix, the matrix has stopped being a chart and started being a paragraph.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=837b80da554d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>