Start Your Meetings at 5 Minutes Past
Key topics
The art of starting meetings on time is being reimagined by scheduling them at 5 minutes past the hour, a quirk that's sparking debate about its effectiveness. While some commenters, like etrautmann, swear by this tactic, citing its success at their large tech company, others are skeptical, pointing out that it may simply be a novelty that wears off over time [wvenable]. As exegete wryly notes, when everyone expects meetings to start late, the 5-minute buffer can backfire, causing meetings to run even later. The discussion reveals that cultural context and social pressure play a significant role in determining whether this tactic will succeed.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
2h
Peak period
47
3-6h
Avg / period
13.3
Based on 160 loaded comments
Key moments
- 01Story posted
Jan 9, 2026 at 5:19 PM EST
1d ago
Step 01 - 02First comment
Jan 9, 2026 at 7:48 PM EST
2h after posting
Step 02 - 03Peak activity
47 comments in 3-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Jan 11, 2026 at 11:11 AM EST
4h ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
At previous companies this wasnt the case, so we started meetings on time
I see two flaws:
1) This only works as long as nobody else does it. If the meeting prior to yours follows the same strategy then you’re in the same position as today
2) it starts 5 minutes later but has no plan for ending 5 minutes earlier, which means the next meeting will have to start at 0:10…
I work with a PM who is notorious for meetings running long. People just start hanging up while she’s talking if they have another meeting to go to. When she start hearing a bunch of beeps of people leaving, she starts to get the message that she needs to continue on the next meeting and stop. People are tired of it and don’t entertain it anymore, as much as she keeps trying to talk.
Decades ago at an engineering firm I worked for it was baked into the groupware settings.
The smelly basement nerd running IT seemed normal back then, but here are in 2026… Turns out he was an unsung smelly genius ahead of his time. A giant among men who bathe.
Also every meeting taking the exact time it was scheduled for is a bit of an org smell too. If you have your meeting etiquette dialed in you should hopefully be finishing meetings early more often than running over. If you are running to the minute or over all the time you might just be having crap meetings.
I've never seen this pressure.
> meetings rarely started on the dot anyway before this change.
It's like I live in an entirely different world.
Start meetings when they say they're going to start. People will learn to show up quickly. I think that works better than trying to psychologically game people into cooperation. That just starts the classic treadmill. You might have that one friend that you tell to show up half an hour before everyone else. They mentally add the half hour back because you're always giving such early times. Better IMO to just keep things simple. Let people leave when they need to. Show up on time.
My bosses (leadership) are in meetings literally all day long. Them showing up 5 minutes late to an internal meeting has nothing to do with them "learning". It's entirely about priorities. Teaching them to "show up on time" does nothing and only hurts me for being obtuse with them.
Last job, the senior guy who I knew missed our breakfast meeting to discuss a job. Turned out that he had something come up with one of the regions and his admin didn't have my cell. Ended up with the job anyway where I stayed for a long time.
At the same time, we had a rule that meetings would start when they say they start. This was after being incredibly frustrated by a guy on another team who would schedule his meetings to start on the hour, but then display a message that said we’d start at 5 after, to give people time to join, assuming other meetings would run long. This felt like he was wasting everyone’s time who showed up on time, and had the net effect of everyone showing up late to his meetings. If people learned they should show up late to his meetings, they can learn to show up on time to our meetings. Then we can stop waiting around hoping that everyone shows up. When someone shows up late to a meeting that’s already well underway, that sends a strong signal that they should be on time for the next one.
Obviously it was pretty chaotic at first and I recall us being pretty brutal in our assessment of his “crazy meeting quirk”. However after a few weeks something pretty interesting happened:
- Brevity and productive discussion became common. People usually went with their best opinion
- we usually finished the agenda (probably because we set reasonable agendas for 22 mis) and rarely needed that rollover meeting
- we spent more time at our desks actually doing instead of just talking about doing. I recall that team being really productive overall.
Later when I moved into leadership roles I attempted to bring this methodology but my own leadership generally was not supportive enough to allow me to be as rigid and I didn’t see the same success with the method…but to this day 32+ years later I still think it had merit.
I had asked him where he had learned it. My recollection is that he formulated it after reading that the average person’s attention span in a meeting was 27 minutes and he figured no one was productive after that, so he decided it was pointless to go longer.
At Microsoft it was obvious how five minutes late was optimal - meetings usually dragged on past their end time anyhow, but never started early so it gave folks time to eg get to their next meeting (in person), coffee, bio break, etc.
Does Google have a culture of meetings ending on the dot with finality? I just don't see that working with human nature of "one last thing" and the urge to spend an extra few minutes to hammer something out.
It's just laughable to me to bother with a "ends five minutes early" option. It just doesn't work - you know you're not cutting into anyone's next meeting by consuming those last five minutes. But you can't know that if you push into the next half hour block - maybe they have a customer call up next that starts on time, so you have to wrap up.
This contrast is an incorrect assumption. Outlook does allow starting meetings late as well as ending meetings early, with somewhat arbitrary durations. [1] I have definitely seen these options in Outlook settings (on web, since I hate Outlook).
However, I haven’t used it because the teams one works with need to be alerted and reminded of it before it sticks in their minds (if nobody else is using such settings).
[1]: https://support.microsoft.com/en-us/office/end-meetings-earl...
Whenever I'm having remote meetings with people using a Google meeting room, right at the hour they'll say "I'm getting kicked out", because the next person is waiting to use the booked meeting room.
Instead, I must invite 10 people to do other things while I talk on a zoom call! "Sorry, I was multitasking"
If that is the majority of your meetings, you are in a good place.
The mistake is to think the rules are what makes the meeting useful. Having the right audience, an agenda, and appropriate expectations for the outcomes are the useful things.
Except for the weekly release meetings, those can be 48.
If leadership blesses this cutesy little five-minutes-late maneuver, implicitly accepting that meetings don't end on time, then meetings won't end on time at 5 after the hour either.
Everyone wants to think their time is valuable, but this is relative.
Cancel useless ones.
Start and end on time.
If you're in-person in an office, there are plenty of times for random social interaction. If you're full-remote, pre-meeting/post-meeting time is a low-friction source of social interaction.
> How was your weekend?
Fine, just like literally thousands of previous weekends before this one. And now I’m going to ask you the same and then zone out for 5 minutes because I literally couldn’t care less.
This has nothing to do with being introverted.
Waiting for attendance is simply scheduled into the agenda. The first 5 minutes of the agenda is reserved for quorum. There is absolutely no need for making it any more complicated, or playing games with the scheduled time like the post suggests. Childish nonsense.
;)
Like this.
Aren't going to write themselves, are they? :D
> Starts meeting after 5 minutes
"Uhm, shall we wait for Jeff?"
“Jeff you didn’t show up to the meeting. What happened?”
Jeff is eventually put on a PIP or fired for not showing up to meetings without notice.
You get Outlook reminders 15 minutes in advance. Webex/Teams notifications 5 minutes in advance. I’m sure you can make your watch vibrate or something.
People at my office join every meeting 5 minutes late because no one expects meetings to start on time anymore. So I guess we’re following this advice in all but the nominally scheduled time. Drives me nuts.
In general a lot of people just aren't being serious about meetings, which I guess is also why many hate them. So key indicators of a bad meeting is: runs more than 60 minutes, no meeting plan, documents or talking points provided in advance, more than five people (unless the meeting is more of a briefing).
So 99% of my meetings?
Or are we all using catheters now?
My question is if people can't adapt to it, would it be a helpful technique?
Also conveniently, we also had the calendar data for internal meetings, internal VC software (not zoom) db that logs the participants when they join and leave meetings and employee function db.
I was serendipitously the lead DS for analyzing the effectiveness of the ‘starting 5 minutes past’. After joining and cleaning a lot of the data, the data showed:
1) at the start of the trial, meetings ended on time. Then after few weeks it slip to ending late, negating the usefulness. Other orgs did not see meetings running late. 2) ICs tend to stick around and over run meetings, while managers tend to leave meetings on time. 3) if I remember right, we had a survey data that showed pretty clearly that managers prefer the ‘starting 5 minutes past’ while ICs do not care or have negative sentiment.
The biggest predictor for people who prefer starting late is how crowded their schedules are. Managers tend to have very crowded schedules which means they want a break between meetings, while ICs prefer not having to waste time waiting.
In the end we reverted back to normal schedule. It was just easier for busy people to bounce early.
It's a relatively common term. I wouldn't read too much into it.
I'd rather not have by ass kissed with a term like "everyday innovator". -- "Individual Contributor" is fine.
E.g. If you aren't an SME or a Manager, then why are you in the meeting?
(SME encompasses PM and BA roles, as they too should be experts in their domain and ideally on the domain we are working on.)
It is unparsable Dilbert nonsense to anyone outside of specific scenarios. And it causes interminable discontent. Because what if the SME is the PM because they know business and tech but the SME is actually the IC because they know the tech and its tech but what if the manager is actually the SME because they're running the tech and may need to redelegate if the IC needs vacation, blah blah blah.
(job history: college dropout waiter => my own startup, sold => Google for 8 years => my own startup)
A human being who avoided corporate brainrot just writes “I worked with John and he was indispensable because (insert reasons you wrote here)”
I’m 37 and never heard of this acronym. That’s the entry-level version of my point. Not that other people hurt me or people knowing things is actually bad.
Or, if you truly do not need anyone but a "technologist" to deliver product, you must work in a pretty simple business space! I work in healthcare and our PhD's and MD's have a very, very different knowledge space than I do, I and I deeply respect their contributions.
ICs are generally considered highly valued staff.
if a company doesn’t intend to utilise IC then they don’t have ICs, just regular software engineers.
An IC is only an IC if the organisation is structured to utilise them as an IC. It isn’t a job title, it’s more to do with how an individual is utilised in a company.
> IC execute
IC plus engineers execute. IC are a subset of engineers.
Whereas IC having its own identity means it has many positive connotations. "I'd much rather be an IC, so I can get things done" etc. You can still be very senior without having direct reports or having to do line management, often seen as a necessary evil.
If, instead, you would be Tom, Bill and Biff, there is a risk that the manager would build attachment, and make it harder to treat you bad. If you're IC1, IC2 and IC3, you can be exchanged like machine parts when you break, without anyone crying.
Welcome to the modern world! =)
- Does it even need to be a meeting? Keeping meetings to things that need 'a discussion or decision', and keeping updates and announcements to chat or email works fairly well.
- Does the meeting give you any value, or do you bring value to it? If both are no they should decline it.
- Is there an agenda with expected outcomes? No agenda and no goal means it should be declined.
- Are you doing something that's a higher priority? Seeing one of my reports in a meeting when there's an active incident in progress gets me asking questions.
- Does the person running the meeting share notes afterwards? One thing I've noticed over the last couple of decades is that people are much happier to skip a meeting if they'll still hear about what happens afterwards. People don't skip them if being in the meeting is the only way to know about what was discussed or decided. I always encourage people to write some notes and share them if they've set up a meeting now.
If you're just a 'follower' of what's going on, that's fine. The problem shows up when you have some stakeholder or steering ability.
If you miss meeting about X and don't bring up discussion about Y then other person A may not talk about Z that affects X. But I agree that every meeting should have a point and total number of meetings should be minimized.
I have had a few senior managers (at Google) who ask for all the meetings _they_ attend to start 5 minutes late.
This seems 100% reasonable to me. No need for it to be an org policy. Just a affordance for the people who spend 95% of their working hours in meetings.
I've also had several senior managers at Google who _don't_ do this, but are 5 minutes late for every meeting anyway. This alternative is pretty annoying!
Even better is they only need to use that method when meetings actually run full time rather than every single meeting they are in
That makes 200% sense. A couple or more ICs tend to want to stick around to go off topic or drill down on some thing if they don't have a conflict. People who aren't expressly relevant to that or have a conflict drop at that time.
You're basically seeing the post-meeting hall conversation of the ICs in your data.
Covid is supposed to have started in October 2019, and no one locked down until nearly six months later.
What was really awful, however, was when your calendar was a random mishmash of starts at :00, :05, :30 and :35 :-)
Dunno if people here know this Paul guy, but he wrote about this: https://paulgraham.com/makersschedule.html =)
We did this at Google too while I was there (only the started 5-mins past part). It works really well.
No need to change the Calendar events though. It's just implicit that we'll start 5-mins past. (Or, well, explicit in MIT's case).
There’s a famous example from the Lucasfilm/Pixar deal: a Lucasfilm exec used to arrive late as a power move, until Steve Jobs started the meeting exactly on time without him. The exec walked in 5 minutes later and had already lost the room. And Jobs gets the deal.
Agree, but that doesn't solve the problem of back to back mtgs. In some cases people have to physically move from one mtg room to another, or they need to use the restroom, etc.
Having the 5 min gap really is needed for those types of things.
I think the point is to reduce meeting time from 60 minutes to 55 or even 50 and be firm about it. People need to expect to start and end on time; giving them a natural break between helps make this happen even for people whose job requires them to be in back-to-back meetings.
Personally, I think starting on the hour (or half-hour, etc) and ending "early" is better, because it tends to sync well with the calendars of external folks.
But in the end, moving start or end time is only part of the solution. This is a time-management problem, and in addition to constraining the available time, it also needs proper management of the available time within the meeting.
It matters because there sometimes are meeting where it is very important to know how much time you have to prepare appropriately. As long as the expectations are set beforehand, it matters less.
I roughly agree with the rest of your post. "Just be punctual" is a cop out that ignores the fact that I need to have enough breaks between meetings before I can even think about being punctual. Make space for breaks and enforce the time allocated is imo the solution, it matters less where exactly the 5-minute break fits (but I tend to agree that people would more likely end on the full hour, so that would mean we need to start 5 past).
Otherwise, people will simply come 10 minutes past if you start 5 minutes past.
In fact, having done it for so long, it surprisingly really annoys me when our vendors schedule 60 minute meetings on the hour.
Engineering Managers which see value in giving coworkers a five minute break between meetings ensure the breaks exist. Those which do not and only pay lip service to the concept will burn through predefined breaks no matter where they exist on a clock face.
Setting meetings to start at :05 or :20 or :35 or :50 adds friction.
Defaults matter for habit formation.
There is your golden opportunity to point out internal Gemini to the Calendar codebase and make it become reality.
Any meeting that goes over an hour has a mandatory 10 minute break at the 50 minute mark every hour.
If you're not on time..tough sh*t we're starting without you. Use the AI minutes or something to catch up.
People magically show up on time and pay attention and the meeting ends on time or early.
I have to assume this discussion is about the 90% of meetings that could have been a group chat or email chain.
This will surely solve the problem.
We mostly turned our internal and partner meetings around these days; meetings are organised and distributed by who thinks they are needed, everyone who could be needed is included (they basically have to answer when called upon during the meeting; that also keeps the meetings within bounds as no-one is going to answer anymore once the time passed) but they are called in only when needed which is to say, almost never in reality. This showed us the enormous waste of these meetings before.
48 more comments available on Hacker News