Refactoring

Refactoring

Share this post

Refactoring
Refactoring
Unconventional Team Structures (Part 2) 🏰
Copy link
Facebook
Email
Notes
More

Unconventional Team Structures (Part 2) 🏰

The story of rebel companies such as Zappos, Valve, and Morning Star, with lessons we can take from them.

Luca Rossi's avatar
Luca Rossi
Aug 11, 2022
βˆ™ Paid
8

Share this post

Refactoring
Refactoring
Unconventional Team Structures (Part 2) 🏰
Copy link
Facebook
Email
Notes
More
2
Share

Hey welcome back! Last week I published the first of this two-part series β€” you can check it out below if you haven’t already πŸ‘‡

Refactoring
Unconventional Team Structures (Part 1) 🏰
A couple of weeks ago I had a chat with a VC who is also a reader of Refactoring. We agreed that today there starts to be some consensus about how to structure engineering teams, while just 10 years ago, when I founded my first startup, things were pretty messy…
Read more
3 years ago Β· 7 likes Β· Luca Rossi

In the previous part we covered some introductory topics about scaling tech orgs, including hierarchies and autonomous teams, with examples from companies like Spotify, Coinbase, Amazon, and Riot.

We also covered in-depth case studies about two tech companies (Dimagi and ProntoPro) who came up with originalteam configurations, while still retaining some traditional processes and roles.

This second part is dedicated to rebellious companies that challenged most conventional wisdom about how teams should work. They turned things upside down and were successful with it.

We will talk about:

  • πŸ₯Β Alan β€” one of the largest insur-tech companies in Europe. It runs without managers and without HR.

  • πŸ‘Ÿ Zappos β€” a 1500-people e-commerce that turned into a self-organizing city, by applying the fairly obscure holacracy framework.

  • πŸ•ΉοΈ Valve β€” one of the most successful names in gaming. There are no managers and people can work on whatever they want.

  • πŸ… Morning Star β€” the largest tomato processing company in the world. Employees self-manage by creating contracts between themselves.

Researching these companies has been quite a journey. I went into a rabbit hole that includes articles, interviews to former and current employees, glassdoor reviews, and more.

The goal of this piece is to give you the most important bits of how such companies work, and, most importantly, why they do so.

At the end, I will comment on the main, common ideas behind how these teams work, covering:

  • βš–οΈ Upsides and downsides β€” based on my own experience and on opinions from former and current employees of those companies themselves.

  • Who is this for β€” which kind of companies would benefit from applying these systems, and which not.

  • What can we take from it β€” can we take only few pieces and apply them to our traditional team? Or are these all-or-nothing frameworks?

Let’s go! πŸ‘‡


Hey πŸ‘‹ this is Luca! Welcome to a new πŸ”’ weekly edition πŸ”’ of Refactoring.

Every week I write advice on how to become a better engineering leader, backed by my own experience, research and case studies.

You can learn more about Refactoring here.

To receive all the full articles and support Refactoring, consider subscribing πŸ‘‡

Become a better tech leader today ✨


This post is for paid subscribers

Already a paid subscriber? Sign in
Β© 2025 Refactoring ETS
Privacy βˆ™ Terms βˆ™ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More