When someone checks their phone in a meeting, the meeting goes strangely slack. Plenty of times, that someone was me. After our team set a meeting phone rule, the meetings got shorter, and the effect came less from the rule than from the setting of it.
A phone in a meeting doesn't only cost the person holding it. It thins the entire meeting. One person's screen licenses the next person's, the speaker feels the room not listening and trims the explanation, and trimmed explanations defer decisions into more meetings. The strongest fix is a rule the team sets together: phones face-down in the middle, 30-minute meeting defaults, phone-needed meetings marked as such. And with no team rule, one person can still start: phone in the bag, notes on paper.
Three things happen. First, you miss things. The remark made during your 30 seconds of scrolling went unheard, and when it becomes the basis of a decision, you can't follow. Second, the next person joins. One phone out sets the permission for every phone out. Third, the speaker shrinks. Watching an audience of bowed heads, the speaker trims the explanation, trimmed explanations postpone the decision, and the postponed decision books the next meeting. This is how meeting phones lengthen meetings.
| Rule | How | Effect | Watch for |
|---|---|---|---|
| Face-down in the middle | All phones to the table's center, screens down, at the start | Reaching gets visible. A threshold appears | Urgent-call people keep sound on |
| 30-minute meetings | Default length drops from an hour | Too short to scroll | Needs a set agenda |
| Phone-needed meetings marked | Only meetings that read materials on phones allow them | Every other meeting runs phone-free | Mark it in the invite |
| Laptops closed too | One note-taker opens one laptop | Otherwise laptops recreate the problem | Rotate the note-taker |
| Cameras on, online | Camera-on as the default | Being visible cuts other-screen time | Agreement over mandate |
Handed down from above, a rule breeds resistance, and resistance goes underground: checking under the table. Better to book one meeting and set the rule together. Two questions suffice: has a phone in a meeting ever bothered you, and what rule could we actually keep? In most teams, everyone answers yes to the first, and the second converges on face-down in the middle.
Why the process outweighs the rule: that meeting is where everyone discovers they've been having the same problem. After ours, whenever my hand moved toward my phone, I could feel the eyes beside me. It wasn't the rule that put the phone away. It was the eyes.
Online, the problem isn't the phone. It's the other windows. Closing everything but the meeting window is the home-desk version of the bag.
A buddy in Sumbi is a partner who dives with you. Set a colleague as your buddy and dive for the length of the meeting, and you both walk in with phones already down, with each other notified when it ends. Instead of a meeting about the rule, there's also just going down together.
Dive with a buddy →If a meeting keeps sending you to your phone, the problem may precede the phone: the meeting doesn't concern you, runs too long, or decides nothing. No phone rule repairs that. Fewer meetings, or fewer attendees, does.
Teams that dropped the default from an hour to 30 minutes say the same thing: no time left to scroll. Short forces an agenda, an agenda cuts the drifting, and less drifting means fewer phones.
When the meeting ends, the backlog gets read. That's fine. The problem was during, never after. Designating the five minutes after as phone time makes the abstaining during far easier.
One line from a phone-down day. The first meeting I entered with my phone in my bag was the first meeting I could recall without the minutes. Nothing missed, so it stayed.
This article is general information, not medical advice. If sleep or daily life stays disrupted, talk to a professional.
Sumbi