Don't Fall Off Either Side of the Roof: Too Many Meetings, Too Little Talking

Alireza Avatar

In Persian we have a saying about falling off the other side of the roof: you try so hard to avoid one edge that you fall off the opposite one. I've done exactly that with team communication. I've worked with almost no meetings, and with far too many. Both went wrong.

Meetings that ate the day

In the first years of Dropout Games, our mobile studio, we worked fully remotely, and our meetings were bad. There were too many of them. Some lasted three or four hours. Many drifted away from the topic they were called for, and we'd leave without a clear decision.

Eventually we cut them back hard. It was the right call, because the meetings were eating the time we needed for actual work.

Everyone in every room

Later, I worked as a team lead somewhere with the same problem in a different form. There were meetings all the time, and many people in the room had no connection to the topic. They sat there, looked around, and waited for it to end.

Part of the problem was how decisions were made: everyone together, about everything. Democracy is great for a country, but it's a poor way to run every decision on a team. When everyone has to agree, decisions get slow, diluted, and owned by nobody. A good team needs people who own specific decisions, and who invite only the few who need to be involved.

The other edge: the update nobody released

The third story is the opposite edge. Recently, a finished update for our game sat unreleased for weeks. I started worrying. Had our publisher lost interest? Were we no longer a priority? I prepared carefully for a difficult conversation.

It took a few minutes to solve. He thought we were still adding features and was waiting for us to say it was done. We were waiting for him to release it. Nobody was wrong. We simply hadn't been talking.

The irony is that when we worked with him remotely, we had regular calls and everyone knew the next step. Once we were in the same country, we assumed being nearby was enough. It wasn't.

The meeting in my head

There's one more kind of miscommunication, and it happens without anyone else in the room.

Something bothers me: a short reply in a chat, a task that hasn't moved, a decision I don't understand. Instead of asking, I think about it. Then I think about it again. I build explanations, prepare arguments, and imagine the conversation in different ways.

Then I finally talk to the person, and it's solved in two minutes. The short reply was just someone busy. The task was waiting on me. The decision made sense once I heard the reason. Most of the time, the problem wasn't what I thought it was. Sometimes it wasn't a problem at all.

Overthinking feels like preparation, but it's often just a way to delay one simple question.

Staying in the middle of the roof

No meetings and too many meetings are two edges of the same roof. Here's what I try to do now:

  1. Keep a routine meeting. Once a week, or once every two weeks. Short, with a simple agenda: what's done, what's blocked, what's next.
  2. Invite only the people who need to be there. Everyone else can read the notes.
  3. Let owners decide. Ask for input, but don't turn every decision into a vote.
  4. Say the obvious thing. "It's done," "it's your turn," "I'm waiting on you." The obvious sentences are the ones that get lost.
  5. Don't carry a worry for long. If something keeps bothering you, bring it up early, outside the routine meeting if needed.

The routine meeting keeps the team in sync. The habit of asking early keeps your own head clear. You need both.

Next time something keeps bothering you, don't let it live in your head for days. Say it to the person. It may not be what you think at all.