Hey, welcome to the briefing. What I'm going to cover with you today is this. Before you change the schedule, look at next week's shift. I want to take this one into the kind of business where the schedule is not just a document, it is the operating plan, retail, restaurant, hotel, quick service, specialty store, front desk, sales floor, kitchen line, banquet setup, housekeeping, host stand, curbside pickup, drive-thru, fitting rooms, stock room, closing shift. All of it lives or dies through coverage. And if you have ever worked in one of those environments or led one, you know exactly what I mean. The schedule is not just names and hours. The schedule decides who opens ready, who closes clean, who trains the new person, who covers the rush, who handles recovery, who keeps the floor moving, who watches the lobby, who saves the kitchen from getting buried, and who inherits the mess when the last shift cuts too deep. That is why this topic matters. Because when labor pressure shows up, changing the schedule can feel like the cleanest move in the world. Sales are soft, labor is high, forecast missed, somebody called out. The district manager is watching labor percentage. The store manager sees idle time. The restaurant manager sees a quiet section. The hotel manager sees arrivals lighter than expected. So the answer feels obvious. Cut a shift, move a closer, trim the mid, delay training, reduce overlap, protect labor, get through today. And sometimes that is the right move. Let me be clear about that. Labor control matters. Margin matters, payroll matters, no serious operator ignores the labor line, but a schedule cut is not always just a labor cut. Sometimes it is a service cut, sometimes it is a training cut. Sometimes it is a prep cut. Sometimes it is a recovery cut. Sometimes it is a future problem disguised as a clean labor decision. That is where leaders get caught, not because they are bad operators, not because they do not care about the guest, not because they do not understand service. A lot of leaders make schedule changes because they are trying to do the responsible thing. They are trying to protect the number, answer the labor pressure, and keep the business in control. But here is the part experience teaches you. The schedule can look better on paper and still make the next shift worse. That took me time to respect. I have made versions of that mistake before. Not because I did not care, because I trusted the short read too much. I looked at the current pressure, made the clean adjustment, and then later the operation paid for it somewhere else. A rough close, a weak open, a new person left unsupported, a rush period with no flex, a guest recovery situation that never should have gotten that far. That is the lesson, the labor number can improve while the operation gets weaker. Long range observation is the tool here, and I'm not going to turn this into a formal lesson. Think of it simply as looking past the schedule decision sitting in front of you and asking, what does this create next? Not just what does this save right now, what does this create next? What does it do to the next shift? The next day, the weekend, the new hire, the close, the open, the lobby, the ticket times, the floor recovery, the guest experience. The schedule is not just coverage. It is tomorrow's operating condition. That is the real point of this briefing. Picture a restaurant general manager on a Monday morning. We will call her Marisol. She runs a casual dining restaurant connected to a busy hotel and shopping district. So her business is not one clean traffic pattern. She has office lunch traffic, hotel dinner traffic, weekend families, patio demand when the weather holds, walk-ins from nearby retail, and the occasional event that makes the dining room go from manageable to slammed in about 12 minutes. The business is profitable but tight. Food cost is up. Labor is being watched. Guest reviews have slipped a little because seating has been slow and service recovery has been inconsistent during peak windows. That detail matters. Because this is not just a schedule problem. This is labor, service, guest flow, training, prep, and manager coverage all sitting on top of each other. Now Marisol opens next week's schedule and it looks heavy. There is host overlap on Friday night, there is an extra mid shift server on Saturday. The assistant manager is scheduled on a weekday lunch that looks soft. A new server has a supervised training shift during dinner. The kitchen has added prep coverage going into the weekend, and if you only look at this week's sales trend, you can already hear the voice in your head. Too many hours, too much overlap, too much training time, too much manager coverage when the forecast does not justify it. Cut the host overlap, shorten the mid, move the assistant manager to close, push the training shift, trim the prep, get labor back in line, and that sounds reasonable, that sounds responsible. That may also be the exact move that damages next week's shift. Because next week is not this week. That is the first thing long-range observation forces the leader to respect. Next week has a youth sports tournament at the hotel. Next week has a local concert expected to push dinner walk-ins. Next week has a weather forecast that could put patio demand back in play. One senior server is returning from days off and maybe close to overtime. The new host has not run a full lobby alone. The kitchen has a new menu item that slows the grill station when prep is light. There is a catering pickup before Saturday dinner, and the district manager wants labor controlled, yes, but also wants review scores stabilized. So now the question changes. It is no longer just how do I cut labor. The better question is what will this schedule change create next week? That is a different read. The host overlap is not just extra labor. It may be lobby control when the tournament families all show up at the same time, the phone is ringing, online wait list is active, and three parties are asking how long the quote really is. If you have worked a host stand on a loaded weekend, you know that one week lobby can poison the whole shift before the first entree hits the table. Guests get irritated before service starts. Servers get sat unevenly. The kitchen gets hit in waves. Managers start doing table touches on problems that started at the door. So the question is not can we cut one host? The question is what does that host protect? The extra midshift server is not just a body on the floor. That person may be the difference between lunch recovery and dinner setup. Sidework, table resets, ice, silverware, to go staging, patio readiness, section balance, helping the closer not walk into a dining room that looks ready on the floor plan, but is actually behind in all the small ways that matter. And if you have ever closed a restaurant after the mid was cut too hard, you know what happens. The closer inherits everything. Service slows, attitude changes, guests feel it, the manager feels it. The shift starts to run from behind, and once that happens, you are no longer managing the shift, you are recovering it. The training shift is not just training expense. That is one of the easiest things to cut because it does not look urgent on the schedule. But training that gets pushed too often becomes a hidden service debt. The new server who needed supervised dinner reps now gets thrown into a higher pressure weekend section without enough live practice. They do not know the rhythm yet. They miss a pre-bus, they hesitate on upselling, they do not catch when a table is starting to turn cold. They ask for help too late, that does not make them bad. It means the operation removed the practice window and then acted surprised when performance was uneven. Training hours are easy to cut, but weak readiness gets expensive fast. Same thing in retail. A specialty retail manager may look at a Tuesday sales forecast and think the floor is too heavy. Cut one associate, reduce overlap, keep coverage lean. But next week there is a promotion, a new product drop, a return wave from the weekend, and the stock room is behind. Now the thinner floor is not just saving hours, it is reducing conversion, it is delaying recovery, it is leaving fitting rooms backed up. It is pushing a top seller into task work instead of selling. It is creating shrink exposure because the floor is stretched thin during a traffic pocket. The schedule looked efficient, the store got weaker. Same thing in a hotel. Front desk overlap might look like extra coverage when arrivals look light, so the manager cuts it. Then a youth team arrives early, two rooms are not ready, one guest needs a billing issue fixed, the phone is ringing, a loyalty member wants an upgrade, housekeeping is updating room status in real time, and the line starts forming. Now the saved hour becomes a check-in line, lower arrival experience, rushed problem solving, and a front desk associate who spends the rest of the shift trying to recover from a jam that the schedule created. The schedule did not just remove labor, it removed margin for guest flow. That is the whole point. Long range observation helps the leader look at the schedule as an operating system, not just a cost sheet. And that does not mean you keep every hour. I want to be very clear about that. This is not an excuse to overstaff. This is not a soft argument for keeping labor just because people want the hours. The leader still has to control labor, the leader still has to protect margin, the leader still has to adjust. But the adjustment has to be shaped, not just cut. That is the word I want you to hold on to. Shaped. A weak schedule read only asks what can I remove? A stronger schedule read asks, what can I remove without weakening the next operating condition? That is a better question. Maybe Marisol still cuts labor, but maybe she does it differently. Maybe the host overlap stays Friday because the lobby is the known pressure point. Maybe the midshift server is shortened instead of removed. Maybe the training shift stays, but the new server gets a protected section. Maybe prep coverage moves earlier instead of disappearing. Maybe the assistant manager stays on the weekday lunch because that is the only low pressure coaching window before the weekend. That is not overstaffing. That is operating discipline. Now think about what happens if she makes the short read. She trims host overlap and the lobby stacks. Guests are frustrated before they ever sit down. She cuts the mid and the closer gets buried in resets, side work, and service recovery. She delays training and the new server enters the weekend underprepared. She reduces prep and the kitchen survives the first wave but collapses during the second. She moves the assistant manager away from the coaching window and now the new host and newer servers get corrected during the rush when correction is more expensive and more stressful. What did the schedule save if the shift pays for it later? That is the leadership trap. The labor percentage may look cleaner. The shift may become more fragile, and fragile shifts are expensive. They cost you table turns. They cost you check quality. They cost you guest recovery. They cost you team confidence. They cost you manager attention. They cost you reviews. They cost you repeat business. In retail, they cost conversion and shrink control. In hotels, they cost arrival experience and guest trust. In quick service, they cost speed of service and drive-through rhythm. In hospitality, the guest does not care that you saved labor at 10 a.m. if they feel the miss at 7 p.m. That is why long range observation matters. It asks you to read the future pressure before the next shift has to live inside your decision. So if you are looking at a schedule right now, here is the practical read. First, name the current pressure. What is actually driving the schedule change? Is labor too high? Are sales soft? Did the forecast miss? Is overtime at risk? Is there a call out? Is manager coverage thin? Is the truck landing at a bad time? Is a new hire still not ready? Is the problem truly too many hours? Or is it the wrong hours in the wrong place? Name the pressure before you touch the schedule. Do not let frustration make the decision for you. Then look at the next shift impact. If you remove this person, who inherits the work? If you cut this overlap, what gets slower? If you delay this training, when does the new person get the reps they need? If you move the manager, what coaching window disappears? If you trim prep, when does the kitchen feel it? If you thin the sales floor, what happens to conversion, recovery, and loss prevention? If you reduce front desk coverage, what does check-in feel like when arrivals bunch up? That is not overthinking, that is leadership. Then check the future signals, reservations, event calendars, weather, hotel occupancy, delivery timing, school schedules, promotions, new hire readiness, recent guest complaints, known weak handoffs, online order spikes, catering pickups, truck delivery, patio forecast, return patterns, traffic flow. If you are in a restaurant, look at covers, reservations, walk-ins, patio demand, to go volume, and kitchen prep load. If you are in retail, look at conversion periods, task load, fitting room pressure, product launches, truck, promos, and closing recovery. If you are in hospitality, look at arrivals, departures, room status, group blocks, housekeeping timing, front desk overlap, shuttle needs, breakfast rush, and maintenance calls. That is real world schedule reading, not just hours, conditions, then separate cost from protection. Not every hour protects the operation. Some hours may truly be extra, some coverage may be in the wrong place, some shifts may need to move, some overlap may not carry enough value. Fine. Cut it. Move it. Tighten it. But do not treat every hour as the same kind of hour. A host hour before a known lobby crush is different from an extra slow hour body standing around. Prep before a heavy weekend is different from idle time. A training shift before a new person gets real tables is different from unnecessary overlap. Manager coverage during a coaching window is different from manager coverage that only watches the rush burn. That is the read. Which hours are waste? Which hours are protection? Which hours prevent recovery work later? Which cut creates a bigger cost than it saves? That is where the leader earns the decision. And then adjust with the next shift in mind. Do not freeze the schedule. Do not be afraid to change it. But change it with a future read. Trim where the impact is low. Protect where the next shift depends on it. Move coverage toward the pressure that is coming, not just the pressure you are feeling right now. Then watch what happens. Did labor improve and service hold? Did the lobby stay controlled? Did prep carry the rush? Did the new hire perform better because training stayed protected? Did the closer leave the building ready for tomorrow? Did guest complaints stabilize? Did conversion hold? Did check-in lines stay manageable? That is how you learn. Long range observation is not guessing once and pretending you were right. It is looking forward, acting with discipline, and watching the consequence. If the cut worked, you learned something. If the cut saved labor but damaged service, you learned something. If the shift still failed even after you protected coverage, then maybe the issue is not the schedule alone. Maybe it is training, maybe it is standards, maybe it is prep execution, maybe it is weak handoff, maybe it is the wrong manager presence, maybe the forecast is off, maybe the traffic pattern changed. That is why the read matters. I want to hit one warning sign hard. If training is always the first thing removed, you are probably building tomorrow's weak performer. That does not mean training never moves. Sometimes it has to. But if every labor correction cuts the new hire's supervised reps, do not be surprised when the new hire struggles during live pressure. That is not mysterious. That is cause and effect. You removed the practice and kept the expectation. Another warning sign managers are present during the rush but absent during preparation. That can look good from the outside because the manager is there when it is busy. But if the manager is never present during setup, coaching, pre-shift standards, station readiness, lobby prep, floor recovery, or kitchen handoff, then the rush starts weak, and the manager spends the whole peak period correcting problems that should have been prevented earlier. Sometimes the best manager coverage is not only during the visible rush, sometimes it is before the rush when the shift is being built. Another one, the same shift keeps starting behind, the opener is short on prep, the floor is not recovered, the fitting rooms are already backed up, the line is not stocked, the front desk starts with unresolved issues from the prior night, housekeeping is already behind room status before check-ins begin. If the same shift keeps inheriting the same problem, do not only look at that shift, look backward. What schedule decision fed it? What coverage was missing before it? What handoff failed, what training was delayed, what prep was trimmed, what did yesterday save that today is now paying for? That is long-range observation. It is the discipline of seeing that today's labor decision can become tomorrow's operating condition. And if you lead in retail, restaurant, or hospitality, you already know how fast this gets real. A store can lose conversion because the sales floor is thin at the wrong time. A restaurant can lose table turns because the host stand and kitchen prep were cut too tightly. A hotel can lose guest trust because front desk overlap disappeared before a heavy arrival window. A quick service restaurant can lose drive-through speed because training hours got cut before the weekend rush. A specialty retail location can lose repeat business because the best associate is stuck in task work instead of selling. These are not abstract leadership issues. These are schedule decisions becoming guest-facing consequences. So before you change the schedule, look at next week's shift. Ask what you are reacting to. Ask what the change creates next. Ask which future signal you have not checked yet. Ask whether the hour you want to remove is waste or protection. Ask who inherits the consequence. Ask whether the schedule will look cleaner while the operation gets weaker. That question right there will save a lot of leaders from a lot of avoidable damage. Because the schedule is not just coverage, it is who is ready, who is supported, who is trained, who is overloaded, who recovers the miss, who faces the guest, who protects the clothes who owns the handoff, who walks into tomorrow with control, or walks into tomorrow already behind. Do not only ask what the schedule saves today, ask what the schedule creates next, read the next shift, check the future pressure, then make the move with control. Thanks for listening to the briefing.