The Host or the Gatekeeper

"Is that it?"

That was the question I got asked recently at a Costa drive-through, the moment after I'd ordered a single drink. Not "anything else for you today?" Not even a neutral "next?" Just four words, flat, faintly accusing, as if wanting only a coffee was itself the inconvenience. At the window to pay, the person actually leaned out (well, not exactly leaning, more making me lean in), said two words: "Costa app?" No greeting either side of it. When I asked for a receipt, you'd have thought I'd asked him to write a ten thousand word thesis, or perhaps adopt one of his children. He thrust it into my hand. I said have a good day. Nothing came back.

I could tell you three more of these in the time it takes to read this paragraph. The restaurant where my food arrived close to thrown at the table and I had to ask twice for drinks and once, separately, for cutlery, as though cutlery were an optional extra rather than the basic mechanism by which food gets from plate to mouth. The hotel where I stood patiently at reception while the two staff behind the desk carried on a conversation, clearly more urgent to them than checking in a guest, about a colleague who hadn't turned up for their shift. Nice hotel. Forgettable welcome. And then the one that isn't really about bad service at all: an email complimenting me on a podcast appearance where I hadn't tried to sell anything, followed immediately, in the very same message, by an attempt to sell me their services.

There’s a subtle (or not so subtle) irony that keeps nagging at me. Every one of those examples happened in a setting that exists, by definition, to serve people. A coffee chain. A restaurant. A hotel. Someone whose entire professional purpose is guest experience. And yet the thing on offer in each case wasn't hospitality. It was just service, and grudging service at that, the retail equivalent of someone doing the bare minimum required not to get formally complained about.

Which brings me to a book that's rearranged a fair bit of furniture in my head over the past few years. Will Guidara ran Eleven Madison Park, the New York restaurant that went from ambitious upstart to the best restaurant in the world under his watch, and his book Unreasonable Hospitality isn't really a restaurant memoir dressed up as a business book. It's an argument, and the argument is bigger than food. His claim, stated as plainly as he can manage it, is this:

"Whatever you do for a living, you can choose to be in the hospitality business." Will Guidara

Not might be able to, if your job happens to involve customers. Can choose to be. A decision, available to anyone, regardless of job title.

What Guidara Actually Argues

It would be easy to read Guidara as offering a customer service philosophy with better branding, and plenty of people who've skimmed the book do exactly that. But the more interesting claim sits one layer down, in a distinction he draws early and returns to throughout:

"Service is black and white; hospitality is color [sic]."  Will Guidara

Service, on this account, is the technical delivery of the thing you're contracted to deliver. The right coffee. The correct room. The invoice processed. It's binary. Either it happened correctly or it didn't. Hospitality is what happens on top of that, the part that can't be specified in a job description because it lives entirely in how the other person is made to feel during and after the transaction.

That distinction matters because it explains why my Costa drive-through experience felt worse than merely inefficient. The service was, technically, delivered. I got a drink. I got a receipt, eventually, delivered with the enthusiasm of a man surrendering a kidney. Nothing about the transaction failed on the "black and white" axis Guidara describes. What was missing was entirely the coloured-in part, the part that costs nothing in ingredients or time but apparently a great deal in whatever internal resource makes a person choose warmth over indifference.

The line I find myself returning to most, though, isn't really about restaurants at all. Guidara describes unreasonable hospitality as being relentless, unreasonable, creative and intentional in pursuit of relationships, whether that's with the people who work for you, the people you serve, or the people in your life outside work entirely. Notice what's doing the work in that sentence. Not a job title. A stance. Something you bring to a relationship, any relationship, rather than something switched on because your contract mentions "customer facing."

The Gatekeeper Trap

So why doesn't everyone just choose hospitality, if it's genuinely a choice and genuinely costs nothing? Because gatekeeping offers something hospitality doesn't: a feeling of control, and with it, a feeling of importance.

The social psychologist Kurt Lewin coined the term "gatekeeper" back in the 1940s, originally to describe something almost domestic. His research looked at how households decided what food actually made it to the family table, and he noticed that whoever controlled that channel, typically the person doing the shopping and cooking, held disproportionate power over outcomes that looked, from the outside, like collective decisions. He later extended the idea to explain how information moves, or doesn't, through any social system, with a "gatekeeper" positioned at each junction deciding what passes and what gets stopped.

