<?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/">
  <channel>
    <title>Management on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/management/</link>
    <description>Recent content in Management on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Aug 2023 11:20:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Navigating Org Change as an Engineer</title>
      <link>https://blog.turboawesome.win/2023/08/navigating-org-change-as-an-engineer/</link>
      <pubDate>Wed, 16 Aug 2023 11:20:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2023/08/navigating-org-change-as-an-engineer/</guid>
      <description>Reorganisations, leadership changes, and strategy shifts are facts of life in growing companies. The engineers who navigate them well share some common practices — and some common misconceptions about what&amp;#39;s actually changing.</description>
    </item>
    <item>
      <title>Postmortems as a Learning Tool: Structure, Culture, and Follow-Through</title>
      <link>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</link>
      <pubDate>Wed, 05 Oct 2022 11:27:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</guid>
      <description>A postmortem that concludes with &amp;#39;be more careful&amp;#39; has failed. The structure and culture of blameless postmortems, and why follow-through is where most teams fall short.</description>
    </item>
    <item>
      <title>On-Call Culture That Doesn&#39;t Burn Out Your Team</title>
      <link>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</link>
      <pubDate>Wed, 06 Jul 2022 09:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</guid>
      <description>On-call is a forcing function for reliability — when engineers are paged for their own systems, the feedback loop on quality is immediate. Done badly, it burns out your team. The practices that keep it sustainable.</description>
    </item>
    <item>
      <title>Engineering Roadmaps: Planning for Uncertainty</title>
      <link>https://blog.turboawesome.win/2022/02/engineering-roadmaps-planning-for-uncertainty/</link>
      <pubDate>Wed, 16 Feb 2022 09:30:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/02/engineering-roadmaps-planning-for-uncertainty/</guid>
      <description>Engineering roadmaps are commitments made under uncertainty. The planning practices that keep them honest — time horizon discipline, explicit uncertainty, and the difference between a roadmap and a plan.</description>
    </item>
    <item>
      <title>Technical Debt Is a Balance Sheet Item, Not a Moral Failing</title>
      <link>https://blog.turboawesome.win/2021/10/technical-debt-is-a-balance-sheet-item-not-a-moral-failing/</link>
      <pubDate>Wed, 06 Oct 2021 10:18:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/10/technical-debt-is-a-balance-sheet-item-not-a-moral-failing/</guid>
      <description>The language around technical debt is usually moral: &amp;#39;bad code&amp;#39;, &amp;#39;dirty shortcuts&amp;#39;, &amp;#39;cutting corners&amp;#39;. The financial metaphor it&amp;#39;s named after is actually more useful. Debt is a tool. Manage it like one.</description>
    </item>
    <item>
      <title>Hiring Senior Engineers: What the Interview Loop Can&#39;t Tell You</title>
      <link>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</link>
      <pubDate>Wed, 07 Jul 2021 14:02:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</guid>
      <description>After running hiring loops for senior engineers at the European fintech firm, the pattern was clear: the things that determined whether a hire was successful were almost never well-measured by our interview process.</description>
    </item>
    <item>
      <title>After the Startup: Joining a Larger Organisation Without Losing Your Mind</title>
      <link>https://blog.turboawesome.win/2021/03/after-the-startup-joining-a-larger-organisation-without-losing-your-mind/</link>
      <pubDate>Wed, 17 Mar 2021 09:11:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/03/after-the-startup-joining-a-larger-organisation-without-losing-your-mind/</guid>
      <description>Two years into a fast-moving startup, I joined a larger, more structured European financial technology firm. The culture delta was significant in both directions.</description>
    </item>
    <item>
      <title>From IC to Lead: The First 90 Days Managing a Technical Team</title>
      <link>https://blog.turboawesome.win/2020/05/from-ic-to-lead-the-first-90-days-managing-a-technical-team/</link>
      <pubDate>Wed, 13 May 2020 13:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/05/from-ic-to-lead-the-first-90-days-managing-a-technical-team/</guid>
      <description>The transition from individual contributor to technical lead is the career move that most engineers underestimate. The skills that made you good at the IC role don&amp;#39;t automatically transfer — here&amp;#39;s what the first 90 days actually taught me.</description>
    </item>
    <item>
      <title>Why I Left: On Risk, Pace, and Ownership</title>
      <link>https://blog.turboawesome.win/2019/01/why-i-left-on-risk-pace-and-ownership/</link>
      <pubDate>Wed, 09 Jan 2019 09:04:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2019/01/why-i-left-on-risk-pace-and-ownership/</guid>
      <description>After three years at a large financial institution, why I took a significant pay cut to join a tiny startup. The reasoning, the fears, and whether it was the right call.</description>
    </item>
  </channel>
</rss>
