<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Culture on Thiago Avelino</title><link>https://avelino.run/tags/culture/</link><description>Recent content in Culture on Thiago Avelino</description><generator>Hugo</generator><language>en-us</language><copyright>© Avelino</copyright><lastBuildDate>Mon, 27 Apr 2026 11:40:27 -0300</lastBuildDate><atom:link href="https://avelino.run/tags/culture/index.xml" rel="self" type="application/rss+xml"/><item><title>Flat Engineering Teams Aren't an Org Chart Decision. They're a Maturity Filter</title><link>https://avelino.run/flat-engineering-teams-maturity-filter/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://avelino.run/flat-engineering-teams-maturity-filter/</guid><description>&lt;p&gt;Meta built an AI engineering team with &lt;a href="https://fortune.com/2026/03/14/metas-ai-team-50-flat-management-structure/"&gt;50 engineers per manager&lt;/a&gt;. The Wall Street Journal called it &amp;quot;ultra-flat.&amp;quot; André Spicer, from Bayes Business School, &lt;a href="https://fortune.com/2026/03/14/metas-ai-team-50-flat-management-structure/"&gt;was more direct&lt;/a&gt;: &amp;quot;it's going to end in tragedy.&amp;quot; Both are wrong for the same reason: they treat flat team structure as an org chart decision.&lt;/p&gt;
&lt;p&gt;Flat team structure is not an org chart decision. It's a cultural consequence.&lt;/p&gt;
&lt;p&gt;And most companies cutting middle management right now aren't going flat. They're going broken with extra steps.&lt;/p&gt;</description></item></channel></rss>