What Lewin's framework captures, and what I think explains a great deal of what goes wrong inside organisations, is that gatekeeping isn't necessarily malicious. It's structural. Once you put a person at a junction point, in charge of the gate, they will, almost without meaning to, start experiencing that position as one of authority rather than service. The gate becomes theirs. Passing through it becomes something done to them, a request they grant or withhold, rather than something they exist to facilitate.

This is where I think the Costa employee and the school IT department are doing more or less the same psychological manoeuvre, just at wildly different stakes. Neither set out to be obstructive. But somewhere in the daily grind of standing at a junction point, fielding requests from people who need something only they can provide, the junction itself became the job. Not what flows through it. The gate, not the gift.

Two Kinds of Hospitality

There's a philosophical distinction that sharpens this further, and it comes from an unlikely source for a piece that started at a coffee drive-through: Jacques Derrida, and specifically his late work on hospitality, published as a set of seminars with Anne Dufourmantelle. Derrida draws out what he treats as a genuine, unresolvable tension between two kinds of hospitality. On one hand there's unconditional hospitality, which requires receiving the other without conditions, restrictions, or the expectation of anything in return. On the other, there are the conditional laws of hospitality, the ones that establish a right to and duty of hospitality while simultaneously restricting it by attaching conditions to who gets welcomed and how.

You don't need to have read a page of continental philosophy to recognise the tension in daily life. Unconditional hospitality is Guidara's ideal: welcome the person in front of you fully, on their terms, before you've established whether they've ticked the right boxes. Conditional hospitality is what most organisations actually run on: you're welcome, provided you've filled in the form, provided you're the right kind of visitor, provided you haven't triggered whatever internal rule currently governs the gate. Derrida's point, and it's a genuinely useful one for anyone running a team, isn't that conditional hospitality is the villain of the piece. Organisations need conditions; a school without safeguarding conditions is a school in crisis, not a school being unreasonably hospitable. His point is that conditional hospitality drifts, almost invisibly, into something that has lost any relationship to the unconditional ideal it's meant to be in service of. The rule stops being a rule that protects hospitality and starts being the whole of the transaction.

That's the authenticity question underneath all of this, and it's the one I think matters more than the customer service framing. It isn't really "are you good at service." It's "who are you actually serving when you enforce the condition, the person in front of you, or your own sense of authority over the gate." Those two things can look identical from the outside and feel completely different on the inside, to both parties.

The Education Case Study

I keep coming back to education because it's the sector where I've watched this play out most consistently, and because the stakes of getting it wrong are higher than a lukewarm coffee. I've said a version of this a few times recently, enough that I suspect it isn't coincidence so much as something I've been circling without quite landing on it: a great deal of what's dysfunctional in education happens because the services that exist to support teaching and learning, IT, safeguarding, admin, sometimes leadership itself, start behaving as though they're the destination rather than the corridor.

Ask yourself honestly why anyone becomes a school IT lead, a safeguarding lead, a member of an admin team, a college Quality Director, a head of department. Very few would answer "so that I could decide, from a position of gatekeeping authority, what teachers and students are and aren't permitted to do." And yet that's precisely the lived experience many teachers report when they need something from those functions: a password reset that becomes a three-step ticketing ordeal, a safeguarding referral that gets slowed by process rather than accelerated by urgency, a reasonable request for a resource that gets treated as an imposition on someone's afternoon.

None of this is usually about bad people. It's Lewin's gatekeeper dynamic operating at institutional scale. Put a person at a junction, real needs flow through it constantly, and over time the junction becomes the identity. "I'm the one who decides" quietly replaces "I'm the one who helps," and because the first version comes with a feeling of authority the second version rarely offers, it's the easier one to settle into, especially under pressure.

The Guidara reframe applied to a school is deceptively simple, though not easy: every support function exists in service of two groups, the staff trying to teach and the students, parents and community trying to learn, be safe, and be understood. That's the "guest" in Derrida's sense. Safeguarding leads aren't gatekeepers of child protection; they're hosts of it, and the difference shows up in whether a worried teacher experiences raising a concern as being welcomed into a process or interrogated by one. IT teams aren't gatekeepers of the network; they're hosts of it, and the difference shows up in whether a struggling teacher experiences asking for help as an admission of failure or a normal Tuesday. None of this means abandoning conditions. Safeguarding absolutely needs process; a school running on unconditional hospitality alone would be negligent, not admirable. It means the process should exist visibly in service of the person it's meant to protect, not as a monument to the department administering it.

