Strangeworks 2022–2026

Brand & Systems Leadership

Leading the evolution of the Strangeworks brand identity and building a scalable design system to unify product, marketing, and developer-facing surfaces.

timeline
2022–2026
role
Senior Designer
team
Marketing & Design, Product
tools
Figma, Keynote, Google drive
The Brief

Evolve the brand to match the ambition

Strangeworks needed a visual identity that communicated to both technical sophistication and startup energy — without losing the personality that made it distinctive.

Brand evolution — before and after
Context

The existing brand had served the company well in its early stage, but as the product matured and the audience shifted toward enterprise buyers, the identity needed to project more confidence and polish while retaining warmth.

Previous brand applications
Updated brand direction
Insights
  1. 01Enterprise buyers associated visual polish with product reliability — brand perception directly influenced sales conversations.
  2. 02The developer community valued clarity and consistency in documentation and tooling surfaces.
  3. 03Internal teams were creating assets ad-hoc because no shared system existed, leading to drift.
Brand audit findings
The Problem

No single source of truth

Design decisions lived in individual files, Slack threads, and people’s heads. There was no brand guide, no template or token system. Every new page or asset was a follow up on the last design without a clear process.

Solution

A living design system

built a comprehensive design system from the ground up — starting with brand foundations (color, type, spacing, patterns, icons) and extending into a component library that served both marketing and product surfaces.

Brand Foundations

A refined color palette, type scale, spacing system, and illustration style that could flex across contexts without losing coherence.

Component Library

A shared Figma library with tokenized components, auto-layout patterns, and usage documentation that designers and engineers could reference directly.

Governance

A lightweight contribution model so the system could grow with the team rather than becoming a bottleneck.

Design system — component library overview
Color and type tokens
Component documentation
Usage guidelines
The Outcome

A brand that scales

The system became the default starting point for every design and engineering task. New hires onboarded faster, cross-team handoffs became smoother, and the brand finally felt like one coherent thing across every surface.

Brand system in production — across touchpoints
This site is currently being refreshed — things may look a little weird for a bit.