Fieldnote
Design system and component library giving a small team a shared visual language.
2025
Systems design
Placeholder client
Shipped
Design System
Overview
A small product team was rebuilding the same buttons, forms, and cards in every feature — each slightly different. Fieldnote is the shared system that replaced that drift: tokens, components, and usage guidance in one place.
What I did
Defined the token architecture — color, type, spacing, radii — then built the component library on top of it, documented with real usage examples rather than abstract specs. The system lives in code first, so design and build never disagree about what exists.
Outcome
New screens compose from existing parts instead of spawning variants, and onboarding a new developer no longer starts with “which button is the real one?”