It takes more than
to build great products.
It takes wearing many hats.
Many Hats is for the generalists. Designers who move between research, strategy, design, and delivery because the work demands it and the systems to support that range weren't built for them.
designops for teams of one
Infrastructure for the
generalist designer.
Many Hats isn't about doing more. It's about doing what you already do with the systems to support it. The frameworks, toolkits, and knowledge to work efficiently and scale your impact without burning out.
When designers can show what they actually do, the work gets recognized and compensated. That's how you move from individual survival to collective leverage.
01
Blog
Observations on design tools, operations, and what it actually looks like to run design as a team of one.
Read →02
Book time
Want to talk through your design ops challenges or compare notes on running design solo? Book a session.
Coming soon
03
Toolkits
AI-powered skill packs that handle the operational overhead. Ongoing systems that grow with your practice, not one-time templates you stop using.
Join the waitlist →Why this matters
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. Figma's 2025 research found that nearly two-thirds of product builders identify with two or more roles.
The gap isn't in skill. It's in infrastructure. NN/g found the typical ratio is one designer for every twenty developers. Engineering and product have had operational systems for years. Design is still improvising. 92% of designers say their own process needs improvement.
64%
identify with 2+ roles
92%
say their process needs improvement
1:20
designer-to-developer ratio
Behind the name
The IRL behind the URL
I'm Edna, and I've worn many hats. Graphic designer, marketing manager, UX designer, agency consultant, founding designer building teams from scratch. Now I'm leading product design at an AI startup as the only designer on the team. Many Hats comes from living the problem: figuring out how to do the work of many roles when nothing around you was built for that.
Get in touch
Let's talk
Running design solo and want to compare notes on what actually works? Reach out.
hello@manyhats.one →Stay in the loop
Updates
Frameworks, toolkits, and honest perspective on the state of design work. No spam, just what's useful.