Iron Goo
Three coworkers review five different button designs on a monitor in a small office.

Design System for Small Teams: What to Build

Atamyrat Hangeldiyev
Atamyrat Hangeldiyev
Systems Architect
March 12, 2026
On this page
UX

Imagine three people edit your website: the owner, an office manager and a freelancer. Across ten pages, the main call-to-action button has accumulated five colors and four labels. Nobody chose that result.

For a design system for small teams, start with the smallest set of decisions that fixes the problem for the people editing the site. Most small teams do not need a complete system in Nielsen Norman Group's sense: its Design Systems 101 article says creating and maintaining one requires a dedicated team. Consistency is one part of UX for a small business, alongside the usefulness and clarity of the experience.

Six options, from a one-page guide to coded components

A style guide records decisions about appearance and content. A design system, as NN/g defines it, is a complete set of standards for design at scale, supported by reusable components and patterns. Between those two descriptions are several useful, smaller choices.

The ladder is ordered by typical effort, although an existing builder theme can be quicker to configure than a guide is to write. Sources and prices were read on 30 October 2026.

OptionWhat it isWhat it protectsOne sourced fact
One-page style guideA short record of approved visual and writing choicesDecisions editors otherwise make independentlyNN/g includes a style guide in a design system repository.
Builder theme settingsShared values and reusable settings in the website platformColors, type and other settings the platform can apply across pagesShopify saves theme editor selections in settings_data.json.
Design tokensNamed values stored in a format code and tools can readShared values across implementationsThe 2025.10 format is a W3C Community Group Final Report, published 28 October 2025.
Figma component libraryShared design components people can use in FigmaConsistency in design filesTeam-wide design libraries are a Professional plan feature.
Adopted open-source systemAn existing system adapted for an eligible useReusable patterns and components without starting from scratchGOV.UK Frontend code is MIT licensed unless stated otherwise.
Coded component libraryReusable site components maintained in codeThe actual components developers put on pagesNN/g's minimum design system team includes a developer.
An amber arrow rises beside four steps labeled Style Guide, Tokens, Component Library and Code.

The picture shows four of the six options, with each step adding something to maintain. Choose the lowest step that resolves the decisions your editors repeatedly face.

A useful one-page guide records one primary and one secondary button, including their color pairs and intended uses. Give action labels a verb plus an object, such as “Request a quote,” and use the same label for the same action; the UX writing and microcopy guide helps with that wording. Add the type scale, spacing steps, link style, form field and error styles, logo rules, navigation order, and the position of repeated help links.

Five inconsistent button variants become one primary and one secondary style.

The five variants have accumulated different appearances. The two approved styles give editors a clear choice based on the action's role.

In Shopify, settings_schema.json defines theme settings and settings_data.json stores the selections made in the theme editor. Webflow variables include color, size, percentage, number and font types. These settings can enforce shared choices where editors use them consistently. Shopify's theme settings documentation describes the two files.

Design tokens give those choices names. A token is at minimum a name and value; $value is required, while $type can be left off a token when a parent group or a referenced token supplies it; otherwise the token is invalid. The Design Tokens Format Module 2025.10 is a Community Group Final Report, not a W3C Standard or a document on the W3C Standards Track. Files can use .tokens or .tokens.json, and curly braces identify aliases.

This minimal file names a brand color, aliases it for actions and defines a spacing value. The color and dimension values are objects in the 2025.10 format; an old example that uses a plain hex string for the color does not follow this format.

{
  "color": {
    "$type": "color",
    "brand": { "$value": { "colorSpace": "srgb", "components": [0, 0.4, 0.8], "hex": "#0066cc" } },
    "action": { "$value": "{color.brand}", "$description": "Primary buttons and links" }
  },
  "space": {
    "$type": "dimension",
    "md": { "$value": { "value": 16, "unit": "px" } }
  }
}

White text on #0066cc has approximately 5.6:1 contrast by our calculation, above the 4.5:1 threshold for normal text. That check applies to this color pair; other states and adjacent colors need their own checks.

Figma components protect decisions in design files, while coded components can carry those decisions into the site itself. Figma's pricing page lists a Professional Full seat from $16 per month; check the page for billing terms and the seats your team needs.

Brad Frost's Atomic Design offers a way to describe a library: atoms, molecules, organisms, templates and pages. Frost calls the five stages a mental model and says the process is not linear. You can start by fixing a problematic page or form; there is no requirement to build every atom first.

28 October 2025
Design tokens report published
From $16 per month
Listed Figma Professional Full seat
24 by 24 CSS pixels
Minimum target size

