# Creating Design Language: Turn Shared Look, Feel, and Behavior Into Clear Choices

> Learn how a team picks a few words, turns them into visual traits, tests them on real screens, and repeats them so a product feels like one voice.

**In short:** Creating a design language means a team picks a few words, turns them into visual traits, tests them on real screens and repeats them so a product feels like one voice.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/creating-design-language

## Start Here: What You Will Learn

Many products look like several different apps. One screen has sharp corners and tight rows, another has soft shapes and lots of empty space, and a third uses words in a different way. Users notice this even when they cannot say why. This lesson shows how a team decides, in one place, what the product should look and feel like, and then repeats those choices on every screen. That shared set of choices is called a design language.

By the end, you will be able to explain what a design language contains, turn a few describing words into visual traits, test those traits on real screens, and see why repeating them builds trust and speeds up work.

- **Design language:** A shared set of look, feel, and behavior choices that makes all the screens of one product seem related.
- **Visual trait:** A specific thing you can see or sense on a screen, such as corner shape, spacing, color mood, or type style.
- **Density:** How much content fits into a space. Dense screens pack a lot in. Spacious screens leave more room around each item.
- **Motion:** Movement on screen, such as a panel sliding in, a button changing when pressed, or a page fading to the next.
- **Corner radius:** How round the corners of a box or button are. A small radius looks sharp. A large radius looks soft.
- **UI audit:** A review of what a product already has, such as its screens, colors, fonts, and spacing, before anything new is decided.
- **Design system:** The wider kit of reusable parts and rules that is built on top of a design language.

## What Is a Design Language?

A design language is an overall style that guides how a set of screens or products is designed, so they look like they belong together. Good design languages give a product a recognizable character and a sense of one coherent whole.

A design language covers three areas. Each one is a set of choices, and together they make the product's personality visible.

- **Look:** The visible surface: shapes, corners, colors, type, icons, pictures, and how much depth or shadow appears.
- **Feel:** How the screen seems to the user: calm or busy, tight or roomy, firm or playful. Density, spacing, and the weight of type all shape this.
- **Behavior:** How things respond: what happens when a user presses, scrolls, opens a panel, or moves between screens, and how quickly those things happen.

The choices should come from the product's purpose and its audience. A tool used by accountants at the end of a long shift needs a different feel from a game for young children, even if both come from the same company. A design language is therefore not a list of trendy styles. It is a set of decisions with reasons behind them.

> **Tip:** Before you pick any style, ask two questions: who uses this product, and how should they feel when they finish a task? Write the answers down. Every later choice should be easy to check against them.

### Coherent, Not Random

A random collection of styles looks fine on one screen and clashes on the next. A team might copy rounded buttons from one app, sharp panels from another, and a bright color from a marketing page. Each piece may look nice alone. Together they confuse the user, because nothing tells the user what kind of product this is.

A coherent language is different. Each choice has a reason that the whole team can explain. When a designer asks why a card has a soft corner, the answer should point back to the product's purpose and audience, not to personal taste.

## How Do You Build One?

Teams often start in one of two ways. Some begin with the brand, researching the audience, competitors, and identity first. Others begin with the existing product, doing a UI audit to list what is already on screen. Many guides recommend doing both: learn what the brand promises, then look at what the product already does before you write new rules. The steps below follow that order.

1. **Pick a few describing words:** Choose three to five adjectives that describe the product, such as calm, clear, and trustworthy. Keep the list short. Long lists give no clear direction.
2. **Check the words against purpose and audience:** For each word, ask whether the people who use the product would need it. If the audience is busy and stressed, playful may not help them, even if it sounds fun in a meeting.
3. **Translate each word into visual traits:** Turn each word into concrete choices you can see: corner shape, density, color mood, type character, and motion feel. The next part of this lesson shows how.
4. **Write the traits on one page:** Put the words, the traits, and the reasons together in a short document that every designer can read. This is the start of a visual vocabulary, the shared list of named choices.
5. **Test on real screens:** Apply the traits to a few real screens from the product and see whether they still fit the words. Adjust the traits, then test again.

### How Do You Turn Words Into Traits?

A word like calm does not tell a designer what to draw. Traits do. For each trait, ask what the word would look like on a screen. Here are five traits that many teams use, with one example of how the word calm might become a choice.

