Why do I lose the room when I explain a technical decision?
You know the work cold. You could explain it to another engineer half-asleep. But put a non-engineer in the room and something breaks — not in the code, in you. You reach for words that made sense to you and find they mean nothing to anyone else. This is not a sign you lack some gift for people. It is a sign you have only ever built one language for your ideas — the internal one. You have never had to build the second one, so you never did. That is a fact about your practice, not your character. Do this with your team, not alone in your head. Alone, you will just get more precise in the language no one else speaks. With others, you find out in real time which words carry and which don't.
You are not losing them because they are slow or you are unclear inside your own head. You are speaking one language and expecting them to already know it. Build a second language for the same idea — short, plain, tied to cost or risk they already track. Practice it with your team before you need it live.
What changes unlock by starting
- Your team can repeat your explanation back correctly, in their own words.
- Meetings with non-engineers get shorter, because less gets lost.
- You catch yourself over-explaining and stop, mid-sentence, to check understanding.
- Non-engineers start asking sharper questions instead of nodding along.