<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Team-Effectiveness on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/team-effectiveness/</link>
    <description>Recent content in Team-Effectiveness on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 18 Aug 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/team-effectiveness/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Actually Makes an Engineering Team Effective</title>
      <link>https://www.secdev.uk/blog/leadership/3.1-what-actually-makes-an-engineering-team-effective/</link>
      <pubDate>Mon, 18 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.1-what-actually-makes-an-engineering-team-effective/</guid>
      <description>&lt;p&gt;I spent the early part of my career believing that team effectiveness was mostly about talent. Get the best engineers, give them interesting problems, and get out of the way. It&amp;rsquo;s an appealing theory, and it&amp;rsquo;s wrong, or at least, it&amp;rsquo;s missing the most important part.&lt;/p&gt;&#xA;&lt;p&gt;Google&amp;rsquo;s Project Aristotle studied 180 teams and ran 35 statistical models to find what made some teams effective and others not. The finding that surprised everyone, including Google, was that who was on the team mattered far less than how the team worked together. Individual talent, seniority, even team size, none of these were the primary drivers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
