Book a call

WritingTopic

Building a system

Auditing what you have, choosing what to build first, and documenting it so people can use it.

19 articles

Building a systemHow to build a design systemAudit, foundations, tokens, first components, docs and governance, in order. A staged 12-month plan with gates, so you invest only as fast as it pays off.11 min read · GuideBuilding a systemHow to run a design system audit (with an interface inventory method)Screenshot, group, count and prioritise every button, field and colour in your product. A step-by-step UI audit that ends in a ranked plan, not a slide.8 min readBuilding a systemDesign system documentationWhat people actually read in design system docs, the sections every component page needs and how to structure the portal. A page template to copy.8 min readBuilding a systemWhich components to build first: a prioritisation methodHow to choose your first design system components: count frequency and trouble, plot a 2×2, pick a pilot, and the eight components most teams start with.5 min readBuilding a systemBuild, borrow or buyShould you build design system components, use a headless library or theme a styled one? Trade-offs, a decision table and what we usually recommend.5 min readBuilding a systemComponent complexity: how to estimate design system workA scoring method for design system components: four levels of complexity, an eight-question rubric, and how complexity changes process and effort.6 min readBuilding a systemComponent props best practices: designing APIs people can useHow to design component props: the eight kinds of props, rules for good APIs, controlled vs uncontrolled, and keeping props in step between Figma and code.6 min readBuilding a systemAI in design systemsWhere AI genuinely helps design system teams today (docs, release notes, checks, migrations) and the cautions that matter when mistakes spread to every product.5 min readBuilding a systemDesign system patterns: when components aren't enoughWhat design system patterns are, how they differ from components, the four pattern families to start with, and a template for documenting them.9 min readBuilding a systemForm design patterns: layout, validation and error messagesSeven form decisions a design system should make once: layout, required fields, when to validate, where errors go, what they say, long forms and buttons.7 min readBuilding a systemContent design in a design systemHow to put words into a design system: voice and tone, a shared vocabulary, formulas for buttons, errors and empty states, and writing for everyone.7 min readBuilding a systemKeeping Figma and code in sync: five habits that stop driftHow to stop Figma and code drifting apart: one vocabulary, one token source, a shared definition of done, a monthly twin check and links between them.7 min readBuilding a systemDesign system tools by stageThe design system toolchain mapped: design, tokens, code, docs, quality and insight. The minimum tools for each stage, and what to automate first.6 min readBuilding a systemComponent states: designing every state before you buildEvery state a design system component needs: interaction, data, content extremes and context, plus combinations and a stress test with real content.6 min readBuilding a systemComposition vs configurationWhen to give a component settings and when to compose it from parts: slots, compound components, recipes, and the signs a component should be split.5 min readBuilding a systemTesting a design system: visual, behaviour and accessibilityHow to test design system components: lint rules, behaviour tests, visual regression tests, automated accessibility checks and manual keyboard testing.6 min readBuilding a systemAccessibility in a design systemHow to build accessibility into a design system's foundations, components and patterns, and what product teams still own. WCAG 2.2 AA in plain words.5 min readBuilding a systemHow to organise a Figma design system library people can useHow to structure a Figma design system: separate libraries, pages grouped by job, names that match code, descriptions, life-cycle status and detach data.6 min readBuilding a systemA design system roadmap for the first twelve monthsA realistic first-year design system roadmap: four workstreams over four quarters, a gate that earns each next quarter, pilots and the rhythms to start.5 min read