If I Built Another Engineering Org Tomorrow, I'd Skip the Org Chart

Twelve engineers and the company ships. At forty the same company feels slow, and the first move is usually a new org chart. I have built DevOps, SRE, platform and product teams, started new ones inside companies that already had their habits, and taken Mews engineering from eight teams to eighty through Series C. The chart was rarely the thing that fixed it.

We go through what I would do differently now: team design before boxes, a mission each team can say out loud without reading it, and the leadership work that survives a reorg. You leave with the 30-60-90 day guide to leading a new dev team, written for the first three months of a team that did not exist before.

The technology changed. The fundamentals did not. Most org-design talks come from someone who drew one chart, once, at one company. This one covers DevOps, SRE, platform and product teams, new teams started inside established companies, and one organization spread across locations and time zones, which is where most clean structures quietly stop working.

Built for CTOs and VPs who already ran the reorg and got three good months out of it. The close is the 30-60-90 day guide to leading a new dev team, so the room leaves with the first ninety days written down instead of a diagram to redraw.