Case studies

Are your resolution processes documented?

Last updated when?

We looked. Eighteen months. In the meantime: duplicates, empty fields where there should be answers, and two procedures that contradict each other on the same situation.

Nobody complains because your long-serving staff compensate. They hold the memory of the department. When an agent gets stuck, they don't consult the knowledge base: they turn to the colleague next to them. Your real documentation lives in four people's heads.

Until one of them leaves. You have just lost one in the restructuring. Thirteen years' service, the only person who mastered the complex-flow management module. He left on a Friday. By Monday his access had been revoked — for security reasons, legitimately. Nobody had organised the handover.

That is exactly the mistake. An organisation does not restructure positions: it restructures human beings, and with them, knowledge. Yours walked out of the door without being counted anywhere.

And that is precisely what the opacity is costing you. Your three repeat contacts on the same case are three times the time of one clean handling. You don't fund documentation with time you don't have: you fund it with the time you are already losing.

For how long now?

In writing?

Have you noticed anything when you raise the subject?

His permit is conditional on passing his studies. Have you seen his results this year?

Then you already know the answer. He has nothing to give you because the document no longer exists. And he comes to work every morning with the same competence and a residence permit that is no longer valid.

This is where the reasoning turns around. Swiss employment law applies the employer's obligations on termination irrespective of the grounds for dismissal. You knew — or you ought to have known. Your repeated reminders prove it: they are an implicit acknowledgement of the risk. A termination letter should have gone out several months before the end of his period of study, from the moment non-renewal became foreseeable.

Several months' salary, yes. The law is not rewarding his concealment. It is sanctioning your lack of procedure.

And the real management question is not a legal one, it is this: why was he unable to tell you the truth? Shame at failing, fear of losing the job — probably. But also, perhaps, because the working relationship never signalled to him that bad news spoken is worth more than a comfortable silence.

We have reviewed them. They are sound. So are the tools. The workload is demanding but not abnormal.

From two people on your team who no longer speak to each other directly. They were in a relationship, and they separated. Since then, every piece of information that should pass between them takes a detour.

It is not for you to intervene in their relationship. It is for you to intervene in a chain of information that depends on it. Their colleagues are held hostage to a situation they did not choose, and they adapt — at the price of a growing inefficiency nobody dares to name.

Because it is uniform. We observed the opposite case in another engagement: two employees in different departments, no reporting line between them, no professional interaction, no shared access to sensitive data. Objectively zero risk of collusion. And yet they hid it, with the discretion of people who know a rule applies to them without really being about them.

A clear rule, yes. An undifferentiated rule, no. A relationship between a senior manager and their direct report does not carry the same risk as a relationship between two watertight departments. Declaring should not automatically mean being sanctioned. And a policy that pushes competent people into concealment is a policy that has failed, even if it is technically compliant.

Nothing disciplinary. You treat the vulnerability, not the people.

On what basis do you draw up that ranking?

Whose general impression?

So you measure speed and guess the rest. On what the customer actually experiences, you have nothing factual.

That is the point on which we disagree. Everything that belongs to the human register shows up in concrete behaviour, and concrete behaviour can be observed. Three minutes into a level-2 complaint, did the agent reflect back the emotion before offering the solution? Did they use the customer's name? Did they ask again for information already given? Did they announce the hold with an estimated duration?

No. And that is a condition of our involvement.

We will tell you everything that allows you to act: the categories where the team is structurally weak, the call types that generate the most difficulty, the training needs, the excellent practices worth standardising, and the places where your processes make the agent's job impossible. What we will not pass on is names.

And a recording captures one call out of hundreds, in a context you do not always know. An agent whose relative is in hospital. A week of understaffing. An exceptionally difficult customer who had already worn out the whole team before reaching that line. Judging on that isolated moment is not rigour, it is injustice dressed up as objectivity.

Then your existing disciplinary process takes over, with all its procedural safeguards for the employee. It is not our role to short-circuit it.

Are you looking for someone responsible, or for a flaw?

