Back

Work

/

ZenAdmin

ZenAdmin Brand Guidelines

ZenAdmin Brand Guidelines

Building a brand identity from the ground up for an IT asset management platform.

Building a brand identity from the ground up for an IT asset management platform.

ZenAdmin had a product. What it didn't have was a consistent visual identity to match. The logo, colors, and communication style were all over the place across touchpoints. I built a complete brand system covering identity, guidelines, and application across every surface the brand appears on.

ZenAdmin had a product. What it didn't have was a consistent visual identity to match. The logo, colors, and communication style were all over the place across touchpoints. I built a complete brand system covering identity, guidelines, and application across every surface the brand appears on.

ROLE

Lead Product Designer

Lead Product Designer

TEAM

Solo

Solo

DURATION

1 Month

1 Month

RESULTS

  • Design requests for social assets dropped by one third

  • New joiners and external collaborators could follow the brand without a designer in the loop for every deliverable

  • The product and marketing aligned with same typeface, same color logic, same illustration style

  • Design requests for social assets dropped by one third

  • New joiners and external collaborators could follow the brand without a designer in the loop for every deliverable

  • The product and marketing aligned with same typeface, same color logic, same illustration style

The Problem

  • No consistent color system across product and marketing materials

  • Typography was unstructured with no defined hierarchy

  • Logo usage was inconsistent with no clear do's and don'ts

  • Social and marketing assets were designed ad hoc per request

  • No illustration style, photography direction, or tone of voice defined

  • No consistent color system across product and marketing materials

  • Typography was unstructured with no defined hierarchy

  • Logo usage was inconsistent with no clear do's and don'ts

  • Social and marketing assets were designed ad hoc per request

  • No illustration style, photography direction, or tone of voice defined

How Research Shaped the Interface

01. About ZenAdmin The guidelines open with a company positioning section so anyone using the brand understands who ZenAdmin is before touching any visual element.

01. About ZenAdmin The guidelines open with a company positioning section so anyone using the brand understands who ZenAdmin is before touching any visual element.

02. Color Primary blue as the anchor, with a highlight palette and neutrals. Each color has a defined role so there's no guesswork about when to use what.

03. Typography Instrument Sans as the primary typeface across all materials. Type scale, weight usage, hierarchy, and spacing rules are all documented so every piece of communication reads as the same brand.

04. Logo System Primary logo, superimposed variants, and badge versions. Usage rules cover minimum size, clear space, background compatibility, and what not to do.

05. Style and Tone A short section on how ZenAdmin communicates in writing, separate from how it looks. Useful for marketing and social teams working without a designer in the room.

06. Icons A consistent icon set documented as part of the system rather than sourced differently per project.

07. Illustrations A defined illustration style for figures and scenes, in ZenAdmin blue and white, that work across the product, social, and marketing.

Brand Applications

  1. Business Card Branded business cards with the ZenAdmin logo and the defined color system.

  1. Social Media Instagram profile, feed, and story templates. LinkedIn post templates. YouTube channel design. All built on the same visual language so the brand reads consistently regardless of which platform someone encounters it on.

  1. App Icon ZenAdmin app icon designed for iOS, shown in context on a real device.

  1. Website Website visual direction consistent with the broader brand system.

Results & Impact

Before the guidelines existed, every new asset started from scratch. Marketing, product, and external agencies were all making independent visual decisions that had to be corrected after the fact.

After the system shipped:

  • Design requests for social assets dropped significantly because templates covered the recurring formats

  • New joiners and external collaborators could follow the brand without a designer in the loop for every deliverable

  • The product and marketing surfaces read as the same brand for the first time — same typeface, same color logic, same illustration style

The guidelines became the single reference point the team pointed external vendors and new hires to.

Before the guidelines existed, every new asset started from scratch. Marketing, product, and external agencies were all making independent visual decisions that had to be corrected after the fact.

After the system shipped:

  • Design requests for social assets dropped significantly because templates covered the recurring formats

  • New joiners and external collaborators could follow the brand without a designer in the loop for every deliverable

  • The product and marketing surfaces read as the same brand for the first time — same typeface, same color logic, same illustration style

The guidelines became the single reference point the team pointed external vendors and new hires to.

Retrospective

  • Brand work is different from product design in one specific way: the people using the system are not always designers. Writing guidelines that a marketing manager or a developer can follow without asking for clarification turned out to be as much of the job as designing the system itself.

  • The ZenAdmin blue was strong enough to carry the brand without needing a complicated secondary palette. Resisting the urge to add more was probably the most useful constraint I put on this project.

  • Brand work is different from product design in one specific way: the people using the system are not always designers. Writing guidelines that a marketing manager or a developer can follow without asking for clarification turned out to be as much of the job as designing the system itself.

  • The ZenAdmin blue was strong enough to carry the brand without needing a complicated secondary palette. Resisting the urge to add more was probably the most useful constraint I put on this project.

Other Projects

Employee Feedback to Actionable Insights

From Chatbot to Agentic Colleague