c/design-system-stories

Token naming inconsistency ate 3 days of my life last month

Our team spent 3 full days in Chicago tracing a spacing bug that only showed up in production because someone named a token 'space-md' in Figma but the dev file had 'spacing-medium', and it took a designer from another project to spot the mismatch, so has anyone else built a naming convention that actually sticks across teams or do we all just accept this chaos?

0 comments

stellag21•7d ago

TIL my old token naming was the real problem, not the team

I used to fight for semantic names like color-brand-primary and spent a week debating with developers in Austin about it. Then we switched to plain numbers like gray-500 and spacing-4, and suddenly everyone stopped guessing. Maybe it's just me, but the old way felt more human until I saw how fast our QA caught mismatches. Has anyone else found that boring, generic naming actually helps non-designers use the system better?

1 comments

theabennett•10d ago

My spacing token spreadsheet lied to me, took 3 weeks to see it

I built a token map for our checkout flow and every number checked out on paper, but the buttons looked cramped in the real app. My boss walked by and said "why is that padding uneven?" and I spent 2 days tracing values before finding out I'd mixed up two similar key names in the export. The fix took 10 minutes once I spotted it, but the trust hit with the dev team stuck around for weeks. Has anyone else had a naming convention that looked fine until it bit you in production?

0 comments

gavin928•10d ago

A dev in Austin swapped tokens before I could finish my complaint

I was at a meetup last month grumbling about how our button styles kept drifting, and this guy just pulled up our live site, swapped the CSS variables in devtools, and showed me the whole thing snap into place. That 2 minute demo convinced me to build a token layer before touching any more components. Has anyone else converted after watching a live fix like that?

0 comments

roberts.diana•11d ago

That $700 icon library set us back two weeks in Omaha

We bought a big icon package last March thinking it would speed things up, but every icon had weird stroke weights that clashed with our UI. I spent about 14 days patching overrides and custom paths before my boss said, 'just draw them yourself.' Has anyone else burned budget on a premium asset pack only to rebuild half of it manually?

1 comments

cooper.spencer•12d ago

Rant: token naming caught me on a Friday at 4pm

We were shipping a client dashboard in Austin and I found 14 different names for the same gray across 3 projects, like 'ash', 'cloud', and 'mist'. Merging those into one scale took 2 days and broke every shadow style we had. Has anyone else dealt with naming chaos from inherited files, or am I the only one stuck cleaning up someone else's mess?

1 comments

danieljenkins•12d ago

A component rename tore through 47 files and broke our docs for a month

I was in Denver on a Tuesday when I renamed Button to ActionButton to match the new API, and nobody ran the search-replace on the style guide, so our live docs still point to the old token while the codebase moved on, and now I check every alias against the actual export before merging, anyone else's design system versioning work like a game of telephone?

1 comments

ben_shah93•12d ago

My spacing scale broke after our team doubled in size last spring

When we went from 4 to 9 designers overnight, the old 4px grid fell apart because nobody could agree if 12 or 16 meant tight, and our PM literally yelled 'just pick one' during a March review, so has anyone else had to redo their tokens mid-project when headcount shifts?

1 comments

mitchell.shane•17d ago

Just realized I burned 300 hours on a custom icon library nobody asked for

I spent 12 weeks hand-crafting 240 icons for our internal dashboard, only to find out the team was already using a free icon set from the internet, so has anyone else sunk serious time into something the rest of the group never wanted?

0 comments

tessawebb•18d ago

Why does nobody talk about token drift after a team handoff?

Honestly, our design system at the Austin office went from clean to chaos in about 4 months after two senior devs left. The new crew kept adding hex codes straight into components instead of updating the shared tokens, so now our buttons show three different blues and the spacing is all over the place. Has anyone else dealt with a handoff like this, and what did you do to get the token library respected again?

1 comments

val_taylor•19d ago

That time a client said my tokens looked 'too consistent' and I nearly lost it

Working on a fintech design system in Austin about 8 months ago. Had all my spacing, type, and color tokens locked down. Every screen looked clean, aligned, the whole grid behaved. Then the client review comes back and the lead says, verbatim, 'Your system is too consistent. It feels robotic.' I stared at the screen for a solid minute. Turns out they wanted more visual rhythm, like intentional breaks in the grid for key numbers and actions. So I added a 'pulse' token set that lets certain data points scale up and break alignment on purpose. Now the system has rules for when to break the rules. Has anyone else gotten feedback that sounded like a compliment but was actually a complaint? What did you do with it?

1 comments

leo_price•21d ago

Button variants multiplied to 40 and nobody could pick one

At my last job we had 3 buttons on day one, then someone added a ghost with a thicker border, then a dark mode version, and before I left we had 40. The worst part was a new dev asked me which one to use for a checkout form and I literally opened 4 tabs side by side. After 6 months of this mess, we ran a quick audit and found 12 of those 40 were used in exactly zero places. We cut it down to 6 variants and tagged every one with a use case in our Figma file, but the damage was done. Now I ask any team I join how they handle button proliferation before I commit to their system. Has anyone else had to explain to management that extra options actually slow down the whole team?

1 comments

webb.xena•22d ago

That 40-page PDF review I made got printed and used as a coaster

