The Literature Times: What inspired you to write Behind the Pass, and what gap did you feel existed in culinary literature?
Author:
The inspiration came from years of watching talented chefs struggle not because of a lack of cooking skill, but because no one had ever taught them how a kitchen actually functions as an organisation. Most culinary literature celebrates recipes, techniques, and the creative side of cooking. Very little addresses the operational reality — the pre-service planning, the communication breakdowns during peak hours, the pressure a Chef de Partie faces when a section collapses during a full house. I wanted to write something honest. Something that a young commis chef or a newly promoted sous chef could pick up and immediately recognise their own kitchen in. The gap was practical leadership and systems — written from the inside, not from a business school perspective.
The Literature Times: You emphasize that “systems are more important than talent.” Can you share a real-life example where this principle changed a kitchen’s performance?
Author:
During a pre-opening for a luxury resort property, we had a reasonably talented team but no established systems. The first few weeks of soft opening were chaotic — tickets were lost, communication between sections was reactive, and service times were inconsistent. We paused, mapped out every touchpoint from order receipt to plate dispatch, and built structured briefing formats, prep checklists, and section handover protocols. Within three weeks, service times improved by nearly 40 percent and the number of re-fires dropped significantly. The team hadn’t changed. The talent was the same. What changed was that everyone now knew exactly what to do, when to do it, and who to inform when something went wrong. The system carried the shift — not individual brilliance.
The Literature Times: In your experience, what is the most common leadership mistake that causes service collapse?
Author:
The absence of the pre-service briefing. It sounds simple, but this is where most collapses begin. When a leader assumes the team is ready without verification — without confirming cover counts, section readiness, potential allergy alerts, or any last-minute changes — they are walking into service with blind spots. The second mistake, closely linked, is leaders who manage by reaction rather than anticipation. A strong kitchen leader reads the shift before it reads you. They’ve already identified where pressure points will emerge. The chef who waits for something to go wrong before intervening will always be one step behind the crisis.
The Literature Times: How can young chefs balance skill development with the need for speed in high-pressure kitchens?
Author:
They need to separate their learning environments from their execution environments. During service, your job is to perform to the standard already practised — this is not the moment to experiment or figure things out. The skill development happens in prep, in early morning practice, in deliberate repetition outside peak hours. I always tell young chefs: slow down to speed up. If you spend fifteen minutes each morning perfecting your mise en place setup, you will gain back thirty during service. Discipline in the quiet moments creates composure in the loud ones. Young chefs who try to improve everything at once during service usually improve nothing.
The Literature Times: You mention that communication is a system, not a personality trait. How can kitchens practically implement this idea?
Author:
By standardising the language and the moments of communication rather than relying on each individual’s personality to fill that gap. In practice, this means: structured pre-shift briefings with a fixed format, defined call-and-confirm protocols between sections, a clear system for flagging problems up the line without fear, and post-service debriefs that are brief and factual rather than emotional. When communication is designed into the workflow — when it is expected and structured — it no longer depends on whether your sous chef is naturally expressive or your grill cook is introverted. The system asks for the information, and the team delivers it as part of their role.
The Literature Times: What are some key elements of effective prep planning that most kitchens overlook?
Author:
Three things stand out consistently. First, most kitchens plan prep around the recipe rather than around the service flow — they think about what to make, not when it will be needed and in what quantity. Second, there is often no real accountability for prep completion. Tasks are assigned but not tracked, and gaps are discovered at the worst possible moment — during service. Third, kitchens rarely factor in buffer time for raw material inconsistencies, equipment delays, or staff absences. Effective prep planning is not a list of tasks. It is a sequenced, time-allocated, accountability-driven schedule that anticipates variables and builds in contingency.
The Literature Times: How should chefs train their teams to handle unpredictable factors like inconsistent raw materials?
Author:
By training for decision-making, not just execution. Most kitchen training is technique-focused — here is how you butcher this, here is how you reduce that. But when a delivery of fish arrives below standard at 11 AM and service starts at noon, you need a chef who can assess, decide, and adapt — not one who freezes because nothing in their training covered that scenario. We run what I call “disruption drills” — controlled situations where the team has to solve a problem with a missing ingredient, a substitution, or a quality issue. Over time, this builds a calm, practical problem-solving reflex. The goal is not to eliminate unpredictability — that is impossible in a kitchen. The goal is to make your team comfortable inside it.
The Literature Times: In Indian kitchens, hierarchy often limits open communication. How can leaders overcome this challenge?
Author:
This is one of the most important cultural conversations we need to have as an industry. The hierarchy in Indian kitchens carries a great deal of value — respect for experience, discipline, clear chain of command. But when hierarchy becomes a barrier to information flowing upward, it becomes a liability. A junior cook who notices something wrong but doesn’t feel safe saying so is a risk the kitchen cannot afford. The solution is not to dismantle the hierarchy but to create structured and safe channels within it. A daily feedback moment in the debrief. An open question during briefing — “what is one thing you needed today that you didn’t have?” These small, repeated acts signal to the team that information is valued, not penalised. The chef who hears hard truths early will always outperform the one who hears them too late.
The Literature Times: What advice would you give to restaurant owners who focus more on menu creativity than operational systems?
Author:
The menu is the promise. The operation is what keeps that promise, night after night. I have seen exceptional menus fail because the kitchen behind them could not execute consistently under pressure. Creativity without a delivery system is a concept, not a restaurant. My advice is practical: before your next menu redesign, audit your kitchen’s execution rate on the current one. How many dishes are sent back? How many re-fires happen during peak service? Where does consistency break down? Fix that first. A focused menu that is executed flawlessly will always outperform an ambitious menu that is executed poorly. Guests return for consistency and experience — not just novelty.
The Literature Times: If you had to summarize the most important lesson from this book in one line, what would it be?
Author:
“Structure is not a constraint — it is the foundation that sets you free. When your kitchen runs on disciplined systems, consistent processes, and a team that understands their role at every moment of the shift, excellence stops being an accident and starts being a standard. That is the real lesson behind this book: build the structure, and the results will follow — every service, every day, without exception.”
