Mike Gebremeskel

Writing

Write it down before you say it

Put the idea on paper before the meeting. I cut our meeting times in half.

I cut our meeting times down by 50%. The fix was not a better agenda. It was one rule. Write the idea down before the meeting. Then we talk.

For a long time my team did the opposite, and so did I. Someone would say an idea out loud. The rest of us would ask what they meant. We would go back and forth until it finally clicked. Only then could we do anything useful with it.

Think about how backwards that is. We were spending most of the meeting just getting to the starting line. The real work, the part where you pressure test an idea and make it better, only began once the clock was almost out.

So we flipped the order.

The change was small and it was not optional

I told the team I would never just speak an idea to them. I would write it down and share it first. Then we could edit it and actually discuss it.

I cared about this enough to build it into how we ran. We started a habit where people dropped what they wanted to cover into the channel ahead of time, so I could build an agenda and everyone could understand it at a high level before the call. The point was simple. Walk into the meeting ready to discuss something on paper, not ready to start thinking from zero.

We borrowed structure from people who had already figured this out. We picked up the Amazon style memo for our leadership meetings. The narrative memo forces you to actually make the argument, not just list bullets you can hide behind. The first time we used a real template for that meeting, a one hour call dropped to thirty minutes. Same decisions. Half the time.

I was also strict about one thing that sounds soft but is not. Capture every idea, no matter how simple or dumb it seems. Being able to read an idea and then discuss it is how you build a shared perspective. If it only ever lives in someone’s head, it is not a shared anything.

Why writing first actually works

Here is what I think is really going on.

When you talk an idea out, the other person spends their energy decoding you. What did he mean by that? Is that the same as the thing we said last week? By the time everyone understands the idea, you are out of time and you have done none of the thinking that matters.

When you write it down, the decoding happens before the meeting. People show up already understanding the idea. So the meeting gets spent on the useful part. Pushing on it, finding the holes, making the call. As I told the team back then, the goal was to put our notes in a document, so that by the time we met we were discussing what we had already seen. That drives the conversation faster. And the meeting only lasts as long as it actually needs to.

There is a second benefit I did not see coming. The writing becomes a record. When we moved more of our work async, I told the team the reason out loud. We needed future teammates to be able to read what we had discussed and understand why we made a decision, not just what we decided. The context stops living in one person’s head and starts living somewhere the whole team can reach.

That turned out to matter more than the time savings. A small team moves fast and forgets faster. The doc is the memory.

The honest tradeoff

Writing first is more work up front. You cannot fake it. You have to actually know what you think before the meeting, which is uncomfortable, because a lot of meetings exist precisely so people can avoid figuring out what they think.

But that discomfort is the feature. The blank page does the thinking the meeting used to waste time on.

So here is where I land. If your meetings feel slow, do not reach for a better agenda or a shorter time box. Change the order. Make the idea show up on paper before it shows up in the room.

Talking feels faster. It is not. The doc does the thinking. The meeting just confirms it.

Does that match what you have seen on your own teams?

October 2025