- **Corner radius:** For calm, choose medium-soft corners on cards and buttons. Very sharp corners can feel cold, and very round corners can feel playful. Use the same corner rule on related parts.
- **Density:** For calm, leave more space between items and show fewer things at once. A dense screen can feel urgent, which may not suit a calm product.
- **Color mood:** For calm, use muted blues, greys, and soft neutrals with one clear accent color. Bright, loud colors often feel more excited than calm.
- **Type character:** For calm, use one plain, readable typeface with clear size steps between headings and body text. Decorative or heavy type can add tension.
- **Motion feel:** For calm, use short, smooth movements that finish quickly and do not bounce. Long or springy motion can feel lively, which may be more than the product needs.

Notice that each trait is a choice someone can check. A reviewer can look at a screen and ask whether the corners match the rule, or whether the spacing matches the feel. That is what makes the language usable.

## How Do You Test the Language on Real Screens?

A language that reads well on paper can fail on a busy screen. Testing finds the gaps early. Pick three real screens that cover different jobs: one busy screen with lots of data, one simple screen with a single task, and one form. Apply your traits to each one. Then ask a person who has not seen the project to describe what the product feels like. If their words differ from your adjectives, the language needs work.

A case study of Material Design on Medium reported a small survey in which many people noticed the depth effect more than the paper idea behind it. The lesson is useful even if the survey is small: a trait is only working if people perceive it the way you intended.

> **Tip:** Test with a small group of real users, not only with your team. Designers often see the intent behind a trait, while a new user sees only the result.

## Worked Example: Material Design's Paper and Ink

Material Design is a design language from Google. It is used for Android apps and for other platforms, and its pages show how one idea can grow into many concrete traits. Its starting idea is that digital surfaces should feel grounded in the world of paper and ink. Follow the steps to see how that idea becomes choices you can see on a screen.

1. **Start with one metaphor:** Material's guidelines say the material is inspired by the study of paper and ink, yet it is allowed to do things paper cannot. This one metaphor is the core word that every later choice comes back to.
2. **Turn the idea into layered surfaces:** Surfaces and edges give visual cues that look real, so users can tell what is a sheet and what sits on top of another sheet. Screens are built from layers, not from one flat picture.
3. **Turn light into shadows:** The guidelines say realistic lighting shows seams, divides space, and shows which parts can move. Shadows therefore do a job: realistic lighting shows seams, divides space, and indicates which parts can move.
4. **Turn movement into a purpose:** Material treats light, surface, and movement as the basics that explain how objects move and relate to each other. Motion is therefore a meaningful choice, appropriate to focus attention and maintain continuity, not just decoration.
5. **Add print-style structure:** Material borrows from print design: type, grids, space, scale, color, and images create hierarchy, so the most important item on a screen is easiest to find.
6. **Check the traits across many screens:** Material is described as a system for Android and Flutter, and its iOS and web implementations are discontinued. In 2021 Google revamped the language as Material You, which is now called Material Design 3. The team can compare how the same metaphor is applied on each screen and see the repeated traits.

> **Tip:** Notice what Material did with its words. It did not stop at the phrase paper and ink. It wrote traits for light, shadow, surface, motion, and type, so a designer can apply the idea without guessing.

## Why Do Consistency and Recognition Matter?

When the same decisions repeat across screens, users learn the product once and then use it again without relearning. Consistency is the reason a design language exists. Recognition is the result: users see a familiar corner, color, or motion and know what it means. The benefits below are the main reasons teams invest in a language.

- **Users trust the product:** A product that looks and behaves the same way from screen to screen feels more reliable. Surprises make users wonder whether something is broken.
- **Users predict what happens:** Repeated interaction patterns let users guess what a button or panel will do before they press it. This improves ease of use.
- **Designers work faster:** When the corner rule, spacing feel, and color mood are written down, a designer does not have to invent them again for each screen. Decisions get faster and arguments get shorter.
- **Teams stay aligned:** A shared language gives designers, writers, and developers the same reference, so the product reads as one voice even when many people work on it.

Language also helps teams that grew without a plan. Many teams have a product built by different people over several years. A design language gives those screens one reference point, so the next change moves the product toward one identity instead of adding another style.

