A culture you can inspect before opening
Before the first order, Michel Falcon checks the takeout bags, the napkins and the beverage cans. Bags should be replenished. Napkins should be full. Can labels should face out. These are ordinary restaurant details, which makes them useful evidence: someone either completed the closing checklist or left the next team to catch up.
In his ChatGTM conversation with Michael Beck and Chad Horn, the founder of Brasa Peruvian Kitchen explains why those details belong in a discussion about people-first leadership. He describes an exchange of commitments. The employer invests in the team, and the team follows through on the work it has agreed to do. When either side repeatedly falls short, the relationship becomes harder to sustain.
Falcon calls Brasa's culture friendly and high performance. Both expectations apply at the same time. A warm personality cannot excuse unfinished work indefinitely; strong performance cannot excuse treating people badly. For leaders trying to make culture more concrete, that combination offers something far more useful than another adjective for the careers page.
Hiring is the first operating decision
Falcon traces much of his thinking to his time at 1-800-GOT-JUNK?, where he observed the connection between employee experience and business performance. At Brasa, that thinking appears early in the candidate experience. He describes a lengthy career description, videos, an application and a potential group interview. Candidates get a meaningful picture of the business before either side makes a commitment.
Some applicants leave the process. Falcon accepts that outcome. His aim is to find people willing to invest effort in understanding an opportunity that also asks the employer to invest in them. In the episode, he reports paying above comparable industry roles and attributes Brasa's low turnover in part to the effort invested before hiring. Those are his account of Brasa's experience, rather than a forecast for every restaurant that adopts a longer application.
Length alone would be a poor measure of a hiring process. The useful question for another operator is whether each step reveals something relevant. Does the candidate understand the standards? Can they explain what good service looks like? Have they seen enough of the actual role to make an informed choice? Adding friction without adding clarity would defeat the purpose.
One question Falcon uses asks candidates to describe a company that gives them excellent service. He listens for detail. Someone who notices the mechanics of a good experience has something specific to draw on when delivering one. It also gives an interviewer a better conversation than a rehearsed promise to be a team player.
The leader answers the difficult question first
Another interview question asks what unbecoming quality the company will discover about the candidate during the first ninety days. Falcon answers it himself before asking the other person to respond. He describes his own impatience and visible frustration when documented work has not been completed correctly.
That sequence changes what the question asks of a candidate. The leader has already admitted that the working relationship will include imperfections. There is room to discuss them plainly. An interview still cannot remove all uncertainty, and Falcon acknowledges that hiring remains an informed guess. The point is to improve the information available to both sides.
His closing-checklist example makes the accountability portion equally plain. Expectations have been documented, the employer has made a commitment, and the work still needs to happen. Kindness continues to matter when addressing a failure, including when employment ends. It does not make the expectation disappear.
A practical application is to examine where managers currently rely on silent expectations. If a standard matters enough to create frustration, it deserves to be taught, documented and checked consistently. Otherwise, a conversation about performance can become a guessing game about what the manager meant.
Give generosity an operating context
Falcon applies the same relationship thinking to customers. He describes avoiding small charges that leave a guest feeling nickel-and-dimed, and recounts accommodating a customer who had forgotten a wallet. His reasoning considers the longer relationship, including the possibility of future catering business, alongside the immediate transaction.
That does not establish that every exception will pay for itself. Falcon acknowledges the possibility of being disappointed. He is explaining the tradeoff he chooses to make and the scale of the risk he is willing to absorb. Another restaurant needs its own understanding of food cost, employee discretion and appropriate limits.
The episode closes the loop with customer journey mapping. Falcon argues that hospitality needs deliberate design across the experience, including touchpoints a leader may overlook. His recommendation is to start where the greatest pain exists, rather than wait until every interaction can be perfected.
For an operating team, that could mean following one visit from arrival through payment and asking where an employee lacks the authority, information or preparation to help. Choose one failure, give someone responsibility for improving it, and return to see whether the experience changed. The culture becomes visible in that follow-through, just as it does in the bags waiting for the next morning's orders.
