The first time I tried this, at Hana Group, I hired a videographer, wrote scripts, added lower-thirds, and shipped a fifty-video training library that I was proud of. Watch-through data came back three months later. Nobody was watching past forty seconds. The library that actually got used, when I stripped everything out and just handed a shift lead a phone, ended up being a hundred and forty clips, unedited, filmed at station, indexed in Airtable. That library cut new-hire ramp from three weeks to eight days.

What follows is the build I would run on day one now, in any group past three units, with no budget past a Loom subscription and a stack of laminated QR cards.

Why sixty seconds is not a suggestion

A new line cook does not have five minutes. They have the gap between tickets, or the two minutes before service kicks off, or the walk from the walk-in to the salad bench. In that window they will watch a sixty-second video. They will not watch a three-minute one.

Every deployment I have run has produced the same watch-through curve. Full watch rate for a sixty-second clip is around eighty-five percent. At ninety seconds it drops to sixty. At two minutes it drops to forty. By three minutes you are showing videos to nobody.

The corollary is that most tasks do not fit in sixty seconds. That is fine. Break the task into three clips, each with its own tag. Prepping the tandoori chicken marinade at Zareen's is not one video, it is four: measure spices, blend the wet, combine with the yogurt, portion into hotel pans. Each one stands alone. Each one is under a minute. A new hire can watch clip three at the station without having to remember where clip two ended.

The library shape

The whole thing lives in one Airtable base per brand. The record is a video, the fields are the metadata, the views are the filters a phone can hit. There are three primary views: by station, by shift, and by "new hire first ten days." Every video has a tag for each of the three.

Library structure · from station QR to video on phone Grill · QR scan on phone Salad · QR scan on phone Walk-in · QR scan on phone Dish pit · QR scan on phone Airtable base station · shift · task tags filtered view per QR Loom clip internal · 60 sec YouTube unlisted for shared links Zapier · Make new-hire push

Fig. 1 · Station QR to Airtable view to video on the trainee's phone.

The record

Each video record in Airtable has eight fields and no more. Title, station, shift, task category, prep versus service, video URL, filmed by, and search phrase. That last one is important. A new hire does not type "sear technique proteins." They type "how do I cook the chicken." The search phrase field is the phrase the trainee would actually use, and it is what the Airtable search bar hits.

The views

Views are what the QR codes point at. The grill QR opens the Grill view, filtered to that station, sorted by service versus prep, with the most-watched clips at the top. The walk-in QR opens the Walk-in view, which is mostly organization, rotation, and receiving. A trainee never has to scroll past twenty rows to find what they need, because the view for their station already has the right twenty rows.

The QR cards

Laminated. Four inches by six. Printed at every station and every workstation the new hire will spend time at. The card has the station name, the QR, and one sentence: "scan for videos." No branding, no logos, no QR-generator watermark. The point is speed of access, not visual identity.

Placement matters more than the card does. The grill QR goes on the pass, at eye level, not on the wall behind the station where nobody looks. The salad QR goes on the front of the reach-in, not on the side. The walk-in QR goes on the inside of the door, so a trainee pulling product can scan without setting the tray down. Every card that ends up somewhere inconvenient gets scanned a third as often as the ones that live where the hands already are. I now walk every new unit with a shift lead and reposition cards for a full week before I trust the placement.

Who films

The line-level leader who does the task best. That is the rule. Not the general manager. Not corporate training. Not the founder. The shift lead who plates the best salmon at Zareen's Palo Alto is the one who films the salmon video for Palo Alto. If Redwood City plates it differently, Redwood City films their own.

Two reasons that matter. First, the video shows the actual technique used at that unit, not a corporate ideal that the line does not follow. Second, the person who films it becomes the accountable owner of that standard. If the video is out of date, they get asked to re-shoot. If the standard changes, they get asked to update it. That ownership is what keeps the library from ossifying.

The library that gets watched looks like it was filmed on a phone at 2pm on a Tuesday. Because it was.

The recording rhythm

The library dies if the recording stops. Every deployment I have seen fail has died the same way: someone got promoted, someone else got busy, the last new video was uploaded eleven months ago, and the trainees stopped scanning the QR codes because they knew the clips did not match what was actually happening on the line.

