It takes more thanto solve complexproblems.It takes wearing many hats.
Designops for teams of one
Infrastructure for the generalist designer.
Many Hats is for designers who move between research, strategy, design, and delivery because the work demands it. It's not about doing more. It's about doing what you already do with the systems to support it.
The Bar No One Can See
When leadership says 'we have a high bar' but never shows anyone what it looks like, the message is clear. Growth isn't the plan. Replacement is.
Design Ops When You're the Whole Team
I learned what operations meant before I had a word for it. Growing up in my family's restaurant, I saw what it takes to keep a kitchen running. Design ops isn't that different.
From Pixels to Prompts
I've used every generation of design tools, from MS Paint to Figma to vibe coding. The pattern keeps repeating.
Resources
Book time
Coming soon
Talk through your design ops challenges or compare notes on running design solo.
Toolkits
Waitlist →AI-powered skill packs that handle the operational overhead. Systems that grow with your practice.
By the numbers
Designers carry the work of many roles but the title of one
You run discovery in the morning, present strategy at lunch, build prototypes in the afternoon, and update stakeholders before you log off. None of that shows up in your title.
The gap isn't in skill. It's in infrastructure. Engineering and product have had operational systems for years. Design is still improvising.
64%
identify with 2+ roles
92%
say their process needs improvement
1:20
designer-to-developer ratio