Brad Feld

Tag: meeting

I used to be chronically late to everything, both personal and professional. In my twenties, before cell phones, I was one of those people that others referred to as having “Brad time” which did not correlate with the actual time in the world. My calendar and schedule was a rough sketch, not even a guide.

My lack of attention to time finally imploded on me around age 35 when Amy said she’d had enough on multiple dimensions of our life. The foundational issue for us was that my actions didn’t match my words, and by being late all the time, I wasn’t honoring my priorities (which I would regularly say was Amy over everything else …) If you ever get us together at a meal and want to hear some epic “Brad was late” stories, ask her about the Postrio dinner of 2000.

Since then, I’ve gotten a lot better at being on-time. I’m not a “five minutes early to everything” person, but I’m rarely more than a few minutes late to anything. I’m very scheduled throughout the week, so it’s often hard to transition between the thing that ends at 2:30 and then be on time to the thing that starts at 2:30 and get it exactly right each time. And, throughout the day, when I end up going until 2:35 for whatever reason, the 2:30 call then goes a little long, and everything backs up a little so that I’m 15 minutes late for the last meeting of the day. And now I know to always say “I’m sorry for being late” whenever I’m late.

Over the years I’ve tried many different approaches to managing the clock. For a while, I tried using Google’s “speedy meeting” option which defaults to 25 minute meetings (instead of 30) and 50 minute meetings (instead of an hour), but no one ever paid any attention to it and it just seemed to create weird openings in my calendar for anyone who had access to it.

Today, I use a different approach. I try manage the clock better during a meeting when I’m in charge, and prompt others when I’m not. That works a little, but it’s annoying.

I find this particularly challenging on calls that are an hour long with multiple people. Or, in three hour-ish board meetings with a lot of people. I don’t control the agenda in those meetings, so clock management is up to someone else. And, most people are painfully bad at it.

There are a few tips for anyone who wants to do this well.

The first is to publish an agenda with times allocated to each section. Then, have an enforcer (not the person running the meeting) who gives a five minute warning on each section. Then, end each section on time. Basically, break up the meeting into smaller chunks (15 – 30 minutes) and adhere to the schedule.

Next, front end load the meetings. Do the stuff you need everyone on the call or at the meeting for up front. Some things need you to build into them, but don’t leave them “for the end” – build deliberately to each deeper discussion or decision you want to have. Leaving the critical discussions and decisions for the end of the meeting is a guaranteed way not to get to them.

Send out materials well in advance (at least 48 hours) and assume everyone can read. If they don’t, that’s their problem, not yours, and they’ll get the hint pretty quickly. Instead of going page by page through your materials, or using the materials as a crutch to “review” things, summarize they key points and focus on discussion and debate, rather than review.

Finally, build in buffer. Almost everyone needs to go to the bathroom during a three hour meeting. At the minimum, it’s good to stand up and stretch your body. All video conferencing systems, no matter how good, continue to have weird friction at the beginning of the meeting, so have a front-end start buffer, rather than anxiety around the inevitable five minute delay. And, when the meeting goes off the rails and you get ten minutes behind because someone (e.g. me) can’t shut up about something and your time enforcer was daydreaming about Dali paintings, use the buffer to catch back up.

This is a problem that has been persistent in my life for over 30 years. If you have magic tricks that have worked for you, I’m all ears.


I love Scott Kveton, the CEO of Urban Airship. He and his team are building an amazing company in Portland. If you do anything mobile-related and use push notifications of any sort, or real-time location targeting, you need to be talking to them. But even more impressive is how Scott leads his company.

The other day, I got an email from my partner Jason with a photo of the Urban Airship Meeting Rules posted on the wall. They are so logical as to be rules that should apply to every meeting at every startup from now until forever.

Urban Airship Meeting Rules

0. Do we really need to meet?

1. Schedule a start, not an end to your meeting – its over when its over, even if that’s just 5 minutes.

2. Be on time!

3. No multi-tasking … no device usage unless necessary for meeting

4. If you’re not getting anything out of the meeting, leave

5. Meetings are not for information sharing – that should be done before the meeting via email and/or agenda

6. Who really needs to be at this meeting?

7. Agree to action items, if any, at the conclusion of the meeting

8. Don’t feel bad about calling people out on any of the above; it’s the right thing to do.

I particularly love 0, 1, and 4. I rarely walk out of a meeting when I’m not getting anything out of it. I’m going to start paying more attention to this one.