The mechanic that keeps it alive is a weekly ritual. One video per shift lead per week. Fifteen minutes on Tuesday afternoon during the lull. The general manager reviews new uploads on Friday, retires clips older than a year that have not been re-shot, and promotes the best new clip to the new-hire first-ten-days view. That is it. If the ritual holds, the library holds.

I keep a simple scorecard in Airtable. Videos filmed this week, per unit, per shift lead. The scorecard gets shared in the weekly area director meeting. Nobody gets in trouble for a zero, but a zero in three consecutive weeks means the general manager is not running the ritual, and that is a coaching conversation.

What the numbers look like

Across two Zareen's locations, the ramp from a new line cook's first shift to shift-lead-approved dropped from about three weeks to about eight days. Front of house dropped from ten days to four. The gain came from three places.

First, trainees could re-watch the specific step they got wrong without pulling a shift lead off the line during service. That saved on average nine minutes of a shift lead's time per new hire per shift, which is a real number when you are running a workforce of 215 and putting through fifteen to twenty new hires a quarter across three restaurants.

Second, the video was always available. A trainee who worked Tuesday and did not come back until Saturday could refresh on Friday night on their phone. That is not something a printed SOP binder in the office lets them do.

Third, the videos surfaced technique gaps in existing staff. When a two-year cook watched the grill lead's video and realized they had been searing off the wrong side, that is a training win the library was not designed for and delivered anyway.

Front of house saw a different kind of gain. Wine service, coursing at a four-top, and the credit-card gratuity flow at close are all things that used to take a manager standing at the trainee's shoulder for a full shift. With the videos, the manager checks in twice, the trainee re-watches the flow on their phone between covers, and the third shift they run solo. That saved roughly twenty manager-hours per new server across the three Zareen's locations, on a team that hired seventy-eight front-of-house staff in a year.

The traps

Over-production

This is the biggest one, and I have fallen into it twice. The moment someone decides the videos need a title card, a script, background music, a corporate logo, and consistent framing, three things happen. The videos take four times longer to make. The line-level leaders stop filming because it is not their job to produce content. And the videos start to feel like corporate messaging instead of a teammate showing a teammate how to do the thing. Watch-through drops. New uploads stop. The library dies.

The rule I now write into the rollout document is: no editing, no music, no titles, no logos. If the video needs any of those to be useful, it is the wrong video for this library.

The compliance-training temptation

The video library is not a learning management system. It does not track completion. It does not certify. It does not replace ServSafe, the harassment training, or any regulated module. Those live in a real LMS. Trying to make Airtable and Loom do compliance training breaks the library, because the moment you add a completion checkbox and a passing quiz, the tool feels like homework and the trainees stop opening it for the sixty-second clips they actually need.

The single-champion failure

If one person at HQ is the only one who films, indexes, and reviews, the library dies the day that person changes roles. Every unit has to have its own filming rhythm and its own general manager review. If the library requires a corporate role to keep running, it will not survive a reorganization.

The private link problem

Loom is great for internal, but if you ever need to share a clip with a franchisee, a landlord, or an outside chef consultant, you cannot send a Loom link without a Loom account on the other side. The workaround I use is that any video we might ever need to share externally also gets uploaded to a YouTube unlisted channel. It doubles the storage step but it saves a real headache the first time an outside partner asks for the video.

Where this fits in the broader stack

The SOP video library sits next to the written SOPs, not on top of them. The binder still exists. The Toast recipe cards still exist. The line check still exists. The video library is a fast-access companion for the moment the new hire is at the station and cannot remember the step. It is not a replacement for hands-on training and not a replacement for the shift lead's judgment.

Combined with a custom GPT that answers new-hire questions in text, and a Zapier flow that pushes the "new hire first ten days" video playlist to their phone on day one, the whole training experience compresses. The library is the piece that made the biggest single dent for us. Everything else built on top of it.

The point

You do not need a training platform, a videographer, or a corporate learning department to cut a line cook's ramp in half. You need Loom, Airtable, a QR generator, a stack of laminated cards, and a shift lead who cares enough to film one clip a week. Sixty seconds, one task, unedited, filmed at the station by the person who does it best.

Keep the library alive with a weekly ritual. Retire the stale, promote the good, review on Friday. The rest is discipline.