Episode 5. Giving the Keys

Listen on Spotify Apple Podcasts

Episode five takes up Giving the Keys, the chapter that closes the first part of The Luxury of Attention and asks what empowerment means once the word stops being a slogan. The hosts open with Alexander Pichel’s order of operations, train the team first and only then let them act, and with Aaron Kaupp’s rule against micromanagement, the most misunderstood claim in luxury hospitality. They walk through the four kinds of authority, decision, spending, language and escalation, with Adrian Gray, Horst Schulze’s $2,000 rule at Ritz Carlton and Will Guidara’s unscripted gestures. Preparation follows, with Pedro Dias on continuous coaching, Kai Speth’s habit of pushing the challenge back, Emma Bengtsson on patience and restraint, and Emmanuel Stroobant on attitude over skill. Michael Ziemer frames the recovery test, Jonnie Boer the pronoun discipline, and Mahmoud Skaf, José Andrés, Ralph Radtke and Kevin Fehling make the business case before the senior team, the checklist and the bridge to The Creative Act.

In this episode

Alexander Pichel’s sequence: train the team, then empower them to act.
The four kinds of authority: decision, spending, language and escalation.
Horst Schulze’s $2,000 rule and why a defined ceiling makes empowerment real.
Kai Speth’s question, how would you solve it, and Emma Bengtsson’s patience.
Michael Ziemer’s recovery test and the three responses to a wrong call.
The pronoun discipline, the senior team and the Empowerment Preparation Checklist.

Transcript

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

Read the full transcript (7859 words)

