The word designer doesn’t mean what it used to. Designers used to solely craft. Now they’re shaping systems, behaviors, and even algorithms. Design has become an operating system for how organizations think and make decisions.
For emerging designers, learning to build in these areas might be as important as learning how to design within them.
I’m curious how Seniors / Leaders might be encouraging their teams to take these leaps?
One initial thought I have is giving designers visibility into how decisions actually get made. It seems when designers understand the system around their work, they can influence it more effectively.
Ah, the classic debate…Capital D Design vs design craft. It’s always been a thing, but when teams retract and scale down, those old patterns come right back too. What’s old feels new again.
We’re seeing a split in how people approach design today.
Some are doubling down on the craft (pushing the edges with motion, layers, and immersive visuals like liquid), and it’s got that same energy Flash (dating myself) once gave designers, a playground to explore and experiment.
Others are taking a different path, realizing that design impact comes from influence…which requires working across systems, technology, and people to make change. Both paths matter, but it’s how they connect that will shape where design goes next.
@Raul_Jimenez of course! For context, I’m coming from an Ops perspective
I think there can be obvious nuance (org maturity, etc) but here are some examples that come to mind: In our world, our team (designer included) are actively creating AI system prompts / structures to ensure a strong data output based on the parameters we want for our product.
Additionally, leveraging systems, review processes, and design delivery “standards” creating guardrails (if you will) that guide how design is implemented across the organization. (The expectation IMO has shifted to the idea that every designer should be able to uphold these vs just a Lead)