If you want people to show up, data shows these are the best meeting times
blog.boomerangapp.com
blog.boomerangapp.com
> Avoid Wednesday and Thursday afternoons. These are the most popular times to offer, meaning the potential for conflicts is high.
In case anyone else was interested in just their answer to the title question.
I always curse people who schedule meetings first thing in the workday, last thing in the workday, or immediately adjacent to lunch time. If the meeting is an hour long, I'll avoid attending an 11am meeting if I possible can.
Meetings that are adjacent to lunch are fair game. They just need to start/end on time.
Well, it can work, of course. I often have meetings scheduled like that. I hate it, though, because it means that I either have to cut lunch short or skip it altogether. A meeting may start and end at a set time, but I'll still need 10-15 minutes before the meeting to prepare, and sometimes 10-15 minutes after the meeting to perform action items that can't wait (such as updating my task list, my work notes, etc.)
(Lest people think that I value lunch too much, in nearly every place I've worked, taking lunch was required by management. If it weren't, I'd always skip lunch so that I could have an 8 hour long instead workday of 9)
The Wednesday one rings true. I always have an absurd number of conflicts on Wednesday.
EU and even more so Asia-based employees prefer to first discuss the idea on multiple 1:1s for a long time, to discuss / think / make decision with everyone, come up with some harmony before any formal meetings. And the meeting itself would serve only ceremonial needs -- to let the manager officially declare the idea live.
That creates cultural clashes, when some people schedule a meeting to discuss something, but others decline or don't understand why are they here.
This is so that the manager doesn't lose face in front of his subordinates. In the US, if the junior employee has a stroke of genius during the meeting and comes up with a better idea than the manager, then the manager just looks good for hiring that guy.
Not really, at least in my experience. Arguing against managers in Europe is common, sometimes I feel like more common then Americans expect. Americans tend to expect sort of submission - they interpret disagreement with boss as rudeness. "You can not say no to manager" is something Americans believe in and then they are shocked to come into meeting with Eastern European who just say "no" and acts as if it was normal.
The one on ones are to large extend about forming opinions, testing both ideas and arguments in safe situations, rethinking everything again. You can say something wrong in them and then figure it out next day and change opinion.
Instead of having one high stakes meeting where what you said is set in stone, you have to react instantly in well phrased arguments and don't have that time to think about others arguments.
Obviously life isn't so black and white but I am wondering where these generalizations come from.
The two are two different issues, basically. Also, the directness of a discussion kind of depends on a topic. Americans tend to be hierarchical and tend not to want to hear negative things. Eastern Europeans are more likely criticize, express doubts or pessimism. These are seemingly taboos for Americans. But that is kind of orthogonal to the meetings topic.
I can’t speak about other Europeans or their culture, but here in Eastern Europe we historically had very little education in presentation, debate skills and critical thinking. So people have strong opinions, but little skill in presenting or confronting them with other perspectives and ideas. Of course, it never is all black and white. But this is my own experience with tech millennials at least.
Americans (at their best) are in some ways the opposite - they’re good at diplomatically navigating a variety of imperfect voices to arrive at a mutual agreed upon point of view. Coming with that (idealized) American mindset into Eastern Europe isn’t easy.
I think this is reasonably accurate. It's rather necessary in order to be able to function in a nation where you are interacting with a huge variety of people with a huge variety of sensibilities, from all over the world.
I am a genuinely positive person and my interactions reflect that. But I have learned to to be more dour when interacting with people from other countries (mostly from European nations) because they think I'm being phony.
The thing is... I'm not. Being dour to put them at ease is me being phony, but they'll accept that as being "authentic".
So much bizarreness all around.
> They just try hard to make the words very polite. So polite, that Europeans take that for positiveness or indirectness.
Read: Fix your shit. Or give me a good reason to not block your PR until hell freezes over and we all need ice skates.
Phrasing things like this works well with junior developers. They feel safer having an opinion or asking questions.
My enlightenment was that this meaning is so instinctive to me that I doubt that it would occur to me that it could be misinterpreted.
Polite and direct to me would be something like "I think you should change this code".
This is probably why the vast majority of meetings I've had in my career have been utterly without value -- productive discussions, brainstorming, and decision-making rarely happen in those meetings.
When I became the leader, I was informed that we also needed to hold "Officers' Meetings" every month, just prior to the general meeting. The purpose of the Officers Meetings was to come to rough agreements on big issues, before they were put to a vote, and also to set the agenda for the upcoming General Meeting. With a set agenda on paper, we were much less likely to deviate from the action items listed therein.
Unfortunately for me, it proved impossible to schedule Officers' Meetings, because of facilities considerations and nearly nonexistent turnout. I held some at my own home and one person would attend. It was wholly ineffective for the intended purpose.
We also had trouble splitting off into Committees. If a significant event was planned, such as a breakfast, then it was logical to form a committee and then have them form up and communicate. This committee should be in touch via email/phone of course, but also hold planning meetings where details of the event could be hammered out. Unfortunately, due to low participation, these Committees never did their own thing, and instead were folded into the General Meetings, wasting everyone's time discussing things like bacon and napkin counts.
I really tried. I tried to stick to the prescribed structure of the meetings; I tried to set an agenda and stick to it; I tried to redirect endless debate and discussion into more productive action. But as a first-time leader, I found out just how limited my power really was, and the sacrifices we make as servants, when the organization is dysfunctional and we're just trying to stay together as an informal family unit.
The meetings where decisions are made can be large, because that gives legitimacy to the decisions. Discussions tend to happen in smaller groups, because it's impossible to have an actual discussion with more than about six people. If there are more people, some will dominate the discussion, while others will remain silent.
Perhaps things are different at the top of the tower, but in my experience if your meetings are regularly longer than an hour I'd say you're doing it wrong, or you're holding a workshop and not a meeting.
Get the right people in the room, have a clear agenda and someone to lead the meeting if needed, and it's rare that more than an hour is needed. Often far less. At least in my world. My most productive meetings are around 15-20 minutes.
If you're holding a workshop then I agree, take breaks.
What do you mean by "top of the tower"? If you refer to my position as software architect, that has nothing to do with it.
I worked at many companies and meeting length was ALWAYS a factor of the company culture not of my role.
Personally I schedule meeting that take 45 minutes max. Most of the time i schedule 25 minutes. The 5 minutes are so people have a break in their Outlook calendar.
I meant the executives, board members and such. Poor phrasing on my part.
> The 5 minutes are so people have a break in their Outlook calendar.
This is a good point. Multiple consecutive meetings with no break sucks.
In my former life as an employee managing teams and projects, I was infamous for having meeting scheduled for 30 minutes which ended in 20 with a plan of action as output.
Long meetings are such a waste.
Breaks are good when you're having half-day or all-day meetings. For example, when someone has travelled to the office and you're meeting all day.
For regular meetings with your normal office mates, if they're so long that you need to insert breaks then they should probably have been separate meetings.
Having everyone leave the meeting and then slowly meander back in always takes longer than it should. That 5 minute break can turn into 10, 15, or even 20 minutes as you try to track down the last person who wandered off and then got pulled into something else.
Just make the meetings concise enough to handle without a break. If you have more material, schedule a separate meeting for it.
I don't think any meeting should go on that long, period.
That quick break has made a huge difference.
Definitely counterintuitive, the strength of the effect (2.4x acceptance rate for 3+ options) was eye opening.
> The best time to schedule a meeting is at 11am Monday morning... this time period has the least potential for conflicting with other meeting invites.
> Avoid Wednesday and Thursday afternoons... the potential for conflicts is high.
> Providing three meeting slots will suffice. [The article actually says seven, but only because it's content marketing for an app that lets you offer seven slots]
> Time of invite matters. Adding a last-minute event to someone’s calendar probably won’t be well-received
As much as I have afternoon meetings, either first thing in the morning, or after lunch is best. Gives enough time to get stuck into things without disruptions.