This week on Freaky Friday: Workshops? Noooo need!*

Workshops? Nooo need, they just burn time! You can get this answer loads of times, esecially when working for small and medium size organizations. Go for it and say: Yes you are sooo right! Workshops do burn a lot of time for sure. Have you ever thought about it? Just take the number of persons and the time they invest in the workshop, meaning preparation, attending and wrap-up.

Let’s take an example: 6 people for a workshop on technical issues, for example catalogue data import for a new shop system. You will need the project manager, who also needs time for preparation and wrap-up, the project manager on client side, a technical specialist from the customer, your DB guy, a shop developer and for sure someone for what ever. The workshop takes 4 hours. With all time (also travelling) you have something around 20 hours, plus 4 preparation/wrap-up and assumed 10 hours travelling (2 persons x 2,5h x 2 times). That’s  34 hours summed up! Meaning more than 4 days burned! That’s quite an argument, isn’t it?

So why make workshops anyway? That is quite easy. Every time you have topics that involve more than just one or two counterparts, the communication effort will rise with every person added. And as you know (from the previous posts) communication can and will lead to misunderstandings. If you were on the Jedi side of project management, you would schedule a workshop, create an agenda and a time table and go for 4 hours of rock’n’roll! After the meeting you will in most cases have a solution for your problem and also a plan on how to get this solution to life. So workshops are essentially there to find solutions and get rid of communication problems. It’s always good to have the relevant people in a room to talk everything through.

For you as project destroyer that means: encourage clients who look at money and time. Avoid worksshops. Point out how expensive they are. Have fun watching the project slow down…

* Legal disclaimer: What you read here may cause havoc to your project, when applied. Neither nor the author will take any responsibility for the effects. So read carefully. You are responsible for any action you take after reading!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s