When I first got into design, the message was clear: there weren’t many jobs. It was competitive. Unpredictable. You had to fight for your place, and even then, nothing was guaranteed.
Over the years, we’ve watched the industry shift and evolve. We’ve had booms and busts, layoffs and hiring waves, moments of optimism and uncertainty. And right now, we’re in another one of those moments.
Designers are being told they need to know everything to get hired. And if that wasn’t overwhelming enough, there’s a new fear creeping in:
Too many people are getting into systems.There aren’t enough system roles.It’s already saturated.
But here’s the thing, I don’t think that’s a problem.I think it’s a sign of progress.
Let’s clear something up: when we talk about “getting into systems,” it’s not just about components, tokens, or managing a Figma library.
Those things matter, yes, but system thinking goes much deeper.
It’s about how you approach problems. How you design something that works across teams, use cases, and time. How you contribute to something that scales beyond your screen or your sprint.
System thinking is product thinking, just at scale.
Engineers have operated this way for years. Reusable logic. Shared patterns. Scalable architecture. When designers adopt that same mindset, collaboration shifts from parallel to genuinely cross-functional.
It’s easy to view the shift toward systems as just another trend. Another skill to cram into an already overloaded job description.
But what if it’s not just another box to tick? What if it’s a sign the industry is growing up, becoming more intentional, more collaborative, and more equipped to scale?
Because the more people who understand systems, the better supported those systems become. It’s no longer about relying on a single “system person”, it becomes a shared effort, baked into how teams work and grow together.
And that shift brings real results:
And you don’t need a “systems role” to play a part in that.
I get it — the idea of needing to be “full-stack” is exhausting. Designers are already being stretched in every direction.
But system thinking doesn’t have to add to the overwhelm. In fact, it can do the opposite.
It gives structure to your thinking. It connects the dots between scattered efforts. And it helps you design with intention, not just speed.
You stop reinventing the wheel. You design smarter. You understand where things connect, where they repeat, and where they fall apart. That clarity makes you more impactful, not because you’ve mastered everything, but because you’ve learned to zoom out.
This mindset benefits everyone on a product team —
System thinking helps entire teams align, not just individuals improve.
In smaller teams and startups, system skills help you grow smart from the start. You save time. Avoid waste. Build in a way that can scale without having to start over later.
In large orgs, it’s a different challenge, but just as urgent. Systems thinkers are the ones who bring alignment to chaos. Who spot duplication and help unify it. Who know how to adapt when needed, but also when to push for consistency.
Wherever you work, thinking in systems is a multiplier.
Yes, there may be fewer roles with “design systems” in the title right now. But that doesn’t mean the work isn’t happening. Systems show up in every product team trying to scale something well, whether or not they call it that.
Systems thinking makes you a stronger designer.A more collaborative teammate.A more intentional contributor.
And you don’t need to wait for permission to start thinking this way.
So if you’ve been curious but hesitant, consider this your sign:
The future needs more systems thinkers.And you don’t need a job title to become one.