esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Vision: The Short Statement That Guides Every Design System Decision

Learn what a design system vision is, how it differs from principles and style, how to write one that works, and how to use it to make hard calls.

In short

A design system vision is a short statement that guides every decision about the system, and it differs from principles, style and tone.

14 min readFree

What you will learn

A design system is a shared set of parts, rules, and guidance that a team uses to build its products. Teams that build one often lose sight of why they started. A vision keeps that reason in front of everyone. In this lesson you will learn what a design system vision is, how it differs from nearby ideas, what makes a good one, how to write and use one, and how to use it to settle hard choices about what goes into the shared system.

Key words

Design system
A shared collection of reusable parts, rules, and guidance that product teams use so their screens look and behave in a consistent way.
Vision
A short statement of the future a team wants to create. It says what the work is for and who it serves.
Vision statement
The written sentence or two that holds the vision. People can read it in a few seconds and remember it.
North star
A fixed point to steer by. In design, it is the goal that every choice is checked against.
Principle
A guiding idea that helps a team choose between options when the right answer is not obvious.
Trade-off
A choice where gaining one good thing costs you another. For example, a faster launch may mean fewer checks.
Stakeholder
Anyone with an interest in the outcome, such as a product manager, an engineer, a researcher, or a business leader.
Shared library
The central place where approved, reusable parts of the design system are kept for every team to use.

What is a design system vision?

A design system vision is a short, shared statement of what the design system exists to achieve and for whom. It describes the future experience the system should help create. Some teams call this a north star because it guides decisions from the big ones, like which problems to solve, down to the small ones, like which parts to build first.

Writers on design teams describe a vision as a statement of the desired future state. It should be aspirational, which means it sets a high goal, but it should also feel realistic. A vision is not a to-do list. It does not tell you the steps. It tells you where the work is heading and why it matters.

Atlassian shows how this looks in practice. Its official page says the goal is to be the cornerstone of crafting quality user interfaces in Atlassian apps, and its mission is to make it easy for teams to design, develop, and deliver high-quality Atlassian interface work. Read that and you learn the purpose and the audience at once. You do not learn the rules for buttons or spacing. Those belong elsewhere.

A vision also sits inside a bigger picture. Design system guides often describe a mix of parts: a vision, principles, visual elements, and documentation. The vision is the top layer. It gives the rest of the system its reason for existing.

  • Purpose

    The vision says what the system is for. For example, helping teams ship consistent products faster.

  • Audience

    The vision says who benefits. Often that is the product teams, and through them, the people who use the products.

  • Desired outcome

    The vision describes the result you hope to see in the future, not the work you do each day.

Tip

Ask one question to test a draft: does this sentence say what the system is for and who it serves? If it only describes what the team makes, rewrite it.

How does a vision differ from principles, style, and tone?

New designers often mix up four ideas. They sound alike, but each one does a different job. The vision sits at the top. Below it come principles, then the look and feel of the system, and then the way the words sound. Keeping them apart stops arguments that go in circles.

Principles are the next layer down. A design principle is a guiding statement that helps a team make trade-offs when the right answer is not clear. Writers who study this topic say principles focus on why a team decides something, while the principles of design focus on how a layout is put together, such as contrast, balance, and alignment. Principles guide judgement. They do not prescribe one exact result.

  • Vision

    Answers: what are we trying to achieve, and for whom? It is short and rarely changes.

  • Principles

    Answer: when two good options clash, which way do we lean? Each principle takes a stance that someone could disagree with.

  • Style and design language

    Answers: what should the system look and feel like? This covers colour, shape, and mood. It is covered in its own lesson.

  • Tone of voice

    Answers: how should our words sound? It describes the personality behind the text on each screen.

A simple way to remember it: the vision says where you are going, the principles say how to pick between roads, and the style and tone say how the trip should look and sound. A vision that talks about button colours has drifted into style. A vision that lists five rules for writing error messages has drifted into guidelines.

Tip

If a sentence starts with 'Always use' or 'Never use', it is probably a rule or a guideline, not a vision. Move it to the right place and keep the vision short.

What makes a vision statement good?

A good vision is easy to repeat. If a new team member cannot say it back after one reading, it will not guide anything. Several design writers suggest the same core traits. Here are the five that matter most for a design system.

  • Short

    One or two sentences is the usual target. Writers say the vision should be simple and easy to read, with no padding. A long vision becomes a document that nobody opens.

  • Memorable

    People should remember it without looking. Punchy wording helps, and so does a clear image of the outcome.

  • User and product focused

    The vision should show that the team thinks about the people who use the products first. It should not be only about the team's own tidiness.

  • Ambitious but believable

    It should stretch the team. Writers ask for a goal that challenges people, yet one a reasonable team could reach in a few years. A vision that nobody believes is decoration.

  • Tied to real goals

    The vision should connect to outcomes you can name, such as consistency, speed, quality, and accessibility. Accessibility means making products usable by people with a wide range of abilities, such as those who use screen readers or who cannot use a mouse.

Those last goals are worth a closer look. Consistency means the same part behaves the same way on every screen. Speed means teams can build new screens without starting from nothing. Quality means the parts are well made and tested. Atlassian's accessibility guidance says its components have accessibility features built in and that using the same components for the same experiences lowers the mental effort people need to use an app. Accessibility can be a goal inside a vision. The detailed rules belong in a separate lesson.

A vision should also set the system apart. Writers note that a good statement reflects what makes the product or company different from others. For a design system, that might be a promise to help small teams work like large ones, or to keep a large product family feeling like one product.

Tip

