Don't add your 2 cents
I think it&#x27;s good to note, as Derek does, the distinction between &quot;2 cents&#x27; worth&quot; and larger changes that do require senior input - otherwise you&#x27;re just being the manager that the team create ducks for [1].<p>This is where coaching skills as a manager can prove useful. If you feel there are some minor changes that could be an improvement, but don&#x27;t want to impose your will&#x2F;opinion, coaching (&#x27;ask&#x27;) can be a better response than managing (&#x27;tell&#x27;).<p>For example, you might ask &quot;If you had to improve anything, what would you change?&quot; It&#x27;s an open-ended question that will encourage your team member to think. They can reply &quot;Nothing&quot; if they&#x27;re confident in the final solution, or they may propose some tweaks they weren&#x27;t fully happy with - &quot;I&#x27;m not sure if that&#x27;s the right shade of blue&quot; or &quot;I think that&#x27;s the right call to action, but maybe we could get another opinion&quot;. If those are reasonable improvements, empower them to implement the additional change; if you disagree with the extras they raise, tell them you consider the version they proposed to be superior, which empowers their original decision.<p>Just don&#x27;t be the manager who expects a detailed response and change every time ... then you&#x27;re right back to where you started.<p>[1] See point 5 <a href="https:&#x2F;&#x2F;blog.codinghorror.com&#x2F;new-programming-jargon&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.codinghorror.com&#x2F;new-programming-jargon&#x2F;</a>