In software development, momentum is everything. When a team is in the flow, complex problems get solved, features ship, and products evolve. But speed is rarely bottlenecked by how fast engineers can type or how quickly code compiles.
More often than not, development speed dies in the calendar.
Too often, teams are brought to a grinding halt simply trying to get a meeting together. In my experience, this calendar-induced drag manifests in two distinct ways—one is easy to fix, and the other requires a fundamental shift in how your leadership operates.
Trap #1: The "Wait-to-Sync" Anti-Pattern
The first way meetings kill speed is when people default to waiting for a scheduled block to communicate. Instead of unblocking a teammate right now, you hear: "Let's put a pin in this until our sync on Thursday."
Suddenly, a 5-minute clarification turns into a three-day delay.
Fortunately, this is the easier of the two problems to solve. It comes down to culture, guidance, and mentoring. You have to train your teams to embrace immediate, low-friction communication. If a question can be answered in a quick chat message, do it. If you need to hash out a complex logic flow, tap them on the shoulder or jump into a spontaneous five-minute huddle.
When leadership models the behavior that immediate, asynchronous, or ad-hoc communication is preferred over a formal calendar invite, the team will follow suit.
Trap #2: Calendar Tetris
The second manifestation is much harder to solve. It happens when a decision requires multiple people, and scheduling the meeting becomes a drawn-out nightmare dictated by everyone's calendar preferences, time zones, and double-bookings.
If you have six people who "need" to be in a room, the earliest available 30-minute slot might be eight days away. That is eight days of lost momentum.
So, how do you solve it? At some point, you have to hold the meeting without someone to keep moving forward.
You document the decision, share the notes, and trust your teammates to catch up. For high-functioning, autonomous teams, this is standard operating procedure. But for others, it’s a deeply uncomfortable shift.
The Micromanager's Friction
Moving forward without perfect attendance doesn't always sit well with people—especially those who are historically micromanagers.
Micromanagers are particularly challenging in this regard because they operate in a low-trust paradigm where visibility equals control. For a micromanager, asynchronous work like a decision made in a chat thread or a smaller, unobserved meeting feels invisible. They struggle deeply with the unknown. A calendar invite provides a contained arena where they can observe the work, direct the flow of information, and maintain their grip on the process. Furthermore, they often use large consensus meetings as a shield to spread accountability.
When you prioritize momentum over perfect attendance, you strip away that shield and trigger their fear of missing out. You are taking away their proxy for control.
I’ve seen this firsthand. I once witnessed a leader throw quite the tantrum because a meeting occurred without one particular person present. Yelling and throwing markers across the room. It was pretty ridiculous to see. I was actually stunned that in today's day and age I saw such bad behavior over something as basic as this, but there it was in all its sad glory. The irony? Multiple people in that very meeting had already held 1:1s with the absent person the day prior, and had follow-ups scheduled for later that day. The absent person was fully in the loop. The process was working. The teams were doing what they needed to do to move quickly and maintain alignment. But the leader panicked because the ritual of the meeting was broken, their perceived control was threatened, and their lack of trust couldn't let them accept that things were working.
When leaders equate "being in the room" with "doing the work," the speed of development dies.
How to Reclaim Your Momentum
If you want to protect your team's development speed, you have to change your relationship with the calendar.
- Default to Async:
- If it can be a chat, make it a chat. Save the calendar for deep debates and complex problem-solving. If the chat starts to get too complicated, don't schedule a meeting; instead, ask everyone to jump on a quick call right then to clear it all up.
- If you think the initial concepts are too big for a chat, fine, throw it in a document, but then don't schedule a meeting to go over the document. All you're doing then is delaying the discussion about something that people won't even read. Instead, create the doc, give them comment rights, and share it, saying "Get me your comments in this doc by DATE X. If I don't get any feedback, I'll assume you're good with this proposal, and I'm going to move forward with it."
- Establish the "Optional" Rule: If someone is invited as "Optional," they are truly optional. The meeting goes on with or without them, and they agree to abide by the decisions made in their absence.
- Document and Route: Have the meeting with the core people who are available now. Take excellent notes, make the decision, and route the outcome to the absentees.
Perfect attendance is a terrible metric for team alignment. Stop waiting for the stars (and the calendars) to align, and just keep moving forward.