Hint: it isn’t the logo. And if the role reports in as a service desk, it isn’t a CDO seat.

Early in a leadership role, a senior exec asked me to “make the new release look more premium” a week before it shipped. The product underneath was confusing, the onboarding leaked users, and the pricing page contradicted the sales deck. None of that was on the table. The ask was paint.

I did the work. It looked better. It also changed nothing, because the problem was never the surface. A few months later the same exec was frustrated that design “wasn’t moving the numbers.”

That gap — between what design was asked to do and what would have actually moved the business — is the entire reason the Chief Design Officer role exists. And it is the thing most companies get wrong about it before they even write the job description.

The fair version of the misunderstanding

Let me be fair to the companies that get this wrong, because the instinct is reasonable. Design, for most of its history inside business,

was a service. You had a thing, you needed it to look good and work well, and design made that happen. Treating it as a function you route work to is not crazy. It is just a decade out of date.

So a lot of organizations hire a senior design leader and, without quite meaning to, build the role as the most expensive version of that service. A very good taste-maker who makes the company’s output look finished. They put the title high and the authority low. Then they are puzzled when nothing strategic shifts.

Here is the verdict underneath the fairness: a Chief Design Officer who only makes things look finished is not a CDO. It is a senior-most pixel-pusher with a better title. The seat is defined by what it owns, not by how good the work looks.

Four domains, one seat

A real CDO owns four things at once, and the role is hollow if any one of them is missing.

Brand direction. Not the color palette. The company’s meaning — what it stands for, what it refuses, how it shows up as a coherent thing across every surface a customer touches. This is strategy wearing a visual coat, and it is owned at the top or it fragments.

Product experience. How the thing actually works, end to end, not how the marketing site presents it. The CDO is the one person accountable for whether the brand’s promise and the product’s reality are the same thing. When they diverge, trust leaks, and no amount of premium polish seals it.

The design organization. How the team is shaped, hired, leveled, and rewarded. I have built these — grown a practice from a handful of people into a layered org with directors, seniors, researchers, the whole structure. The CDO owns whether that org produces judgment or just throughput, and in an AI era that distinction is the whole game.

AI strategy. Where design and the model meet inside the product. This is new, and it is not optional. The companies that win the next decade will be the ones where someone senior is deciding how AI shows up to the user — what it decides, what it surfaces, where the human stays in control. That is a design question before it is an engineering one.

Brand. Product. The org. AI. Owned together, or the role is hollow. The title is cheap. The mandate is what matters.

Why this is a business role, not an aesthetic one

The reason these four belong in one seat is that they are the same decision viewed from four angles: what experience does this company deliver, and is it coherent?

That is not a taste question. It is a strategy question that happens to be expressed through design. Nearly three-quarters of CEOs now say they own AI strategy directly, which means design decisions are being made at the very top whether or not a designer is in the room. The CDO is how a company keeps taste, coherence, and customer trust in that room while those bets get made — instead of bolting them on afterward, the way my premium paint job got bolted on.

I learned the difference the slow way, on both sides of it. Running a client practice, joining the sales calls, sitting in rooms where design was either a line item or a lever depending entirely on whether someone could connect it to the outcome the business actually cared about. The leaders who could make that connection got the seat at the table. The ones who stayed in the service lane stayed in the service lane, no matter how good the work was.

So when a company asks what a Chief Design Officer does, the honest answer is not “oversees design.” It is: owns whether the brand promise and the product reality are the same thing, builds the org that can keep them aligned, and sits at the table where the bets get made — including the AI ones.

Put design where the decisions are. Everything else is paint.

Joe Cahill has spent 25+ years leading design across enterprise and fintech. He writes about design, judgment, and leadership in the AI era.

Related Articles