Phalanx Engineering: Lessons in Building Teams That Hold the Line
I’ve always liked the analogy of a phalanx for engineering teams. It captures something deeper than “teamwork” or “collaboration.” It’s about survival, discipline, and trust under pressure.
In a phalanx, soldiers overlapped their shields to protect the person beside them. Strength came not from heroes but from formation: no gaps or egos, just clarity, discipline, and commitment.
The Leader’s Position
The rightmost position in the phalanx was known as the “position of honor.” It was also the most exposed. The leader stood there without protection on one side, responsible for making the hard calls and absorbing the pressure.
Leadership in engineering often feels the same. You don’t get a shield. You take hits. Your role isn’t to be protected, it’s to protect.
Lessons From the Phalanx Model
Over time I started thinking about this metaphor not just as imagery but as a way to shape how teams operate. A few lessons emerged:
- Shield: Support each other, hold the line, advance together.
- Spear: Drive forward with new products while clearing tech debt with precision.
- Helmet: Stay focused through discipline and clear priorities.
Different situations call for different “formations”:
- The Bash: A coordinated strike to knock down major tech debt.
- The Push: An all-out effort to deliver a high-impact initiative.
- The Turtle: A defensive stance, protecting stability while still moving forward under pressure.
Scaling the Formation
I’ve found this way of thinking useful as teams grow:
- Squad: 5 engineers
- Line: 2 Squads (10 engineers)
- Formation: 5 Lines (50 engineers)
- Phalanx: 2 Formations (100 engineers)
Every engineer belongs to a Home Team for domain ownership and mentorship, while Task Forces form across domains for speed and focus. An Architecture Review Board helps keep direction coherent without slowing execution.
Growth and Leadership
Advancement in this model isn’t about titles, it’s about how much of the shield line you can protect:
- Technical leaders scale impact across systems and domains.
- Engineering managers hold the line for multiple squads.
- Executives are responsible for the entire phalanx.
Progression is measured not by individual brilliance but by how much trust and resilience you can add to the formation.
Why This Matters
Google’s Project Aristotle studied 180 teams and found that psychological safety, not individual talent, was the strongest predictor of team performance. Rewrites, pivots, and crises will always come. The question is whether your team breaks formation, or holds.
Phalanx Engineering isn’t a rigid framework. It’s an ethos, a set of lessons that I’ve seen work in practice, and a reminder that the strength of a team comes not from individuals, but from how well we protect and advance with each other.
What would your engineering culture look like if you ran it like a phalanx?