The interface is the product

A few years ago I watched a CEO use his own company's app for the first time. Properly use it, as a customer, with his own money. He got stuck at the second screen. Then he turned to his team and asked the most expensive question I know: "Who owns this part?"

Three people answered at the same time. That was the answer.

Here is the truth that took me half my career to accept. The customer never sees your strategy deck. Never reads your values. Never attends your offsite. The customer sees one thing: the interface. The screen, the call, the email, the invoice. That thin surface where your company touches their life. The interface is the product. And whether you mean to or not, you ship your org chart straight into it.

You have felt this as a customer, even if nobody named it for you. An app that feels like three apps stitched together is not a design problem. It is three teams, three roadmaps, three sets of targets, rendered in pixels. A support call where you repeat your story to four people is not bad service. It is a department boundary, and you are standing on it. An invoice written in legalese inside an otherwise friendly product is a touchpoint one team owned and nobody else wanted.

My engineer brain likes equations, so here is the simplest one I know:

What the customer experiences = what your teams own + how your teams talk to each other.

Notice what is not in the equation. The features. Features are temporary. Seams are structural. Every seam the customer feels is a seam between two teams, and no designer can polish a seam the organization keeps reopening.

But here is the part I find genuinely hopeful. The interface never lies. It is the most honest audit of your organization you will ever get, and it is free. Internal surveys are polite. Steering committees are political. The interface just quietly renders the truth.

So use it. Once a month, walk your entire customer journey as a stranger. Sign up with a private email. Hit the problem. Call your own support line. And every time you feel friction, resist the reflex to ask which designer should fix it. Ask instead: which boundary caused this? Which two teams meet, badly, exactly here?

Fix the boundary, and the interface heals on its own. Fix only the interface, and the seam reopens within two quarters. I have watched both happen more times than I can count.

Your customers are reading your org chart every day. They just call it your product.

Make it a good read.