The two are incompatible. If the meeting is looking for someone to blame, nobody will say what they actually did, and you will never find the flaw.

There is no formal procedure for updating the security lists when the guest-reception plan changes late. Each department assumed another was handling it. Nobody handled it.

Exactly. And that is the real problem. Your ticketing desk is aiming for flow: no queue, visitor directed within thirty seconds. Your cultural team wants to slow time down so the visitor leaves with something. Your events team is under pressure to deliver and has to hold to a schedule. Your security team's brief is to stay invisible, and it gets consulted after the decisions have been made.

Four definitions of success that have never had a space in which to be set against one another. They are not in conflict over people: they are in structural tension. Each one is right within its own logic. What is malfunctioning is the service chain.

Monthly, with an agenda and minutes. Those are governance meetings. They do not replace what a large hotel does every morning: fifteen minutes, all the department heads, one single question — what is happening today, and who needs to know what.

Information shared in advance costs less than an incident handled in a hurry. You have just paid for a private view. Count the time the handling of that incident took up, and compare.

You appoint someone whose only brief is this: to check that the critical information has circulated before the doors open. With no hierarchical authority.

They will have something better than authority: a functional legitimacy granted explicitly by all the department heads, to ask one single question. Does everyone know what they need to know tonight?

Which ones?

We analysed her calls. She consistently takes two to three seconds before responding to a complex complaint.

It is not hesitation, it is selection. She is choosing one word rather than another. And her customers ask for her by first name.

No. But it shows where the value is created. Take the same call, the same agent, the same customer. Version A: fast delivery, the greeting reduced to a department number. The customer is immediately on the defensive — sensing, without putting it into words, that they have entered a system that processes tickets. Version B: the tempo slightly slowed at the greeting, the customer's name in the first sentence, one second of silence before the answer. The customer relaxes. Nothing in the content has changed.

We want to replace it with an architecture. A script says what to say. An architecture says in what order to build, and leaves the agent to choose the words. That is what frees them from the anxiety of not knowing what to say next — and gives them back the attention they need for the quality of the exchange.

That is the delicate point. A script designed to extract rather than to serve turns every word into an instrument of manipulation, even when each word taken on its own sounds benign. Your agents feel it. And an agent applying a script they do not believe in gradually stops thinking for themselves.

I am asking you to teach your agents the cognitive mechanisms they already use without knowing it — anchoring, social conformity, confirmation bias — so that they can recognise the moment a conversation tips from legitimate persuasion into manipulation. A team that can name that boundary holds it. A team that is unaware of it crosses it without noticing, and you will pay for that in customer distrust.

How many of your future customers have already heard of you?

That is not your problem. Your problem is that you are a foreign brand, German, grown out of a public administration, arriving in a B2B market where decisions are made on relationships, recommendations and proof of competence. Billboards buy none of that.

Awareness without trust does not convert in this segment. A Swiss-French SME director who sees your name on a hoarding does not call you. They call a peer to ask what they think of you.

You don't need to. You bring twelve of them together at a time, over breakfast, with a speaker who genuinely has something to teach them about how their sector is changing. Morning format, two hours, respectful of their time.

The cost per contact, no. The cost per qualified, engaged contact, yes. And above all: you sell them nothing that morning.

You give them value before they are customers. They leave with concrete information about their sector, they have met peers, they have had access to experts they would not have found on their own. You will not have proclaimed your competence: you will have demonstrated it in front of the people who matter.

They will not always be. That is exactly why the relationship is your differentiator, and not the spec sheet.

We will not reduce your lead times. That is engineering and supply chain, not relationship management.

On what the customer lives through during those three months. Take a real case. A watch brought in for servicing. The customer hears nothing at all for eleven weeks. He calls twice and is told he will be contacted. The piece comes back with no explanation, and an invoice that differs from the initial estimate.

Technically, yes. But that customer had not bought a movement. He had bought an object to mark an event — a graduation, a wedding, something passed down. Across eleven weeks of silence, that story eroded. It is not your workshop that failed. It is your communication.

