<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Feedback on sofiakodar.github.io</title><link>https://sofiakodar.github.io/tags/feedback/</link><description>Recent content in Feedback on sofiakodar.github.io</description><generator>Hugo -- 0.161.1</generator><language>en</language><lastBuildDate>Wed, 18 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sofiakodar.github.io/tags/feedback/index.xml" rel="self" type="application/rss+xml"/><item><title>Feedback – why, how and when?</title><link>https://sofiakodar.github.io/posts/feedback/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://sofiakodar.github.io/posts/feedback/</guid><description>&lt;p&gt;I’ve been a manager for about 11 years now and a team lead for a few years before that. Two of the most important leadership responsibilities, in my opinion, are setting clear expectations and giving feedback.&lt;/p&gt;
&lt;p&gt;When I’ve mentored new engineering managers and team leads, this is usually where they struggle most. I’ve seen countless managers struggle to give feedback and feel unsure about how to do it effectively. I’ve also repeatedly seen the consequences of missing feedback, how one person’s behavior can sink a whole team. Across all the companies I’ve worked at, only one has offered any kind of feedback training. I&amp;rsquo;ve read and learned a lot by myself and by experience. Here are some of my tips and thoughts, because feedback can be an incredibly valuable gift if done right.&lt;/p&gt;</description></item></channel></rss>