Episode 4. First the Team

Listen on Spotify Apple Podcasts

Episode four takes up the subject the book’s interviews return to more than any other: the team. It opens with Aaron Kaupp and the manager who sent an exhausted young hotelier home and finished the shift himself, a gesture the book treats as an allocation of attention that has compounded across a career. From there the episode follows the chapter’s five movements in order. Joan Roca and Tom Roelens establish that the team is the work. Marc von Arnim, Graham Ledger, Matthew Orlando and Jonnie Boer show what hiring for character looks like in an interview or a kitchen trial. Roelens, Stephen Ansell, von Arnim, Ledger and Patrick O’Connell describe onboarding as induction. Patrizio Cipollini, Hans Neuner and Nicolai Nørregaard show how culture is built daily. Cipollini and Taljinder Singh illustrate the leader as protector. The episode closes on the dignified departure, the four costs of a bad hire, the team as moat and the Select, Develop, Defend model.

In this episode

The manager who finished Aaron Kaupp’s shift, and why it still matters.
Joan Roca and Tom Roelens: the team is the work.
Hiring for character: von Arnim’s intuition, Ledger’s 80/20 rule, Boer’s trials.
Onboarding as induction, from two days at Lanaʻi to three weeks at Singita.
Cipollini’s four verbs, Neuner’s four pillars and Nørregaard’s no shouting rule.
Six practices of the dignified departure and the Select, Develop, Defend model.

Transcript

Automatically transcribed from the audio and lightly corrected. Speaker turns are not marked.

Read the full transcript (6754 words)

