ADM Design System — From Zero to a Scalable UI Platform

When I joined ADM (Archer Daniels Midland), there was no design system—teams shipped bespoke screens, UI drifted, and handoffs were slow. I championed, along with another UI designer, the need for a reusable system, aligned stakeholders in the CoE(Core of Excellence), and built an extensible foundation. Leveraging Untitled UI as a pragmatic baseline, I accelerated initial production, then expanded into a branded, token-driven platform with 2,000+ versioned components. We’re live on v2.1 today and actively building v3—a redesign that modernizes key products and raises our quality bar across the portfolio.

Research and discovery phase

Audit → align → accelerate
  • UI audit: Cataloged patterns across flagship apps; identified inconsistencies in spacing, color contrast, and interaction states.
  • Benchmarking: Selected Untitled UI as the starting blueprint to speed foundation work (grids, form controls, states).
  • Governance model: Defined contribution workflow, versioning, and “breaking change” policy to keep teams moving safely.
  • Accessibility bar: WCAG 2.1 AA color tokens, focus states, and keyboard interaction specs.
  • Initial design exploration

    Bootstrap the system, fast—without cutting corners

    We stood up a tokens-first architecture (color, type, spacing, radii, elevation), mapped Untitled UI primitives into ADM brand, and created base components for common cases (buttons, inputs, selects, alerts). Documentation shipped with usage guidance and do/don’t examples so teams had clarity on day one.

    • Foundations: Color scale + contrast matrices, type scale, spacing grid, shadow/elevation rules.
    • Base components: Buttons, inputs, text fields, selects, checkboxes, radios, toggles.
    • Docs: “Buttons should look like buttons” best-practice notes, interaction recipes, and naming conventions.

    Refining the design approach

    From kit to platform

    After foundations, we expanded into complex components and patterns (tables, filters, pagination, empty states, banners, wizards). We versioned everything and added changelogs, migration notes, and a request → review → publish pipeline.

    • Versioning: Semantic releases (e.g., 2.0 → 2.1) with migration guidance.
    • Theming: Light/Dark tokens + high-contrast variants.
    • Dev parity: Figma specs mirrored in code with properties/variants mapped 1:1.
    • Quality gates: A11y checks, design review, and token tests before publishing.

    Project impact and user feedback

    Outcomes across products

    The system turned design from a project-by-project craft into a product platform.

    Reusable components reduced duplicate work and UI drift across teams
    Faster delivery from shared tokens and ready-to-use patterns (smoother handoff, fewer re-reviews)
    Consistency + accessibility: AA contrast baked into tokens and states
    Adoption across apps including Chat ADM; teams cite clearer specs and predictable behavior
    Roadmap:v2.1 live; v3 in development with a visual refresh, 2000+ components and project redesigns aligned to the new version

    Explore more design work

    Interested in seeing how design can transform digital experiences? Check out more case studies showcasing innovative UX solutions