Last Tuesday my boss printed out my 40-page design system audit to hold his coffee mug during a zoom call. He said the ring marks actually improved the readability, so now I'm wondering if I should add a 'stain resistant' layer to future decks. Has anyone else had a deliverable get repurposed in a weird way?

1 comments

betty_ward•25d ago

Color tokens that fall apart at 60% opacity

I kept seeing teammates pick a hex from our Figma library and paste it into code without checking how it handled on tinted backgrounds. Last month we shipped a dashboard where the success green turned muddy on a light gray card, and everyone blamed the monitor. Turns out our tokens didn't define any opacity steps, only solid values, so developers improvised with 60% alpha and it broke the contrast ratio. I added a tiny table in our docs showing each token at 40, 60, and 80 percent, and it's already cut three Slack questions this week. Has anyone else run into token opacity being the silent killer in their system?

1 comments

gavinwood•25d ago

Token-based theming doubled our CSS size, still worth it?

We moved our design tokens to a fully token-driven theme system for a client app in Austin, and the CSS bundle jumped from 120KB to 240KB. The upside is that swapping dark mode or brand variants takes minutes now, not days. My teammate thinks the bloat is fine on modern connections, but I'm seeing slower first paint on older phones. Has anyone else seen bundle size explode after going token-heavy, and did you find a way to trim it without losing the flexibility?

2 comments

the_shane•25d ago

Just crossed 1,200 components in our internal library, not sure if that's a flex or a red flag

We hit 1,200 components last Tuesday when someone added a third variant of a badge we already had two versions of, and I'm wondering if anyone else has a line where their design system stops feeling helpful and starts feeling like a hoarder's garage, or is that just me?

1 comments

pipergonzalez•27d ago

I thought token naming conventions were overrated until a 6 month project made me eat my words

Honestly, I used to think spending hours on naming tokens was just designer fluff. But after I had to redo 40% of a dashboard's spacing because nobody agreed on what 'small' meant, I finally got why folks push for something like 'spacing-4' instead of 'tiny gap.' Has anyone else had a project where bad naming cost real time?

2 comments

veraramirez•27d ago

Saw a pattern at a coffee shop in Austin last week

Three different teams all came in with their laptops open to the same crappy bootstrap grid and none of them had customized a single spacer. Has anyone else noticed agencies just copying each other's broken systems instead of building their own?

2 comments

-1

tara345•28d ago

Spotted a pattern library fail at a coffee shop in Portland last week

Honestly, I was grabbing a latte and noticed their digital menu board had 3 different button styles for 'order here' - rounded, square, and one with a drop shadow. It took me a second to figure out which one actually worked. Has anyone else seen a design system fall apart in a public space?

2 comments

lucas159•28d ago

Unpopular opinion: Bootstrap 5 actually saved my project last month

I've been hating on Bootstrap for years, calling it bloated and overused. But I took on a freelance job for a small restaurant site that needed to go from zero to live in 4 days. I caved and used their utility classes for spacing and typography, and honestly it cut my CSS time by like 60%. The grid system just worked on their menu page without me fighting media queries. Has anyone else had a moment where you ate your words on a framework you swore you'd never touch again?

2 comments

cameron_craig•1mo ago

I spent $300 on a premium icon library and it slowed down our whole project instead of speeding it up

Bought a big icon set from a well-known vendor for a dashboard redesign thinking it would save weeks of custom work, but the inconsistency in stroke widths and missing key symbols like 'export' and 'filter' made me spend more time patching than just making them from scratch in Illustrator. The team ended up overriding half the icons anyway, so that $300 basically bought us a lesson in what not to do. Has anyone else dropped real cash on a design asset that actually made things worse?

2 comments

josephb35•1mo ago

Just saw a weird color mismatch in a hotel lobby in Nashville

I was staying at a newer hotel off Broadway last weekend and noticed their design system fell apart at the edges. The lobby signage used a bright orange from their brand guide, but the digital kiosk screens showed a dull peach that clashed hard. Has anyone else run into issues where physical and digital versions of a color don't match up, and how did you fix it?

2 comments

miller.paul•1mo ago

Appreciation post: The atomic design method finally clicked for me after 3 years

I always thought Brad Frost's atomic design was overkill for our small team managing a few client sites in Chicago. But after rebuilding our button component for the 4th time in 6 months, I gave it a real shot and saw how the hierarchy actually prevents those duplicate component headaches. Has anyone else fought against a methodology for years only to have one messy project change your mind?

1 comments

patricia_wright•1mo ago

Hit 500 component variants in our design system last month, totally accidental

I was cleaning up old Sketch files from 2022 and realized we somehow drifted to 500 button variants across 3 projects before anyone noticed. Has anyone else run into variant bloat like this and found a good way to rein it in without breaking existing stuff?

1 comments

kai779•1mo ago

Had to choose between tokens in JSON or YAML for our design system last quarter

We had this big project where we needed to store all our design tokens. Half the team wanted JSON because it's what the devs already use. I pushed for YAML since it's easier for designers to read and edit. After 3 weeks of back and forth, we went with JSON because it played nicer with our frontend tools. Has anyone else had to fight this battle in their team?

2 comments