Designing the culture from day 1
I crafted a warm, welcoming, and playful tone for the internal environment, so the culture felt like a place people wanted to be from their first day.
Designing an early-stage start up from zero the same way I design a product: in the small moments that compound.

I joined Element14 as the third hire, Head of Product, and the only designer to shape the company itself alongside the products it ships. The website I’d designed before being hired was the only external-facing artifact we had, and the rest was open ground. In the first six months I designed the onboarding every new hire now receives, built the design system and the operating process behind every client deliverable, ran the workshops that set the team’s working rhythm, and shaped how product, data, and engineering decided to collaborate.
The frame I brought in is that a company is a product. It has a voice, a system, an experience, and a set of rituals. The deeper belief underneath the frame is that both culture and design work the same way: the first few moments matter disproportionately, and getting them right early does most of the downstream work. Small decisions, made with intention, compound.
Before

After

Every new hire at Element14 opens the same door with a warm welcome moment built around the company’s own name: silicon, element 14 on the periodic table, the foundation of modern technology.
Each person on the team gets their own element tile with a symbol, a short bio, and AMA. The periodic motif gives the team a shared visual language that builds retention and belonging instantly.

Culture, like design, is mostly about getting the first moments right: the onboarding, the weekly rhythms, the shared vocabulary. The rest tends to grow on its own.
In my first weeks, I ran workshops to name how we wanted to work together while the team was small, so we could carry that rhythm forward as we grew.
From there I shaped the rituals that give the team its rhythm, designed into the environment rather than written down as policy. These “Elementals” now guide our client conversations, hiring, and how we keep showing up for each other.


The operating process moves the team from an ambiguous brief to a clear direction everyone can build toward. Alongside team documentation, I built four artifacts that now anchor how every project works: a requirements-gathering method that keeps clients and the team speaking the same language, an interview synthesis process that turns scattered conversations into shared insight, a product vision narrative that gives the whole team one picture of where we’re going and why, and a living prototype that keeps engineering moving at full speed.
The product vision and journey, built to align the team and show how it will fit within the current workflow and ecosystem.
Each federal client we serve brings something different: different data, different users, different procurement needs, different brand expectations. Rather than rebuild for every one, I designed the system to flex. Underneath every deliverable sits one design system skeleton, with components, tokens, patterns, and documentation that stay constant across projects with the ability to still tailor to each client.
The engineering team doesn’t have to re-learn structure for every project, and the clients get something that feels built for their world from the start.


Voucher submission
Owner-Occupied Rehab, Zone 3
Supporting documentation
Contextual documentation
Attach documentation supporting every line item on this voucher: invoices, proof of payment, and internal approval.
Framing lumber, pallet 14 · Meridian Timber Co.
Supporting documents
$368,600.00
B-23-DL-13-0001 · Act. 0114
I crafted a warm, welcoming, and playful tone for the internal environment, so the culture felt like a place people wanted to be from their first day.
Building the right design system as a base that grows and flexes across clients and their unique brands lets us move faster without starting over.
I designed how the domains work together, so teams arrive aligned on shared statements rather than assumptions.
Voice, system, experience, and rituals designed as one whole, so the company feels cohesive from the inside out.
Coming soon
Right now we have two different tones since I built the website before the company even formed:
The external brand is dark, sleek, tech-forward, a confident counter to the sterile consulting look that fills federal procurement.
The internal brand is warm, playful, and deeply human. Two expressions, each pitched perfectly for its own audience.
The two tones make sense for their audiences but they feel disconnected. I want to rethink the website with really simple touches that let our periodic element shine through and round out our full brand and design system. The internal brand already uses two-letter element tiles for every teammate. The external brand can inherit the same grammar for services, methods, and principles. What I’m working on now is the thread that ties them together and how far to extend the motif externally while keeping the credibility the current site has.
A company is a product that never stops needing design. The onboarding, the system, the brand, the culture, the way the team moves together, all of it keeps growing as the firm grows, and that’s the part I find most generative. Where we are now: seven people, four Elementals, one design system, one operating process, six client variants, and two brand expressions learning to recognize each other. One company I’m continuing to design.