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

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

Construction issues resolution in Sydney - part 17

It's been a while since  the last post In January 2016 the owner lodged an application to NCAT against owners corporation to fix three major defects: - waterproofing of large windows in the living room and bedroom which led to windows full replacement - bathroom drain fix - planterbox fix The owners corporation didn't come to mediation and tribunal ordered to fix all defects within 2 months (the deadline was 8th July 2016). The owners corporation as usual didn't rush to comply with the order regarding two items: bathroom and planterbox. The windows works started end of April 2016. At the same time owners corporation decided to check whether it's a warranty and original builder should fix the issues. That was also related to the fact that the variation was submitted by the current contractor who started fixing the defect. So the owners corporation stopped all works in the middle and went off for a month to "make decision". The decision was mad

How strata owners corporation "solves" problems or Construction issues resolution in Sydney - Part 16

Almost 8 months passed from the time of previous post and here's how the owners corporations activities looked like to "resolve" the defects/problems: 1. Independent inspection report was ordered and completed 1st June 2015. The report confirmed the defects that were known to owners corporation already. It should be noted that in the period between December 2014 and June 2015 the only attempts by owners corporation to resolve the issues were to convince the lot owner that it's the owner's personal responsibility. Therefore half a year gone with a couple of meetings only, because people were "on holidays", "busy" etc. 2. Between 3rd July 2015 and end of July 2015 the strata manager spent "contacting the builders for quotes". Until owner called the strata manager nothing have happend. 3. By the end of August 2015 all quotes were in place. The meeting of all owners was set up for the 7th October! Because as usual "holid