OUTERSPATIAL · BADGE SYSTEM
Three levels, one system.
A challenge identity, the tasks that earn it, and the milestones that mark the journey — each level coded by shape.

OVERVIEW
OuterSpatial serves hundreds of organizations from one platform, each displaying badges for its visitors. Over time the badges had drifted — no shared system, no consistent hierarchy, no scalable way to represent a new organization without hand-building each set.
I defined the requirements and architecture the system had to satisfy; Equinox designed the visual system against that brief. This case study is the architecture I set — the illustration, shape language, and palette are Equinox's execution.
THE PROBLEM
Give organizations free rein and badges look inconsistent; lock everything down and every org looks identical. A designer can't hand-craft a set for every organization. This system doesn't scale.
I defined the requirements and architecture the system had to satisfy; Equinox designed the visual system against that brief. This case study is the architecture I set — the illustration, shape language, and palette are Equinox's execution.

THE QUESTION
How do you define a badge system flexible enough for any organization, yet coherent and legible across all of them?
THE APPROACH
Rather than restyle badges one at a time, define a system with a structure robust enough that any organization could be represented within it without breaking coherence, and clear enough that a badge's shape told you what it was.
The guiding requirement, stated plainly: a system flexible enough to work across any organization, regardless of the landscape they represent. Structure and hierarchy locked; organization identity (color, landscape, illustration world) as the surface that varies.
A leveled hierarchy tied to how the product actually works. The structure resolves into levels that map onto real platform concepts rather than arbitrary tiers: Challenge, Task, and Milestone.
THE ARCHITECTURE
Five decisions that make it a system, not a set of badges.
Structure and hierarchy are fixed by design; organization identity is the single place the system is allowed to flex.

Every badge is built in the same five steps: silhouette, color, element, type, ornament. Only two of them change between organizations.

Shape carries the hierarchy. Challenge, task, and milestone each get their own silhouette, so a badge tells you what kind of badge it is before you read a word on it.
Organization identity is the one variable surface. The skeleton stays locked while color and landscape absorb whatever an organization brings. Category families like Landscape, Explorer, and Fauna, and per-state theming for Florida or Arkansas, all ride on the same structures.
The palette had to expand without breaking. More organizations and more biomes meant more background colors, added to the existing range rather than replacing it, so new badges sit alongside old ones without a reset.
DESIGNS
One system that supports every organization.
The system's proof is coherence under variety: distinct organizations, categories, and lanscapes all producing badges that read as one intentional family, with a hierarchy a user can parse at a glance.






BADGE ILLUSTRATIONS BUILT ON ONE ARCHITECTURE - CHALLENGE, TASK, AND MILESTONE. VISUAL BY EQUINOX.
BUILT TO GROW
Shipped as an iterative system
Right now this powers the challenges and badges organizations host on OuterSpatial. Longer term, it's the foundation for how the whole app rewards, engages, and delights the people who use it.