> **Tip:** Consistency does not mean every screen must look identical. A settings page can be quieter than a dashboard, as long as both use the same corner rule, color roles, and motion feel.

## The Foundation for Later Parts

The design language comes before the parts that use it. A design system is built on the language. Once the look, feel, and behavior are clear, a team can define reusable components, patterns, and written rules that follow the same traits. A button, a card, or an alert without a language has no clear rule to follow, so each one is decided alone.

Some guides describe the language as the visual principles and rules, while the design system is the practical toolkit of reusable parts built on that language. Others list the language as the first step of a longer process. Either way, the order is the same: decide the language first, then build parts that follow it.

> **Tip:** Keep the language short enough to read in one sitting. If it grows into a long manual, people will skip it. Update it when the product, audience, or market changes, rather than letting it drift.

## Quick Checks

**Quick check:** A team's app has sharp-cornered, dense, serious dashboard screens, but rounded, playful, spacious settings screens. The brand goal is calm and trustworthy. What should the team change first?

A. Rewrite the labels on the settings screen so they sound more formal.
B. Agree on one set of traits that fits calm and trustworthy, then test that set on a dashboard screen and a settings screen before changing anything else.
C. Add more animation to the dashboard so it feels lively and modern.
D. Keep both screen types as they are and build a separate component library for each one.

**Answer:** B. The mismatch shows that the team has no written traits yet. Traits come first, because every later screen change depends on them. Testing on both screens shows whether the traits work across the product. Label wording belongs to a different lesson, and more animation on the dashboard would move the product away from calm.

**Quick check:** A children's reading app team wants its screens to feel gentle and encouraging. Which plan follows the method in this lesson best?

A. Copy the bright, busy look of the most popular game in the app store so the app feels current.
B. Choose soft corners, generous spacing, a warm but muted color mood, clear type with large sizes, and short, gentle motion, then test those choices on a lesson screen and a reward screen.
C. Reuse the dark, dense layout from the team's finance product, since the team already knows it works.
D. Build the component library first and decide the feel later, once the buttons are finished.

**Answer:** B. The strong plan starts with the words, turns them into visible traits, and tests the traits on real screens. Copying a trend ignores the audience. Reusing a finance layout ignores the purpose. Building parts before the language skips the step that guides them.

## Key Takeaways

- **A language is a set of reasons:** Each look, feel, and behavior choice should trace back to the product's purpose and audience.
- **Words become traits:** Describing words only help when they become visible traits such as corner shape, density, color mood, type, and motion.
- **Testing is required:** Apply the traits to real screens and ask real people what they perceive.
- **Repetition builds recognition:** Repeated choices build trust, speed up design, and give later parts a stable base.

## Sources

- [Material Design: Introduction (m2.material.io)](https://m2.material.io/design/introduction/)
- [Material Design 1 Guidelines (mdui.org)](https://www.mdui.org/en/design/1/)
- [Material Design case study (principles.design)](https://principles.design/examples/material-design)
- [Material Design case study and Blogger redesign concept (Medium)](https://medium.com/10to24/material-design-case-study-and-google-blogger-redesign-concept-67dd112e2098)
- [Material Design (Wikipedia)](https://en.wikipedia.org/wiki/Material_Design)
- [Design language (Wikipedia)](https://en.wikipedia.org/wiki/Design_language)
- [What is a design language and how to create one? (UX Design Institute)](https://www.uxdesigninstitute.com/blog/create-a-design-language/)
- [Design Language: What It Is and How to Build One (Entropik)](https://www.entropik.io/resources/blog-articles/design-language)
- [Design Language System: The Role, Build and Implementation (VERSIONS)](https://versions.com/design/design-language-system/)
- [How To Develop A Design Language In 5 Simple Steps (Hapy Design)](https://hapy.design/journal/how-to-develop-a-design-language/)
- [Design Language: The Complete Guide to Building a Consistent Visual System (Daily Grammar Tips)](https://dailygrammertips.com/design-language/)
- [What Actually Constitutes Design Language? (UXPin)](https://www.uxpin.com/studio/blog/design-language/)
- [Design Systems (Part II: Design Language) (DEV Community)](https://dev.to/emmabostian/design-systems-part-ii-design-language-217k)
- [Creating a Design System Language for Your Product (Speckyboy)](https://speckyboy.com/creating-design-system-language/)
