Abstract:

The article identifies a common workplace eating pattern it calls “catering drift,” where leftover meeting-room food—croissants, mini chocolates, chips, an ambiguous fruit tray—has fuzzy ownership and no clear start/stop, so it gets eaten like background noise in tiny, forgettable bites during transitions, awkward silences, and slide reviews, leaving people oddly not hungry at lunch but “feral” around 15:30 and treating dinner as damage control. Rather than framing this as a willpower problem or a ban on treats, it argues the issue is a systems bug driven by default permission, lack of endpoints, snack types optimized for quiet one-handed eating (often low protein/fiber), and cues anchored to meeting moments, plus the reality that people underestimate intake when it’s spread across micro-bites. The proposed fix is deliberately low-friction: a “one unit rule” where shared food only counts if you take one visible unit (e.g., one cookie on a napkin, one handful of nuts) and eat it in one go, which leverages unit bias and improves bite-memory; then “pair or pause” by either adding a simple protein/fiber co-pilot like yogurt, nuts, a cheese stick, hummus, edamame, a tuna pouch, milk, or half a sandwich, or doing a 60-second debounce (water + two slow exhales) before deciding. It suggests a tiny 5-day experiment and minimalist log (shared-food units and your 16:30 state) to see fast signals like fewer automatic kitchen laps, less urgent extra coffee, less brain fog, and dinner feeling like a normal decision again, while also noting guardrails for medical red flags, diabetes/hypoglycemia, and eating-disorder history, and even includes a personal aside about doing occasional “physics brain” calorie math on something like a pastel de nata as a sanity check rather than daily tracking.

A meeting ends. The slides stop. And there is still that open box on the side table.

It is not “a snack”. It is not really “yours”. It has no start, no stop, and no clear owner. So it behaves like background noise. A bite here while someone asks a question. Another while you wait for the next person to join. By lunch you are not hungry, by 15:30 you are suddenly feral, and dinner feels less like a choice and more like damage control.

If your days are already 10 hours at a desk, stacked meetings, lunch at the keyboard, and exercise pushed to “later”, this will sound familiar. And yes, it is annoying to add yet another thing to manage.

This article is here to name the pattern and make it fixable without turning your workday into a new system. The point is not discipline, or banning croissants. It is giving shared office food a boundary so your brain can actually register it. You will get a simple rule for meetings, two small stabilizers, and a way to tell in 3 to 5 days if it’s helping.

If your week is already packed and remote work removed the last bits of incidental movement, this is meant to be low friction. Small boundaries. Fewer late-afternoon emergencies. And a dinner that feels like a normal decision again.

The meeting room buffet bug

Food that is not yours and not a meal

A meeting ends, and there is still a box open on the side table. In offices and hybrid days, this is leftover croissants, mini chocolates near the coffee machine, help yourself chips, or the anonymous fruit tray that may or may not be for anyone. The defining feature is not that this food is bad. It is that it has fuzzy ownership and no clear start-stop boundary, so it acts like background noise.

A typical cookie can be around 50 to 150 kcal and brings little protein or fiber (USDA FoodData Central varies by type and size). That is not a moral issue. It just means it is easy to eat 2 or 3 without it “counting” in your head, and then wonder why your appetite is weird later.

The pattern is easy to miss because it does not feel like eating. It feels like being in meetings.

By 11:30 you can have a muted appetite because you have been running on coffee and context switching and there was always something small available. Then at 15:30 the snack pull shows up, suddenly sharp, and dinner becomes urgent even if you were grazing all day. People also tend to underestimate how much they ate when it was spread across forgettable bites (Livingstone & Black, 2003).

Once you frame it as a workplace systems issue, not a discipline story, it gets easier to fix. Meals usually come with boundaries and at least a small mental note. Meeting room food removes both.

Naming the pattern catering drift

Catering drift in plain terms

Catering drift is when shared room food, not an actual meal decision, ends up shaping how much and when you eat.

Quick signatures, no tracking app needed

• You did not eat, but wrappers exist somewhere
• Hunger hits late, sharp, slightly rude
• Lunch feels optional, dinner feels urgent
• You keep just taking a bite while thinking

The mechanics are simple. You remember lunch. You do not remember 9 bites during a slide review. It is like having logs, but they get dropped because the system is busy.

Meeting culture makes it worse. Eating in a meeting is often silently approved. Taking a real lunch can feel weirdly political when everyone is “available” all the time. This showed up for me in offices in Beijing and Berlin, and it still shows up in hybrid weeks from Lisbon: the food is “for everyone”, so it becomes “for no one”, and it just sits there doing its quiet work. So intake gets smeared across transitions and attention-fragile moments.

Why meeting snacks beat discipline

The mechanics that make shared food sticky

4 things tend to stack

