ZenAdmin
Giving ZenAdmin an Identity & Voice
ZenAdmin's product worked. Its brand didn't hold together. Logo, color, and communication style hadn't been built with the same care as the product itself, so every new asset looked like it came from a slightly different company. I built a complete brand system, identity, guidelines, and application, covering every surface the brand touches.
Role
Lead Product Designer
Timeline
3 Weeks
team
1 Designer
Scope
Branding, Guidelines
The problem
No consistent color system across product and marketing materials
Typography left undecided, with no defined hierarchy
Logo usage inconsistent, with no clear do's and don'ts
Social and marketing assets designed ad hoc, request by request
No illustration style, photography direction, or tone of voice defined
Building the system
About ZenAdmin. The guidelines open with company positioning, so anyone touching the brand understands who ZenAdmin is before they touch a single visual element.
Color. Primary blue as the anchor, with a highlight palette and neutrals around it. Every color has a defined role, so using it is never a guess.
Typography. Instrument Sans as the primary typeface everywhere. Type scale, weight, hierarchy, and spacing all documented, so every piece of communication reads as the same brand.
Logo system. Primary logo plus supporting variants, with rules on minimum size, clear space, background compatibility, and what not to do.
Style and tone. A short section on how ZenAdmin communicates in writing, separate from UI copy, written for marketing and social teams working without a designer in the room.
Icons. One consistent set, documented as part of the system instead of sourced differently per project.
Illustration. A defined style for figures and scenes, in ZenAdmin blue and white, built to hold up across product, social, and marketing.
From there, the system extended into real applications:
Branded Business Cards
9. A full Instagram template set (profile, feed, and stories)
An app icon
11. A website whose visual direction stayed consistent with everything above it
Results
Before the guidelines existed, every new asset started from scratch. Marketing, product, and external agencies were each making independent visual calls that had to be corrected after the fact.
After the system shipped, design requests for social assets dropped significantly because templates already covered the recurring formats. New joiners and external collaborators could follow the brand without needing a designer in the loop for every deliverable. And for the first time, product and marketing surfaces read as the same brand, same typeface, same color logic, same illustration style.
The guidelines became the one reference point the team pointed external vendors and new hires to.
Looking back
Brand work differs from product design in one specific way: the people using the system aren't always designers. Writing guidelines a marketing manager or a developer could follow without asking for clarification turned out to be as much the job as designing the system itself.
ZenAdmin's blue was strong enough to carry the brand on its own, without a complicated secondary palette behind it. Resisting the urge to add more color was probably the most useful constraint I set for this project.
