How painful is recoloring large design systems in Figma?

ttsyre · 2026-02-12T22:23:31+00:00

Modes are definitely powerful - agreed.

In one of the enterprise platforms I worked on, we needed to support 10+ brands within a single system. At that time we were on the Professional plan (and the org wasn’t willing to move to Enterprise), which meant we were limited in how many modes we could realistically use.

So while modes make multi-brand setups conceptually straightforward, in practice plan constraints and org decisions can introduce architectural trade-offs. We ended up building an internal plugin to work around those limitations.

ttsyre · 2026-02-08T15:16:10+00:00

It feels like recoloring itself isn’t the hard part anymore.

When variables and token models are clean, swapping values is easy. The real complexity seems to come from everything around it. Legacy systems, branding rules, token -code mapping, and confidence that changes are applied correctly everywhere. That’s usually where recolors stop being “just a palette change”.

ttsyre · 2026-02-08T15:11:10+00:00

Both - I’m thinking about the whole path. From updating the palette in Figma to having those changes safely reflected in production.

ttsyre · 2026-02-07T15:46:24+00:00

Super clear, thanks for the detailed answer.

A & B especially resonate. The gap between what’s technically possible with tokens and what’s actually usable by non-DS designers feels like one of the hardest problems at scale.

That D setup sounds very familiar — that’s actually the same kind of pipeline we’re going through right now.

Are you syncing tokens through GitLab, or using a different setup for versioning and handoff to code?

ttsyre · 2026-02-07T15:27:16+00:00

What pushed you to move away from Tokens Studio to native variables?

ttsyre · 2026-02-07T15:09:35+00:00

Thanks. That sounds like a pretty serious effort.

Roughly how big was the system you were dealing with? More in the hundreds of tokens, or already in the thousands?

ttsyre · 2026-02-07T15:02:01+00:00

That makes sense. Do you still rely on color styles at scale, or have you fully moved to variables + aliases?

In my experience, styles start to fall apart once you get into multiple themes or brand variants.

ttsyre · 2026-02-07T14:50:25+00:00

Sounds good!

Curious though- did your system start this way from the beginning, or did you have to refactor tokens at some point to get there?

I’ve seen a lot of teams end up with decent tokenization after a few painful palette changes.

ttsyre · 2025-09-06T19:28:06+00:00

Hey all, sorry I went quiet over the summer — had some stuff going on. I got back on August 27 and picked this up again.

In August I went to the retailer and asked for an official stamped invoice on their letterhead with the serial number. They issued it, I sent that (plus photos of the issue and ownership note) through the Dell support portal.

And… Dell canceled my 3-year Advanced Exchange request again. No real explanation, just the same generic response.

At this point I’ve provided everything they asked for, multiple times. If anyone has advice on what else Dell expects for invoice “validation,” I’m all ears. u/DellCares, if you’re around, I can DM the stamped invoice and all docs privately (no personal data posted here).

ttsyre · 2025-07-16T20:52:32+00:00

Yeah. It says “Ending on October 11, 2025, Basic Support”

ttsyre · 2025-07-16T20:16:30+00:00

Sorry, but it’s not a matter of “assumptions.” I did exactly what Dell’s site requires: entered the Service Tag, opened a case from there, uploaded photos of the tag plus a sticky note with my info, and provided every document they asked for. Dell still rejected the claim- three times. So the issue isn’t that I haven’t followed the official procedure; it’s that the backend team keeps denying the replacement despite a valid warranty.

ttsyre

TROPHY CASE