Check your draft against the five traits. If it fails two or more, it is probably too long, too vague, or too much about the team itself.

What goals can a vision point to?

Most design system visions point to a small set of outcomes. Choosing these outcomes is a team decision, and it should match the reasons the system was started. A team that began because products looked different from each other will name consistency. A team that began because launches were slow will name speed.

Atlassian's own history shows why this matters. A shared pattern fixed that. The lesson for a design system is that a vision aimed at consistency is an answer to a real pain, not a slogan.

Tip

Pick two or three outcomes at most. A vision that promises everything gives no help when you must choose.

How do you write and use a vision?

Writing a vision is a team activity. Someone may type the words, but the ideas should come from people who will live with the system. Designers, developers, and stakeholders each see a different part of the problem. Developers know where parts break. Designers see where screens feel different. Stakeholders know what the business needs.

  1. 1

    Gather input

    Hold a short workshop with designers, developers, and stakeholders. Ask each person what the system should make easier, and what problems they see today. Write every answer down without judging it yet.

  2. 2

    Find the pattern

    Read the answers together. Look for repeated words and shared goals. If many people mention speed, consistency, or trust, those are strong candidates for the vision.

  3. 3

    Draft one or two sentences

    Write a first version in the present tense, as if the goal were already true. Writers suggest this because it makes the vision feel real. Keep it short and plain.

  4. 4

    Refine and test

    Cut every word that does not add meaning. Ask: could a new hire repeat this? Could a product manager use it to say no? Check it against the five traits.

  5. 5

    Agree and share

    Get sign-off from the leaders who fund and govern the system. Then put the statement where people will see it, such as the top of the documentation and the first slide of any review.

Once the vision exists, its real job starts. It is a tool for everyday decisions. Two uses matter most for a design system: settling trade-offs and judging whether a new component or request belongs in the shared library.

  • Settling trade-offs

    When two good options clash, the vision tells you which outcome matters more for the system. For example, if the vision values consistency, a clever one-off idea loses to a shared pattern unless it solves a problem many teams have.

  • Judging new parts

    Before a new component enters the shared library, ask whether it helps the vision's goals. Will many teams use it? Does it match existing patterns? Can it meet accessibility standards? Maintaining each new part costs time, so every addition needs a reason.

  • Judging requests

    Stakeholders will ask for features. The vision gives you a neutral question to ask in reply: does this move us closer to the outcome we agreed on? This keeps debates about personal taste from taking over.

One caution applies. A vision is not a club for saying no. Atlassian's own values say the team avoids consistency for its own sake and rejects infinite flexibility. That is a balance. The vision should help teams make the right decision, not police every choice. A design system that blocks every product need will be bypassed.

Worked example: Atlassian's vision in a real decision

This example uses Atlassian's design system because its public pages state its purpose clearly. The short version used in this lesson is helping teams build consistent, accessible products faster. This is a summary of the aim, not a quote. The official page words the vision differently, so read the official wording when you need the exact text. Below, we walk through how one sentence like this could help decide whether a proposed new component belongs in a shared library. The steps are an illustration of the method, not a record of a specific Atlassian decision.

  1. 1

    Start with the request

    Imagine a product team proposes a new, heavily customized carousel, a row of content cards that slides sideways. It would appear in one product only, and the team wants it added to the shared library.

  2. 2

    Read the vision first

    Read the vision out loud. Ask what it asks the system to do: make products consistent, make them accessible, and help teams move faster. Each word is a test.

  3. 3

    Test for consistency

    Ask whether other products already have a similar pattern. If a close pattern exists, a second version creates the very fragmentation that Atlassian's navigation work describes, where each product did things differently.

  4. 4

    Test for accessibility

    Ask whether the carousel can be used with a keyboard, a screen reader, and other assistive tools. A custom part built from scratch needs its own checks. Shared components with built-in accessibility features save that effort.

  5. 5

    Test for speed

    Ask whether the faster path for every team is to reuse the part or to build their own. A one-off part forces each future team to learn it, and it adds upkeep to the library.

  6. 6

    Decide and explain

    The vision points to a clear answer. Keep the carousel out of the shared library for now. The product team can build it inside their own product. If other teams later show the same need, bring the pattern back for review with evidence. Explain the decision by pointing to the vision, not to personal taste.

Notice what the vision did. It did not design the carousel, set its colours, or write its labels. It gave the team one fair question to ask, and a reason to say yes or no that everyone could see. That is the practical power of a short vision.

Check your understanding

Try these two short scenarios. Use the ideas from this lesson, not guesses about what the team likes.

Quick check

Your team is split on whether to add a highly customized, one-off carousel to the shared library at a stakeholder's request. The system's vision is: help every team ship consistent, accessible products quickly. What is the best way to use the vision here?

Here is a second scenario. A design leader writes this vision for the system: make our design system the best in the world. A new designer says the vision is weak. Who is right, and why?

Quick check

Which statement best explains why the leader's vision is weak as a guide?

Key takeaways

  • A vision is the north star

    It states what the design system is for, who it serves, and the future it should create. It is short and stable.

  • Keep it separate from principles and style

    Principles guide judgement in hard choices. Style and tone describe how the system looks and sounds. The vision sits above both.

  • Make it short and believable

    Aim for one or two memorable sentences tied to real goals such as consistency, speed, quality, and accessibility.

  • Use it to decide

    Write it with designers, developers, and stakeholders. Then use it to settle trade-offs and to judge whether new parts and requests belong in the shared library.

Tip

Keep your vision where people will meet it often. A vision nobody reads cannot guide a single decision.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.