← All posts

18 June 2026 · 5 min read

Why you freeze in English design reviews (and it is not your grammar)

Engineers discussing an architecture diagram in a meeting room

A senior backend engineer once told me he could review a pull request in English all day, write flawless documentation, and read any spec you put in front of him. But the moment a design review started and three people were talking, he went silent. He had the vocabulary. He had the grammar. What he did not have was a way in.

The gap is not knowledge, it is timing

Speaking in a live technical discussion is not the same skill as writing English or reading it. In a review you have to interrupt, hold a turn while you think, disagree without sounding rude, and get back in after someone talks over you. None of that is grammar. It is the mechanics of a real conversation, and most English courses never touch it because they are built around one learner and one teacher taking polite turns.

So the engineer who studied for years still freezes, and concludes his English is worse than it is. It is not. He has just never practised the exact situation that is hard.

You cannot rehearse a room by yourself

This is the honest limit of a one-to-one lesson. A tutor can correct your articles and expand your vocabulary, but a tutor cannot be a room. They will not talk over you. They will not push back hard and make you defend a position while two other people wait to jump in. The pressure that makes you freeze at work is the exact thing a single tutor cannot reproduce.

A group can. When you practise a design review with eight other engineers, you get interrupted, you lose your turn, you get it back. You learn the small moves: "let me finish that thought", "I see it differently", "can we come back to that". After a few weeks those stop being things you translate and start being things you say.

What actually changes

The students who improve fastest are not the ones who learn the most words. They are the ones who stop waiting for the perfect sentence and start talking at the right moment. Fluency in a meeting is mostly courage plus a few reliable phrases. Both are trainable, but only against real pressure, with real people, on the real kind of problem you face at work.

Practise this with a cohort of engineers at your level.

View upcoming cohorts