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
ZenAdmin's product had evolved, and its brand hadn't kept up. The logo, color and communication style were never built together with the product, so every new asset looked like it came from a slightly different company. The gaps were specific:
No consistent color system across product and marketing materials.
Typography left undecided, with no clear 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 voice defined.
I read this as a decision-making gap more than a design gap. Product, marketing and outside agencies were each answering the same questions on their own, and each got different answers. A new logo wouldn't have fixed that. What it needed was a single reference that answered those questions once.
Starting with the people who'd use it
I started by collecting what already existed across the product and marketing surfaces, to see where the brand drifted. I also thought about who would actually be opening the guidelines. Most of them weren't designers: a marketing manager building a campaign, a developer needing the right logo file, an agency working with no one from the team beside them.
That shaped the whole project. The guidelines had to be usable by someone with no design training and no chance to ask a question, so everything was written to be followed on its own.
What I wanted it to do
I aimed at three outcomes: the brand should look the same wherever it appeared, recurring requests should stop needing a designer, and anyone outside the team should be able to work from one reference.
Those became the test for every section. If a section didn't help one of them, it didn't go in.
Building the system
About ZenAdmin. The guidelines open with company positioning, before any visual rule. Anyone touching the brand should understand who ZenAdmin is before they see a single logo or color, because rules make more sense once you know what they're protecting.
Color. Primary blue is the anchor, with a highlight palette and neutrals around it, and every color has a defined role so nothing is left to a guess. A secondary palette was the obvious next step and I held back. The blue was strong enough to carry the brand alone, and every extra color gives someone another chance to use the wrong one. Looking back, resisting that urge was the most useful constraint of the project.
Typography.Instrument Sans as the single primary typeface everywhere, with the type scale, weight, hierarchy and spacing documented, so every piece of communication reads as the same brand. I chose one typeface to avoid pairing decisions that non-designers would have to make.
Logo system. A primary logo with supporting variants, plus rules on minimum size, clear space, background compatibility and what not to do. The "what not to do" rules matter most here, because that's where outside teams usually go wrong.
Style and tone. A short section on how ZenAdmin communicates in writing, kept separate from UI copy and written for the marketing and social teams. These people write most of what the public reads, and they work without a designer in the room.
Icons.One consistent icon set, documented as part of the system, so icons stop being sourced differently on each project.
Illustration. A defined style for figures and scenes in ZenAdmin blue and white, built to hold across product, social and marketing.
Putting it to work
I didn't want the guidelines to stay theoretical, so the system went straight into real applications:
Branded business cards.
A full Instagram template set covering profile, feed and stories.
An app icon.
A website whose visual direction stayed consistent with everything above.
The Instagram templates were a deliberate choice. Social requests kept arriving one at a time for formats that repeated, so I designed the recurring formats once instead of continuing to make individual posts on request.
~ Busiuness Cards
~ App Icon
~ Website
Results
Before the guidelines, every new asset started from scratch, and marketing, product and external agencies each built their own visual sets. After the system shipped:
Design requests for social assets dropped significantly, because templates already covered the recurring formats.
New pieces and outside collaborators could follow the brand without a designer in the loop for each deliverable.
For the first time, product and marketing surfaces read as the same brand: same colors, same logo, same illustration style.
The guidelines became the one reference the team pointed external vendors and new hires to.
Looking back
Brand work differs from product design in one way that matters here: the people using the system aren't always designers. Writing guidelines that a marketing manager or a developer could follow without asking for clarification turned out to be as much of the job as designing the system itself.
I'd also keep the habit of restraint. The blue carried the brand without a complicated secondary palette behind it, and the system is easier to use because of what I left out.