• Permission by default. Food in the room signals yes, even if the calendar signals no.
• No endpoint. Micro-bites have no done signal, especially when you are distracted.
• Snack selection bias. Meeting snacks are chosen to be quiet and clean and one-handed, which often means pastries, cookies, crackers. Compared with higher protein or higher fiber options, they keep you full for less time. Carbs are not evil. The meeting context is.
• Cue anchoring. Bites get tied to triggers like waiting for others to join, an awkward silence, a tense question.

So instead of a diet rule, you need a tiny boundary that changes the default behavior inside meetings.

The one unit rule in meetings

Turn grazing into 1 visible unit

Rule

Ambient food counts only if it becomes 1 visible unit and you finish it in 1 go.

Examples

• 1 cookie on a napkin, eat it, done
• 1 handful of nuts in your hand, eat it, done

This is not meant to be strict. It changes the shape of the decision, not the permission. You can still eat the cookie. The change is that drive-by bites and 6 returns just to take 1 more do not qualify.

Why it works

• Once it looks like “a portion,” most people stop at one. Put it on a napkin and you’re done; keep it in the box and you’ll find reasons to come back.
• Better memory. 1 visible episode is easier to remember than micro-bites spread across agenda items. That matters later, when your brain tries to figure out if you “already ate”.

To keep it low drama, scripts help without making it a thing

• I will grab 1 after this item
• I am taking 1 now, then I am done
• I will pass for now, maybe later

Pair or pause for stability

Pairing without meal prep

If you take the cookie or croissant, add a small co-pilot, usually protein or fiber. This makes the treat act more like a real snack and often reduces the late-afternoon crash.

Office-compatible co-pilots

• Greek yogurt
• Nuts
• Cheese stick
• Hummus cup
• Edamame
• Tuna pouch
• Milk
• Half sandwich

Not perfect macros. Just more runway.

People vary a lot in how they respond to the same snack. Pairing is about fewer crashes, not winning an argument about carbs.

The 60-second pause

A pause that creates a choice. Best used when your hand is already doing the thing.

Do this

• drink a bit of water
• do 2 slow exhales
• then decide

It is basically a speed bump between your hand and the snack box. Not magic. Just enough space to notice what is happening.

Where it works best

• after tense updates
• after awkward silences
• right at meeting end
• when not hungry

If you are truly hungry, skip the theater and eat.

A simple if then

If the meeting ends and you reach for food, then do the 60-second pause first.

How to know it is working

Signals that shift fast

Keep the log absurdly small so it does not become the new problem. Look for changes you can notice in 3 to 5 days.

• fewer 15:30 to 17:00 kitchen laps that feel automatic
• less coffee 2 or coffee 3 urgency, especially when sleep is short
• fewer fog moments where you reread the same paragraph 3 times
• dinner feels less like a cliff and more like a normal decision
• you can actually remember what you ate because it had endpoints

A 5 day log that does not ruin your life

A minimal option for 5 workdays

Shared-food units 16:30 state 0 / 1 / 2+ steady / foggy / snacky

No calories. No macros. Just enough to see the pattern.

Keep expectations human. Some dip will remain. The goal is a smaller crash, not becoming a robot at 15:00.

Guardrails

Medical red flags that are not a buffet problem

If any of these show up, stop debugging snacks and get checked. People ignore this stuff because desk days make everything feel “normal tired,” until it isn’t.

• fainting or near-fainting
• severe or new fatigue that is not improving
• unintentional weight loss over 5% in 6 months (Merck Manual)
• persistent appetite disruption plus signs that could fit anemia, thyroid issues, diabetes, or sleep apnea

This article is not diagnosis.

Diabetes and lows are treatment not snacking

For diabetes or other hypoglycemia-prone situations, delaying food is the wrong rule. Standard guidance is to take fast-acting carbs and recheck, not wait for the break, and it can be a workplace accommodation issue.

When rules create anxiety stop

If you have an eating-disorder history, or if rules make you more obsessive or anxious, this tool can backfire. If the boundary increases preoccupation or rebound eating, stop and seek support.

Softer versions that still break the cue loop

• 1 return max to the snack table
• only when seated, not in transitions
• only from a plate or napkin, never from the box or bag

A small reality check not a lifestyle of tracking

With my physics brain, I sometimes do quick calorie math on a pastry like a pastel de nata and compare it to a rough theoretical daily intake, just to see if it is worth it. It is an occasional sanity check, not daily tracking. The practical point: the “1 visible unit” rule is there partly so dinner-time you can remember what happened earlier without playing forensic accountant with crumbs.

A small boundary beats a new system

Treats are not the problem. The infinite script is.

Run a short experiment for 5 workdays where shared food only counts if it becomes 1 visible unit and gets an endpoint, then pair or pause when needed so distraction does not turn into later snacking.

The croissant is rarely the issue. The ownership is. When food belongs to everyone, it can quietly belong to your whole day.