The first time I saw Randi’s social media posts for Aiden Jae after handoff, my gut reaction was: I wouldn’t have made these. The crops were different. The copy cadence was hers, not mine. The palette choices leaned warmer than I would have gone.

But they worked.

Not in a “close enough” way. In a “the system is doing its job” way. Every decision she made was legible inside the visual language I’d built. The brand held, and I hadn’t touched it.

That’s the test. Not whether the client makes the same decisions you would. Whether the decisions they make are governed by the logic you left behind.

Aiden Jae is a fine jewelry brand. Randi is the merchandiser. Pieces are manufactured and hand-detailed by Beauty Gems in Bangkok. I designed the visual identity, the photography direction, the packaging concepts. The whole system needed to function when I wasn’t the one operating it. Randi needed to run promotions, shoot product, write copy, and make layout decisions on her own schedule, with her own instincts.

So the brand couldn’t depend on my eye. It had to depend on its own logic.

I built the identity with explicit rules: color relationships, type hierarchy, photography framing standards, a tone guide specific enough to be useful and loose enough to breathe. The goal was a vocabulary, not a script. Randi could compose her own sentences as long as she was using the right words.

This is scaffolding. The concept comes from education. You meet the student where they are. You build temporary structure around the skill they’re developing. And when the structure has done its job, it disappears. The student doesn’t need it anymore because they’ve internalized the capability.

In brand work, the scaffolding is the design system itself. You build the visual language with enough internal logic that the client can maintain it independently. The decisions are governed by the structure, not by the designer’s continued presence. The designer steps away. The brand holds.

I saw the same principle at work in the CSS class system I built for Encore. The development team needed to make layout and styling decisions without a designer reviewing every commit. So I built the vocabulary into the markup: semantic class names, composable objects, predictable overrides. A developer who understood the naming conventions could build a new page that looked right without asking anyone. The logic was in the code.

The parallel is exact. In both cases, you’re building a system where the person making decisions doesn’t need the designer’s eye. They need the system’s logic. And if the logic is clear, their decisions will be different from yours but still correct.

That’s how you know the scaffolding worked. The client made their own choices inside a structure that made bad choices hard and good choices obvious. When the scaffolding comes off and the brand still holds, the system did its job.