A brand is a system you develop, not an artifact
Leo Tanaka
Motion & Systems Lead
Every week, another venture-backed startup unveils an immaculate brand identity complete with custom display typography, tactile packaging mockups, and a 60-page PDF manual. Six months later, visit their Twitter feed or product changelog: the system has eroded into generic Canva templates and inconsistent gradients.
“Design for the intern creating a slide deck at 11 PM six months after your agency has left the building.”
The artifact fallacy
Most agencies treat identity as an artistic artifact — a museum piece to be unveiled, celebrated on social media, and cataloged into their portfolio. But brands exist in the wild, subject to entropy. They are operated by junior copywriters, growth marketers, and engineering leads who have never heard of grid ratios or optical kerning.
Designing for operational survival
At Arca, we evaluate our systems not by how sublime the master Figma file looks, but by how difficult it is for non-designers to break. This means establishing rigid constraints: two type sizes instead of six, four colors instead of twelve, and explicit negative space boundaries baked directly into code components.
Living code over static PDFs
Static brand PDFs are where good design goes to die. Our deliveries center on production-ready React / Tailwind token packages, pre-composed layout primitives, and video walkthroughs. When brand guidelines live in your codebase and CMS, consistency ceases to be a disciplinary struggle and becomes the default path of least resistance.
Leo Tanaka
Motion & Systems Lead at Arca®. Writing on design systems, studio velocity, and architectural digital craft.