The Different Types of Meetings

The “Technology Fail” Meeting

Wait for everyone to connect via their conferencing system choice.  Mute people who are driving through a tunnel that don’t want to mute themselves.  Try to share a screen that gets pixelated or worse you realize you can’t share until the last moment.

It ends with everyone saying – “Let’s meet in person next time” – defeating the purpose of everyone being online.

The “Yesterday’s Update” Meeting

Everyone drops what they are doing to hear everyone say – “I’m working on what I said I’d be working on”.

Loved by Managers, despised by Leaders, detrimental to project completion, great for checking completion boxes.

The “No Action” Meeting

Everyone discusses what is happening with their work, real conversation happens, real discussion takes place.

But at the end there are no assignments for what is to happen next, no commitment to what is should take place next – that’ll be saved for an email where the sender flips furiously through their notes trying to remember what so and so said.

There are more types, many more, despite all of our advances, the meeting still has the most prolific amount of waste associated with it and even though we have pockets of success the waste continues to be profound.

If you’re looking for a field ripe for disruption, innovation, creativity and improvement – after all these years it is still the meeting.

Start here…

“What would it take to make you excited before arriving at a meeting and leave feeling refreshed, energized and on point to continue on?”

What does that look like?

How do you replicate that feeling across meeting upon meeting?

An interesting problem.

Suggestions for Developer Presentations

At some point in your career, if you want to move from Developer to Architect or Team Lead or Manager or something you are going to need to stand-up in front of people and deliver a worthwhile presentation.

It might be a presentation for a new idea or initiative or perhaps a status update on a project you are on or a simple roadmap update.

Whichever one it is, you’ll want to, no need to deliver a compelling presentation in order to get your message across.  As developers, we typically lean to the verbose, with lots of information on the slides but in a presentation this will not help you and in fact will distract from your message.

Some suggestions for your first presentation as a developer when developing that crucial deck;

  • Keep the deck simple – minimal words, some basic types, no crazy animations on every slide – READ: eliminate the distractions so the audience focuses on you.
  • You are the centre – people are here to listen to you, not the deck the deck is a compliment to you with some supporting points to what you are talking about – READ: do not read from the deck.
  • Stay on Point – how long do you have to talk?  15 minutes?  Deliver the message in 10 – your points should be punchy and delivered in a manner that conveys your confidence but also covers your bases – READ: don’t get up there and blubber on about your life history in the component you are reviewing
  • Get feedback – the best way to deliver a successful deck is to send it out for review to a full key people that will be there, get them involved and invested in what you are doing – READ: validate your message before delivery.

If you are able to do the above well and on target, then you will most definitely be able to end on the last item that we all want to deliver after each and every presentation.

Drop the mic, exit stage right, see you at next week’s status meeting.