11 Comments

Anton, Thank you very much.

I learned some lessons from this article, and I'm sure it can help many team leaders too.

About your side note: "If you ask them to think and get back to you, forget about a response" -

I've noticed that for some developers, the "offline" thinking lets them find the real issues. Remember that they don't think all the time about the things that you can improve. Sometimes they need to remember a specific situation or a specific feeling they experienced when you acted wrongly in their opinions, so it may take them time, and it can be embarrassed to start thinking about it in a face-to-face meeting. It can sometimes even feel like a Black-out.

A good tip for this type of developer is - to ask them to **write down** the feedback, not only "get back with it". It'll force them to talk honestly about all the issues they want you to improve on in the next 1:1 meeting, and prevent them from thinking about how and what to say in front of you.

Expand full comment

Thanks Raz!

That’s a good point, I haven’t tried that. I think if you do that, you must show that you are serious and expect a response in the next meeting. Maybe even print a form with questions that interest you, in advance.

I’m going to try it :)

Expand full comment

Anton, I read it and found it enjoyable! Thanks and waiting for more content :)

Expand full comment

Thanks Yair 🙏

I hope it was useful too :)

Expand full comment

Anton, the writing and lessons in here are so amazing.

I loved the in-depth examples and personal insights.

That example of the LinkedIn conversation in public is really something too 😂

Expand full comment

Thanks Jordan! The whole article came from a comment you wrote on some post :)

Expand full comment

Haha, now I'm curious :D

Expand full comment

Haha well that adds up 😂

Expand full comment

So thanks for the great idea, let me know if you have anymore of those 😂

Expand full comment

Haha, if it leads to more awesome posts like these, certainly!

Expand full comment