The Job I Turned Down...

Why I said no to a title, a salary, and a department that should not exist.

Recently I was offered a full-time job many would have jumped at the chance to take.

“Director of Customer Care.” A real title, a decent renumeration package, an offer from someone who wants to keep me and had gone to the trouble of creating a position where none had really existed before.

I said no, not out of pride, and not because the offer was poor. I said no because taking it would have required me to spend the rest of my working life doing the opposite of what I have spent forty years arguing for.

What A Department Really Does

Here is the thing nobody says out loud about organizational structure.

A department is where an organization puts a problem it has decided to stop thinking about.

That is not cynicism, it is just how the mechanism works. The moment something becomes somebody's job, it quietly stops being everybody's job. The naming is the real issue, you draw the box on the chart, you hire the person, and in the same movement you send an unspoken message to every other function in the building: this is handled now, you can go back to your own targets.

Watch how it plays out. A guest is unhappy at the front desk. In a company without the department, the person standing there owns it, because there is nowhere else for it to go. In a company with the department, that same person now has somewhere to send it. Not out of laziness but out of structure. The routing exists, so the routing gets used.

The complaint is now a ticket, the ticket is now a queue and the queue is now a metric. A customer who wanted thirty seconds of genuine attention from the human being in front of them, instead receives a case number and a reply within forty-eight hours.

Nobody chose that outcome, the structure chose it.

The Same Trick, Different Names

If you think this is unique to customer care, look at what has happened to everything else we cared enough about to formalize.

Quality used to mean nobody let bad work leave the building. Then Quality Assurance arrived, and quality became a checkpoint that work passed through rather than a standard everybody held.

Safety used to mean everyone watched out for everyone. Then it became a department, a folder, and an annual training video that people click through while answering email.

Sustainability, culture, well-being, innovation. Every one of them followed the same path. Universal responsibility, then a box on a chart, then a budget line, then a poster, then nothing.

This is not an argument against structure; some things genuinely need dedicated ownership. It is an argument about what you lose the moment you concentrate a shared responsibility into a single pair of hands, because what you lose is everybody else's.

Why This One Cannot Be A Department

Customer care is different from quality control in one specific way that matters.

Quality can be inspected at the end, care cannot. Care only exists at the point of contact, in the moment, in the tone of voice of whoever happens to be standing there. It cannot be reviewed later, delegated upward, or routed to the correct team. By the time it reaches the correct team, the moment where care was possible has already passed.

Which means care is either present in the person in front of the customer or it is not present at all. There is no second location where it can be stored.

A Director of Customer Care can write policy. They can train people, design standards, and analyze complaints. What they cannot do, ever, is care on behalf of somebody else. The one thing the title implies is the one thing it structurally cannot deliver.

And in most organizations, the honest version of the job is narrower still. “After-sales and complaint handling.” Cleaning up the failures that the rest of the operation generated upstream and had no incentive to prevent, because prevention was never anybody's target.

That is not a customer care department. That is a repair shop with a nicer name, and the better it performs, the longer the upstream problem survives, because the pain never reaches the people creating it.

What To Do Instead

If care cannot be a department, it has to be a condition of employment. Which means it belongs in places most companies never think to put it. It simply must be an attitude from every department.

It belongs in hiring, where you select for it rather than hoping to train it in afterwards. It belongs in the first week, before anyone learns the products. It belongs in how you promote people, because the moment you elevate someone who delivers numbers while treating people badly, you have told the entire building exactly what actually counts. It belongs in finance, in maintenance, in the warehouse, in every function that never meets a customer and shapes their experience anyway.

And it belongs in what leadership pays attention to on an ordinary Tuesday, because people care about what they see their leaders notice.

There is a simple test. If a customer has a poor experience in your business, does anyone outside the customer-facing team feel that as their problem? If the answer is no, you do not have a culture of care. You have a department, and everybody else has been quietly excused.

What The Refusal Actually Cost

I want to be honest about the arithmetic, because a principle you never pay for is just an opinion.

The offer was real money at a moment when real money would have helped considerably. The person making it meant well and was trying to solve a genuine problem in a generous way. Turning it down was not comfortable and it did not feel noble at the time, it mostly felt expensive.

But I have written three books arguing that care is not a function you can delegate. Accepting a title built on the opposite premise would have made every one of those pages a lie, and there is no salary that repairs that.

Care is not a department, it is the attitude of everyone in the building, or it is not really there at all.

Trust is the only currency that compounds without inflation.

Relationship. Not Transaction.

Georgios B.