The genuinely hard question for any school leader reading this isn't "do we have good customer service." It's the one I keep returning to: why did you actually take this role? Leader, decision-maker, gatekeeper, those job titles get used almost interchangeably in the way people talk about senior roles in education, and I don't think that's an accident of language. It reveals which version of the job people think they signed up for.

Beyond the School Gates

I want to be honest that the podcast email I mentioned earlier isn't a story about poor service at all, and it's worth including precisely because it shows the pattern isn't confined to hospitality-adjacent industries. Someone got in touch, kindly, to say they'd enjoyed a podcast conversation I'd been part of, one where I'd deliberately not tried to sell anything. And in the same message, having just praised the fact that I hadn't pitched them anything, they pitched me their services.

That's not gatekeeping, but it is the mirror image of Guidara's argument, and worth naming precisely because it shows how the same failure can turn up wearing an entirely different costume. It's performed hospitality rather than withheld hospitality: warmth deployed as a technique to extract value, rather than warmth offered because the other person is, briefly, your entire focus. Guidara's whole argument depends on hospitality being genuinely unconditional in the moment it's offered, not a softening agent applied ahead of the actual transaction. He puts it more bluntly than I would:

"No one who ever changed the game did so by being reasonable."  Will Guidara

Reasonable, in this context, includes the calculated kind of warmth that's really just sales wearing a nicer jumper. The uncomfortable implication, for anyone in a service-adjacent role, whether that's sales, consultancy, or a school office, is that the test of genuine hospitality isn't how warm you sound. It's whether the warmth survives the moment there's nothing obvious in it for you.

Becoming the Host

If gatekeeping is the default, the position that requires no particular effort to slide into, then hosting has to be a stance you actively choose, repeatedly, probably several times a day in any role that puts you at a junction other people depend on. That's the genuinely useful, slightly deflating truth buried in all of this: it isn't solved once. There's no training day that installs it permanently. It's closer to what Guidara describes as relentlessness, a word he uses more than any other, because the gatekeeper's version of the job is always easier and always available as the path of least resistance.

Practically, I think it starts with noticing the language you use about your own role. Do you describe yourself, even privately, as the person who decides, approves, signs off, grants access? Or as the person who helps, unblocks, enables, hosts? Those aren't just softer synonyms. They describe genuinely different relationships to the people depending on you, and Lewin's original insight was precisely that the person controlling the gate rarely notices they've started identifying with the gate rather than with what's supposed to pass through it.

It also means being honest about which of your conditions are Derrida's necessary kind, the ones that genuinely protect the person you're serving, and which have quietly become the whole point, existing mainly to preserve your own sense of authority over the junction. Safeguarding process protects children. A three-step ticketing system for a password reset mostly protects the IT department's sense of order. Both look, from a distance, like reasonable process. Only one of them is actually in service of the guest.

Key Takeaways

1. Service is the correct completion of a transaction, hospitality is how the other person feels during and after it, and organisations routinely deliver the first while quietly abandoning the second
2. Gatekeeping isn't usually malicious, it's structural, and Kurt Lewin's original gatekeeper theory shows how anyone positioned at a junction point can start identifying with controlling the gate rather than with what's meant to pass through it
3. Derrida's distinction between conditional and unconditional hospitality explains why necessary rules and safeguards can quietly drift into becoming the whole point of a role, rather than staying in service of the person they were designed to protect
4. In education, support functions such as IT, safeguarding and admin exist to serve teaching, learning and the people affected by it, not to gatekeep access to it, even though the daily pressure of the role pushes constantly towards the latter
5. Genuine hospitality has a mirror image: performed warmth. This exists to extract value, rather than warmth offered with nothing obvious in it for you.
6. Choosing hospitality over gatekeeping is not a one-off decision, it is a stance that has to be renewed at every junction, every day, because gatekeeping is always the easier, more available default

None of this started as a grand theory. It started with a man behind a Costa counter who couldn't summon two extra words, and a hotel reception more interested in a colleague's absence than the guest standing in front of them. Small moments, in the scheme of things. But they're diagnostic, because they show what happens when service exists without hospitality, when the transaction gets completed correctly and something essential is missing regardless.

The uncomfortable question this leaves for anyone reading, whatever your job title actually says, is a simple one. Next time someone needs something only you can grant, will you experience yourself as the person guarding the gate, or the person who exists to open it?