Key Takeaways
- Alexandr Wang structured Meta Super Intelligence Labs so that more than 200 technical researchers report directly to him.
- The reporting structure in the lab's TBD group serves as a structural barrier against middle management and project managers.
- Wang stopped trying to do every job himself, shifting away from his early Scale AI operating habits to run MSL under extreme time pressure.
- MSL uses technical lead pods to set technical strategy, keeping the team flat while steering clear of administrative bottlenecks.
- Top technical researchers do not want standard administrative management; they want an environment free from bureaucratic friction.
The Org Chart as an Anti-Bureaucracy Shield
Standard management theory teaches that an executive should oversee six to eight direct reports. Any more, and the org chart supposedly collapses. When Alexandr Wang took over Meta Super Intelligence Labs, he deliberately broke that rule. Within a research group called TBD, more than 200 top technical researchers report directly to Wang.
That flat structure is an organizational firewall. By assigning 200 builders to a single executive, Wang removes the possibility of conventional supervision. He cannot run weekly status syncs, review daily task lists, or demand progress memos. That lack of oversight is deliberate:
Wang admits this setup contradicts standard managerial habits: “So it's certainly like an unconventional way to run the team. And like I would be lying if I said I was like the best manager to more than 200 um people. But this part of the point is that like they don't need managers, they need a great environment.”
Elite researchers leave large technology companies when administrative red tape slows them down. By flattening the reporting tree, Wang removes the middle management layer before it can establish itself.
Small Pods Over Corporate Ladders
At Scale AI, Wang succeeded early on by mastering every internal function himself. When he arrived at Meta to build consumer AI, that playbook was useless. The technical scope was too broad, and the timeline was too tight:
Instead of adding administrative supervisors to coordinate work, MSL relies on technical lead pods. These small pods set direction without becoming administrative gatekeepers. Wang took inspiration from how Elon Musk runs fast-moving engineering teams:
When talent density is high, management layers do not add value; they add drag. Replacing supervisors with technical lead pods ensures that decisions stay in the hands of the people writing code and training models.
What to Do With This
Map your engineering org chart tomorrow morning. Identify every approval gate that requires an engineer to seek permission from someone who does not write code. Eliminate those checkpoints, group your builders into small technical lead pods, and let technical goals dictate direction instead of middle-management status meetings.