So there's this really strict operational sequence that Alexander Pichel insists on when he talks about leadership. Right, the train then empower sequence. Exactly. He argues that you have to train your team first, and I mean only then do you empower them to act. Yeah, you can't flip those. You really can't. He points out that, you know, you might have 30 years of experience in the business,but it is your team that serves on the front lines and most often interacts with guests. Which is such an easy thing for leaders to forget, honestly. It really is. And his exact directive is, quote, after training your team, empower them to act. If you are confident you have the right people in place, trust them to do the right thing at the right time. You may have 30 years of experience in the business, but it is your team that serves on the front lines and most often interacts with guests.Empower them to adapt and make decisions. I mean, that sequencing is just absolute. Yeah, we are getting into chapter 5 of Rahim B. Kanani's book, The Luxury of Attention. Chapter 5, Giving the Keys. It addresses one of the most critical structural challenges in literally any organization.And the failure almost always happens when leaders try to compress or reverse that sequence, right? Right. Because you cannot simply empower an employee into competence. It just doesn't work. The competence, which is built through rigorous training, has to exist before the authority can be safely handed over. We're basically going to extract the core insights from Kanani's work here.Yeah, focusing specifically on this massive and honestly often unspoken gap between empowerment as this corporate slogan and empowerment as an actual operational discipline. And it is a profound gap. I mean, the corporate world has adopted the vocabulary of empowerment almost universally. Everyone uses the word. Oh yeah, it's on every motivational poster. Exactly. But they have rarely adopted the structural sacrifices required to make that vocabulary real.You know, leaders want the benefits of an empowered team. They want the speed, the innovation, the guest satisfaction, right? Right. But they are deeply hesitant to actually hand over the control required to achieve those outcomes. Okay, I actually want to push back on that just a bit or at least explore why that hesitation exists. Because, you know, on paper, no leader actively wants to be a micromanager.Nobody wakes up wanting to micromanage, yeah. Right. And Kanani brings in a formulation from Aaron Kaupp that kind of highlights this perfectly. The one about ownership? Yeah, Kaupp argues, quote, never micromanage your team. They need to be empowered to take ownership and responsibility of their roles.This empowerment leads to mutual trust. And a team that trusts you will look out for the best interests of guests and the company, as if they were their own. Which sounds completely logical. Right. Like who would ever argue against mutual trust and ownership? Well, no one would argue against the sentiment.But Kanani actually identifies this as perhaps the most quoted, cited, and utterly misunderstood claim in luxury hospitality. Misunderstood how? It's misunderstood because of how it is typically executed in the field. So let's look at the reality on the ground. A leader might stand up in an all-staff meeting and, you know, deliver a highly motivational speech about empowerment. Right. The classic rallying cry.They tell the team to take ownership. They tell them to treat the business like it's their own. But then look at the structure those employees return to. What happens when they go back to their desks? Well, the leader is telling their team to take ownership of outcomes that the team has absolutely no structural authority to influence. Oh, I see.Yeah. They're told to ensure every guest leaves completely satisfied. But they are not given the authority to say remove a charge from a bill. Or change a room assignment. Exactly. Or alter a menu item without seeking a manager's permission first.Okay. I see the friction there. The directive is take ownership, but the actual operational reality is ask for permission. It's completely contradictory. It reminds me of, you know, the concept of a dual brake pedal in a driver's education car. Oh, that's a good analogy.Right. You put the student in the driver's seat. You tell them they are driving. You tell them to take ownership of the journey. But you keep your foot hovering over that brake pedal on the passenger side the entire time. Let's examine the mechanics of that friction though.Because what does that dual brake pedal actually do to the psychology of the person in the driver's seat? Well, it creates immense hesitation. I mean, the driver's nervous system knows with absolute certainty that they aren't really in control. They know you can stop them at any second. Right. They know that at any second their decision could be overridden.So they stop making fluid decisions. They become like hyper vigilant about what the person in the passenger seat wants them to do, rather than just focusing on the road ahead. Precisely. And in a workplace that translates to a deeply ineffective operational environment. A manager might praise a team member's initiative in the moment, but then pull them into the office later and second guess every single granular decision they made. Which has to be so demoralizing.It is. When an organization talks about empowerment publicly, but reverses empowered decisions privately, the employees learn very quickly to just stop making decisions. Because making a decision suddenly becomes a liability. Exactly. Like if they make a call and it gets overturned or criticized, they realize the safest route is just to ask the manager what to do in the first place. They revert to seeking permission for everything. And when an entire team reverts to seeking permission,the operation slows down to the exact speed of the manager's personal bandwidth. Which is always a bottleneck. Always. The leader becomes the bottleneck for every minor issue, which honestly defeats the entire purpose of even having a team. Okay, so if true empowerment isn't just telling people to take ownership as a slogan, what are the actual mechanics of it? Like what does it look like when a leader truly steps back? Well, Kanani breaks this down with an incredible level of precision.He argues that there are four highly specific types of authority that a leader absolutely must hand over. The four keys. The four keys. And the precision here is what makes this framework so valuable. It moves empowerment away from a general feeling, you know, and turns it into a structural transfer of distinct operational keys. Okay, let's unpack this and walk through these four keys. Because I think this is where we reallyseparate the slogan from the discipline. Let's do it. So the first key is decision authority. And this is defined basically as the right for a frontline employee to make a call without coming back to a manager for permission. Right. This is the operational freedom to execute the standard.It means the employee has the structural right to solve a problem the exact moment they identify it. Which sounds simple, but it's huge in practice. It's massive. Kanani provides very concrete examples of what this looks like. So consider a front desk agent. Okay.If a guest approaches the desk with a legitimate complaint about their suite, decision authority means that agent has the power to immediately move that guest to a completely different suite. Without asking anyone. Without having to page a manager to approve the room change. They just do it. Which completely changes the dynamic of that interaction. The agent isn't just a messenger anymore. They are the actual solution.Exactly. Kanani also uses the example of a line cook, which I thought was fascinating. If a line cook is plating a dish and realizes it just doesn't meet the executive chef's standard, decision authority means that cook can pull the plate. They can just stop it from going out. Right. They have the right to refuse to let it go out to the dining room, even in the middle of a super busy service.That example is vital because it requires the frontline employee to act with the judgment of the leader. Yeah, that takes a lot of trust. It does. And to support the necessity of this, Adrian Gray, who has extensive experience in luxury hotels, he provides a really compelling perspective here. What does he say? Well, his quote is, Once you clearly communicate your organization's objectives, empower your team to make decisions to achieve those results, particularly with respect to guests.As a leader, you need to support their ability to make decisions and allow them to improvise. Only then will they take ownership in the success of the company and pride in their work. I really want to focus on that word, improvise. Because in standard corporate environments, improvisation is almost always viewed as a risk, right? It's usually seen as a negative, yeah. It is seen as a deviation from the protocol.But Gray is framing improvisation as a positive, like a completely necessary component of ownership. Because improvisation in this context is not chaos. Improvisation is what happens when an employee intimately understands the final objective, but encounters a reality that a rigid flowchart just couldn't foresee. Right, because manuals can't cover everything. A manual cannot account for every single variation of a guest's problem. If the employee lacks decision authority, they cannot improvise.They can only tell the guest that the manual does not allow them to help. Which is the most frustrating answer a guest can hear. Absolutely. But if they have the authority to make the decision, they can adapt the solution to the specific nuance of the situation right in front of them. And Gray notes that the pride and the ownership are downstream of that ability to make the decision. I mean, you cannot take true pride in your work if your only job is to execute a script written by someone else.You're just a robot at that point. Right. The pride comes from the actual agency of solving the problem yourself. And that leads directly to the second key, which honestly often triggers the most anxiety for leaders. Oh, I bet I know where this is going. The second key is spending authority.Yes, this is where the commitment to empowerment is really tested financially. And Kanani highlights the practice established by Horst Schulze at Ritz Carlton, which is widely recognized as a benchmark in the industry. That's a legendary policy. It is. Under this policy, every single employee is allowed to spend up to $2,000 per guest per incident to resolve a problem. Per incident.Let that sink in. And they are authorized to do this completely without seeking management approval. Okay, I have to stop and unpack this because looking at this from a standard financial control perspective, it sounds deeply alarming. It terrifies most accounts. Yes. $2,000 per employee per incident without asking a manager for a leader managing a strict budget handing that kind of blank check of authority to hundreds of front line staff seems like an open invitation to massive financial loss.How does a property sustain that without just descending into total chaos? Well, it's a completely natural reaction to view that limit as a huge liability. But Kanani's analysis of this policy reframes the mathematics of the situation entirely. Okay, how so? First, it's important to understand that the specific number, the $2,000, is less important than the principle it actually represents. It's just a ceiling.Right. That figure was chosen because it is high enough to cover virtually any in property recovery scenario you could possibly imagine. Right. So it covers moving someone to a premium suite or, you know, absorbing the cost of an elaborate dinner, what the industry calls a comped meal, where the property simply eats the cost to rectify a bad experience. Exactly. It allows the employee to completely neutralize the problem.But your question about the financial risk is the core issue here. Like, why take the risk of an employee misusing those funds? Because here is the economic reality that luxury operators understand. The friction of an approval chain costs the property far, far more, in loss to guest loyalty than the isolated misuse of funds ever could. Okay, let's break down that friction. What actually happens when a guest has a problem and the employee doesn't have spending authority?All right, imagine a guest encounters a significant issue. Say, perhaps a major plumbing failure in their room. Ugh, the worst. Right. They are frustrated and they're inconvenienced. They approach the front desk.If the agent lacks spending authority, the agent has to say, I am so sorry. Let me fix this, but I need to page my manager to approve a room change and a complimentary dinner. And now the guest is just standing there waiting. Exactly. The guest is standing there stewing in their frustration for 10, 15, or even 20 minutes while the agent tries to track down a senior manager who is probably busy somewhere else on the property. And that delay basically becomes a second injury to the guest.It does. The delay communicates a very specific message. It tells the guest that the property prioritizes its internal bureaucratic controls over resolving the guest's immediate distress. Which destroys loyalty. But by providing that high financial limit directly to the frontline employee, you completely eliminate the friction. The problem is solved in three minutes instead of 30.Exactly. The employee can immediately apologize, hand over the keys to a new suite, and assure the guest that their dinner is covered. And the lifetime value of that loyal luxury guest, you know, someone who returns year after year because they know the property will always take care of them, that value completely dwarfs the occasional cost of a misjudged, comped bottle of wine. It's not even close. Spending authority is ultimately an efficiency mechanism designed to protect revenue, not waste it. That is such a fascinating way to look at a financial limit as a tool for speed and revenue protection.It flips the whole concept on its head. It really does. So we have decision authority and spending authority. The third key shifts away from operations and finances and moves into communication. The third key is language authority. Right. This is the right for an employee to speak to the guestin their own voice rather than reciting from a corporate script. And this is deeply tied to the concept of authenticity. Kanani's examples illustrate the difference really clearly here. What's a good example of that? Consider a chef who comes out to the dining room to describe a dish to a curious guest. If they have language authority, they describe the dish using their own words, you know, expressing their genuine passion for the ingredients in the process.They aren't just reciting a marketing blur written by a corporate office somewhere. Exactly. Or consider the role of a concierge. If a guest asks a concierge for a restaurant recommendation, language authority means the concierge is empowered to recommend a place they actually personally love. They get to share a genuine insight. Right. The alternative is a concierge who lacks this authority,who is forced to simply read off a preferred vendor list that the hotel has a preexisting arrangement with. Which everyone can always tell, by the way. Guests know when they're being sold to. Oh, absolutely. They can feel it. Kanani also references Will Guidara's practice at Eleven Madison Park to highlight how this authority extends to gestures, not just words.Oh, right. Guidara allowed the floor staff the latitude to extend small unscripted gestures to surprise the guests. It wasn't planned by management. Right. It was the staff reading the table. But what is the underlying logic against scripts?I mean, from a management perspective, a script guarantees that the employee won't say the wrong thing. It protects the brand's tone. Why is Kanani arguing that leaders must hand over language authority? Because a script can only establish a baseline. It is fundamentally a defensive mechanism. Defensive?Yeah. A script absolutely prevents terrible offensive service, sure. But it also absolutely guarantees that the service will never be extraordinary. Oh, I love that point. Scripted hospitality cannot, by its very nature, surprise a guest. It cannot adapt to the unique emotional state of the person standing in front of the employee.A script makes the guest feel processed. Like, they know they are hearing the exact same phrasing that the previous 100 guests heard that day. Right. Unscripted moments, you know, the genuine conversation, the personalized recommendation, the unexpected gesture, those are the only things guests actually remember years later. Those moments create the emotional connection to the brand. And those moments are structurally impossible unless the staff has the language authority to step outside the script and just interact as human beings.Which brings us to the fourth key. And, you know, from an ego perspective, this might be the most demanding key for a leader to hand over. It's definitely the toughest for a lot of managers. The fourth key is escalation authority. Escalation authority is the right to interrupt a senior person. Including the leader of the organization.Yes. When something goes wrong, the team must have the structural authority to pull the emergency brake and stop the operation, regardless of who they have to interrupt to do it. Even if it's the very top boss. Kanani gives the example of a line cook stopping the executive chef during peak service because they spot a piece of fish that just isn't right. Which is terrifying for a junior cook to do. Oh, incredibly terrifying.Or a night auditor, you know, the person who manages the property's financial reconciliation and operations during the overnight hours, waking up the general manager at three in the morning because a specific security situation demands their immediate attention. Right. And Kanani's exploration of the psychology behind this authority is crucial. How so? Because you can grant escalation authority on paper. You can write it into the employee handbook.You can tell your staff, you know, my door is always open, interrupt me anytime. Everyone says that. Everyone says it. But that authority is sustained strictly by the senior leader's reaction in the actual moment of interruption. Ah, it comes down to gratitude versus annoyance. Exactly.When that junior line cook stops the executive chef in the middle of a chaotic service, how does the chef react? Does the chef sigh, roll their eyes, and snap at the cook for breaking their concentration? Or do they stop, examine the issue, and express gratitude for the catch? Right. And Kanani notes that a team will learn within exactly three interruptions. Whether this escalation authority is real, or if it is purely rhetorical.Just three times. Because humans are highly attuned to social punishment. If a leader punishes the interruption with their annoyance, and I mean, even just a subtle change in tone or body language, the team learns that the written policy is the complete lie. They will learn that interrupting the leader is unsafe. Yes. So they will never interrupt again.And the substandard product will go out to the guest, or the operational crisis will just compound, because the team decided it was safer to let it fail than to face the leader's irritation. That is so true. And this leads to Kanani's synthesis of this entire framework, which he calls the key chain concept. This is a great visual. It is. To truly empower a team, a leader must provide all four forms of authority.Decision, spending, language, and escalation. If a leader provides all four, they have quote, given the keys. But the reality is that most operations attempt to compromise. They cherry pick. Exactly. Leader might provide language authority, allowing the staff to speak freely, but absolutely refuse to hand over spending or decision authority.And Kanani argues that in this scenario, the leader has merely handed over a key chain that mostly does not open the doors the team actually needs to walk through. It is a heavy key chain with no useful keys on it. Right. The organization can jingle it around and tell everyone how empowered they are. But when an actual problem arises, the team is still locked out of solving it. And Kanani points out that leaders withhold these keys out of an unspoken anxiety.Fear of what happens if they let go. Right. They are anxious about losing control, about financial waste, about the brand's image. Kanani suggests that the honest move for a leader is to clearly identify that anxiety. You have to own it. If you are terrified to give spending authority, you must admit it to yourself.Once you acknowledge the fear, you have two choices. You either build the intensive training programs required to resolve your anxiety, or you must accept the fact that you are choosing to run a slower, more brittle operation. Because pretending to give authority while reserving the right to constantly reverse it produces the worst possible environment. It's worth it just being an honest dictator. Seriously. So let's address that leader.The leader who recognizes they are holding onto the keys because they are anxious about what will happen if they let go. How do they bridge the gap? It all comes down to what happens before the keys are handed over. Right. How do they build the confidence to hand over decision, spending, language, and escalation authority? This brings us to Kanani's severe qualifier regarding preparation.It is one of the most important concepts in the chapter. Kanani writes, quote, Empowerment without preparation is abandonment. Empowerment without preparation is abandonment. That completely reframes the act of delegation. It isn't just about letting go. It's about what you do before you let go.Because if you simply throw authority at an employee who has not been rigorously prepared to handle it, you are not empowering them. You are just setting them up to fail. You are setting them up for an inevitable failure and you are abandoning them to face the consequences of that failure completely alone. To prevent this scenario, Kanani outlines specific non-negotiable components of preparation that must occur before the keys are handed over. Let's dig into those. Yeah.The first component is training. But we need to define what training means in this context. Because it goes far beyond an orientation manual. It's not just showing them where the bathrooms are. Right. Pedro Dias provides a comprehensive view of this.His exact quote is, Through continuous learning, training, coaching and mentoring, an empowered workforce can be critical to success. Continuous being the operative word. Yes. He notes that empowering staff to make decisions eliminates the need to escalate issues to higher management in a time-consuming, unnecessary way. This will create a much more streamlined and effective operation. The training is what actually makes the transfer of authority safe.But this type of training is not just about procedural knowledge, is it? No, not at all. It is about training the employee's judgment. It's about teaching them how to think through a problem the way the leader would think through it. Kanani brings in a tactical approach from Kai Speth to illustrate exactly how this judgment is cultivated in real time, which I love. Speth outlines a very specific response mechanism for leaders.Right. He explains, quote, One of the most important ways to engage and empower your colleagues is to let them problem solve. Oftentimes, you will be expected to resolve an issue that was voiced by your team, but the real solution is to push back the challenge. How would you solve it? Empower your team to not only identify challenges, but to also propose solutions. When an issue is resolved in this way, instead of from top down, there's a much higher chance of success.Let's examine the daily friction of this tactic, though, because it's hard. It is. An employee approaches the leader with an operational problem. And the fastest, easiest, and most immediately satisfying thing for the leader to do is simply provide the answer. It takes three seconds. It takes three seconds.And the leader gets to feel competent and decisive. They feel like the boss. But Speth is arguing that the leader must resist that urge. They must absorb the time penalty of asking, how would you solve it? Which requires the leader to invest significantly more time in the short term. Instead of a three-second answer, it becomes a five-minute coaching session.Who has five minutes during a dinner rush? Right. Kanani points out the compounding interest of those five minutes. The first time the leader asks, how would you solve it? The employee might freeze. They might not have an answer at all.Exactly. The second time, they might have a half-formed idea. But by the third or fourth time, the dynamic fundamentally shifts. The employee stops bringing the leader raw problems. Yes. They start arriving with proposed solutions.And eventually, they stop bringing the easy questions altogether because they already know the leader trusts their judgment to solve it independently. The leader trades short-term time for long-term operational speed. It's an investment. Okay. So, training and coaching judgment is the first component of preparation. The second component Kanani emphasizes is clear boundaries.Now, on the surface, this sounds contradictory. Right. Doesn't a boundary inherently restrict empowerment? Yeah, that's what you'd think. It is a common misconception, but the exact opposite is true. Boundaries would actually make empowerment real and operable.Because it gives them a safe zone. Kanani explains the psychology behind this. If a leader simply tells an employee, use your best judgment, but fails to provide a ceiling or a framework, the employee's left guessing. They have no idea where the invisible line is. You know, the line that will get them reprimanded or fired. And when human beings don't know where the danger line is, they become extremely cautious.Because they don't know the boundaries, they default to the most conservative interpretation of their authority. Which practically means they exercise no judgment at all. They freeze. But consider Horst Schulze's policy again. You have up to $2,000 to solve a problem. Anything beyond that, you must escalate to management.That is a definitive, clear boundary. The employee knows exactly what they can do safely and exactly when they need to stop. Kanani argues the boundaries are protective, not restrictive. They create the safe operational sandbox within which true empowerment can actually function without fear. Which leads to the third component of preparation, the coaching posture. Like how does a leader need to carry themselves day to day to sustain this?Kanani explores this through the perspective of Emma Bengtsson, the head chef at Aquavit. She articulates a very delicate balance. Bengtsson explains, quote, As a leader, a big part of how I work to create an open and collaborative environment at Aquavit is by being patient. There are definitely days when that's not easy, but losing your temper is more counterproductive than taking the time to nurture someone. That is the first half of the posture. The absolute patience required to receive the question.She adds, quote, Another crucial aspect of exercising patience is being open to any and all questions, no matter how silly. Letting anyone on my team ask anything allows me to find ways to help them learn in a way that works best for them. So the leader must create an environment where the team is completely safe to expose their ignorance. But if a leader only possesses that first half, they create a dysfunction, don't they? Kanani analyzes this deeply. If a leader has endless patience and constantly answers every single question, they inadvertently create a highly dependent team.The team feels very safe to ask questions, but they never develop the independence to act on their own. They basically use the leader's patience as a crutch. Which is why Bengtsson immediately introduces the second half of the posture. She states, quote, On the flip side, as head chef, knowing when to ask your team questions and when to let them solve problems for themselves is equally important. The feeling of accomplishment for being able to achieve something on your own is one of the greatest tools of motivation. Right.Kanani points out the necessity of holding both postures simultaneously. It's a tight rope walk. It is. The leader needs the patience to receive the question without anger, but the restraint to redirect the question back to the employee just as Speth suggested. If the leader only has the second half, like constantly forcing the team to solve things independently without creating the psychological safety to ask questions first, they create a terrified team that neither asks for help nor acts independently. Which is the worst of both worlds.The preparation demands a massive emotional investment from the leader. And if a leader goes through all of this and still feels their team simply cannot handle the responsibility, Kanani points to a deeper systemic issue here. He references Emmanuel Stroobant. Yes, who states, quote, For me, the right attitude will always trump skill. Skills can be taught. Kanani observes that a leader who is terrified to empower their team, assuming they have provided the training and set the boundaries, does not actually have an empowerment problem.They have a hiring problem. Exactly. Empowerment cannot fix a team that was selected based on the wrong criteria. It will only expose the bad hiring decisions faster. The logic is brutal, but clear. If you do not trust the employee enough to hand in the keys after they are trained, why were they allowed into the organization in the first place?It's a tough pill for leaders to swallow. It is. I want to move to what I think is the most critical juncture in this entire framework. Because even if an organization hires perfectly, trains endlessly, sets clear boundaries and maintains the perfect coaching posture, human beings are still human beings. Mistakes are always inevitable. Right.Here's where it gets really interesting. What happens when an empowered employee operating entirely within their boundaries makes a decision that is just completely wrong? They use their decision authority, they utilize their spending authority, and the outcome is a total failure. This is the crucible. Kanani frames this as the recovery test. This specific moment is where the leader's actual internal belief in empowerment is put on trial.And to set the philosophical stakes for this moment, Kanani highlights Michael Ziemer's approach. Ziemer states, quote, As a leader, you need to trust and empower your employees to make decisions, good ones and bad ones. The only way they will learn and grow is by doing. I would rather them ask me for forgiveness than for permission. You learn from your mistakes. And that's exactly what I did.I would rather them ask me for forgiveness than for permission. It is a really powerful standard. But Kanani asks us to examine the operational reality of what happens when the employee actually does ask for forgiveness. Right. The empowered call went wrong. Resources were wasted or a situation was escalated unnecessarily.The employee brings the failure to the leader. Kanani outlines three distinct responses a leader can choose in that exact moment. And the choice dictates the entire future of the organization's culture. Let's look at response number one. Okay. The leader revokes the authority.The leader gets angry, tells the employee they clearly lack the judgment for the responsibility and permanently takes the keys away. The structural impact of that response has to be devastating. It sends a shockwave through the entire team, not just the individual employee. The unspoken message becomes empowerment is a trap. Right. If you use the authority and succeed, everything is fine.But if you use it and fail, you are publicly punished and stripped of your agency. So the logical conclusion for every observing employee is to never use the authority again. Okay. So response number two is much more subtle. And Kanani calls it performing forgiveness while tightening the leash. Yes. This happens when the leader says,it's okay. I forgive you. Don't worry about the mistake. But just check with me next time before you do something like that. That sounds so reasonable on the surface though. With the second response, the leader gets to feel magnanimous.They view themselves as a forgiving, progressive manager. But operationally, by adding the phrase, just check with me next time, they have completely revoked the decision authority. Oh wow. They have reinstalled the dual brake pedal. Precisely. Check with me next time is the literal definition of returning to micromanagement.So sneaky. Kanani points out that whether a leader chooses response one or response two, the operational outcome is identical. Within three months, the entire team will quietly revert to asking for permission for absolutely everything. The culture of empowerment is effectively dead. So to maintain the culture, the leader must choose response number three. Absorb the cost, teach, and reaffirm the authority.So the failure becomes a private teaching moment, not a public revocation. Yes. The leader must absorb the financial or operational cost of the mistake themselves. They use the moment to coach the employee, dissecting the decision process to understand why the call was wrong. And then crucially, the leader must explicitly tell the employee, you still have the authority. Next time, use this new insight, but make the call.That is the only response that ensures the empowerment actually survives the failure. It requires immense emotional discipline to execute that third response, especially when the mistake was highly visible or costly. Because the leader's natural instinct is self-preservation and control. Right. Kanani recognizes how difficult this is, which leads him to offer what he calls the cleanest diagnostic tool for determining whether true empowerment exists within a culture. He calls it the pronoun discipline.It is an incredibly elegant observation of leadership behavior. Think about a leader addressing their team, or maybe explaining a situation to upper management. If the leader consistently uses the phrase, we got that right when a project succeeds, but shifts to they got that wrong when the frontline team makes a mistake, what is actually happening structurally? Well, structurally, the leader is signaling that credit travels up the hierarchy to the leader, and blame travels down the hierarchy to the team. It is a fundamental defense mechanism. The leader is associating themselves with the success, but distancing themselves from the failure.But Kanani asks us to explore the exact inverse of that dynamic. What happens if a leader rigorously disciplines themselves to say, they got that right when the team succeeds, and we got that wrong when the team fails? The environment that creates is transformative. When the leader says they got that right, they are actively pushing the recognition and the credit down to the frontline employees who executed the work. They're reinforcing the team's competence. And when the leader says we got that wrong, right, when the leader says we got that wrong, they are absorbing the blow.They are standing between their team and the failure. The leader is acknowledging that they are responsible for the system, the training, and the environment that produced the error. They are sharing the burden of the failure. Kanani points out that this pronoun discipline costs the leader absolutely nothing in terms of capital. It requires zero budget. It is the ultimate acid test for whether the four forms of authority have actually been handed over.Because a leader cannot honestly say we got that wrong if they are secretly furious that the team didn't ask for permission first. The discipline forces alignment. It forces a profound level of emotional regulation. The leader must suppress their ego. Which aligns perfectly with the philosophy of Jonnie Boer. Boer states, quote, 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.Yelling does not help any situation. Yelling does not help any situation. It sounds so basic, but maintaining that calm, that bird's eye view, when an operational failure is occurring right in front of you, is a massive discipline. It really is. So if we look at this entire framework, if a leader grants the four keys, invests heavily in preparation, successfully navigates the recovery test, and masters the pronoun discipline, we have to ask what is the actual tangible payoff for the organization? Why endure this level of psychological and operational rigor?Kanani answers this by reframing empowerment entirely. It is not a feel good human resources initiative. It's not just to make people happy. No, it is a mechanism of competitive separation. It is an economic strategy. Yes, it is the fundamental mechanism of efficiency in a service environment.Kanani breaks it down into raw operational time. Okay. Consider our earlier example. An empowered property resolves a guest's immediate problem in three minutes. An unempowered property bogged down in approval chains and permission seeking takes 20 minutes to resolve the exact same problem. The difference between three minutes and 20 minutes might not seem massive in isolation.But you have to scale that difference. Multiply that time delta across hundreds of minor interactions a day and thousands of interactions a week. Wow. Over the course of a year, the empowered operation accumulates thousands of small, almost invisible wins. The unempowered operation accumulates thousands of small, exhausting losses. The friction just drains the organization.Empowerment is the property's most reliable mechanism for moving from satisfactory service to memorable service, consistently and at scale. Mahmoud Skaf captures the dual nature of this strategy perfectly. Skaf argues, quote, In order to be successful in this business, you need to unleash the potential of your team by empowering them and giving them the space to deliver. We encourage the ladies and gentlemen of the hotel to engage our guests if the opportunity presents itself and to make decisions, craft special moments and resolve customer issues in any way or form they chose to. This is as much a service decision as it is a business decision. As much a service decision as it is a business decision.That encapsulates Kanani's argument. Unleashing the team is not an act of philanthropy. It is how you execute the thousands of micro adjustments that define a world-class operation. And to achieve that, Kanani notes that leaders must rethink the very shape of their organizational structure, which means challenging the traditional hierarchical pyramid. José Andrés provides a stark structural philosophy on this. Yes. Andrés states, quote,I am always hiring people who are smarter than me, those who could be my boss. The other key to success is to flatten the organizational structure. Running a company as a pyramid, where messages from the very top get filtered down to all the people at the bottom is not an effective system. If there is an open line of communication all around the company, the best ideas will surface no matter who came up with them. The traditional pyramid assumes that all the intelligence strategy and judgment resides at the top, and the bottom merely executes orders. But in a hospitality environment, the bottom of the pyramid, the front line, is where the guest actually experiences the reality of the brand.Right. If a leader does not flatten that structure and empower the front line, the strategic intelligence at the top is completely useless because it cannot reach the guest in time. And there is a paradox here. Handing over this power does not diminish the leader's authority. It actually strengthens their strategic position. Ralph Radtke connects empowerment directly to the leader's own confidence.Ralph Radtke notes, quote, one of the most important aspects of leadership is to trust your team to make the right decisions and empower them to take action as necessary. Of course, this is tied to hiring the right people for the right job. But when the right people are in place and you trust them to execute and deliver, you as a general manager can have more confidence in your own decisions. Kanani observes that this reverses the standard assumption. Most leaders assume that controlling every minor detail gives them confidence. But Ralph Radtke pointing out that having a team you trust to execute independently is what actually frees the leader to have confidence in their own macro level decisions.Exactly, because their bandwidth is no longer consumed by operational minutia. This requirement for independence is even more pronounced in unique operational models. Kanani looks at Kevin Fehling, who operates as a solo entrepreneur. Fehling does not have the massive safety net of a global hotel group or corporate investors. So how does empowerment work for him? Kanani points out that this extreme structural independence sharpens the empowerment calculation immensely.For a solo operator like Fehling, empowerment isn't a mandate sent down from a corporate office. It is literally the only way the work can be completed. His team must handle the daily operational decisions independently so that he can concentrate on the specific elements that only he can execute. Right, like the menu direction, the ingredient sourcing, and the overarching shape of the guest experience. The operation fails if he becomes the bottleneck. So what does this all mean for the day-to-day operation?This brings us to a harsh logistical reality that applies to operations of any size. Kanani highlights a simple constraint of time and physics. Time is always the enemy. It is. No matter how dedicated or skilled the leader is, they are only physically present on the floor directly observing the work for a limited portion of the day. Right, perhaps two or three hours during peak operational times.So the fundamental question becomes, who is holding the operational standard for the other 21 hours of the day? It cannot be the leader. It has to be the senior team. The layer of management directly below the leader. The assistant general managers, the department heads, the chefs de cuisine who run the kitchen's daily service when the executive chef is focused elsewhere. Kanani identifies this as a critical vulnerability for most properties.An organization with a strong, highly empowered senior tier will maintain the standard on every single shift, regardless of whether the primary leader is sleeping, traveling, or locked in a meeting. Conversely, a property with a thin or unempowered senior tier only maintains its standard when the primary leader is physically in the building to enforce it. The moment the leader goes home, the operational standard drops. Kanani argues that forming this empowered senior tier should not be viewed as a midterm goal. It must be one of the very first three priorities for any leader building an operation. Because without that empowered senior tier, any broader empowerment efforts will hit a ceiling immediately.The leaders simply cannot scale their own attention. So to pull all of these concepts together and ensure that empowerment actually takes root and survives under pressure, Kanani provides a very rigid framework to close out the chapter. It is called the Empowerment Preparation Checklist. And Kanani stresses that the exact chronological order of these steps matters immensely. Skipping a step or executing them out of sequence means the empowerment will fail when tested by an actual operational crisis. Let's walk through the sequence.The first step is authority defined. A leader must be explicit about which of the four keys they are handing over. Is it decision, spending, language, or escalation? Ambiguity here creates immediate paralysis. The second step is boundaries clear. The leader must define the operational sandbox.And as Kanani insists, these boundaries must be viewed as protective, not restrictive. They tell the employee exactly how far they can maneuver before they must seek assistance. The third step is training complete. This incorporates the continuous learning discussed by Pedro Dias and the pushback coaching tactic from Kai Speth. The leader must ensure the employee has the judgment to handle the authority defined in step one. To empower without the step is abandonment.The fourth step is recovery rehearsed. What happens when the empowered decision goes wrong? The leader must decide in advance that a mistake will be a private teaching moment, not a public revocation of authority. The leader must rehearse their own emotional response before the crisis occurs. And the final step is recognition genuine. Kanani notes this is what completes the operational loop.When an employee utilizes their authority correctly within the established boundaries, after completing the training, the leader must recognize it. Recognition reinforces the precise behavior the organization needs to scale. It brings us back to the central tension of the chapter. There is a massive structural gulf between empowerment as a feel good slogan and empowerment as a rigorous, unforgiving operational discipline. The leader's Kanani highlights, Pichel, Schulze, Speth, Bengtsson. They operate the discipline.They do not just rely on the vocabulary. The slogan in their organizations is merely what would be left over if they ever stop doing the intense daily work of maintaining that discipline. Right. So as you analyze your own approach to leadership, or examine the structure of your own workplace, you have to ask a demanding question. Are you actually handing over the keys? Or are you just providing a shiny keychain that doesn't open any doors the team actually needs to walk through?It is a confronting standard. And I would offer a final thought to consider regarding the mechanics of leadership. We have discussed empowerment extensively as an allocation of authority, resources, and time. Sure. But ultimately Kanani's framework reveals that empowerment is an allocation of attention. Your attention is the most finite and valuable resource you possess as a leader.Every single minor operational decision you insist on making yourself, every minor expense you demand to approve, is actively stealing your attention away from the few highly complex strategic problems that truly require your unique perspective. Exactly. By refusing to empower your team, you are not just restricting their growth. You are actively degrading your own capacity to lead. The dual brake pedal exhausts the driver, but it also traps the passenger. This concludes our analysis of chapter 5.Next time, we shift our focus entirely. Episode 6, The Creative Act. We'll see you then.

In this episode

Transcript

Read what the episode discusses