I used to think great design made great websites.

I began my technical career as a designer long before I was a developer. So I get it. I have been the person obsessing over a mockup at midnight.

But after a decade of building sites for marketing teams, here is what the work keeps telling me:

Content is what moves the needle and design often gets in the way.

The mess I kept inheriting

There is a pattern I have seen with almost every client. I call it design creep.

It starts innocently. A new landing page needs a slightly different hero. A webinar page gets a tweaked button. The brand color list grows one by one, eventually becoming a long list of variants.

Like with one client, I counted six variations of the same button.

This was because three different designers had passed through over the years. Every mockup I got handed always had a small adjustment. A new color. A different border radius. A card that almost matched the other cards. But not quite.

None of it was malicious. But my billable hours kept climbing, not because we were building anything new, but because I had to babysit a totally incoherent system.

The site was not designed anymore. It was the accumulation of many designs.

The uncomfortable part

Here is the thing nobody wants to say out loud.

Designers who work hourly are rewarded for this.

When you are paid by the hour, tinkering becomes the job. A new mockup every week is guaranteed income. And a component that gets decided once and reused forever is a threat.

I do not think most designers do this consciously. The tinkering does not feel like padding because it feels like craft. You are never fully satisfied, so there is always one more knob to turn.

This incentive to tweak is real because it means more hours of work. But if I push a client to consolidate everything into one unified design system. No longer can the designer just tweak because it would go against the whole system. And it would drastically cut their hours.

Most designers would not want this, and I understand why. Because focusing on a design system would automate away a big portion of her job.

I learned this by pushing for it, which ended my engagement with a long-term client who was more hung up on design than writing good copy.

Which clarified something for me.

The test I use now

Every design decision gets one question.

Does this serve the whole, or is it just tinkering?

Do the cards match the border radius of every other card? Does this new icon actually belong in the system? Is this tweak in service of the story the site is telling, or is it busywork?

Because most of the time, it is just busywork.

A good design system ends that. It says that the type scale is decided. The colors are decided. The spacing is decided. Nobody has to have an opinion about the button ever again.

Because good design knows when to stop designing.

What I build instead

After that engagement ended, I started building what I call a design dictionary for every client.

It is the full set of decisions that are made once. Like typography, type scale, colors, spacing, border radius, and the components built on top of them. Every knob you would ever touch on a website is defined and already locked in.

The result even surprised me.

When the system is coherent, not only does everything look good no matter which components you grab, but the owner also stops thinking about design entirely and focuses on what actually sells: content.

Will it win design awards? Absolutely not, and it's not meant to.

It's supposed to move the needle to get the sale.

Then AI changed the math

Here is the best part about the system.

Once a design dictionary exists, AI tools can plug into it. My clients now can generate full pages using Claude Code within their own systems, with accessibility and SEO baked into the framework I gave them.

The dictionary is what makes that safe. Without it, an AI writing pages will hallucinate over time, and what you get is design creep at machine speed. With it, the machine has nowhere to drift to. The colors it can reach are the only colors that exist.

This has grown past web pages. It can make PDFs, invoices, and one-pagers, all generated from the same core structure and looking like they belong to the same brand.

They no longer need me for every page because I have enabled them.

That is because I would rather be the person who built the engine than the person you have to call every time you want to drive.

The real philosophy underneath

If you zoom all the way out, this was never really about design.

It is all about incentives.

The hourly model rewards never being finished. Outcomes reward deciding things once and building on top of them. A design system is what outcome-based work looks like when you can actually see it.

The designer paid hourly is financially aligned with touching the knobs forever.

Which is why I am aligned with the opposite. We decide it once, lock it in, and let your team ship.

That is the whole philosophy. Stop paying for motion. Start paying for the machine.