Meetings, Meetings, Meetings and not an outcome to drink

It would be fair to say that when working with customers defining or implementing BI strategies or architectures, I spend a bit of time in meetings with them.

Meetings are always booked for at least an hour often two.  (as compared to workshops that are normally 1/2 a day or a day). Sometimes you get the dreaded “I have booked this for two hours just incase but we shouldn’t need all that time”, true, but surprise surprise we always use the full two hours anyway! Often the meeting is a talk-fest with no clear outcome stated at the beginning.  Or if an outcome is defined the meeting gets railroaded and off topic.

So that got me thinking, what should the outcome of a meeting be:

• Sharing Knowledge
  Somebody wants/needs to pass information on to others.  This can’t be done via Yammer, Blog, Wiki or even email, so a face to face is needed.
  • The participation component of this is for attendees to listen.  You can ask questions to clarify your understanding but that is it!
  • Success is when at the end of the meeting the answer to the question “so is that all clear” is a set of nods.

• Identify Solution
  There is a problem/issue/idea that can be solved easier by getting input from a number of other people
  • The participation component of this is for attendees to contribute.  Bounce ideas and see what the collective wisdom can come up with.
  • Success is when at the end of the meeting there are some viable options to investigate further (you are not likely to actually find and agree the solution in the meeting itself).

• Review Something
  Somebody wants/needs to pass information on to others.  This can’t be done via Yammer, Blog, Wiki or even email, so a face to face is needed.
  • The participation component of this is for attendees to provide feedback.  You can ask questions to clarify your understanding but that is it!
  • Success is when at the end of the meeting the answer to the question “so is that all clear” is a set of nods.

• Agree Something
  There is a problem/issue/idea that can be solved easier by getting input from a number of other people
  • The participation component of this is for attendees to negotiate.  You can ask questions to clarify your understanding but that is it!
  • Success is when at the end of the meeting the answer to the question “so is that all agreed” is a set of nods.

• Have a good time
  Sometimes there is a need to get people together to just have fun.
  • The participation component of this is for attendees to party!.  Well maybe if its a meeting just to have a good time.
  • Success is when at the end of the meeting people are smiling and a sight of happyness.