An adopted system requires a fit check before anyone starts copying components. The GOV.UK Design System is intended for people working on government services. GOV.UK Frontend code is MIT licensed unless stated otherwise, and its documentation uses the Open Government Licence v3.0. For a service outside GOV.UK, its unbranded guidance requires Frontend v6.3.0 or later, the Generic header, your own brand color and image assets (favicons, home screen icons, sharing image), and a font other than GDS Transport.

Shopify Polaris is for applications that integrate or interoperate with Shopify software or services. Its custom MIT-based license restricts use accordingly, so it is not the choice for a storefront theme or an unrelated company site. Polaris React is deprecated; Polaris Web Components were released on 1 October 2025 for Shopify app development.

Material 3 is the latest version of Google's open-source design system. The @material/web library is Apache 2.0 licensed and is in maintenance mode pending new maintainers; that status applies to the library, not a claim that Material as a whole is deprecated. Check the Material Web repository before making it a dependency.

Check the system before adopting it

Polaris has a license restricted to applications that integrate or interoperate with Shopify. GOV.UK Frontend requires removal of GOV.UK branding for use outside GOV.UK. Adopting either wholesale for an ordinary company website creates a licensing or branding problem.

If one person edits the site

Our rule of thumb: for one owner or marketer editing fewer than about 30 pages, start with a one-page style guide and the builder's shared settings. Count the pages you maintain, including landing pages, rather than counting only the pages in the main navigation.

  • If consistency is the need, use the one-page guide to settle button purposes, labels and color pairs. Then apply those choices through the builder's theme settings wherever available. Review the ten most visited pages and record each button variant before changing it.
  • If new pages take too long, save a reusable builder section for each repeated layout. Give it a name that describes its job, such as a contact section, and specify which content an editor may change.
  • If accessibility is the need, record the checked color pairs, focus treatment, navigation order and help-link position in the guide. Check each new page against the accessibility floor; a saved setting cannot check whether its label or context makes sense.
  • If you generate page drafts with AI, provide the one-page guide and a closed list of allowed sections. Review the resulting page against that list and the guide before publishing. Our inference is that a closed vocabulary reduces drift by limiting the choices the generator is asked to make.

A style guide is sufficient only while someone keeps it current. When you intentionally change a button label or color, update the guide and the shared setting together, then check the pages that use the old choice.

If two to five people edit with a freelancer

Our rule of thumb: with two to five editors, use a one-page guide plus locked theme settings. Componentize when the same component has been hand-built three or more times, or when you produce more than about two new landing pages a month. Tokens earn their keep when someone writes code that can use them.

  • If consistency is the need, agree on who can change the shared settings and restrict access where the platform permits it. Give every editor the guide, including the allowed button labels and the owner of changes to those labels.
  • If speed is the need, turn repeated work into builder sections or symbols, a Figma library, or coded components, depending on who produces the pages. Start with repeated steps in the conversion path, where an unclear action or an inconsistent form affects a visitor's next decision.
  • If accessibility is the need, make the approved component include its label, states and checked colors. Have an editor check each use in context, including whether navigation and repeated help remain in the expected order.
  • If AI-generated pages are the need, give the generator the approved component names and the guide, or the tokens file if a developer uses one. Treat its output as a draft: an editor checks the selected components, labels and color pairs against the approved list.

NN/g says design systems are best suited to companies that foresee years of future, repeatable design work. It also says adopting or adapting an existing system costs less time and money than building one. Check intended use and licensing first, then compare the work of adapting the system with the smaller job your editors actually repeat.

If an agency built the site

Our rule of thumb: commission a coded component library only if a developer will maintain it at least monthly. Ask for that responsibility and its cost to be explicit in the handover; a library without an owner is another place for decisions to go stale.

  • If consistency is the need, request the tokens file or theme settings and a component inventory. The inventory should name each reusable component, where editors can use it, its available states and who can change it.
  • If speed is the need, ask the agency to show an editor how to assemble a representative new page from the existing sections. Record which changes the editor can make without developer help and which require a code change.
  • If accessibility is the need, ask for the checks performed on shared components and for known exceptions. Assign someone to check actual pages as content and layouts change; a component inventory is evidence of what exists, not a conformance certificate.
  • If AI-generated pages are the need, provide the generator with the handed-over tokens or allowed component list and the one-page guide. Have a person compare the generated page with the inventory and guide before it goes live.

If the agency proposes an open-source system, ask which version it will use and whether the license and intended use fit the site. A company whose existing pages have drifted across multiple implementations may need a rebuild; Iron Goo's site rebuild moves patterns into templates and components so they are reused by construction.

If the site runs on a no-code builder

