Engineer
In my second year as a senior engineer, my tech lead told me my code reviews were slowing the team down. He said my comments were technically correct but read as combative, and two of our junior engineers were waiting hours on small fixes because they were nervous to push back. My first reaction was to push back myself. I sat with it for a day and then asked him to send me three review threads as examples. Reading them felt different than writing them had. The comments were curt, and I had not separated nice-to-have from blocking. I changed two things. I started prefixing every comment with blocking, suggestion, or nit. And I started leaving an explicit approval message instead of silent merges. Review turnaround on my reviews dropped from a day and a half to about four hours. One of the juniors told me a quarter later that she had stopped dreading my reviews. That mattered more to me than the time saved.