|
1) Paint blue circles on your eyelids, and try not to snore.
2) Always take the minutes. It's a thankless boring job, but ... it has its compensations*
* The minutes are the official record of the meeting: if it's not in the minutes, it didn't happen. Conversely, if it is in, it did. So if you write the minutes, you control who gets what actionables. Get my drift?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That's a major reason why I avoid meetings and insist on E-mail. You get a full paper trail, and people can respond to individual points without interrupting or being interrupted.
In meetings, my boss hears only what he wants to hear.
|
|
|
|
|
As somebody said: Quote: "The IQ of a meeting is equal to the IQ of the dumbest member divided by the number of people attending.”
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I always thought the IQ of a meeting was calculated by assuming IQ is a resistance value and we add the resistance in parallel.
|
|
|
|
|
1 Have a concise agenda.
2 Give people more than a 5 min notice about the meeting.
3 Make sure the right people are there.
4 Respect people's time. If the meeting isn't moving along... move it along.
5 Respect people's time. If the meeting gets off-course... bring it back to course and take whatever off-course chat that needs to happen offline.
But, the most important thing is...
Nerds love to never agree. They love to argue. They never love to commit to an answer for fear of looking wrong. So, the absolute most important thing to understand is, take your time to hash crap out. But after the arguing phase, once y'all agree on something... agree on it and move forward. If things need to be changed later they can be, but later. If the right decision makers didn't get to chime in, you set the meeting up wrong and wasted people's time.
The worst thing that can happen is to have a useless meeting where nothing gets decided or done. People will zone out and it's just going through the process so you can appear productive even when you're not.
Jeremy Falcon
modified 27-Jan-23 13:04pm.
|
|
|
|
|
And if you're simply going to tell people to do what you tell them to do and not allow dissent, then don't have a meeting.
|
|
|
|
|
Been there done that. The ol'... "we just want you to agree with what we're going to do anyway."
Jeremy Falcon
|
|
|
|
|
"Nerds". You above that all?
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Not sure what you mean... but I'm a total nerd. Clearly... I'm on CP.
Don't go be all over-sensitive now. It's Friday. Lighten up.
Jeremy Falcon
|
|
|
|
|
Objective criteria
1 Have a concise and precise agenda. Concise is the optimal word.
2 Give people at least an hour (5 minutes is too short) notice about the meeting. If it pops up too quickly people will tend to ignore it (my experience).
3 Make sure the right people are there. Absolutely
4 Respect people's time. If the meeting isn't moving along... move it along. Absolutely
5 Respect people's time. If the meeting gets off-course... bring it back to course and take whatever off-course chat that needs to happen offline. Absolutely
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I would add:
6) Everyone is muted except the current speaker. If there’s a question or comment, wait your turn or raise your hand. If possible of course.
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
Mark
Just another cog in the wheel
|
|
|
|
|
Have an agenda; or you'll be the agenda.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
turn on camera and have a good agenda
diligent hands rule....
|
|
|
|
|
. keep them as short as possible.
. make sure only people required are invited.
. have an agenda.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
u failed to mention if its with a client or a co-worker
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Avoid meetings, stupidity is contageous.
|
|
|
|
|
If the meeting is to arrive at a decision, then have your RACI matrix or equivalent defined before invitations are sent to know who to invite and who will have final decision (R).
Ensure that R knows they are making the decision.
|
|
|
|
|
Same ones that work completely to make in person meetings effective.
...hmmm...oh wait...I forgot those don't exist either.
|
|
|
|
|
Do not invite rabble-rousers.
Make sure the agenda items will be pertinent for all invitees; anything that is not should be kept to a brief (30 second) summary (I despise all-hands meetings because they do not take care to do this)
If agenda items will not/do not pertain to a person, do not invite them.
iow do not waste my time. I enjoy meetings where work gets done, decisions get made, pertinent information gets shared, and therefore camaraderie gets built.
|
|
|
|
|
Cpichols wrote: Do not invite rabble-rousers.
Certainly no point in inviting anyone that is going to point out that the 'new' idea either can't work at all or it would take years to implement. After all reality isn't needed.
|
|
|
|
|
Some meetings are useful and important. Many more aren't.
As with all meetings (remote and otherwise) have an agenda ready beforehand and stick with it. And be uncomfortably brutal with asking yourself and others "Is this meeting necessary?" and behave accordingly.
When the discussions stray off the agenda quickly ask for that to be taken to a discussion afterwards between the parties that actually need to discuss.
Have a clear ending when done and let people escape who need to. Those that want to talk more at that point might be free to do so, I guess.
|
|
|
|
|
Most of this has already been said. But
1. Agenda - and do your best to stick too it.
2. Concise - Not just the agenda but the time. If you scheduled for an hour but only need 42 minutes. STop at 42 minutes.
3. People Management - Those that yell loudest need to be stifled(a bit) and those that are shy need to be encouraged. Get something from them. You invited them to hear their opinion. Get it. and DO NOT let them be overtalked by the loud ones.
To err is human to really elephant it up you need a computer
|
|
|
|
|
Stop having them...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Fewer. It is possible to meet once a week, look at what was done the previous week, what needs to be done the next week, and assign as makes sense.
With rare exception, have team members use ad-hoc communication (e.g. Teams) to communicate directly with only who needs to be involved.
Hire or train your people to act professionally, take ownership of their projects and assignments, take initiative, use their abilities, and just get it done. Don’t hire or keep those whose best effort is to follow a recipe book and unable to use deductive reasoning.
|
|
|
|
|
I literally had a conversation this morning where we hit all four popular things programmers say:
"It works for me"
"It worked a couple days ago"
"Huh"
"The JSON is bad"
|
|
|
|