The Conversation We Have with Every New Hire on Day One
The average tenure of someone working at Tuk Tuk is over five years.
We're not telling you that to brag. We're telling you because the reason is not what you'd guess. It's not the pay (we pay market). It's not the schedule (we run a normal restaurant). It's not the food (we feed staff a meal but so does everyone). It's not the family-style culture (every indie says they have one).
The reason is a 30-minute conversation we have with every new hire on day one. Same conversation, every time, for years.
We want to walk you through it because most restaurant retention advice is the wrong altitude. It's either too abstract ("invest in your people") or too tactical ("use a stay interview at the 90-day mark"). The conversation we run is concrete, takes half an hour, costs nothing, and changes the math of who walks out the door in month four.
The conversation, in five questions
It happens on day one, usually the morning before the first lunch shift. New hire, us, two cups of tea, a corner booth before service. Not in the office. Not on a clipboard. Just two adults talking.
These are the five questions, in order. The wording varies, the order doesn't.
1. "What was the last job you left, and why?"
Not "tell us about your work history." That's the interview. This is different. This is one specific question about the most recent exit.
The answers tell you almost everything. Someone who says "the schedule kept changing and we have a kid" is telling you what they need from you. Someone who says "the manager was awful" is telling you the criteria they use to evaluate managers, which means they're going to evaluate yours that way too. Someone who says "we just wanted something different" without elaborating is telling you they don't have language for what they need yet, and you'll figure that out together.
The wrong move is to evaluate the answer. The right move is to listen for what the person is asking you for, implicitly, before they know how to ask for it explicitly.
2. "What's something you'd want us to know that won't show up on the schedule?"
This is the most important question. It's the one that catches the kid in second grade with a pickup at 2:45, the night class on Thursdays, the parent in hospice, the recovery meeting on Mondays at 7am, the partner who works opposite shifts and means Sundays are sacred.
Most restaurant operators discover these things in month three when the person no-shows or asks for a Thursday off and we act surprised. Asking on day one means you build the schedule around the actual life from week one, not after a no-show breaks the trust.
You don't have to honor every constraint. Some you can't. But you have to know.
3. "If something at Tuk Tuk pisses you off, who do you tell?"
The answer is "you, the floor manager, the chef." But the question matters more than the answer. We're telling them, on day one, that there is a path for "this is not working." we're naming it.
Most staff at most restaurants don't quit because of a thing. They quit because the thing kept happening and there was no path to say so. The 30-second declaration on day one — "if something pisses you off, here's who you tell, and the answer will not be 'deal with it'" — is the second-biggest retention move in the conversation. The first is question 5.
4. "What does this job need to do for you, in the next year?"
Not "what are your career goals." That sounds like a corporate HR script and it pulls performative answers.
The honest version is: what does this job need to be FOR YOU, for it to be working a year from now? Pay X dollars? Cover health insurance? Let you take a class? Be flexible enough to do another gig? Be the path to your own restaurant in five years? Be a steady thing while you figure out what's next?
There are no wrong answers. The right answer is the one that's true for them. Once we know it, we can build toward it. If it's "we want to be a chef in five years," we know to give them line time and recipe input. If it's "we need this to pay rent and not stress us out," we know to keep their schedule predictable and not throw curve balls.
If you don't know what the job needs to do for them, you can't be intentional about whether you're delivering on it. And when month nine comes and they're walking, you'll be confused.
5. "What do you want to be paid in a year if this is going great?"
This is the conversation almost no operator we've talked to is willing to have on day one. It's also the question that does the heaviest retention work.
The honest version is: we set wages here based on what the position is worth, but we want to know what you're aiming for, because we can either build toward it together or we can pretend we're not having that conversation and have it implicitly when you start interviewing elsewhere.
The answer is usually a number 20–30% above their starting wage. That's a real, manageable target. We can build toward it through skill expansion (cross-training to a higher-paid station), shift premium (taking weekend doubles), or formal raises tied to milestones (90-day, 6-month, 1-year).
We're not promising the number. We're acknowledging that the number exists, that we both know it exists, and that we'd rather work on it together than pretend it's not the thing they're going to think about every time they look at their paycheck.
Why this works
Three reasons, and they compound.
First, you've made the implicit explicit. Most restaurant labor problems are quiet — a schedule conflict that grew, a manager grievance that festered, a wage expectation that drifted. The conversation surfaces all of them on day one, before they have time to fester.
Second, you've earned the right to manage them. When something does happen — a no-show, a missed shift, a pay-bump request — you have a baseline. You can refer back: "we talked about Thursdays being a hard day for you. What changed?" or "When we hired you, you said you wanted to be at $22 in a year. We're at $18 now. Here's the path to get to $22 — does it still match what you want?" The conversation gives you authority that "company policy" doesn't.
Third, you've signaled a different kind of operation. A new hire who's been through eight restaurant jobs has never had a conversation like this on day one. Most onboarding is paperwork, a uniform, and a "follow Maria around for a shift." When you sit down for 30 minutes and ask questions like a human, you've already differentiated yourself from every previous job they've had. The signal is "this place treats us as a person, not a position." That signal is worth months of retention by itself.
What it costs
Half an hour of an owner or manager's time per new hire. That's it.
Compare to the cost of replacing a back-of-house employee at the industry average — $2,000 to $5,000 per turn between recruiting, training, and the productivity loss during ramp. If a 30-minute conversation cuts your annual turnover from two events to one, you've earned back the time roughly 4,000-fold.
The math is so absurd that we keep waiting to find the catch. There isn't one. The catch is that most owners are too busy on day one to have the conversation. Or they have a junior manager run onboarding because the owner is "in the weeds." Or they have it on day 30 instead of day one, by which point the new hire has already decided whether the job is going to work.
What to do this week
- Block 30 minutes for your next new hire's first day. Owner or senior manager runs the conversation.
- Print the five questions. Don't read them off the page in front of the new hire — that ruins it. Internalize them, then have a real conversation.
- After the shift, write down the answers. Especially question 2 (life constraints) and question 5 (wage target). Both should inform every scheduling and pay decision you make for that person going forward.
- Six months later, sit down again with the same five questions. Compare answers. The drift between day-one and month-six answers is the single best leading indicator of who's about to leave.
If you want the printable card version of these questions, join the waitlist and we'll send it to the first 50 operators who reply.
— Chayadol