
Systems Architecture + Governance
Associate Creative Director
Web & app — 3 foundation libraries · 3 child libraries · 30+ layout files
Overview
Brightspeed's digital product suite spans a marketing website, e-commerce buy flow, and a native iOS app, each with distinct layout requirements, component needs, and team workflows. Building cohesive experiences across that ecosystem required more than good design. It required architecture.
It started with a migration. I led the move of the original buy flow and account files from a single Sketch page into Figma, setting up the teams, file structures, and shared libraries the ecosystem grew from.
I established and maintained a network of interconnected Figma libraries, foundation libraries plus product-specific child libraries, alongside a FigJam governance environment documenting global patterns, visual rules, and design standards for the full team. The handoff system standardized developer documentation, component specifications, and annotation conventions across web and app, creating a single source of truth that product, design, and engineering could all build from.
App Foundation
App System Governance
The app foundation established the visual and component standards for Brightspeed's iOS account management experience. Built around 390px layouts, a 4-column grid, 8pt spacing system, and Figma variables, every element was validated against WCAG AA before entering the applied component library.
App Style Standards → Applied Components
Visual standards were established before any component was built, ensuring the system was consistent from the foundation up. Applied components pull directly from the app’s variables, so color, spacing, and type stay in sync across light and dark modes and both platforms.
Web Foundation
Web System Governance
The web foundation defined the shared visual language across the Account Management and buy flow web experience. Color tokens, typography scales, elevation, and motion principles were standardized here first, then extended through child libraries into both desktop and responsive web experiences.
Web Visual Foundation → Component Library
One foundation serving two distinct web products, Account Management and the buy flow, maintaining consistency without limiting either. Progress indicators, product cards, cart elements, and payment and service details are shared across both, so purchasing and managing an account feel like one experience.
Core Foundation
Core System Governance
The core foundation powers Brightspeed.com and serves as the brand’s core design system, supporting a high-velocity publishing environment. Reusable components for marketing pages, campaign layouts, promotional modules, and content templates gave the team the flexibility to move fast without drifting from the design system.
Core Standards → Page Components
Built for speed: a component library designed to support frequent content updates without requiring design intervention on every publish. Iconography, color, button states, and a responsive grid system give the team a consistent toolkit for every marketing page and campaign.
Handoff Foundation
Variables → Tokens
I designed and launched the variable systems behind both our app and web files. The app foundation shown here holds 260 variables across color, spacing, radius, sizing, and type, with modes for light and dark and for iOS and Android, so components reference intent instead of hard-coded values.
Because every component references variables instead of raw values, a single change updates the entire system, from a brand color to a spacing step, across every library and file that uses it. Each variable mirrors the token engineering uses in code, so developers see the same names and values in Dev Mode that they build with, and design and code stay in sync.
Flows → Handoff
Building on all three foundations, I designed the flows and led our product design team in extending them across every file. A shared page labeling system, template files, and reusable flow layouts keep all 30+ Figma files organized the same way. In our app and buy flow files, I also orchestrated a local component system that lets us make content updates on the fly, changing a component once and updating it everywhere, without disrupting handed-off screens or breaking documentation links. These flows are what our design team uses for product and engineering handoff, the basis for Brightspeed’s Confluence and Jira documentation, and engineering’s long-term reference in Dev Mode.
The app flows shown here map every journey from log in and the dashboard to account, billing, and support, with annotations from our UX team added through Figma’s built-in annotation tool, so behavior and requirements live right alongside the design. Designers, product managers, and engineers can open any file and find flows, states, and specs in the same place, which speeds up reviews, documentation, and build.
Outcome
One multi-library system. Three foundation libraries and three product-specific child libraries across web and app, serving as the single source of truth for design, development, and product teams.
Updates that flow through every layer. A layered system, from foundational tokens and variables through applied component libraries to local layout files, let design changes reach every flow step while preserving UX annotations, Confluence documentation, and live dev references.
A living rulebook. A FigJam governance environment documented global patterns, visual rules, and design standards for the full design team across 30+ layout files.
Consistent handoff. Standardized flows, page labeling, and file templates across every web and app file, feeding Confluence and Jira documentation and long-term Dev Mode references.
More Projects
Follow me
All rights reserved | ©2012–2026 | Michael Miller