<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Growth on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/growth/</link>
    <description>Recent content in Growth on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 12 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/growth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Scaling Your Team Without Breaking What Works</title>
      <link>https://www.secdev.uk/blog/leadership/3.8-scaling-your-team-without-breaking-what-works/</link>
      <pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.8-scaling-your-team-without-breaking-what-works/</guid>
      <description>&lt;p&gt;I lived through this at a growth start-up where the engineering team tripled in under two years. At fifteen people, we were fast, aligned, and effective. Everyone knew what everyone else was working on. Decisions happened in hallway conversations. The culture was strong because it was small enough to be transmitted through proximity.&lt;/p&gt;&#xA;&lt;p&gt;At forty-five people, almost none of that was true. Communication had broken down. New hires didn&amp;rsquo;t understand the culture because nobody had time to transmit it. Decisions that used to take minutes now took weeks because the number of stakeholders had multiplied. We were bigger, but we weren&amp;rsquo;t better, and for a painful period, we were actively worse.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
