Designing for Yourself vs Designing for Clients. The Difference Nobody Talks About Honestly.

I want to say something that most designers know but rarely say out loud because it sounds harsh.

When you're doing client work, your job is not to be right. Your job is to feed the client's ego.

That's a blunt way to put it. I've sat with it long enough to know it's also accurate.

What Designing for Yourself Actually Feels Like

When I'm making a font for Phoenix Dungeon, the only conversation happening is between me and the work.

I have a starting point, a rough idea of what the font should feel like, where it might live, what kind of designer would reach for it. I start building. Something doesn't work. I change it. Something works better than I expected. I follow it. The whole process is a negotiation between my instincts and the material, and nobody else is in the room.

That's a specific kind of freedom that's easy to take for granted until you've spent serious time in the other mode.

The constraints are still there. The grid, the technical requirements of a functional typeface, the need for consistency across every glyph. But the constraints are craft constraints, not preference constraints. They're the kind that make the work better, not the kind that make the work someone else's.

When I finish something I'm proud of, I'm proud of it because I made a decision and it worked, and that decision was entirely mine. When I finish something that doesn't work, I know exactly why and what I'd do differently. The feedback loop is clean.

That's designing for yourself. Clean feedback loop, no external ego in the room, the work is entirely yours to succeed or fail with.

What Designing for Clients Actually Feels Like

The first thing to understand is that clients come to a designer because they have something they want to say, a brand, a product, a service, an idea, and they need someone to help them say it visually. That's the brief.

What the brief doesn't always include, but is almost always present, is a pre-existing image in the client's head of what the result should look like. Not a finished design, but a feeling. A reference. A sense of what they want without the vocabulary to fully describe it.

Your job as a designer is to find that image in their head and make it real. Not the best possible design solution. Not the most strategically sound visual direction. Their image.

This is where ego enters the room.

Because here's what happens when you're a designer who has spent years developing taste, building knowledge about what works and why, studying brands that succeed and brands that fail. You look at what the client wants and sometimes, often, you see something that could be better. A direction that would serve the brand more effectively. A choice they're not considering that would solve the underlying problem more cleanly.

You present it. You explain your thinking. You show the reasoning.

And the client says no. Not because your reasoning is wrong. Because it's not what they imagined.

I've been in that situation. More than once. I've had disagreements over creative direction that I was certain, not arrogantly but genuinely, were in the client's best interest. I believed the work I was proposing would serve their brand better than what they were asking for. I made that case clearly.

It didn't matter. The work ended. Sometimes messily. Sometimes with refunds. Sometimes with the particular frustration of watching someone take a direction you told them wouldn't work and watching it not work exactly the way you said it wouldn't.

The Hard Lesson

It took a few of those situations to understand something I probably should have understood earlier.

Client service is not a creative collaboration in the way designers like to imagine it. At its most functional, it's a translation service. The client has a vision, however clear or unclear, and you are the person who translates it into something that can exist in the world. Your taste matters in so far as it helps you execute the translation well. Your opinions about what the brand should be doing are secondary to what the person paying the invoice wants to do.

This sounds like a diminishment of design. I don't think it is. Translation is skilled work. Understanding what someone is trying to say and helping them say it clearly, even when you'd choose different words, is a real skill. Good client designers are genuinely good at this.

But it is different from what most people who get into design actually want to do. Most people get into design because they have things they want to say visually. They have taste. They have instincts. They have opinions about what looks good and what doesn't and why. And client work, at its core, requires you to subordinate most of that to someone else's vision most of the time.

The math only works if you're okay with that trade. And I'm not sure I ever fully was.

The Ego Collision

Here's the honest version of what happens when designer ego and client ego meet.

The designer has spent years developing the ability to make things that work. They have a professional identity built around that ability. When they make a recommendation, they're drawing on real experience.

The client has spent years building a business or a product or a brand. They have a personal investment in what it looks like. When they have a vision for the visual direction, that vision is connected to something deeper than aesthetics. It's connected to their identity, their sense of what they've built, their image of where they're going.

Both egos are real. Both are legitimate. And they're frequently pointed in different directions.

The power dynamic is simple: the client is paying. Which means when the two clash, the designer's job is to adapt, not to win. Winning a creative argument with a client and losing the relationship is not a victory. It's just a messy ending.

I learned this the way most people learn it, through the mess. Through the situations that ended in refunds and the tension of disagreements that didn't have clean resolutions. Through realizing that being right about a design decision and having that rightness acknowledged by the person paying you are two completely different things, and only one of them matters in a client relationship.

Why This Led Me to Build Things Instead

The alternative to subordinating your ego in client work is to build something where your ego is the point.

Not arrogance. Not refusing to take feedback. But finding contexts where the thing you're making belongs to you, where the decisions you make live or die on their own merits rather than on whether they match what someone else imagined.

For me, that meant Phoenix Dungeon. Making fonts where the creative direction is mine. Where if I decide a pixel font should feel a certain way, that decision stands until I decide to change it. Where the feedback comes from the market and my own standards, not from a client's pre-existing image.

This is why the two modes feel so completely different from the inside. It's not just about freedom in the abstract sense. It's about who owns the ego in the room.

When I'm making something for Phoenix Dungeon, and I look at Udeyna or Pestonya and think it works, that judgment belongs entirely to me. I don't have to convince anyone. I don't have to navigate someone else's vision to get there.

That's not a luxury. For someone who got into design because they had things they wanted to say, it's the whole point.

Client work taught me a lot. It taught me to listen better, to communicate design decisions more clearly, to understand that the person across the table has real stakes in the outcome even when they're wrong about the direction. I don't regret the experience.

But I'm not going back to it as the main thing. I've got my own ego to work with, and I'd rather put it into something that's actually mine.

If you want to see what that looks like when it's working, the shop is the place. Everything there came from a decision nobody had to approve.