<?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>Team-Dynamics on Rafiul Alam</title>
    <link>https://alamrafiul.com/tags/team-dynamics/</link>
    <description>Recent content in Team-Dynamics on Rafiul Alam</description>
    <image>
      <title>Rafiul Alam</title>
      <url>https://alamrafiul.com/papermod-cover.png</url>
      <link>https://alamrafiul.com/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 15 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/tags/team-dynamics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Management Patterns: Proven Practices from the Field</title>
      <link>https://alamrafiul.com/blogs/management-patterns/</link>
      <pubDate>Mon, 15 Sep 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/management-patterns/</guid>
      <description>&lt;p&gt;Software engineers love design patterns. Factory, Observer, Strategy-we have names for recurring solutions to recurring problems.&lt;/p&gt;
&lt;p&gt;Management has patterns too. Not organizational structures or methodologies, but specific, repeatable practices that work across different contexts.&lt;/p&gt;
&lt;p&gt;Here are patterns I&amp;rsquo;ve seen work in startups, scale-ups, and enterprises.&lt;/p&gt;
&lt;h2 id=&#34;pattern-1-the-written-decision-record&#34;&gt;Pattern 1: The Written Decision Record&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Intent:&lt;/strong&gt; Make decisions visible, reversible, and learnable.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Context:&lt;/strong&gt; Teams waste time relitigating old decisions, or worse, making decisions without knowing why previous choices were made.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>The Dunbar Number: Why Organizations Break Down After 150 People</title>
      <link>https://alamrafiul.com/blogs/dunbar-number/</link>
      <pubDate>Fri, 31 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/dunbar-number/</guid>
      <description>&lt;p&gt;In the early 1990s, British anthropologist Robin Dunbar made a curious observation while studying primates.&lt;/p&gt;
&lt;p&gt;He found a correlation between the size of a primate&amp;rsquo;s neocortex (the brain region handling social relationships) and the size of its social group.&lt;/p&gt;
&lt;p&gt;Chimps, with smaller neocortices, lived in groups of ~50.&lt;/p&gt;
&lt;p&gt;Gorillas: ~30.&lt;/p&gt;
&lt;p&gt;Humans, with the largest neocortices, should be able to maintain stable social relationships with about&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;150 people.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s it. Not 500. Not 1,000. &lt;strong&gt;150.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Groupthink: How Smart Teams Make Dumb Decisions</title>
      <link>https://alamrafiul.com/blogs/groupthink/</link>
      <pubDate>Mon, 15 Apr 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/groupthink/</guid>
      <description>&lt;p&gt;We were going to launch the feature on Tuesday.&lt;/p&gt;
&lt;p&gt;Everyone on the team knew it wasn&amp;rsquo;t ready. The code was buggy. The UX was confusing. We hadn&amp;rsquo;t tested the edge cases. One of our engineers literally said in standup, &amp;ldquo;I&amp;rsquo;m not sure this is going to work well,&amp;rdquo; but immediately followed it with, &amp;ldquo;but I guess everyone else thinks it&amp;rsquo;s fine.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The PM wanted to hit the deadline. The CEO was excited about the demo. The team had momentum. So we all nodded along.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
