DESIGN SYSTEM -Design at Scale

Vijay Chouhan
Sep 18 · 5 min read

Ever Tech and non-Tech company introducing design at scale in organization. they want to make more human-centric design or great experience. Building trust and responsibility.

the organization challenge of scaling digital product design and reveal How to design system can unite teams and provide consistency in the face of growing product demands. You are starting from scratch or evolving an exiting system, this up-close conversation offers real-world insight into modern design system and what they can solve. Effect of every complex system that works was invariably created from a simple system and that every complex system that was created from scratch as a complex system always breaks and fails and cannot be patched to work.

Design to scale is the next step of the design system. it’s the responsibility of the designer to identify the need of the customer and create great experiences with memories. Designer focus on thousand of brand and product and improving the interaction between them.

Design System

The component-based model was a massive step in the right direction. There was a reduced need for hand-off, however, there were now multiple sources of truth — in design tools, in code and sometimes in the documentation. There were reusable components, but usually no governance model of how to iterate. Which again lead to inconsistent UI or a need for constant design oversight.

that scalable, flexible, performant and assessable. I’m concerned with how this UI component finds their way into actual working software products. Need to focus on design for what’s next.

“A design system is not about invention, it’s about curation”

it’s not just lots of people working on the one thing, it’s lot of people working on lots of things, and I think that lots of organizations are finding themselves in that mode where they’re just, like, “How do we do this intelligently and efficiently?”

What I’m seeing more and more is that there is this challenge, particularly for larger organizations, but really for anybody who’s working on a large project or a large series of projects or products — one hand doesn’t know what the other hand is doing, even when they’re my own hands.

Imagine what happens when you multiply that times many people, times many projects, times many teams, times many years. What we get is this sprawl of design solutions where I have an idea and I implement it, but somebody across the hall or across the building or even across the world comes up with a similar solution for the same product, for the same company, maybe on a different page. They look sort of the same, but it’s a little through the looking glass. In any case, we’ve built this thing twice, we’ve done the same work for the same result, maybe with uneven results multiple times. It’s a waste of energy and effort and — frankly — of creativity and talent because we have great people solving the same problem over and over again.

There are a ton of different benefits of having a design system. They promote UI consistency and cohesion, allowing users to get done what they need to get done. It allows for faster production. It allows higher-quality production. It establishes a shared vocabulary between disciplines and different products. It makes things easier to test, so you’re able to create sturdier, more resilient solutions.

“We believe that design systems are a way to solve that problem by essentially pulling together the best solutions so that we can all profit from them. It creates a useful reference to keep coming back to as your teams do their product design work. Lastly, it provides a future-friendly foundation to grow and evolve the system over time.”

What a design system is a UI kit. That’s not what a design system is. That might be part of a design system, but just having a Sketch UI kit or a Photoshop UI kit or Studio UI kit, that’s only one tool. That’s only one piece and one that only designers can use.

Part of a good design system is that it’s a tool that everyone on a team can use, and the fact that a UI kit is locked up in a certain tool that other people aren’t familiar with means it’s not accessible to everyone. So, by definition, it’s not really a design system. It’s part of one. It could help you make one, but really we should be liberating all of our design tools from outside of a particular environment where it’s locked down and, instead, working on something that everybody can touch.

It’s important to reiterate that the kit of parts. One thing that’s dangerous about treating UI kits as a design system is that it really just reinforces what designers do all the time. Part of having a good design system is that it gets everyone a little bit outside of their comfort zone to be able to work with each other more, to engage more with each other. That might mean changing some process and changing some tooling and changing some of the work dynamic. So, for a designer to have a UI kit and Sketch or whatever tool or Illustrator or whatever they want, it really just says, ‘Just keep working the way that you’re working. Keep working in your environment. You don’t have to talk to anyone. You don’t have to collaborate with them.’

“I think part of what having a good design system will do is actually just get you outside of that comfort zone.”

A design system can include things like design principles, design tokens, high-level UX guidelines, development guidelines, the UI patterns, of course, but even going so far as to put those together into common page templates and user flows and sort of baking things into design tools.

It can include things like brand voice, tone, and writing guidelines. Processes are a big one, and including things like how you deploy the system into individual applications and how you contribute back into the system. Internal and external resources, things like links out to internal wikis and stuff like that, but also industry best practices. Articles, you know, links out to Smashing Magazine or CSS-Tricks to help understand why things are designed the way they are. All of these ingredients work together to help tell that canonical story of ‘here’s how our organization designs and builds products.’

“It’s not that UX design or visual design is no longer important, it’s just that you’re bypassing a lot of the artefacts that used to get a lot of attention.”

Thank you :)

Vijay Chouhan

Written by

Product Designer | Game Development | Mechanical Engineering

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade