Skip to content
Hospitality Tech

Should Tech Leaders Replace Standups With a Pre-Shift Lineup?

Richard Yu argues tech leaders running customer-facing teams should swap status standups for a 10-minute pre-shift lineup, with a template and 86 list.

Your customers keep hearing promises your product cannot keep, and the daily standup is not catching them. If your customer-facing team spends its standup reciting yesterday's tickets, replace it with a pre-shift lineup. That is a 10-minute briefing, led by the manager, on today's constraints. For teams driven by inbound customer demand who share a working window, a briefing on open incidents and at-risk accounts produces fewer customer-facing mistakes than a round-robin about yesterday's progress. For engineering teams doing planned sprint work, the status standup stays the better format.

You can run the lineup tomorrow from the fill-in template further down, with a written 86 list and a two-week trial log, and no new tools.

Hypothetical: engineering disables the custom-field sync at 8:15 after a data bug and posts it in the incident channel. At the 9:30 standup, a customer success manager sits through everyone's yesterday, and nobody mentions the sync. At 10:30 the same manager tells a renewing customer that the sync is the answer to their reporting problem. Nobody did anything wrong in the standup, and the customer still heard a promise the product could not keep.

What a Restaurant Pre-Shift Lineup Covers

Before doors open, a restaurant manager pulls the floor staff together near the pass, the counter where finished plates leave the kitchen, and talks for a few minutes. A lineup at a neighborhood bar in North Beach, San Francisco covers the same ground as one in a hotel dining room. First comes what is 86'd tonight, meaning sold out or pulled, so nobody offers it. Then the large parties and private dining bookings on the book. Then guests with allergies or notes on the host sheet, and the focus for the shift, such as pacing second courses on a full book. Nobody reports what they did last night.

The comparison shows something software teams leave unnamed. Most customer-facing mistakes are timing failures. The information existed somewhere in the building, just not in the head of the person facing the guest when it mattered. The kitchen knows it ran out of short rib, and the server selling it to the next table does not, unless someone told the floor. On a software team the engineer who rolled back a release knows it, and so does the incident channel. The customer success manager on back-to-back calls does not.

So the lineup changes two things about how you run your team. The manager gathers the constraints before the meeting and briefs them, so the person with the full picture does most of the talking. And the team keeps a written 86 list of what nobody offers customers today. The parallel holds while the team shares a start time, the way a floor shares the moment the doors open.

What Tech Leaders Should Cut From the Daily Standup

The round-robin standup suits engineers coordinating planned work. Each person reports progress and blockers, so teammates can untangle dependencies. On a support or success team the work arrives from outside, and the recital stops coordinating anything. Yesterday's tickets are already in the help desk. Yesterday's calls are already in the CRM.

I'd cut the yesterday report first, because the systems of record hold it and saying it aloud gives a rep nothing to act on before lunch. Then I'd cut the fixed speaking order. On a bad day the person who knows an integration is broken is seventh in line, and by then the room has tuned out.

I think the round-robin survives on customer-facing teams because it feels fair. Everyone gets the same airtime. Fairness is a fine goal for a retro and the wrong one for a meeting whose purpose is to stop the next bad call.

Keep the blocker question. It moves to the closing questions slot in the template, where anyone raises one. The owner takes it to a thread right after, so one ticket does not hold the whole room.

The 86 List for Software Support and Success Teams

In a kitchen, 86 means an item is off for the shift, and the useful part is that the server stops offering it before a guest has to hear no. The software version is a written list of features, integrations and promises the team does not offer customers today, each with a reason, an end date and a person who can lift it. It has to be written because the rep who needs it is mid-call when it matters, long after the meeting where it was said.

An item qualifies when saying yes to a customer today would create a promise the company cannot keep this week:

  • a feature behind an open incident or a rolled-back release
  • an integration with a known sync failure
  • a roadmap date engineering has not confirmed in writing
  • a discount, contract term or SLA that finance or legal has paused
  • an onboarding kickoff date the implementation team cannot staff

The lineup owner is the only person who adds or removes items, and anyone can ask them to. Each item comes off on its until-date unless the owner re-confirms it, so the list cannot quietly grow into a museum of old problems. If the list runs long day after day, take it to engineering leadership as a product quality problem; a meeting format will not shorten it.

