<?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/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Team Management · Jared Lynskey</title>
    <link>https://jared.lynskey.co.nz/en/tags/team-management/</link>
    <description>Short stories of value on software engineering and engineering leadership — performance reviews, hiring and scaling teams, CI/CD, DevOps monitoring and agentic AI. Written from Seoul.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2026 Jared Lynskey</copyright>
    <lastBuildDate>Wed, 28 Oct 2026 00:00:00 +1300</lastBuildDate>
    <atom:link href="https://jared.lynskey.co.nz/en/tags/team-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Software Engineer to Engineering Manager: What Actually Changes</title>
      <link>https://jared.lynskey.co.nz/en/posts/2024/2024-01-02-engineeringmanager/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2024/2024-01-02-engineeringmanager/</guid>
      <pubDate>Tue, 02 Jan 2024 00:30:03 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Engineering Manager</category>
      <category>Career</category>
      <category>Leadership</category>
      <category>Team Management</category>
      <description>Going from software engineer to engineering manager is a career change, not a promotion. How the two jobs differ day to day, the skills that matter, and how to prepare for the move before the title arrives.</description>
      <content:encoded><![CDATA[<p><strong>It&rsquo;s a career change, not a promotion</strong></p>
<p>I&rsquo;m about to make this move myself, so I&rsquo;ve spent the last while talking to people who&rsquo;ve done it and reading whatever I could find. The clearest lesson so far: going from engineer to engineering manager isn&rsquo;t a step up. It&rsquo;s a step sideways into a completely different job. Your output stops being code and becomes whatever your team produces. Everyone says this, and from what I can tell, everyone still underestimates it.</p>
<p><strong>What actually changes</strong></p>
<p>You stop solving technical problems directly and start solving people problems. The calendar fills up with 1:1s, planning meetings, and cross-team alignment. Hiring and performance reviews land on your desk. Most of the job becomes making sure the team has what it needs — context, clear priorities, and as little nonsense as possible — to get on with the work.</p>
<p>The awkward part is that you still have to stay technical enough to hold your own in architecture discussions and make sensible judgment calls, while accepting that you can&rsquo;t be the one writing the code anymore. The managers I&rsquo;ve watched try to do both usually end up doing both badly.</p>
<p><strong>Engineer vs engineering manager, side by side</strong></p>
<table>
	<thead>
			<tr>
					<th></th>
					<th>Software engineer</th>
					<th>Engineering manager</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Your output</td>
					<td>Code, designs, reviews</td>
					<td>What the team ships, and the team itself</td>
			</tr>
			<tr>
					<td>Judged on</td>
					<td>The quality and impact of your own work</td>
					<td>Delivery, retention, and how much people grow</td>
			</tr>
			<tr>
					<td>A typical day</td>
					<td>Focus time, pull requests, design discussions</td>
					<td>1:1s, planning, hiring, unblocking people</td>
			</tr>
			<tr>
					<td>Feedback loop</td>
					<td>Hours or days: the tests pass, the feature ships</td>
					<td>Months: a hire works out, someone gets promoted</td>
			</tr>
			<tr>
					<td>Hands-on technical work</td>
					<td>Most of the week</td>
					<td>Reviews and architecture calls, rarely the critical path</td>
			</tr>
	</tbody>
</table>
<p>The feedback loop is the row people warn about most. As an engineer you get a small win most days. As a manager the wins are real but slow, and you have to get used to not knowing for a while whether a decision was right.</p>
<p><strong>The skills that seem to matter</strong></p>
<p>Communication is most of it. You become the translator between your team, product, and leadership, and a surprising amount of the job is making sure those three groups are talking about the same thing. Trust matters more than any process: if people don&rsquo;t feel safe telling you what&rsquo;s broken, you&rsquo;ll be the last person to find out. Your calendar will genuinely try to eat you alive, so protecting time to think — and time for your team — is a constant fight. And you need to understand what the business is actually trying to do, or you can&rsquo;t point anyone in a useful direction.</p>
<p><strong>Preparing before the title arrives</strong></p>
<p>The advice I keep hearing, and the bit I can already vouch for: start leading before anyone gives you the title. Run a project, mentor someone, organise something. I&rsquo;ve spent the past year acting as a project lead, and that experience is doing far more for me than any book. That said, books help — &ldquo;<a href="https://www.oreilly.com/library/view/the-managers-path/9781491973882/" target="_blank" rel="noreferrer">The Manager&rsquo;s Path</a>&rdquo; by Camille Fournier is the one everybody recommends, and having read it, I see why. Keep your technical skills sharp, because the architecture debates don&rsquo;t stop. And find a mentor who&rsquo;s already made the transition; they&rsquo;ll steer you around mistakes that only look obvious in hindsight.</p>
<p><strong>The trade-off</strong></p>
<p>More influence over how things get built, but you&rsquo;ll rarely build them yourself. I expect some days that will feel great, and other days I&rsquo;ll badly miss writing code. Everyone who&rsquo;s done this tells me that&rsquo;s normal. Ask me again in six months.</p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2024/2024-01-02-engineeringmanager/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
    <item>
      <title>What Does a Scrum Master Do? Focus on Process, Not Just Results</title>
      <link>https://jared.lynskey.co.nz/en/posts/2023/2023-10-16-outcome-indepedent/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2023/2023-10-16-outcome-indepedent/</guid>
      <pubDate>Mon, 16 Oct 2023 00:30:03 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Scrum</category>
      <category>Scrum Master</category>
      <category>Agile</category>
      <category>Retrospectives</category>
      <category>Team Management</category>
      <description>What a Scrum Master is accountable for under the Scrum Guide, how the role differs from a project manager, and why the job is improving the process rather than chasing sprint results.</description>
      <content:encoded><![CDATA[<p>The short answer first. Under the 2020 Scrum Guide, a Scrum Master is accountable for establishing Scrum as the guide defines it, and for the Scrum Team&rsquo;s effectiveness. In practice that means serving the Developers, the Product Owner and the wider organisation: coaching the team to manage itself, getting impediments removed, and making sure the Scrum events happen, stay productive and stay within their timebox. Nothing in the guide asks a Scrum Master to assign work or chase the team for results, and that difference is most of what this post is about.</p>
<p>The worst retrospectives I&rsquo;ve sat through all had the same shape: we missed the sprint goal, so the whole hour turned into an inquest about the goal. The best ones barely mentioned the goal at all. We talked about how we&rsquo;d worked, what got in the way, and what we&rsquo;d try differently next time. That difference is what people mean by an outcome-independent mindset, and having run sprints myself for a while now, I think it&rsquo;s the most useful attitude a Scrum Master can hold.</p>
<p>To be clear: results matter. Nobody pays us to have a lovely process and ship nothing. But delivering the sprint is the team&rsquo;s job. The Scrum Master&rsquo;s job is to improve the machine that delivers sprints. Those are different jobs, and mixing them up causes most of the dysfunction I&rsquo;ve seen around Scrum.</p>

<h3 class="relative group">Scrum Master vs project manager
    <div id="scrum-master-vs-project-manager" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#scrum-master-vs-project-manager" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p>The two roles get confused all the time, partly because plenty of companies hand both to the same person. The core difference:</p>
<table>
	<thead>
			<tr>
					<th></th>
					<th>Scrum Master</th>
					<th>Project manager</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Looks after</td>
					<td>How the team works, and how well</td>
					<td>Scope, schedule and budget</td>
			</tr>
			<tr>
					<td>Assigns work?</td>
					<td>No. The Developers plan their own work</td>
					<td>Often, yes</td>
			</tr>
			<tr>
					<td>Success looks like</td>
					<td>A team that gets better sprint by sprint</td>
					<td>The project delivered on time and on budget</td>
			</tr>
	</tbody>
</table>
<p>Scrum itself has no project manager role. Much of what a project manager would usually do is split between the Product Owner, who decides what gets built and in what order, and the Developers, who plan how to build it.</p>

<h3 class="relative group">What changes when you let go of the outcome
    <div id="what-changes-when-you-let-go-of-the-outcome" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-changes-when-you-let-go-of-the-outcome" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p>The team gets room to actually own things. Scrum is supposedly built on self-organising teams, but a Scrum Master who sweats every result ends up steering decisions, and the team quickly learns that decisions aren&rsquo;t really theirs. Focus on process instead and you can let people experiment, make the occasional wrong call, and learn from it — which is the only way real ownership ever develops.</p>
<p><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-09-01-retrospecs/" >Retrospectives</a> get honest. When the question in the room is &ldquo;why did we miss the number?&rdquo;, the true answers go into hiding. When it&rsquo;s &ldquo;what slowed us down, and what do we try next?&rdquo;, people talk. The same goes for impediments mid-sprint: an outcome-obsessed Scrum Master panics about the deadline, while a process-focused one just gets on with removing the blocker, or suggests a time-boxed <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/" >spike</a> when the blocker is something nobody knows enough about yet.</p>
<p>Stakeholders calm down too. If the only story you can tell is the burndown chart, every wobble looks like failure. If you can also talk about what the team learned and how it&rsquo;s adapting, expectations become more realistic — and the team gets shielded from a lot of pressure that would otherwise land on them halfway through a sprint.</p>

<h3 class="relative group">If you&rsquo;re already fixated on a result
    <div id="if-youre-already-fixated-on-a-result" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#if-youre-already-fixated-on-a-result" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p>Easier said than done, I know. When you&rsquo;re deeply invested in something turning out a particular way, &ldquo;just focus on the process&rdquo; sounds like a fridge magnet.</p>
<p>A few things that actually help. First, don&rsquo;t beat yourself up for caring — wanting a result is normal, and pretending otherwise doesn&rsquo;t work. Second, translate the outcome goal into process goals you control: not &ldquo;win the competition&rdquo; but &ldquo;practise 30 minutes a day&rdquo;. You can&rsquo;t control whether the release lands well; you can control whether it was reviewed, tested, and demoed early. Third, notice what&rsquo;s feeding the fixation. If you&rsquo;re refreshing a dashboard or a stock price ten times a day, pick set times to check and stop otherwise. And celebrate the small wins along the way, because the distant goal will happily eat all your attention if you let it. If the fixation is genuinely wrecking your sleep or your daily life, that&rsquo;s worth talking to a professional about — no shame in it.</p>
<p>Results still matter. But the teams I&rsquo;ve seen get them consistently are the ones where somebody is looking after the how, not just the what.</p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2023/2023-10-16-outcome-indepedent/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
  </channel>
</rss>