That is exactly what you are going to do. A mid-point update, even when there is no news. It is not the information that reassures, it is the presence.

Five points of contact per case, only one of which is a call. The marginal cost is low. The effect is not: customers who had nearly left the brand after a bad service experience became its most loyal ambassadors.

And that is where your relationship is decided. Luxury is not played out solely in the act of purchase, it is played out at every point of contact that follows. After-sales service is invisible in your campaigns and decisive in loyalty. It makes or breaks the relationship over the long term.

It is easy to identify once you have seen it. In the better-rated centre, when a deadline is going to be missed, the technician calls before the customer calls.

That's all. And it is very hard to obtain.

Because calling a customer to announce a delay means exposing a failure. In the other centre, the technicians protect themselves: they retreat behind the complexity of the case, refer the customer to another department, play down what is at stake. They are not bad professionals. They are professionals who have understood that acknowledging a problem costs them something.

That is precisely the paradox we observe, and it is counter-intuitive: this form of honesty is rarer in prestige brands than in accessible ones. The higher the promise, the stronger the temptation to protect it with silence or with jargon.

A disappointed customer treated honestly often stays loyal. A disappointed customer treated with arrogance never comes back. Silence does not protect your promise, it destroys it more surely than the delay itself.

They are not permitted to, more precisely. As things stand, whoever flags a delay exposes themselves; whoever lets it slide does not. You have organised the silence without meaning to. As long as that asymmetry exists, no instruction will hold.

Hotel craft is passed on through apprenticeship, through osmosis, through years of practice. It cannot be rebuilt in a few weeks. An accelerated programme will give you gestures, not a profession.

They did not come back because other sectors offered better conditions without demanding as much of them. This is not a shortage of vocations. It is a renegotiation of the implicit contract.

What there is, above all, is an inversion of the terms of the negotiation. What was tolerated for decades was tolerated because candidates had no alternative. The crisis made the alternative visible. Split shifts, the culture of sacrifice as a rite of passage, hierarchical deference — those models were not functional, they simply had no competition.

Two moves. The first: win back experienced professionals by demonstrating to them that working conditions have genuinely changed. It is not skills that are missing from the market, it is reasons to come back.

Widen the pool. We observed the opposite movement in another engagement: a Geneva private bank with an international clientele recruited former luxury-hotel doormen and receptionists into front-of-house and client relationship roles.

Banking codes can be taught in a few weeks. What they brought could not: the instinct for service at the highest level, the ability to read a situation before it becomes a problem, the art of making a customer feel expected rather than merely tolerated. Service competence is transferable — and that holds in both directions.

It will optimise your revenue per available room. It will not create the experience, it prepares the ground for it. A guest can book through a flawless interface and arrive at an establishment where the welcome is indifferent. The algorithm that calibrated the price does not make up for a doorman who doesn't smile.

You are mistaken about what the tool does. It does not replace professions, it shifts the value within them. The lawyer freed from searching for precedents refocuses on strategic judgement. The accountant freed from data entry becomes an adviser. Your first level does not disappear: it moves up a notch.

You need whoever validates, whoever monitors the impact, and whoever carries the ethical responsibility. The machine has no ethics: it has parameters, set by humans with their biases and their interests. In the age of AI, a leader's responsibility is not technical, it is moral.

That is where an explicit red line has to be drawn. A customer whose needs are anticipated accurately feels understood. A customer whose needs are anticipated excessively feels watched. The difference is not technical. It is ethical, and it is decided by whoever configures the system.

In the intent behind the configuration. An engine designed from the customer's point of view reinforces trust. Designed from the margin's point of view, it becomes a sophistication of manipulation — harder to detect, precisely because it speaks the language of personalisation.

That is your principal risk, and it appears in none of your indicators. An ultra-optimised system collapses precisely where it was most efficient. You are producing fragility disguised as performance.

It is only useless in calm periods. That is the very definition of an insurance premium.