Software helps here only by putting the list where the rep already looks: pinned at the top of the team channel or shown as a banner in the help desk, with the until-date visible and the item dropping off when that date passes. It should not become another dashboard to check or a bot that pings the channel on every edit, because a rep between calls skips any new place to look.

For more on teaching a team what to do when a mistake reaches the customer anyway, see Restaurant Operations Training Should Start With Fixing Mistakes.

A Pre-Shift Lineup Template for Customer Success and Support Teams

The owner, the team lead in most setups, preps before the meeting and speaks for most of it. The lines are short so they can be said out loud to a room of people about to start calls. Fill the brackets each morning. The clock times give a 10-minute run starting at 9:00.

Prep, by 8:50, [owner]: check the incident page, the CRM report of renewals due this week, and messages from product and engineering. Update the 86 list.

9:00, [owner]: Morning. It's [date]. Ten minutes, then we're on calls.

9:00 to 9:02, the 86 list: Not offering today: [feature or promise]. Why: [reason]. Off the list [until when].

Also off: [feature or promise]. Why: [reason]. Back [until when].

[newest rep], read the list back to me.

9:02 to 9:04, open incidents: Live right now: [incident]. If a customer asks, say: "[customer-facing message]." No fix dates unless engineering gives us one.

9:04 to 9:07, accounts to watch today: [account]. [renewal date or risk]. [account owner] has it. If they reach you first, loop in [account owner] before you answer.

Next: [account]. [renewal date or risk]. [account owner] has it.

Three accounts at most. Anything else goes in the channel.

9:07 to 9:08, today's one focus: One thing today: [focus].

9:08 to 9:10, questions: What did I miss? Anything the room should hear before your first call?

9:10: That's it. The 86 list is pinned in [where it lives]. Go.

Hypothetical: on a Tuesday the owner spends two minutes on one 86 item, the custom-field sync, off because of a data bug until Thursday, and the newest rep reads it back. Two minutes go to one incident, delayed CSV exports, with the line "Exports are running late today, and we'll email you when yours is ready." Three minutes go to one account, Northwind, renewing Friday, owned by Priya, with the reminder to loop her in before answering. One minute covers the focus, confirming every kickoff date in writing, and two minutes stay open for questions. That is 2 + 2 + 3 + 1 + 2 = 10 minutes, ending at 9:10.

The read-back feels awkward for about a week. Keep it anyway. It turns a list people heard into a list somebody said, and the newest rep is the one most likely to promise something off it.

Keep the account slot to accounts a rep might hear from today, such as a renewal due this week or a champion who just left. If the conversation turns into a deal review, the owner says "take it to the account channel" and moves on. The customer-facing message in the incident slot comes from whoever owns incident communications, so the reps and the status page say the same sentence.

Put the lineup on the calendar to end before the earliest booked customer call. On a heavy day, end at 9:10 and keep accounts to three. A long lineup on a bad day is the one people stop attending.

Running the Lineup Async Across Time Zones

This is where the restaurant parallel stops. A shift starts for the whole floor when the doors open, so one spoken briefing reaches everyone at the moment it matters. A team spread from Lisbon to Seattle has no doors-open moment: each person's day starts at their own first customer call.

So the lineup becomes a written post with the same fields as the template, and the rule changes from being in the room to reading it before your first customer call. I'd set it up in this order:

  1. The owner in the earliest region posts the lineup as a new, dated message each morning and pins it, and unpins yesterday's so nobody works from an old 86 list.
  2. Each person reacts to the post before their first customer call; the owner checks reactions against the call calendar and messages anyone with a call coming who has not acknowledged.
  3. Changes during the day go in as edits to the pinned post plus a reply in the thread, so the current version lives in one place.
  4. Before signing off, the outgoing owner updates incidents and the 86 list and tags the next region's owner. That tag is the handoff.
  5. The thread replaces the questions slot, and the owner answers what is posted there before the next region's day starts.

A reaction is a weak substitute for the read-back. For an 86 item serious enough to lose a renewal over, ask each rep to reply in the thread naming it in their own words.

Where This Breaks

The strongest case against all of this: a standup exists to surface blockers, and a manager reading out a list turns it into a broadcast nobody listens to. Software teams are not line cooks waiting for doors to open. They already have channels and dashboards that carry this information in real time.

