<?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 Further Heitz</title>
    <link>/tags/leadership/</link>
    <description>Recent content in leadership on Further Heitz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Kelly Heitz</copyright>
    <lastBuildDate>Sun, 08 Feb 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/tags/leadership/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Liner Notes for a Diagram</title>
      <link>/post/liner-notes-for-a-venn-diagram/</link>
      <pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>/post/liner-notes-for-a-venn-diagram/</guid>
      <description>At a friend&amp;rsquo;s job, they ask newcomers what the kids movie song for their career would be. It&amp;rsquo;s an oddly revealing question (I suppose unexpected queries have that advantage even if I think asking someone how many golfballs would fill a schoolbus is pretty obnoxious. I&amp;rsquo;m not sure that it&amp;rsquo;s any more ridiculous and aggravating than making experienced professionals design high scale systems alone on a whiteboard in front of a panel of dudes named John and Dave)</description>
    </item>
    
    <item>
      <title>Speed and Safety</title>
      <link>/post/speed_and_safety/</link>
      <pubDate>Thu, 07 Mar 2024 00:00:00 +0000</pubDate>
      
      <guid>/post/speed_and_safety/</guid>
      <description>&amp;ldquo;You have to go slow to go fast.&amp;quot;
and
Speed is safety&amp;rdquo;
Both of these phrases are oft-quoted in software. Each have individually been well-explained by better writers and engineers than me, but I think the combination can get confusing when we talk about innovation and building new software systems.
The best metaphor I have for this is downhill skiing (I did a lot of ski racing in high school).</description>
    </item>
    
    <item>
      <title>Building Psychological Safety</title>
      <link>/post/psychological-safety/</link>
      <pubDate>Wed, 17 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>/post/psychological-safety/</guid>
      <description>A few years ago, I read this article in the NYT What Google learned from its quest to build the perfect team, by Charles Duhigg. A lot of it resonated with me, especially this finding:
 The researchers eventually concluded that what distinguished the
‘‘good’’ teams from the dysfunctional groups was how teammates treated
one another. The right norms, in other words, could raise a group’s
collective intelligence, whereas the wrong norms could hobble a team,</description>
    </item>
    
    <item>
      <title>Greatest Hits: Tech Talks</title>
      <link>/post/favorite-talks/</link>
      <pubDate>Fri, 12 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>/post/favorite-talks/</guid>
      <description>I watch a lot of tech talks. These are my favorite that I&amp;rsquo;ve watched recently, with what I love about them and keep returning to for inspiration or clarity.
Teamwork &amp;amp; Leadership Being Glue - Tanya Reilly
Confession/boast: the nicest feedback I ever got from another developer was that I&amp;rsquo;m &amp;ldquo;like slime&amp;rdquo;. By that this person clarified they meant I&amp;rsquo;m good at filling the gaps of a project to move things forward.</description>
    </item>
    
  </channel>
</rss>