<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Delegation on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/delegation/</link>
    <description>Recent content in Delegation on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 26 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/delegation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Trap of Doing Two Jobs</title>
      <link>https://www.secdev.uk/blog/leadership/2.7-the-trap-of-doing-two-jobs/</link>
      <pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.7-the-trap-of-doing-two-jobs/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve fallen into this trap more than once. You get promoted, you take on the new responsibilities, and you keep doing the old ones too. Not because anyone asked you to, but because the old work is familiar, you&amp;rsquo;re good at it, and there&amp;rsquo;s a voice in your head saying &amp;ldquo;if I don&amp;rsquo;t do this, it won&amp;rsquo;t get done right.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;That voice is wrong. Or rather, it might be right in the short term, but it&amp;rsquo;s catastrophically wrong in the medium term. Doing two jobs doesn&amp;rsquo;t make you indispensable, it makes you a bottleneck, and it prevents your team from growing into the space you&amp;rsquo;re supposed to have vacated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learning to Delegate (and Why It Feels So Wrong)</title>
      <link>https://www.secdev.uk/blog/leadership/2.4-learning-to-delegate/</link>
      <pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.4-learning-to-delegate/</guid>
      <description>&lt;p&gt;Early in my management career, I had a team of six engineers and I was still the person who knew the most about every part of the system. When something urgent came up, I&amp;rsquo;d fix it myself. When a design decision needed making, I&amp;rsquo;d make it. When a PR needed reviewing, I&amp;rsquo;d review it. I was efficient, responsive, and completely unsustainable.&lt;/p&gt;&#xA;&lt;p&gt;It took a holiday, a proper two-week break where I was genuinely unreachable, for me to see the problem. The team didn&amp;rsquo;t fall apart while I was away. But they didn&amp;rsquo;t move forward either. They&amp;rsquo;d been waiting for me on three separate decisions, and nobody felt empowered to make them without my input. I&amp;rsquo;d created a team that was dependent on me, and I&amp;rsquo;d done it by being &amp;ldquo;helpful.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
