<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Leadership on Justin Carmony</title>
		<link>https://www.justincarmony.com/tags/leadership/</link>
		<description>Recent content in Leadership on Justin Carmony</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 17 Jan 2019 19:09:11 +0000</lastBuildDate>
		
			<atom:link href="https://www.justincarmony.com/tags/leadership/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Engineering Managers: Don’t Forget the Individual Contributor’s High</title>
				<link>https://www.justincarmony.com/2019/01/17/engineering-managers-dont-forget-the-individual-contributors-high/</link>
				<pubDate>Thu, 17 Jan 2019 19:09:11 +0000</pubDate>
				<guid>https://www.justincarmony.com/2019/01/17/engineering-managers-dont-forget-the-individual-contributors-high/</guid>
				<description>&lt;p&gt;I was having a conversation with one of my engineers, and they were pretty worked up. They felt frustrated about a hiccup in one of our processes resulting in a minor delay of finishing their feature.&lt;/p&gt;&#xA;&lt;p&gt;I empathized with their plight and reassured the hiccup wouldn’t have any major effects. The team was still on schedule for their deliverables, their boss (me) understood why for the delay, and I knew it wasn’t the fault of the engineer. We also had a good plan in place to prevent the same issue in the future.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
