The Vista Iconic Language.

2003 · The problem

Sixteen agencies. Three products. Zero consistency.

Chris was brought on as the first Senior Product Designer at Citrix, joining a handful of human-factors engineers to form a UI design team. Every screen across Installation Manager, MetaFrame XP, and Password Manager was outsourced to one of sixteen different marketing agencies — with no style guide, no rules, no shared vocabulary. Software was 4-bit color and pixelated unpredictably across systems.

The first move was a screen-by-screen, folder-by-folder audit of all three products, sitting with SMEs to learn each feature's intricacies — knowing Citrix's long-term plan was a unified suite, and that Microsoft was absorbing more of the territory into the base Server SKU every year.

The four-year ride · NT → Vista

A timeline of consolidation.

The breakthrough

An atomic icon design system.

The Citrix Iconic Language was built as a true atomic system — long before "atomic design" was a phrase in common circulation. Five layers, each composed from the one beneath it:

1. Layer 1

   Shapes

   Primitive geometry

2. Layer 2

   Elements

   Re-usable parts

3. Layer 3

   Base icons

   Canonical forms

4. Layer 4

   Applied icons

   Domain-specific

5. Layer 5

   Complex frames

   Full scenes

Operating principles

Five rules that made it scale.

• 01

  Icons must read at every size, every color depth, every theme.

• 02

  All icons must look like one designer drew them.

• 03

  The creation process must be fast and teachable — so resources can scale.

• 04

  A logical naming convention, machine-readable, managed automagically by code.

• 05

  One gatekeeper, one key master, one source of truth — the icon depot.

The naming convention

Filenames as grammar.

Before "design tokens" was the dominant phrase, the team encoded meaning into filenames themselves — so code, build systems, and humans could all read them:

000_EastArrow_h256_16.gif
000_EastArrow_Combo_All.ico
075_SampleIcon_hweb_158.gif

[ Platform / Style ] _ [ Graphic Name ] _ [ Color Depth ] _ [ Size ] . [ Ext ]

Combined with a Perforce depot (the VDSG — Vista Design Style Guide tooling), every icon had exactly one canonical home, one canonical name, and a deterministic path for every variant.

Artifact · circa 2006 · the actual VDSG browser interface

The team model

Principal designer as grammarian.

A dedicated Studio Team handled suite-level UI and image files. Each major product kept its own VD/UI lead for product-specific needs and to request new suite-level graphics from Studio. The principal designer controlled the grammar; product teams composed within it.

"We not only solved the Vista and Mac large-icon deficiencies — we created a reproducible process with single-designer optics, and a true iconic language using an atomic design system."

— Chris Anthony, on the win

Two registers · Branding & Verb-state

Product icons and Status icons.

Inside the iconic language, working icons split into two distinct registers — each with its own grammar, its own approval path, and its own place in the product surface. Confusing the two is the most common way a design system drifts.

From Vista to Digital SanSkrit

The same idea, formalized.

The Vista project proved the thesis: iconography for complex systems is a language problem, not a style problem. Digital SanSkrit takes that proven practice — shapes, elements, base icons, applied icons, complex frames — and gives it the formal vocabulary of Sanskrit grammar: dhātu, samāsa, vākya, śāstra.

एक भाषा, अनन्त रूप · One language, infinite forms.