Customer Focus Isn't a Sales Job. It's a Leadership One.
You signed a contract. Somewhere in it, you made promises — delivery windows, tolerances, configurations, service levels, the specific things this customer needs. Here's the question that actually matters: does the work that follows keep those promises, consistently, without anyone having to chase it?
If your honest answer is “probably, mostly, when the right people are paying attention,” you have a customer focus problem. And it isn't sitting in the department you think it is.
The reflex is to file customer focus under sales
Sales and account management touch the customer, so customer focus must be theirs. It's a natural read. It's also the wrong one — not because account management shouldn't own the relationship (they should), but because owning the relationship and delivering what was promised are two different jobs. One happens at the handshake. The other happens everywhere the handshake can't see: in design, in planning, in what gets resourced and what gets cut.
That second job belongs to leadership. And it hides for a long time before anyone notices.
When you're small, customer focus takes care of itself
You're close to the customer. Requirements travel through the building on their own, because there's barely any building to travel through. The person who took the order is three feet from the person who fills it. Nobody has to manage the thread between what was promised and what gets done, because everyone is already holding it.
That closeness is doing a lot of quiet work. And it's free. You never had to build it, so it's easy to assume it will always be there.
Then you grow.
Scale replaces proximity with distance
You add people between yourself and the customer. Each one carries a slightly different read on what matters — their own priorities, their own interpretation of the priorities they were handed. Handoffs multiply. The straight line between a customer's requirement and the work that satisfies it bends, then branches, then disappears into a process nobody drew on purpose.
The closeness that used to carry customer focus for free is gone. Here's the trap: nobody decides to stop paying attention. The attention just quietly stops scaling, because the thing that used to provide it — everyone being in the room — isn't true anymore.
This is the moment customer focus has to stop being a reflex and become a system. Built. Owned. And that ownership can only sit in one place.
Only leadership can actually do this job — three reasons
It's the point of the whole system. Strip a quality management system down to its purpose and you get one sentence: make sure customers get what you committed to, consistently. That's not one requirement among many. It's the reason the rest of the requirements exist. Which is exactly why the standard singles it out and puts leadership's name on it. You can be hands-off about a lot of your system. This is the part where the standard says don't be.
It's cross-functional, so only leadership spans it. Meeting a customer requirement almost never lives in one place. It pulls on training and competence, on suppliers, on design, on execution. The authority to prioritize across all of those has to sit at the level that spans all of those. The head of sales can own the customer relationship and still have no authority to reach into another function and force a training gap closed. Leadership does. Delegate customer focus to sales and you've handed the job to the one person structurally unable to enforce it outside their own lane.
It requires mechanisms someone has to build. The standard's word is ensure — requirements determined, understood, consistently met. “Ensure” doesn't mean leadership personally collects every requirement. It means leadership owns the system that does. Three mechanisms have to exist: a way to capture and interpret requirements, so you know what was actually committed to; a way to translate them into procedures and training, with real assurance the people doing the work can comply; and a way to measure, so “consistently met” is a fact you can show, not a hope you carry. Building those mechanisms is deliberate process design, not paperwork. If they don't exist, leadership didn't just under-attend. They never built the thing.
What the gap looks like when it opens
It shows up at two points, and they're the two ends of the same thread.
At intake, on the way in: a commitment gets made in a contract and never crosses into operational reality. Nobody translated it into a work instruction. Nobody trained anyone on it. Nobody confirmed the people doing the work could meet it. The promise exists on paper and nowhere else. It got signed. It never got built.
At feedback, on the way back: the customer tells you something — a complaint, a shift in what they need — and there's no system to capture it, route it across the right desks, and assemble a full accounting. So it dies with whoever caught it. The people upstream who could actually change something never become familiar with it. You can't mount a real response, because you never assembled the whole picture.
Requirements come in. Delivery goes out. Feedback comes back. Customer focus is that entire loop staying intact. When you were small, the loop closed on its own. At scale, both ends fray unless someone built something to hold them.
Feedback is where customer focus compounds — or leaks
Pair customer focus with a well-structured problem and corrective-action process and something useful happens: feedback stops being cleanup and becomes fuel. A complaint comes in about a delivered product or a deployed configuration. If it hits one team and they do their service-level fix, the symptom's gone and the system learned nothing — the deeper cause, maybe a training gap, maybe a design assumption, never surfaces. Route the same complaint through real root cause and corrective action and you've made a focused improvement to the system instead of a patch on the instance. That's the difference between a compliance program that reacts and one built so the system ensures issues get resolved at the root. It's a leadership job twice over, because the fix often lives in a different function than the one that fielded the complaint.
How you'd actually know it's working
Start with the contract. Your written commitments are the core of measurement — build your measures straight off what you promised. Most organizations skip even this, measuring what's easy to count instead of what they actually committed to.
Then widen the aperture. Not up a ladder — sideways, into complementary views. What do customers and competitors in your space benchmark on? (If you don't know, that's worth sitting with — you'd expect to know before you'd grown this far.) And ask your customers what they actually prioritize, rather than handing them a survey built from your own assumptions. The survey theater is the pre-written questionnaire nobody acts on. The real version goes in without the questions and lets them tell you where the line is. This visibility is also what a disciplined internal audit program is supposed to give leadership — objective evidence of whether the system is meeting requirements, not an opinion that it probably is.
The contract anchors it. Everything else is a truer picture layered on top.
Where this lives in the standard
If you work with ISO 9001, AS9100, or ISO 13485, you've met this already: it's clause 5.1.2, customer focus — and it sits inside the leadership clause on purpose. Not in the section on operations. Not in a section on sales, which doesn't exist. It sits inside leadership and commitment, right next to the requirement that top management own the system's effectiveness. The placement is the argument. The standard is telling you who's accountable before it tells you what to do.
One caution about the word “leadership”
Owning customer focus does not mean drawing a new box on the org chart to hold it. Use the authority structure you actually have. Sometimes the real owner is a title at the top. Sometimes it's a process or domain leader who genuinely holds the authority in that area — push the ownership down to where the authority actually lives. What you can't do is manufacture a reporting line to create the appearance of ownership, because appearance is all you'll get. False structure gives you a name on a chart with no power behind it, which is worse than an honest gap — because now the gap is hidden.
A place to start
Pull three customer requirements from a signed contract. Trace each one all the way down — to the work instruction that implements it, the training record that says someone can, and the measure that proves it's being met. The ones that dead-end before they reach the floor are your customer focus gap. That's leadership's to close, not the account team's.