Our rule of thumb: for a Webflow, Wix, Squarespace or Shopify theme site edited without custom code, treat the available theme settings and reusable sections as the working system. Keep a one-page guide for decisions the settings cannot enforce, and control changes to the shared settings where the platform allows it.

  • If consistency is the need, set the approved colors, fonts and reusable sections in the builder. Prohibit one-off overrides unless the person responsible for the guide approves and records the exception.
  • If speed is the need, duplicate an approved section or use a saved symbol where the builder supports it. The editor should change content and links while preserving the shared structure and styles.
  • If accessibility is the need, check the theme's actual text, component states and target sizes. Record approved color pairs and focus styles in the guide, then verify that each page uses them correctly.
  • If AI-generated pages are the need, supply the one-page guide and the closed list of allowed sections. Review the generated result against both before publishing; our inference is that restricting the vocabulary reduces opportunities for visual drift.

For a Shopify storefront, use the theme's own settings and sections. Polaris is intended for eligible Shopify-integrated applications, not storefront themes. A team may need help configuring a theme, but that decision does not require importing an app design system.

The accessibility floor for every option

WCAG 2.2 became a W3C Recommendation on 5 October 2023. Its consistency criteria describe observable behavior across a set of pages, not a requirement to buy a particular tool or maintain a particular library.

Components that have the same functionality within a set of web pages are identified consistently.

W3C, WCAG 2.2 Success Criterion 3.2.4

That is SC 3.2.4 Consistent Identification, Level AA. For example, if a search control performs the same function across pages, identify it consistently. The criterion does not require two buttons with different functions to have identical labels.

SC 3.2.3 Consistent Navigation, also Level AA, requires repeated navigation mechanisms to appear in the same relative order unless the user initiates a change. SC 3.2.6 Consistent Help, Level A and new in WCAG 2.2, requires repeated help mechanisms to occur in the same relative order. Record the navigation order and help-link position so an editor can check them on each page.

For visual and interaction checks, apply these WCAG 2.2 criteria to the relevant content:

CriterionCheck
1.4.3 Contrast (Minimum), AAText contrast is at least 4.5:1, or 3:1 for large-scale text.
1.4.11 Non-text Contrast, AARequired component boundaries and states have at least 3:1 contrast against adjacent colors.
2.5.8 Target Size (Minimum), AATargets are at least 24 by 24 CSS pixels, subject to exceptions including spacing.

A style guide can fix an approved text and background pair once, allowing you to check that pair once and reuse the result wherever the same pair appears. Check each different pair and state, and check the actual page for other issues. No option in the ladder makes a site conform by itself; use the accessibility and inclusive design guide for the wider work.

Choose what to build for your situation

Effort descriptions are Iron Goo estimates, not guarantees. They assume the team has access to its existing site settings and can make the relevant decisions.

SituationWhat to buildEffortWhat it protects
One editor, fewer than about 30 pagesOne-page guide and shared builder settingsAn afternoonBasic visual and writing choices
Two to five editorsGuide, controlled theme settings and a named ownerAn afternoon, then ongoingChoices shared across editors
A component hand-built three or more timesReusable builder section, Figma component or coded componentAn afternoon to a weekThe repeated component's structure and states
More than about two new landing pages a monthReusable sections for repeated conversion stepsA week, then ongoingAssembly speed and repeated page patterns
Agency-built siteTokens or theme settings, plus a component inventory and handoverA weekThe team's ability to use and maintain what was built
Custom-coded site with a developer available monthlyCoded component library with an assigned maintainerA week to start, then ongoingReuse in the live site's code
No-code builderTheme settings, reusable sections and a one-page guideAn afternoon, then ongoingShared choices without custom code
AI-generated page draftsClosed list of allowed components or tokens, plus human review against the guideAn afternoon to prepare, then ongoingThe boundaries and review process for generated pages
Need accessibility checksChecked color pairs, focus style, navigation order and help position recorded in the guide and built into shared components, plus a check of every new pageAn afternoon, then ongoingRepeatable checks against WCAG 2.2 criteria such as 3.2.3, 3.2.4, 1.4.3 and 1.4.11
Free ebook

Put your next steps in order

Build on what you have just read with a free ebook on semantic SEO and AI visibility. Get worked examples, decision rules, checklists and a do-this-week action in every chapter, plus a six-week plan for your site.

By signing up and confirming your address, you consent to receive the free ebook plus one email every two weeks with 3 or 4 new Iron Goo videos, guides and articles, and nothing else; unsubscribe any time with one click.

Related in UX

Ready to move?

Tell us where your business is today. A written assessment lands in your inbox within two business days.

Talk to us