DEV Community

Kinetic Goods
Kinetic Goods

Posted on

The Meeting You Were Late To (And What It Cost)

You arrived ten minutes late. The meeting started without you. Decisions were made. Context was set. By the time you walked in, the conversation had moved on.

Now you're trying to catch up. Someone fills you in. It's partial. You ask a question that was already answered. You don't raise a concern that should have been raised. You leave the meeting not knowing what you actually agreed to.

This happens all the time. And we treat it as a scheduling problem. But it's not.

Being Late Is a Decision

When you arrive late, you're signaling that your time is more valuable than the people in the room. Even if that's not true, that's what it looks like.

And there's a second cost: you missed the conversation. The context-setting. The nuance. The body language that told everyone else what was really being decided.

You can get the notes. You can get the summary. But you can't get the room's energy, the thing that wasn't said, the consensus that formed without a formal vote.

Why Catching Up Doesn't Work

The meeting summary says "we decided X." But it doesn't say "we almost decided Y, and here's why we didn't." It doesn't say "Sarah objected but was overruled." It doesn't say "we agreed to revisit this in Q3."

The summary gives you the surface. You missed the depth.

The Fix

Treat lateness as a cost, not a scheduling conflict.

If you're going to be late, send a message: "I'll be 10 minutes late. Can you hold the decision until I arrive, or give me a two-minute brief before we start?"

After being late, follow up immediately.

Not a day later. Immediately. "I know I missed the first part. What was decided, and what's my part?"

If lateness is chronic, change your defaults.

If you're always running behind, build buffer before every meeting. Not as a preference — as a system.

The meeting you were late to cost more than ten minutes. It cost you the context that everyone else in the room received.

Top comments (0)