Meetings are Bad For You 283
19061969 writes "Though this is obvious to most of us, your PHB's might benefit from knowing that meetings are bad for you. Two psychologists have found evidence that the number of and the time spent in meetings has a detrimental effect on mood. "...a general relationship between meeting load and the employee's level of fatigue and subjective workload was found", write the authors after conducting a diary study. Perhaps we should be more understanding with our moody bosses?"
Memo from your PHB (Score:5, Funny)
We need to have a meeting to discuss these findings!
Re:Memo from your PHB (Score:4, Funny)
DT
Re:Memo from your PHB (Score:2)
That's okay - I have a doctors' note.
Things are different in sales (Score:5, Interesting)
I work in sales. The more that I can understand our products, the better of a salesman I can be. I"m not the type of person that will try to make up things because they want products to look good -- instead, I try to be as knowledgeable as I can, because from what I have seen, the more knowledgeable that the buyer sees that I am, the more trusting they are of me, and therefore more willing to buy what I am selling.
I don't spend a large amount of my time in meetings, but at least for me, the meetings that I am a part of, each bit of information that I receive on a product ends up selling at least another few units, so they're great for me.
Re:Things are different in sales (Score:5, Funny)
Therefore, you CAN'T be a salesman.
Except for the part about liking meetings. Every sales guy I've worked with loves meetings. They want to have meetings for everything - except when they're booking my time on conference calls.
Re:Things are different in sales (Score:3, Interesting)
Re:Things are different in sales (Score:4, Interesting)
On the other hand, when I ask a question and they obviously don't know but make something up or change the subject or tell me I don't want to do that anyway....
Re:Things are different in sales (Score:5, Funny)
Gak! One of them has breeched the outer perimeter and is posting on Slashdot.
Rally the forces, we must stop the incursion of salesmen onto technical forums before the damage is too great.
I sense a great tremor in the force.
Re:Things are different in sales (Score:5, Funny)
Rally the forces, we must stop the incursion of salesmen onto technical forums before the damage is too great.
An example of two statements with no relation to each other.
Re:Things are different in sales (Score:3, Insightful)
Re:Things are different in sales (Score:2)
Not to mention all the meals, drinks, swag, gifts, bribes, etc that you probably get. Oh, and the commission, for selling things that don't exist. Oh, and for promising ridiculous things to the clients that cause many people to work extra hours to deliver it.
At least, that is what our sales team does.
Re:Things are different in sales (Score:3, Interesting)
Re:Things are different in sales (Score:3, Insightful)
I don't know what kind of meetings you go to, but this is exactly WHY they have sales meetings. Instead of having all those people running around making their own interpretations about the product, coming to possibly different conclusions, or getting incomplete information, then having to contact the vendor and clarify, they get them all into one room and do it all at the same tim
Re:Things are different in sales (Score:3, Insightful)
It seems to me that extraverts (who tend to predominate in sales, marketing, and the upper strata of management) are obviously going to enjoy the atmosphere of a meeting far more than introverts (who tend to predominate in programming and other nose-to-the-metal jobs). Other things being equal, an extravert actually gains energy from being with a
Re:Memo from your PHB (Score:5, Funny)
Re:Memo from your PHB (Score:2, Funny)
Well, no freakin' kidding! (Score:5, Funny)
In other news, the sky is blue.
Re:Well, no freakin' kidding! (Score:5, Insightful)
I have found that one meeting a week is sufficient; I tell people where I'm at on what I'm working, what my schedule looks like, and to remind them to provide me with concise details for any projects they may have upcoming. Past that, the odd development meeting where I might have to collaborate with someone, but the fact is you should only ever really have to have one meeting to determine who does what, and then actually give them the time to do it.
Re:Well, no freakin' kidding! (Score:5, Funny)
Looks grey from where I'm sitting. We should have a meeting to discuss this.
Yeeeaaaahh... no. (Score:5, Insightful)
Perhaps not. Most meetings are scheduled by said moody bosses because they can't be bothered to read their email or meet one on one with the people who are actually getting work done. Sure, they're busy otherwise, but most of the reason they're busy is because of this meeting culture that equates sitting around a table talking about what you're going to have your minions do (as soon as they get out of the meetings you force them into) with getting code written and products shipped.
The main reason I hate meetings so much is because I get the impression that the only people getting anything out of them are the ones contributing nothing useful to the project in the first place. I don't care if your job is to sit between me and your boss, if you can't keep up with a project you're a part of without dragging me away from my actual work to hand-hold you through what's going on twice a week, you're wasting my time.
That was 90% of the meetings last place I worked, and this accounted for probably half the reason I got fed up with the place and quit before Christmas. Maybe I'm just not cut out to work somewhere that has more than a few employees, and I've never claimed to be a people person, but everybody I talked to felt much the same way, so I feel at least somewhat validated.
Face to face contact is great, but the instances where that face to face contact's value outweighs the cost of herding a bunch of people into a conference room for a chit chat are few and far between when there are deadlines to meet, IMHO.
It explains a lot... (Score:2, Informative)
Re:Yeeeaaaahh... no. (Score:5, Insightful)
That was 90% of the meetings last place I worked, and this accounted for probably half the reason I got fed up with the place and quit before Christmas. Maybe I'm just not cut out to work somewhere that has more than a few employees, and I've never claimed to be a people person, but everybody I talked to felt much the same way, so I feel at least somewhat validated.
Indeed, maybe you aren't. But assuming you want to join a successful company that will be around next year, you won't be able to avoid it.
I have gone through a few start-ups and can tell you, the number of and importance of mettings is directly proportional to the number of employees at a company. When you first start out and have 4-6 engineering people working in a small office, you don't need meetings. Everyone is on the same "team", everyone knows what everyone else is doing, if you have a question you just spin your chair around and ask.
Fast forward ahead 6 months to a year, assuming the company is a success, you now have 15-20 engineers. You are no longer within casual talking distance without shouting across the office and disturbing everyone. As well, there are at least two teams with different taksk, each having their own project leader, eahc of which reports to some kind of head-hauncho. Now, said hauncho must also report to the sales guys, the CEO, the board, deal with employee issues, overall project planning, etc. He absolutely does *not* have time to do all this, and also keep tabs on 20 other people, no matter what kind of superman he is. This is why authority is delegated to the team leads, and why there *has* to be a meeting between him and the team leads ot keep him up to speed. There are certian things that just go way faster face-to-face than via email communications, and weekly status updates are one of them, because they involve a lot of back-and-forth questioning.
Now, assuming said company stays successful, in another few years you'll have some 50-100 engineers working on multiple teams, which not only need to report to the boss, but also interact with each other, as their projects likely overlap. Of course there has to be meetings for this as well.
Sample meeting... (Score:2, Funny)
OK then. To counter that, bosses should never assign work, or require work be done for a meeting. Make it more like, "Yo dude, what's up?" "Cool." "See Ya."
Fast Meetings for Me! (Score:2)
"I gots this"
"This thing sucks, and I did this -- how 'bout you?"
"Oh, I did this thing, and broke the build."
"Ah-ha, you get the chicken!"
Meetings should be over before your coffee gets cold. More time for work = more productive. People typing in meetings shouldn't be there.
Re:Sample meeting... (Score:2)
Depending on dialect, this meeting may be one of the best, most concise meetings you'll ever be witness to.
Project manager: Yo dude, what's up?
Translation: Good morning and thank you for coming to this little impromptu meeting. Please provide me with an overview of our status on the widget project.
Programmer: Cool.
Translation: We are currently on schedule and there are no projected changes to the future schedule. I am unaware of any outstanding problems or decisions re
I don't understand (Score:5, Funny)
Re:I don't understand (Score:3, Interesting)
1. Get to know your boss's boss(es). It never hurts, and gives you some leverage over your boss.
2. The only thing a boss like that is going to know about what you're doing (and therefor what his job is) is what you tell him you're doing. Start leaving out information that your boss is likely to be asked about in his meetings with his bosses, without being obvious about it.
3. Eventually, due to step 2, your boss will find himself unable to answer questions on a regular b
God I hate Marketing (Score:4, Funny)
No shit
Having to sit with them for an Hour as they drivel total Bullshit, is enough to give anyone a nervous breakdown
Re:God I hate Marketing (Score:5, Funny)
Do you think that "Meeting related stress and depression" would get me off with diminished responsibility , if i perform a killing spree.
If so , I am going to invite the marketing department on a hunting trip
Re:God I hate Marketing (Score:2)
I'm contracting to do web development for this company right now, and they put me under the marketing department because my work "Has more to do with marketing than it does with IT."
While I can see the point they're trying to make, it still doesn't shield me from all the crappy ass copy rewrites these guys do.
I once saw these guys argue over whether to use the word "synergistic" or "co-operative".
Re:God I hate Marketing (Score:3, Funny)
I think the Point they are trying to make is
Boss : My ex-wife was a Web Developer , she ran off with my brother and half my money . SO YOU MUST PAY FOR HER SIN
Shooting yourself in the foot? (Score:5, Funny)
Am I the only one that found this whole statement funny? I would think that they would release the paper to trade magazines and such to get their findings out, rather than waste time with meetings about how meetings are bad. That sounds like shooting yourself in the foot to me.
Re:Shooting yourself in the foot? (Score:5, Informative)
Re:Shooting yourself in the foot? (Score:2)
Re:Shooting yourself in the foot? (Score:2)
But shooting yourself in the foot could be a good thing if you're trying to demonstrate that guns are dangerous. ;)
Too few meetings can be bad too (Score:5, Insightful)
reminds me of a story... (Score:5, Interesting)
Re:reminds me of a story... (Score:2)
Re:reminds me of a story... (Score:4, Funny)
A novice asked the master: ``In the east there is a great tree-structure that men call `Corporate Headquarters'. It is bloated out of shape with vice presidents and accountants. It issues a multitude of memos, each saying `Go, Hence!' or `Go, Hither!' and nobody knows what is meant. Every year new names are put onto the branches, but all to no avail. How can such an unnatural entity be?"
The master replied: ``You perceive this immense structure and are disturbed that it has no rational purpose. Can you not take amusement from its endless gyrations? Do you not enjoy the untroubled ease of programming beneath its sheltering branches? Why are you bothered by its uselessness?''
Re:reminds me of a story... (Score:4, Funny)
*****************
(I do like the original story though...
Because- (Score:5, Funny)
Something needs to be done about meetings... Perhaps more laws, counselling, medication... for the children.
Medication is Meeting Alternative? (Score:2)
Re:Medication is Meeting Alternative? (Score:2)
Productive workers (Score:2)
Considering the cash blown on the .com boom you'd hope a lesson or two would have stuck.
__Funny adult videos daily [laughdaily.com]
Balance is the key (Score:2, Insightful)
Key is to not invite non-Stakeholders. Certain meetings are needed for people to feel empowered to produce and cetrain meetings just make people wither on the vine. What you want to accomplish at the meeting?
Don't just sit there, do something! (Score:5, Interesting)
The biggest problem, in his opinion, was the number of meetings that they had in order to discuss the projects they were working on. Frustration built up among employees due to not having enough time to actually do the work, as well as the number of times that he was interrupted in the middle of doing something productive - simply to go to another pointless meeting.
In his opinion, these meetings caused just as many problems as they tried to solve, and ironically, they would sometimes generate more meetings to discuss how far they were along in meeting their original deadlines.
I would tell you more about it, but I have a meeting to attend.
And Dilbert blushed (Score:2)
My last job (that I quit in frustration) was very much like that.
We used to have meetings. All the time, even to the point where our projects would run late because of the damn meetings.
Our PHB's solution?
Mandatory overtime for the entire department. And - the punch line - an additional meeting every morning for status reports.
True (?) Meeting Story (Score:5, Funny)
Work Safely! Accidents cause Meetings!
Correlation is not causation (Score:2)
Maybe an employer who schedules a burdensome number of meetings is also likely to encourage a workplace that increases employees' fatigue. I don't see any proof of causation here.
Objectives. (Score:5, Interesting)
1)Pool expertise from different departments
2)"Gather" authority for cross-department tasks
3)Get feedback and progress reports from different departments
4)Discuss critical issues that require human interaction
5)Criticise new products and techniques from different points of view
6)Brainstorm
When used properly, meetings can be powerful tools... But the ONLY reason I see meetings being used anymore is POLITICS! To palm off responsibility, blame someone else, avoid work, act important, establish power ("I called a meeting because I can"), or just generally be a waste of organizational oxygen. No wonder people hate them... The last thing most techs and researchers want is to get mired in office politics.
A meeting conducted properly is a huge help. It can speed up things and make your goals and objectives a whole lot clearer than they ever were, but unfortunately some people just don't seem to get that.
Meetings are fine (Score:2)
In most meetings at least one person is dozing off a bit.
The problem isn't meetings, it is too many meetings to the extent that the time taken to do the job is occupied by meetings so there is no time to do the work in hand.
Are you lonely ? Call a Meeting (Score:5, Funny)
Are you Lonely ?
Don't like working on your own ? Hate Making Decisions ?
Then Call a Meeting !!!!
YOU CAN...
SEE people
DRAW Flowcharts
FEEL Important
IMPRESS your collegues
FORM subcommittees
MAKE meaningless recommendations
All on Company Time
MEETINGS
The pratical alternative to work.
Re:Are you lonely ? Call a Meeting (Score:3, Funny)
The guy took 45 minutes to 1 hour EVERY DAY of a 10-man team (all consultants and payed by the hour) for the purpose of making himself look useful.
A couple of guys slept during most of it, another instant-messaged and the rest of us felt our life-force been sucked out of us, slowly.
The meeting where 95% of the time pointless, and the guy scratched endlessly on his notepad every single word, nice and slowly (we had to speak slowly so he cou
disturbing paragraph from article (Score:4, Funny)
Rogelberg has delivered this insight in a talk called "Meetings and More Meetings," which he presented to a meeting at the University of Sheffield. He also does a talk called "Not Another Meeting!", which has been well received at two meetings in North Carolina.
Extremes are bad (Score:2)
Re: (Score:2, Interesting)
Experience with meetings - waste of f***en time ! (Score:2, Interesting)
Re:Experience with meetings - waste of f***en time (Score:2, Interesting)
I worked in a group - developing marketing software for MCI back in the mid-1990's. Our manager decided to order 4 pm meetings everyday especially on Friday. These meetings lasted until 6 or 7 every night. He of course did not show up, his staff people ran the meetings. After attending a few of those meetings, I came to the conclusion they were a waste of time. I
They have a cost, but also a benefit if done right (Score:2, Informative)
Like the URL says (Score:2, Informative)
The article is poking fun at the study. The author of the article is the organiser of the Ignoble Prize competition.
tps (Score:2, Funny)
I enjoy meetings (Score:5, Insightful)
so don't blame meetings. I expect most meetings are bad for you just because most *people* are stupid, boring, selfish, ignorant, incompetent and more likely to get in your way than not.
Re:I enjoy meetings (Score:2)
Re:I enjoy meetings (Score:2)
Look at the source of the article (Score:2)
"Marc Abrahams is editor of the bimonthly magazine Annals of Improbable Research (www.improbable.com) and organiser of the Ig Nobel Prize"
(emphasis added by me)
ie, to all the people complaining: this is supposed to be flaming obvious.
Cheers,
Ian
Meetings (Score:2)
This whole face time thing is ridiculous. We've got technologies to handle that these days.
When I was a director of an I.T. I had two meetings I had to attend per month. One was a weekly meet with my unit for status updates, the other the weekly senior staff meeting. Then once a month I had the technical advisory meeting which I actually blew off a couple times because the office came first.
Otherwise ever
academic psychologists are bad for you (Score:2)
Meetings as a way to expedite the project (Score:5, Interesting)
At this meeting was a very old and experienced PhD who knew everything about the project. He regarded the meeting as an opportunity to display his knowledge at length, but had nothing of substance to put forward; after all, it was his design decisions that had caused the mess in the first place. Did I mention he was now a contractor and paid by the hour?
I know nothing about the branch of engineering concerned but I did go and ask the technicians what they thought. They knew the answer perfectly well - the material of a major tubular component was completely underspecified and was leaking gas when the plant got hot. But the PhD refused to accept it.
We didn't exactly draw straws for who would bring it up - but suffice it to say that I ended up with the short one. The result was an hour or so of listening to the worst metallurgical bullshit I have ever endured. But in the end we got our way, the components were replaced, the system started to work, the PhD was let go, (and a year later I was the engineering manager - it seems the MD had been reading the minutes).
Proof if proof were needed that the real reason for meetings is to drive the engineers to the point at which they will risk their jobs and their credibility to find a solution that means they don't have to go to any more meetings.
Technology and communications skills (Score:5, Interesting)
But the most important thing is that we keep those calls short, and don't need to use them to convey basic information to each other because we do that all the time using e-mail, IM, and a rich portally-intranet-ish web presence.
But the only thing that really makes those supporting technologies a viable replacement for endless facetime is decent communications skills. Being able to cogently write what's on your mind, provide a usable spreadsheet or document that illuminates the matter at hand... even being able to use IM without it decaying into a meandering social tarpit.. those things require a little bit of practice and discipline. But they buy you productive, asynchronous communication that liberates you to work on your actual job on your own schedule.
In-person meetings are saved for when it really matters: gaining and keeping paying customers. Oh, and free food.
irony (Score:2)
Rogelberg has delivered this insight in a talk called "Meetings and More Meetings," which he presented to a meeting at the University of Sheffield. He also does a talk called "Not Another Meeting!", which has been well received at two meetings in North Carolina.
Oh, the irony...
My approach: (Score:2)
Video game industry meetings... (Score:3, Funny)
SETI @ home for your brain (Score:2)
At the company I just left, sometimes we would lose half our work week in pointless meetings. So if I knew we were going to have a long meeting, I'd bring in a bunch of printouts and scatter them around in front of me. And bring a notepad and scribble until someone asked me a question.
But I wasn't coding. I'm a hobbyist woodworker, and I would be making plans for stuff I'd want to do at home later on that day.
The way I see it, it's kind of like running SETI @ home, but for your brain not your PC. Th
Maybe it's just you (Score:2)
Other things that are bad for you: (Score:4, Funny)
2. Drinking the kool aid at a meeting where business developers are present.
3. Falling for the "everyone please send HR a fresh copy of your resume to update your files" ploy
4. Trying to calm down a frantic coworker that is freaking out for a very minuscule thing without at least some caffeine courage.
5. Drinking the last cup in the coffee urn. I can promise you this: it will taste like boiled crap.
6. Eating that last donut from the meeting 3 days ago. The Krisky Kreme box has not moved from the coffee pot table and that one donut looks tempting as hell, but trust me: you don't want it.
7. Come-to-Jesus meetings for a project that is not yours.
8. Any brainstorming meeting involving your newly hired business developer, especially since you don't have a formal "business development" function.
9. Trying to explain to a frantic coworker that mail.app is not crazy and it is not ignoring rules.
10. Trying to explain the same coworker that classifying mail as "ham" helps the filter learn what makes a good email and avoids false positives.
My personal experience (Score:5, Interesting)
I've had three hour meetings where the only conclusion and main focus of the chat was what colour green to place on a website background (the website, incidentally, never got off the ground). And they paid me for that time. Now, I don't mind doing stuff that people are paying me for so long as it's something that I can do (I wouldn't say I could fix something if I couldn't), however I try to avoid all meetings now with those same people because it degenerates into a waste of five or more people's time, money and effort, distracts them from the real work and doesn't actually achieve anything we couldn't do with a poll on a webpage. I could make money from sitting in a room and gabbing nonsense but I consider it a real waste of my own time and talent.
One of the reasons that I won't work 9-5, mon-fri, for someone I don't like is that I can call things what they are if people ask. I've never sucked up to a boss in my life because I've never had one. I've had clients, whom I visit initially to determine their needs and then work for, but I avoid "meetings" at all costs.
Meetings are generally without any sort of focus, any conclusions, any change of opinions. They usually are either explaining things that people don't need to understand ("the network is broke, we're fixing it, it'll take a day and cost us X amount of money" is a perfectly good explanation for someone who's not technically minded), letting people spread responsibility for difficult decisions (or even just a comfort blanket for those same decision-makers) and attempts at micro-managing things that those people just don't understand.
If you have a group of colleagues who are all working on very intertwined things, they will form their own meeting either 1-1 or in small groups. They'll have to, and they'll do it a damn sight better than you organising a meeting for them all to check up with you. If you are managing people whose job you could not do yourself, stay out of their way. Maybe find them once a month or so, just to check that everything's working and that you're aware of any major problems. You hire people into a job to do that job, not to make them spend hours in a meeting explaining things they learned twenty years ago to you because you know nothing about that area.
I find that nonsensical meetings only come about through management. Managed-meetings are rarely productive. Having said that, there is a difference between a meeting and a chat. Chat to your staff, make sure they are okay, make sure things are on track, congratulate them on a job well done but bow to their expertise. If you invite someone to a meeting, it's because they absolutely HAVE to be there. If you are having a meeting with a IT vendor and you couldn't tell the difference between two products without the salesman's help, you need your IT guy there, to tell you and the vendor exactly what you want and don't want. But then, why are you there in the first place if you don't know what you're buying?
Meetings can be so useful in the right hands, but 99% of the really important decisions are made or can be made when those self-same people pass each other in the corridor, or pop into each other's office/cubicle/cupboard to chat. That way, there's also no problem with disturbing each other from important work (they won't chat
FSM logic! (Score:2)
And the number of Prirates in the world is inversely related to the rate of global warming. Honestly, people who are in more meetings usually have to balance multiple projects for multiple people. Multiple projects means more work, and more stress, whether you are in m
In Summary (Score:4, Funny)
Wasting time posting to Slashdot to complain about meetings = Good.
Not all meetings are bad... (Score:2)
We use stand-up meetings in my workgroup every morning. The meetings are useful because it starts the day with everyone on the same page. By standing up, we discourage long-winded discussions and get to the point faster.
It works for us.
Comment removed (Score:4, Interesting)
The Boss Says (Score:2)
-The Boss
Bullshit Bingo! (Score:2)
http://www.bullshitbingo.net/cards/bullshit/ [bullshitbingo.net]
Making Presentations for Meetings (Score:3, Informative)
Having your manager review your presentation is bad.
Invariably, they will have recommendations to make. You could have spent your every waking moment working on this presentation, but that doesn't matter. They'll want to change a word here, make this boldface over here, change this color here, make this a line chart instead of a bar graph. They will want things changed. They'll want you to add tons of things which turn a simple presentation into something more like a narrative, a paper, or a book---something that someone could read without you even presenting it. Often, this has little actual affect on what's really being delivered by the presentation.
And, invariably, they'll want to review those changes again. And, of course, you see this coming, they'll want to change things again. Sometimes they'll even change things back to the way you originally had it. This process of change, review, change, review happens continuously up until the meeting is actually given.
What this has taught me is that it's best to hold your presentation materials until the day before the meeting, if possible, because it will dramatically reduce the amount of time allowed for the reviewer(s). Remember: The reviewer(s) are often people that have no real ability (or need) to contribute to the project that you're working on. These people exist solely to facilitate (i.e., add overhead). The less time you give them to review, the less time you'll be forced to make meaningless changes.
The most recent presentation I gave was reviewed by at least 50% of the group to whom I was presenting, including the two VPs (presumably the people who most needed to see the presentation). They all made recommendations. So, what's the point of me giving it exactly?
(Sigh.) I guess I'm feeling a bit demotivated today.
"Annals of Improbable Research" (Score:2)
http://en.wikipedia.org/wiki/Annals_of_Improbable _ Research [wikipedia.org]
http://en.wikipedia.org/wiki/Ig_Nobel_Prize [wikipedia.org]
I like the ones I go to (Score:3, Interesting)
My boss is extremely hands off, recognizing that I know what I need to do and that I get it done. When we have meetings, he usually takes us to lunch and discusses things over lunch. Usually less than half the time is devoted to work topics.
I have not yet had to go to a meeting that I felt was a time waster. The closest one so far was a meeting to discuss how we were going to prepare a response to a Request For Information.
Many of the meetings I go to are actually presentations to customers. Sometimes I am even presenting. In these meetings, I get to meet and converse with new people, and there is usually food, which is always good with me.
I guess the reason I don't have a problem with the meetings I end up going to is that they are not a distraction that takes me away from my work. When I go to a meeting it is because it IS my work.
Perhaps companies ought to give you a 1 hour project slippage allowance for every one hour meeting that they require you to go to.
Re:central insight (Score:3, Funny)
Re:bollocks (Score:2, Insightful)
Bad management often leads to a plethora of needless meetings.
I always like the approach of having meetings standing up - suitable uncomfortable, focuses minds, people soon only schedule meetings that are really required, and they are brief.
Re:bollocks (Score:4, Interesting)
-nB
you hit (Score:3, Insightful)
I've sat in too many meetings that went an hour simply because they were scheduled for that long. Most of the time, the information could have been covered in 15 min or less and the meeting leader winds up "filling" the extra time with mindless ban
Re:bollocks (Score:5, Insightful)
That's what "Too many" means...
Re:bollocks (Score:4, Funny)
*ducks*
Re:bollocks (Score:2)
Re:bollocks (Score:5, Insightful)
Most of the time, that reason is to make middle managers (whose job consists exclusively of writing memos and attending meetings) look busy. The more incapable the manager is of writing effectively and/or the more unwilling to have a record of exactly what they said, the more likely you are to have a full daily schedule of meetings.
Now watch as I reveal the one most evil and stupid word in modern business - communication. Not simply the actual fact of doing so, but the implication that communication solves all business problems, sort of like how everyone thought communication solved all marital problems back in the 80's when it was popular to say that. Communication is a load of horse shit. There is no such thing as a communication problem. Every "communication" problem in modern business is in fact a confidence problem. The information is readily available, but 2 things block its distribution: 1 - Managers don't like to go on record. They don't reply to e-mails, for example. They lack the confidence to go on record with whatever they want to say. Here's an idea - if you don't have the balls to put your "communication" on paper with your name on it for all to see, then STFU. If you lie frequently enough that committing anything to writing hampers your ability to work, then you need to be fired. 2 - For the reasons documented above, employees have no confidence in anything managers have to say. I've never seen anything cited as a communication problem that was not actually communicated in fact. "I guess we need better communication between you/your department and me/my department." has become the polite and meaningless mea culpa for the business age.
NO! We don't need more communication. We need to STFU and get back to work!
Re:bollocks (Score:2, Insightful)
Re:bollocks (Score:3, Insightful)
I've worked at several large and small companies over the past few years, as an employee and as a contractor. One thing I've found consistent is that meetings with contractors are concise and to the point because they are paying for the contractors time. Meetings with employees only seem to drag on.
Two things are needed for a meeting to actually be productive.
1. A good boss/moderator to KEEP THINGS ON TOPIC!
Re:bollocks (Score:2, Insightful)
Disdain for written communication (hard copy or e-mail) may not be due to lack of confidence. I'm not a manager but I've communicated via e-mail long enough to know that there are many "information exchange" (if you don
Re:bollocks (Score:2)
If you don't communicate, how do you know what to work on? How do you align your efforts with the business interests of your employer?
I've worked remotely for my employer for 6 six years. I look forward to meetings. Not through any personal need for social interaction, but rather that I can achieve more and accomplish my job more easily with meetings.
Re:What's the deal? (Score:2)
Sure. Of course I can only speak for meetings where I work, but I'll give it a shot. A meeting is an hour or so out of your day that could typically be spent get work done. It seems like meetings are most likely to occur just when I get on a roll toward solving a problem. We have some meetings that require us to travel to other
Re:What's the deal? (Score:2)
You may find an explaniation here [phdcomics.com]
Re:Psychologists Are Bad For You. (Score:2)