The BS Meeting Signs: Start and end late


Does this sound familiar?

The meeting was scheduled for 9:00 but somehow at 9:06 Zoom still says "Waiting for host to start the meeting." When it finally starts, the organiser casually mutters "sorry, previous thing ran long" while fumbling with screen sharing.

It's okay though, because they'll happily steal those minutes back by running fifteen minutes over the scheduled end time.

Everyone waiting lost those first minutes. And everyone with a follow-up commitment will nervously look at the clock because it's highly likely the current meeting will run over and create a domino effect. Next meeting will run over, and the next and the next.

For people who plan their energy carefully, especially those with access needs who may require specific accommodations, these unpredictable timeframes aren't just annoying. They're barriers to participation. No one expects you to impose a rigid adherence to the clock. But you need to recognise that everyone's time holds equal value.

When meetings go over, you're essentially declaring your agenda more important than whatever else people had planned.

Here are three solutions to meetings that start late:

  1. Schedule shorter meetings than you think you need (25 or 50 minutes instead of 30 or 60) to create natural buffers between commitments.
  2. If starting late is unavoidable, ruthlessly prioritise your agenda items and be prepared to sacrifice the least important ones to end on time.
  3. Start the meeting with whoever shows up on time rather than waiting for stragglers. When latecomers arrive, don't recap. They'll learn quickly that missing the start means missing information.

Of course, it would just be better to start when you said you would. And end when you promised.

Anything else is just being sloppy.

If the meeting was important, you'd be on time, wouldn't you?

Ship accessible websites. Faster.

Join fellow like-minded product owners looking to learn and contribute to authentic conversations on accessibility and inclusive design packed into just 5 minutes a day.

Read more from Ship accessible websites. Faster.

It's very tempting to hand over responsibility over accessibility to other people. If you're a developer, it's the designer's job. If you're the designer, the developer needs to implement accessibility. If you're the product owner, it's the tester's job to make sure everything works with assistive technology. This is easy. Because if someone else accepts responsibility, then we're off the hook. I see two problems with this: 1. Someone else must always be willing to accept the responsibility...

Accessibility. 13 letters. We thought it was such a lenghty word that we use the numeronym a11y to write it out. It has all these definitions floating around, each one just slightly different than the next. I think the reason why we can't settle on just one is simply because, like the word itself, accessibility is a loaded concept. It's just like a bulky piece of luggage you lug around and when you finally set it down on the floor and start to unpack, it'll likely fill the room. The...

Striking the balance between making the easy thing right and making the right thing easy in web accessibility is a crucial discussion. Do you choose the path of least resistance or fight through the discomfort and take the path of inclusiveness? The easy thing is copy pasting some code you found online. It might seem like the quick fix, but it often doesn't take into account the diverse needs of all your users. The right thing is making your website universally accessible. It involves...