Skip to main content

About Meetings


Meetings are important part of the business activity. Our basic need to communicate is topped by necessity to deliver meaningful results at workplace. As usual though reality is not as rosy as the ideal that many of us trying to achieve with meetings.

What is a good work-related pastime for one is at the same moment a time wasting and useless activity to another. This contradiction is coming from a few factors (among other things):

1.    Core difference in perception of meetings between different levels of workplace hierarchy or among committee/board members

2.    Meeting audiences and agendas

3.    Involvement and focus level of participants during the meetings

Therefore usually instead of being an effective business or private processing tool, meetings become the opposite.

There is an opportunity to adjust existing practices to meet new expectations of the work related activities to be more productive and fun. It is not hard to achieve as well by implementing useful techniques and tricks.

One. Create or utilise existing collaboration software platform that is accessible by everybody. An example of such a platform is Microsoft SharePoint. Integrating end-user technologies into the main platform is not a big problem today, and it will provide valuable outcomes. That helps by allowing visualise meeting information, track attendees, record statuses, showcase agendas, tag and attach collateral etc. The opportunity also arises to review meetings and rate them with comments from actual or potential participants. Good deed!

Two. Think about your business unit values and goals when creating a meeting invite. Does this particular meeting is aligned with it? What are you trying to achieve that corresponds with main goals and values?

Three. Depending on a type of meeting choose the set up wisely. If the meeting is to provide an update or a lecture on some topic it may be worthwhile setting up an online seminar (webinar).

Four.  Only invite people who are interested in the topic and can make decisions. Five-seven persons per meeting maximum.

Five. Always get the action items after every meeting and assign it to responsible people. Otherwise there is no point to meet at all.

Six. Set time for meetings as short as possible. Long meetings without need is evil.


Using the abovementioned ideas should be a great addition to the business meeting framework.  

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like...

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi...