Leading Design Innovation
Design gets positioned as strategic so often that the phrase has stopped meaning anything. The actual work is simpler to describe: showing up in places where design decisions have real consequences and making sure the right calls get made.
Working close to the product
The most useful work I've done has been at the edges of what designers are typically expected to own — where a token architecture means a wrong choice breaks four brands instead of one, where an agentic workflow needs guardrails that account for human judgment, where a QA process either catches a problem before code review or surfaces it in production.
That's not a positioning claim. It's what happens when designers stay close enough to the work to understand what's actually at stake.
Building infrastructure, not just outputs
Most of the leverage I've found comes from the infrastructure underneath the work: a shared token layer that keeps Figma, code, and AI tooling in sync across brands; a lint pipeline that catches hardcoded values before they reach the codebase; a one-command dev loop that lets designers work in real components without touching the dev environment.
None of it shows up as a screen. All of it changes what's possible downstream.
Automating the mechanical parts
A large part of building Genie was identifying which parts of design work are mechanical — audits, component mapping, requirements synthesis — and building systems to handle those, so designers can direct their energy toward what actually requires judgment.
The point wasn't automation for its own sake. It was protecting the time and attention that design thinking requires.
What this looks like in practice
A token pipeline that scales across four brands and two themes. A design agent that removes setup friction from client work. QA processes that catch problems at source rather than after handoff.
Strategic design is the consequence of specific decisions made close to the work, not a way of describing the work from a distance.