There is this interaction that completely shifted my perspective on leadership. And it involves a hotelier named Aaron Kaupp. Oh, right. The shift story. Yeah, exactly. Yeah.So Kaupp had worked multiple consecutive shifts in a row. Just brutal hours, yeah. Right. And his manager, who by the way remains unnamed in the book, noticed that working another consecutive shift would tip Kaupp into this level of fatigue from which he just would not quickly recover. Because there's a limit, right? Exactly.You can only push someone so far before they just break. Exactly. And furthermore, this manager knew that the department would need Kaupp at his absolute best in a few days for a specific arrival. An arrival that Kaupp himself was completely unaware of, right? Yeah, no idea. So the manager possessed this, you know, this broader vantage point.He could see the operational horizon that the employee could not. Which is such a key point. So the manager pulls Kaupp aside, takes him out to lunch, sends him home to rest. And then, and this is the crazy part, steps in to finish the shift himself. Which you just don't see very often. No, you really don't.And Kaupp actually walked home that afternoon convinced he had done something wrong. Oh, he thought he was being punished. Yeah. You assume this was a punitive measure. Like he's being sent home, so he must be in trouble. But you know, he returned for his next shift, fully rested.And what happened? The manager simply asked how he felt. Kaupp replied that he felt better. And the covered shift was never mentioned again. Wow. Yeah.And Kaupp continues to create this unnamed manager for that single action. You know, Kanani's framing of this opening moment with Kaupp is so crucial to understand before we really move forward. Right. Because he explains that this act of protection by the manager is fundamentally an allocation of attention. Allocation of attention. Unpack that a bit.Well, if we consider the traditional mentor's gift, you know, the way a master deliberately passes down knowledge to an apprentice. Like teaching them the craft. Exactly. This act of covering the shift is the institutionalized version of that gift. Oh, I see. The manager takes their own highly valuable attention, their own literal time, and uses it as a protective shield for the team member.That is, that's powerful. Because that one decision, right, to absorb the physical burden of a shift rather than just ringing every last drop of labor out of an employee, it bought decades of loyalty. Right. Kaupp thought he was being managed out, but instead he was being protected. And this, you know, this perfectly sets up our mission for this deep dive. Absolutely.Because today we are examining chapter four, which is titled First, the Team from Rahim B. Kanani's book, The Luxury of Attention. Such a great chapter. It really is. And our goal here, for you listening, is to track the actual chronology of building a world-class team. Moving step by step.Right. Through five distinct movements. We're talking hiring, onboarding, culture, defense, and finally departure. Yeah, we're really looking at why the most revered leaders view their team not merely as a tool to execute the work, but, you know, as the work itself. And that leads directly into the central thesis of Kanani's chapter. Right.He argues exactly that. The team is not a resource utilized to produce the work. The team is the work. Which is a huge paradigm shift for a lot of people. It really is. And to make this tangible for you listening, think of the physical building of a luxury hotel or like a Michelin-starred restaurant as the hardware.The hardware, right. Yeah. So the real estate, the dining room, the expensive kitchen equipment, the chandeliers, that is all just hardware. The team is the operating system. I love that analogy. Right.Because you can have the most expensive hardware ever constructed, but if the operating system is broken, the entire user experience fails. It crashes. And that analogy aligns perfectly with how the operators themselves view their own businesses. Who does Kanani bring in to talk about this? Well, he brings in Joan Roca. Okay.And Roca grew his kitchen from a starting point of just two cooks to an eventual force of 40 cooks. Wow, from two to 40. Yeah, that's massive growth. That's massive growth. Yeah. And Roca actually states, quote, cooking is a team sport.You simply cannot achieve greatness alone. Which makes sense. Right. And he goes on, human capital is the most important capital in the restaurant. And we invest heavily in our team and resources to take care of our staff. This enables them to grow and perform their best.So Roca is explicitly identifying human capital as the primary asset. Yes. And we see this mirrored on the hotel side as well. Definitely. Because Tom Roelens says something very similar. I have it here.He says, ultimately, the luxury hospitality industry is a people business. You can have the most amazing physical asset in a beautiful natural surrounding and in an idyllic location. But it all comes down to people and the service they provide. Exactly. It all comes down to the people. Yeah.He finishes by saying, that's what makes the difference between whether or not guests decide to come back. Right. But, you know, this raises a major question for me. What's that? Well, if the leaders in Kanani's book all recognize that the team is the primary asset, why is it so rare in practice? Yeah.Like, why does so many operations just feel entirely mediocre? So Kanani addresses this by explaining what he calls a fundamental operational reversal. Okay. Reversal of what? Well, the physical asset like that beautiful building or the idyllic location that Roelens mentioned, it merely produces the conditions under which the team can produce loyalty. Okay, right.But most operators reverse this logic completely. They assume the physical building itself is what produces the loyalty. Oh, I see. So they think the view or the marble floors are what bring people back. Exactly. And because of that, they view the team simply as a mechanism to maintain the building.Wow. Kanani argues that this specific reversal in logic is the most common cause of mediocrity. That makes total sense, honestly. If a manager believes the crystal chandelier is what brings the guests back, they can just spend all their time and budget polishing the chandelier. While treating the staff as completely interchangeable, low-cost maintenance workers. Right.But if the team is the actual engine of loyalty, then you have to construct that team with incredible precision. Which forces us to look at the very first step in Kanani's chronology. Hiring. Hiring. Because if the operating system is built out of people, how do these leaders actually select them? Well, the unanimous claim across all the interviews Kanani conducted, and these have multiple continents by the way, is to hire for character because everything else can be taught.Which sounds great, right? Yeah, but I have to challenge the practicality of that. Go for it. Hire for character is one of those phrases that gets tossed around in corporate seminars all the time. Oh, constantly. It's on every PowerPoint.Exactly. But it almost always ends up being this vague platitude. Like, how are these specific leaders operationalizing the search for character in an actual real-world interview? That's a great question. And they do it by looking for very specific indicators that cannot be faked on a resume. Okay, what kind of indicators?Well, take Marc von Arnim. He looks specifically for emotional intelligence. Okay. He explains his approach, saying, quote, when interviewing applicants, I look for people that speak from the heart and display a level of emotional intelligence. Speak from the heart. That's interesting.Yeah. And he continues, the luxury hotel industry is about how we make the customer feel. And therefore, part of the interview process is simply using your intuition when interacting with an applicant. So he's leaning heavily on his own intuition during the interview. Right. And Kanani adds a really sharp observation here.He says a candidate who is fluent only in resumes is the wrong hire. Because if a candidate can only speak the language of, like, corporate achievement, you know, certifications, metrics, efficiency, they lack the raw emotional material required to anticipate and manage a guest's feelings. Exactly. They are literally speaking the wrong language for the industry. But von Arnim's approach relies heavily on intuition. Does Kanani highlight anyone who uses a more, I don't know, structured diagnostic tool to find character?He does, actually. A Graham Ledger utilizes what he calls the 80-20 rule. 80-20. Okay. How does that work? Ledger says, quote, after interviews, including a careful background and reference check of a potential employee, evaluate their candidacy using the 80-20 rule.The 80 refers to enthusiasm and cultural fit, while the 20 refers to the technical side, which can be taught and developed over time. Okay. So 80% is enthusiasm and fit, 20% is actual technical skill. Right. He emphasizes the 80 portion is the key. But the really fascinating part is the diagnostic tool he uses to determine that 80%.What does he ask them? He asks candidates about family values, their school experience, and specifically, he asks whether they keep in touch with old friends. Wait, really? Yeah. He asks if they keep in touch with old friends. Yes.That is brilliant. Right. Why do you think that is? Because asking about old friends to gauge professional suitability, it proves something. And someone has maintained a friendship for a decade. It proves they have relational endurance.Relational endurance, yes. It proves they know how to navigate conflict, how to forgive, and how to sustain effort in a relationship when it isn't easy. Which is exactly what you need in hospitality. Right. That is the exact psychological profile you want handling a difficult guest of the front desk. It really is.Who else does Kanani feature in this hiring phase? Well, Aaron Kaupp from our opening story, he approaches the interview by asking candidates about how they have handled difficult situations in the past. So looking for real-world examples. Yeah. He is actively looking for empathy, reasoning, and calm problem-solving under pressure. Makes sense.And then there's Matthew Orlando, who prioritizes passionate people above all else. He states, quote, you must surround yourself with passionate people that really care about their work. And in that sense, I hire based on personality more than I do skill. So personality over skill again. Yes. And then Jonnie Boer takes it a step further.He actually puts applicants on trial. On trial? Yeah. In what sense? Like a probationary period? No, like an actual operational trial before they are fully hired.Oh, wow. Boer says, quote, we always have applicants to our team on trial for a few days. Experience is not that important. That's a bold statement. Experience is not that important. Right.But he continues, what we look for is people with passion, perseverance, and the right personality. I believe that people perform better when they are treated well. So I always stay calm, take everything step by step, and maintain a bird's eye view. Okay. This is where we really have to pause and look at the gritty reality of this strategy. Okay, let's do it.Hiring for character and just ignoring experience creates a massive immediate problem on the floor. You're talking about the technical gap? Yes. Think about a professional kitchen. They operate on the traditional Escoffier brigade system. Right, the brigade.And that system is a highly interdependent chain. You have the person for wrapping the ingredients, the person cooking the station, the person expediting the plates. Everyone relies on the person before them. Exactly. Every single step assumes technical proficiency. So if a chef hires someone with incredible passion, but no actual night skills, that interdependency breaks down completely.It grinds to a halt. Right. So how can a listener who, say, manages a fast-paced, high-stakes project, realistically absorb the immediate hit to productivity when they choose character over immediate competence? Well, you are identifying exactly what Kanani calls the brigade complication. The brigade complication. Yes, and he acknowledges that it is a severe complication.Because as you said, the traditional Escoffier brigade system absolutely relies on technical proficiency at every single step. It has to, or the food doesn't go out. Right. So when a leader hires for character over skill, that technical gap doesn't just disappear. Someone has to fill it. Exactly.The leader themselves or the senior team members must personally carry that new hires technical gap for months. That means they have to slow down their own work. Yes, they have to teach. They have to double-check the prep, and they just have to absorb the slack. Honestly, that sounds exhausting. It sounds like a recipe for immediate burnout for the senior staff.It is exhausting in the short term, but Kanani asserts that this trade almost always pays off due to what he terms the bounded cost claim. Break that down for me. The logic is purely economic, but you have to look at it over a longer time horizon. A technically superior candidate who lacks character will actually cost the operation more in their first year than a character superior candidate will require in training over five years. Over five years, wow. Let's really look at the mechanics of that bounded cost claim.Let's do it. If you hire someone who has perfect technical skills, but is arrogant or dismissive or lacks empathy. Right, a toxic rock star. Yeah. They might save you two months of basic training initially. Sure, because they hit the ground running.But over the next year, their lack of character is going to alienate guests, which requires expensive service recovery. And it is going to frustrate the rest of the brigade, lowering overall morale and potentially causing your best people to quit. Which is incredibly expensive. Exactly. So the cost of their bad character is unbounded. It just keeps multiplying.Precisely. Where's the cost of training a passionate, high character person is bounded. It has a limit. Right. As a clear end date, once they actually acquire the technical skill. Exactly.You are trading a temporary bounded technical deficit for long-term cultural and operational stability. Which is a smart trade. But, and this is a big but, acquiring that raw material of character is only the first movement. Right. You can't just hire them and abandon them. No.Once you have brought this high character, perhaps technically green individual into the building, the operation has to shift to the second chronological movement. Which is onboarding as induction. Yes. Because if you take someone with great character and just throw them onto the floor without context, their character will quickly mutate into panic and frustration. Oh, absolutely. They'll just feel overwhelmed.And Kanani draws a very hard line here regarding what onboarding actually means to these leaders, doesn't he? He really does. The best operations absolutely do not treat onboarding as an HR checklist. Which is how most places treat it. Right. Honestly.Instead, it is treated as a serious multi-day induction into the values and behaviors of the property. I mean, for you listening, just think about the standard corporate onboarding experience you might have had in the past. Oh, we've all been there. Right. You sit in a back office somewhere, someone hands you a massive manual, you watch your generic safety video from the 90s, you get a login credential, and then you were just pushed out onto the floor. Good luck.Yeah, exactly. Contrast, that mechanical process with what Tom Roelens does. What does he do? He runs a two-day program for every new hire that covers the company goals, the local culture, and the history of the resort. A full two days just on that. And Stephen Ansell extends that structured support even further.Really? He signs a personal coach within the recruits specific department for the first three months. Three months. That's a massive commitment. That's a massive commitment. And it isn't just a casual buddy system either.It is a dedicated three-month coaching assignment to ensure the induction truly takes root. That is incredible. Yeah. And then there's Marc von Arnim again. He personally attends every single new recruits orientation to explain expectations. But he also uses that time to share his own humble background, right?He does. And I want to highlight that specific choice, sharing his humble background on day one. Why is that so important? Because by doing that, he is destroying the artificial hierarchy that so often prevents new staff from asking questions. Oh, that makes sense. It humanizes him.Exactly. He is showing them that leadership is approachable. But I have to ask, what is the operational risk if a property decides they are just too busy for this kind of deep induction? Like they just can't spare the time? Yeah. What if they just need bodies on the floor immediately because they're understaffed?Well, Graham Ledger issues a very stark warning about exactly that scenario. What does he say? He warns that a poorly inducted staff member will fail spectacularly. Spectacularly? Yes. Because the stakes in luxury hospitality are so high.Ledger's own induction process lasts anywhere from three days to more than three weeks, depending on the role. Wait, a three-week induction before someone is fully operational? Up to three weeks, yes. That is a massive upfront investment of attention. It is. But to understand why that investment is considered entirely non-negotiable, Kanani turns to Patrick O'Connell.Okay. O'Connell views his team through a very specific lens. He says, quote, the team is united around a common goal of excellence without compromise. For me, the keyword is collaboration. Collaboration. Right.And he continues, everyone's contribution is important and everyone has to be on cue. It's very much like an orchestra. And my role is parallel to a conductor's. I'm always looking for any flaws and imperfections that need correction. An orchestra. Mm-hmm.That is such a brilliant way to conceptualize an interdependent team. Isn't it? Yeah. Kanani extends O'Connell's quote with his own analysis. And this is where the mechanics of induction become entirely clear. Okay, laid out.Kanani points out that musicians are trained separately, right? They learn their instruments in isolation. Like taking piano lessons by yourself. Exactly. But it is the rehearsal that aligns them. A new musician who has rushed past rehearsal is audible for months.Wow. Let's translate that out of the orchestra analogy and onto the hospitality floor. Let's do it. If you hire a front desk agent and a housekeeper, they learned their basic skills separately at previous jobs, maybe. Right. But the induction is the rehearsal where they learn how to synchronize within this specific property.Exactly. They learn exactly how the property communicates a room status change, how they handle a guest's specific preference, how the timing of the luggage delivery matches the check-in process. It's all choreography. It is. And if you skip that induction rehearsal, the guest will literally feel the dissonance. They'll notice it immediately.The surface will feel disjointed, rushed, and chaotic. And that dissonance will persist for months, damaging the property's reputation with every single interaction. Which is so costly. This is why the induction phase is treated as a critical operational necessity, not an administrative burden. It's mandatory. But you know, even a perfect induction only lasts a few weeks.Right. Which brings us to the third movement in Kanani's chronology. What happens every single day after that? Building the culture. Building the culture. And Kanani attacks a very common corporate myth right out of the gate here.Oh, he really goes after it. Yeah. He argues that culture is never, ever built by an off-site retreat or a consultant. He is emphatic about this. Culture is built by a thousand repeated small choices made by the leader daily over years. It's not a poster on the wall.No. It is the cumulative weight of daily operational behavior. And to illustrate this, Kanani examines Patrizio Cipollini. Okay. What did Cipollini do? Cipollini built his culture through four very specific actions.He stated, quote, respecting your team means listening to them, including them in decision making, asking for their advice and insight, and rewarding them for going above and beyond. Okay. So listening, including, asking, rewarding. Yes. And Kanani labels those four verbs listening, including, asking, and rewarding as the entire definition of a culture of respect. It sounds so simple when you list it out like that, but the friction comes in the actual execution, doesn't it?Oh, absolutely. Because a lot of managers say they listen, but they don't actually include the team in decision making because, well, it slows down the process. Right. It's faster to just dictate. Exactly. But Cipollini practiced a level of inclusion that I think most leaders today would find deeply uncomfortable.You're talking about the financial transparency? Yes. He practiced total financial transparency. He shared the hotel's results and the department budgets directly with the staff. Which financial transparency at the front line level is exceedingly rare, but its psychological impact is profound. Let's unpack the psychology that for a second.Why does showing the budget to a front line staff member fundamentally shift their mindset from being an employee to being an owner? It changes the whole dynamic. It really does. Like, if I am a line cook and you just tell me to save food cost, I might roll my eyes because I think the owner is just being greedy. Right. The boss just wants another yacht.Exactly. But if you actually show me the profit and loss statement, you're trusting me with the reality of the business. You're treating them like an adult. Yes. You are showing me that if we waste 10% of our inventory, the margin disappears and there is no money for new equipment or raises. The math becomes real.When you remove the mystery of the finances, you remove the adversarial relationship between labor and management. Because the team understands the math, so they start making decisions like owners. Exactly. They become true stakeholders in the daily outcome. And we see a similarly structured daily approach to culture with Hans Neuner. Oh, what does Neuner do?He relies on four pillars to build culture. Neuner says, quote, earning respect in this world among your team, colleagues, and beyond comes from several pillars. Doing what you know well, leading by example, sharing your knowledge and expertise with others and by empowering and supporting your team members. Okay. Doing what you know well, leading by example, sharing knowledge, empowering and supporting. Exactly.And Kanani calls Neuner's four pillars an operational specification. I really like that phrase operational specification. It gives it weight, right? It does. It means these aren't just values printed on a break room poster. They are the required specifications for how a leader must operate every single day.Right. If a leader doesn't share their expertise, they're failing the specification. It's a binary metric. Exactly. Joan Roca actually echoes the necessity of this daily effort, asserting that managing inclusively based on various talents is the only sustainable path. Also it's a recurring theme.Very much so. And then Kanani brings in Nicolai Nørregaard, who focuses intensely on the concept of family to build his culture. Family? Mm-hmm. Okay, that's a tricky word in business. It is.But Nørregaard says, quote, we've always viewed our staff as family and work hard to create an environment where our employees feel comfortable and secure. It's vital that staff love their work. There is no shouting or bullying. It is simply not accepted. No shouting or bullying. Right.Furthermore, Nørregaard closes his restaurant every summer so the entire staff can live and work together in a farmhouse on an island. Okay, this is where Kanani's analysis gets really sharp, because viewing staff as family is another one of those concepts that can easily turn toxic. Oh, yeah. It's often used to demand unpaid overtime or ignore boundaries. Exactly. Do it for the family.But Kanani points out three very distinct things about how Nørregaard actually operationalizes this concept. Yes. Kanani points out that first, the prohibition on shouting is a rule treated like a sanitation standard. Which is fascinating. Right. It isn't a suggestion.It is a hard operational boundary just like you wouldn't serve spoiled meat. You don't shout. Right. Second, the team's emotional security is viewed as operationally necessary. Not just a nice to have. Exactly.The restaurant simply cannot function at its highest level if the staff is operating in fear. That makes sense. Third, the farmhouse is the actual practice. The farmhouse is the mechanism. Yes. They aren't just calling themselves a family while working separate shifts and never seeing each other.They are literally living and working together in a shared space for a whole season. Which forces connection. It does. They are forced to resolve conflicts, support each other and build genuine bonds. That kind of shared crucible creates a cultural resilience that no corporate consultant could ever manufacture. Never.Even that strong culture leads directly to the fourth movement, defending the team. Ah, yes. Because once you have built this highly aligned, high character culture, you have to protect it from external forces. You have to guard the moat. Exactly. And Kanani notes that this subject is treated with the most conviction by the interviewees.Yet it is chronically under discussed in traditional leadership literature. The leader as the protector of the team. Yes. This is all about absorbing the shock waves. The leader's job is to absorb the difficult guest, the impatient owner, the demanding investor, and even the visiting brand inspector. This brings us right back to our opening story with Kaupp's manager.Right. The shift cover. That manager recognized a threat to his team member. In this specific case, the threat of debilitating fatigue. And he interposed himself. He interposed himself between Kaupp and the schedule.And Kanani notes that the cost to the manager was just a few hours of physical labor. The return on that investment has run for nearly 40 years. It is the ultimate asymmetrical investment. Truly. And Cipollini approaches this same concept of defense through what he calls extending paternal warmth to the team to build trust. Right.Now Kanani notes that the phrase paternal warmth can imply an outdated parental hierarchy that a lot of modern workers might reject. Sure. It sounds a bit antiquated. But what is the actual substance beneath that phrase? The substance is unyielding protection. Unyielding protection.It is the leader saying, I am responsible for your well-being while you are under my roof. Which is profound. We see this mirrored by Taljinder Singh as well, who was mentored by Patu Keswani and Ronnie Lobo. What did he learn from them? From Lobo specifically, Singh learned to treat people with the utmost respect, fairness and dignity. Okay.And Kanani actually distills all of these approaches into a single protection test for leadership. What is the test? It's a simple question. Does the leader use the team or lead the team? Use the team or lead the team? Let's explore the mechanics of that test in a real-world scenario so we can really grasp it.Okay, give me a scenario. Let's say a high-profile guest is furious about a delay in service, but the delay was actually caused by a system's failure, not by the staff. Oh, it happens all the time. The POS system goes down or whatever. Exactly. The leader who uses the team will throw the front-line staff to the wolves.Right under the bus. Yep. They will blame the server right in front of the guest to instantly relieve their own discomfort and appease the guest. These the staff is a human shield. And Kanani argues that the consequences of that specific choice are permanent. Permanent.Yes. A team thrown to the wolves even once will spend the rest of their tenure quietly disengaging. They never forget it. I want you listening to really consider this dynamic in your own career. It's a powerful reflection. Think about a time a leader stood between you and a crisis.They took the blame from a client or an owner to protect you. How did that change your loyalty? It probably cemented it forever. Right. Your willingness to work hard for them probably skyrocketed. But now think of a time a leader let you take the fall to save their own skin.Oof. How fast did you disengage? You probably updated your resume that same evening. Absolutely. You can never unsee a leader failing the protection test. The team's trust is either solidified or completely destroyed in those moments of pressure.There is no middle ground. But you know even when a leader passes the protection test and builds a phenomenal culture, people still eventually leave. Which brings us to the fifth movement in Kanani's chronology. The dignified departure. The dignified departure. This is such a critical phase because Kanani states that how a leader manages an exit is the truest test of their posture toward the team.Cipollini addresses the reality of staff moving on by saying quote, it is bittersweet when a staff member decides to move elsewhere. But I am very proud of them and am grateful that they had the chance to grow with us first. That's a great attitude. And Kanani glosses this by stating a key principle. The lever is not a defection. The lever is a graduate.The lever is a graduate. That reframing changes everything about how you handle turnover. It really does. Because if someone leaving is a defection, you treat them like a trader. You walk them to the door with a cardboard box. Exactly.It's hostile. But if they are a graduate, you treat them as an alumnus of your system. But Kanani doesn't just offer this philosophical reframing. He breaks down to exactly six practices for letting someone go. These six practices form a really comprehensive mechanism for managing departures, whether the departure is voluntary or forced. Let's walk through these practices practically.Imagine a scenario where a leader has to let someone go because the role is just outgrown their technical capacity. Okay. Tough firing. Right. The first practice Kanani outlines is that the difficult conversation has held privately and in person by the leader. Never delegated to a junior manager.Never. Why is delegating this so destructive? Well, delegating the firing to a junior manager signals cowardice to the person being like, oh, obviously. Right. But more importantly, it destroys the trust of the remaining team. Oh, because they're watching?Exactly. How much does the leader avoid the hard work of looking an employee in the eye? They realize that the leader's previous claims of family and protection only apply during easy times. The remaining team sees the hypocrisy instantly. Instantly. Wow.Okay. Kanani's second practice addresses how the conversation itself is framed. Right. The reasons must be made clear without becoming personal. So the mechanism here is framing the exit as the role no longer being the right fit rather than framing the individual as a personal failure. Exactly.You attack the fit, not the person. What's the third practice? The third practice requires that support must be real, not performative. Real support. So not just saying, let me know if I can help. Right.This isn't just wishing them well. It is actively providing references, offering severance, giving them time to transition, and even making introductions to other operators where they might be a better fit. And then with total dignity on the way out the door. Yes. Okay. The fourth practice is about communication.Right? How the departure is communicated to the rest of the team. Right. The team must be told what happened with discretion and language that doesn't undermine the departing colleague. So no gossiping or throwing them under the bus after they leave? Never.And the fifth practice? The fifth practice dictates that the conversation is held promptly. Promptly. Once the decision is made, the leader does not drag it out. No slow fading them out. Exactly.And the sixth practice is that the leader continues to invest in the relationship after the working tie ends. I want to point out to the listener that these six practices, handling it yourself, depersonalizing it, real support, discrete communication, promptness, and ongoing investment, these are not just about being a nice empathetic person. No, not at all. This is a cold, calculated, long-term economic strategy. It absolutely is. Because the hospitality and culinary worlds are incredibly small.The way you handle a departure dictates exactly what that person tells the industry about you. They will talk. They will talk. If you fire someone without dignity, they become a walking billboard for why talented people should avoid your property. Which hurts your pipeline. Right.But if you follow Kanani's six practices, even a person you let go will respect you. They will tell the industry that you operate with integrity. Which directly impacts your future ability to hire for character. Exactly. It all feeds back into the first movement. It serves as the perfect bridge to the final synthesis of the chapter, the economics of the people first model and the moat.Right. Pulling it all together. Kanani pulls all of this chronology, the hiring, induction, culture, defense, and departure into the harsh operational reality. Because at the end of the day, it's a business. It is. He forces the question, why are these extensive investments in people considered capital expenditures rather than discretionary expenses?Which is how most finance departments view them as discretionary. Right. It is if a financial controller is looking at a quarterly profit and loss statement, taking a manager off the floor to do a three-week induction. It looks expensive. Or keeping a headcount position open for months just to find the right character. That looks like a huge inefficiency.It looks like a discretionary expense that is hurting the margin. But to understand why it is actually a capital expenditure, we have to look at Kanani's four costs of a bad hire. Yes. Kanani outlines these four costs to expose the hidden economic drain of ignoring the chronology we just talked about. Walk us through them. The first cost is the immediate productivity gap.Okay. Because the bad hire lacks character or competence, the rest of the team has to absorb the slack. We talked about this earlier with the brigade system. Exactly. The sous chef has to step down and do the commis prep work, which means the expediter is overwhelmed, which means the food goes out late. The entire system drags.And that costs money. Right. The second cost is service recovery. A bad hire will inevitably make guest-facing mistakes. And service recovery is brutally expensive. Oh, very.A rude interaction at the front desk might require comping a $500 room night just to save the relationship with the guest. Or comping a whole table's dinner. Exactly. It's a hard dollar cost. What's the third? The third cost is team morale.The right hires, the people you carefully selected for character, they deeply resent carrying the burden of a bad hire. They get tired of doing two jobs. Right. And actually, they disengage and leave. Which means you lose your best people. Yes.And finally, the fourth cost is the leader's own time spent managing the fallout. The leader's spending hours mitigating the damage instead of driving the business forward. Exactly. So when you combine the productivity gap, the comforums, the lost staff, and the wasted leadership time. It adds up fast. Kanani rightly calls the bad hire the most expensive line item never entered into the books.Never entered into the books. This economic reality leads directly to Kanani's central conceptual framework for the entire chapter. Which is? The team is the moat. The team is the moat. Now the concept of an economic moat usually refers to like intellectual property, scale, or network effects that protect a business from competitors.Right. It's what keeps the competition away. But Kanani is applying it to the workforce. He argues that a competitor can match your physical assets within 18 months. Oh, easily. So when you're pulling down the street, by the same luxury linens, implement the exact same technology and copy your entire design aesthetic.If they have the capital, they can replicate the hardware. Exactly. But they cannot match a team that has been deliberately built, inducted, culturally aligned, and defended over a decade. They can't buy that. No. The team itself is the only uncopiable asset.Which makes it the moat. Therefore, cutting these investments in the team under quarterly pressure is literally liquidating the property's capital base. Wow. So you're selling off your only true competitive advantage to make a short-term quarterly number. It is operational self-sabotage. It really is.And to formalize how a leader maintains this moat, Kanani details what he calls the people first leadership model, which is built on three core disciplines, select, develop, and defend. Let's review how the evidence we've covered maps to those three disciplines. Perfect. First, select. This requires hiring for character. It utilizes von Arnim's intuition to see if a candidate can speak from the heart.Right. And it utilizes Ledger's 80-20 rule to verify their relational endurance. Second, develop. This is the disciplined, multi-day onboarding we talked about, the leader's daily presence on the floor setting the standard, and the radical financial transparency that builds that true ownership mentality. Exactly. And third, defend.This is the leader actively interposing themselves between the team and eroding forces. Like the bad guest or the demanding owner. Right. The stress is that this defense is largely invisible in peacetime, but it is absolutely decisive under stress. So bringing this directly to you, the listener, evaluate your own operation right now, today. Be honest with yourself.Looking at the select, develop, and defend axes. Which one are you actively working on today? And which one are you neglecting? It's a tough mirror to look into. It is. Are you selecting for character but failing to defend them when the pressure hits?Or are you defending them but failing to develop them through proper induction? Because the moat requires all three. You can't just pick two. Kanani ties all of this together in his final point, really bringing us full circle. How so? He takes Marc von Arnim's practice of listening for candidates who speak from the heart, and he places it right next to the unnamed manager who finished Aaron Kaupp's shift.The chronological beginning of the employee journey and the daily operational reality of protection set right side by side. Exactly. People first leadership is simply leaders treating the team's well-being as a fundamental part of their own job. It is not an HR initiative. No, it is the core work of the leader. Yeah.Yeah. We operate in a business environment obsessed with optimizing systems, right? Automating tasks and deploying AI to remove human error. It's all about efficiency now. But if a unified protected team is the ultimate competitive mode, an asset that cannot be replicated by venture capital or technology within 18 months, then the most subversive and economically powerful thing you can do as a leader is simply to pay deep protective attention to the people working next to you. The human element remains the ultimate luxury.It really does. But once you hire for character and build this moat, the question remains whether the leader will actually give the team the room to operate. Right, because micromanaging ruins all of this. Exactly. Yeah. The question of whether the leader will actually give them the room and what happens in the operation when the leader does is the subject of episode five, Giving the Keys.

In this episode

Transcript

Read what the episode discusses