Minimal Meetings

  • Comments posted to this topic are about the item Minimal Meetings

  • Heh... supposed time wasted in meetings is the least of my worries. A bazillion emails and IM's are a total waste of time compared to the productive time of a meeting or face-to-face dialog. In fact, well structured and informative team meetings cut out a lot of the wasted time of emails and IM's in more ways than one. There's nothing worse than the moroff down the hall trying to get complicated information one bloody IM or email at a time over an hour of instead of getting off his ever widening butt to have a 3 minute conversation.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • For an instant I thought sending this editorial to our bosses. But I rollbacked this idea, I don't need to be such kind of a rebel.



    See, understand, learn, try, use efficient
    © Dr.Plch

  • Hey there,

    Nice post Steve! I agree that meetings can be a waste of time, but a question arise when thinking about it: How do you guys get information shared in a structured, clear, simple, quick way? Even if protocols are sent after a meeting people often don´t read them carefully, because they are a bit offended that they weren`t suppose to participate in the meeting.

    Cheer,

    Georg

  • Jeff makes a fair point, but it can work the other way too. So the real lesson is, use the best tool for the job and use it properly.

    Simples!

  • georg.schumann (4/26/2010)


    Hey there,

    Nice post Steve! I agree that meetings can be a waste of time, but a question arise when thinking about it: How do you guys get information shared in a structured, clear, simple, quick way? Even if protocols are sent after a meeting people often don´t read them carefully, because they are a bit offended that they weren`t suppose to participate in the meeting.

    Cheer,

    Georg

    Most time I am offended when I had to sit 1 or more hours on some meeting. And worst are the moments I said my minority opinion, I realized it was the truth, and I have the work to make things working.

    But I'm a programmer.



    See, understand, learn, try, use efficient
    © Dr.Plch

  • How about warning people that they might be needed, then you can invite them in if/when needed - and just as important, release them afterwards. That way information, time and expertise are used to greatest advantage, and people feel included and valued rather than bored and frustrated.

    A small note though Steve - can you make your editorials a little more suggestive (ie less dictatorial) in tone?

    Dave.

  • The root of the problem seems to be that managers consider meetings to be real work.

    Managers spend their time doing what appears to be busy work because that is their output.

  • Very true. It's worth pointing out the proportion of time spent on meetings from time to time.

    Anyone else here find themselves keeping the meeting on track, identifying milestones, tracking criteria, performance etc because their manager hasn't got a clue?!

  • eplot2 (4/26/2010)


    The root of the problem seems to be that managers consider meetings to be real work.

    Thumbs up!



    See, understand, learn, try, use efficient
    © Dr.Plch

  • david.wright-948385 (4/26/2010)


    Very true. It's worth pointing out the proportion of time spent on meetings from time to time.

    Anyone else here find themselves keeping the meeting on track, identifying milestones, tracking criteria, performance etc because their manager hasn't got a clue?!

    I'll agree with that... that's sometimes (many times) necessary. Meetings are also important in a "Picard" sort of way. One of the responsibilities of a manager is to surround him/herself with intelligent people, ask for opinions and expert ideas, and then make a decision. I hate it when managers make bad decisions simply because the people that work for them don't provide enough input.

    I believe Steve's editorial is mostly about having a defined purpose/agenda and actually getting something important done instead of just having (frequently uncontrolled) meetings with the wrong people in them. A good manager will know enough about the subject matter and their people to know who to invite and when. Personally, I like it when both GUI programmers and DB programmers are invited to design meetings... done correctly, it not only gives everyone a heads up and a chance to provide up front feedback, but it also develops a sense of ownership and, sometimes, comradary between three usually disparate groups (Designers, GUI programmers, DB programmers).

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • eplot2 (4/26/2010)


    The root of the problem seems to be that managers consider meetings to be real work.

    I disagree. The real root of the problem is most people haven't got a clue on how to organize and manage a meeting. Different structures are required for different purposes, as are different levels of direction and control.

    A well organized and managed meeting is worth the cost to the organization.

    As for cost to the company, I read about one years back that required everyone attending the meeting to clock in and a running highly visible toteboard keep track of the cost to the company.

  • I agree with that post above that most people don't know how to run or manage a meeting, or often just don't want to spend the time prepping for a meeting. It's so easy to call a meeting without really thinking about the impact, or the need to actually have a meeting.

    Good meetings are productive, and we definitely need ways to share information. But just calling meetings as a first reaction probably isn't the way to do it.

  • Who has time to read? 😛 Reading the results of a meeting can be just as wasteful. Meeting in person can help you pick up subtleties that don't end up in the report and can be misleading or misunderstood.

    BTW, Steve, I don't consider the tone of your editorials to be dictatorial at all.

  • Steve Jones - Editor (4/26/2010)


    I agree with that post above that most people don't know how to run or manage a meeting, or often just don't want to spend the time prepping for a meeting. It's so easy to call a meeting without really thinking about the impact, or the need to actually have a meeting.

    Good meetings are productive, and we definitely need ways to share information. But just calling meetings as a first reaction probably isn't the way to do it.

    Unprepared meeting with unprepared people is a way to the hell.

    I have one in my memory where I was the only one prepared (with about 10 pages of documents). Total waste of time (about two hours) of all attendants (five pcs). And even with total confusion for further meetings.



    See, understand, learn, try, use efficient
    © Dr.Plch

Viewing 15 posts - 1 through 15 (of 39 total)

You must be logged in to reply to this topic. Login to reply