Part of that is right. A lineup that runs long, or says the same thing every day, loses its audience. Standing 86 items are expected to repeat, because each one stays until its until-date and gets read back every morning. The check applies to the other slots. If the incident and account slots are unchanged from yesterday for three days running, shorten them, or cut the lineup to the 86 list plus the focus. Blockers between engineers also belong in the engineering standup, which stays as it is.

The real-time point cuts the other way for customer-facing teams. Those tools carry everything, as it happens, to people who are on calls when it happens. A support lead who counts on reps reading every channel between calls is counting on the thing a booked rep has no time to do. The lineup filters all of it down to the few items that change what a rep says to a customer today, delivered before the first call.

The advice flips for engineering teams on planned sprint work. Their constraints change weekly, at planning, so a daily constraints brief repeats itself and the status standup fits better. It also flips for teams with no shared start, where a spoken lineup cannot happen and the written post from the async section is the only version that works. And a team with few accounts and almost no incidents has little to brief. A pinned 86 list on its own is enough there.

Run It With One Team for Two Weeks

The head of customer success or the support lead picks one team that shares a working window, runs the first lineup next Monday, and reviews the log on the tenth working day. If you manage engineering, your part is one message to the lineup owner before the prep time each morning with anything that belongs on the 86 list.

Before day one, pull a baseline from the previous two weeks of tickets and escalations. Baseline: [count] customer-raised surprises (problems a customer reported before the team knew) and [count] unkept promises (things a rep offered that the product could not deliver). Then fill in one row of the log below for each trial day.

DayDateEnded by 9:10? (yes/no)Customer-raised surprisesUnkept promisesOf those, already on the 86 list
Day 1[date][yes/no][count][count][count]
Day 2[date][yes/no][count][count][count]
Day 3[date][yes/no][count][count][count]
Day 4[date][yes/no][count][count][count]
Day 5[date][yes/no][count][count][count]
Day 6[date][yes/no][count][count][count]
Day 7[date][yes/no][count][count][count]
Day 8[date][yes/no][count][count][count]
Day 9[date][yes/no][count][count][count]
Day 10[date][yes/no][count][count][count]
Total[number of yes] of 10[sum of days 1 to 10][sum of days 1 to 10][sum of days 1 to 10]

On the tenth day, the log decides. If the lineup ended late on more of days 1 to 5 than it ended on time, cut the account slot to renewals due this week, and for the second week end at 9:10 and keep accounts to three. If the last column shows any promise that was already on that day's 86 list, the list is in the wrong place, so move it to where reps look mid-call before changing anything else. If total customer-raised surprises are not below the baseline, stop and go back to the standup, because the mistakes are coming from somewhere a morning briefing cannot reach, such as release communication or product quality. If the log passes all three, run it with the next team.

, Richard Yu

Frequently Asked Questions

What is a pre-shift lineup in a restaurant?

It is a short briefing a manager gives the whole floor before service starts. Many restaurants also use it to taste a new dish or cocktail so servers can describe it firsthand; a software team can mirror that by giving a one-minute demo of a newly shipped feature on the day it ships.

Won't a manager-led meeting stop the team from raising problems?

Not if the closing slot belongs to the team and the owner visibly acts on what comes up. If the questions slot stays silent for a full week, ask people one by one what they are holding back; silence there means the slot feels unsafe or pointless.

Is a pre-shift lineup a good daily standup alternative for engineering teams?

For teams on planned sprint work, no; keep the status standup. The exception is an on-call or platform team fielding inbound requests all day, whose day looks like support's, so a short constraints briefing at the start of each on-call shift fits them.

What tech leadership skills does running a lineup build?

Mainly editing: choosing the few constraints that change what a rep says today and dropping the rest. Once the format is stable, rotate ownership to a senior rep for a week at a time, which builds that same editing judgment in the next person you might promote.

About the Author

Richard Yu

Richard Yu is the Managing Partner of Rich Ventures, a San Francisco startup consulting and early-stage investment firm, and co-founder and Managing Partner of Equal Parts, a restaurant and cocktail bar in North Beach. He was Director of Strategic Account Management at Lob, founding Head of Solutions Engineering at ChartHop and at Naehas, and in customer success at LeadIQ. He has experience scaling startup post-sales organizations from $1M to $20M+ ARR and advises pre-seed and seed stage founders on go-to-market strategy.