How to foster teamwork on a leaderless team

Fostering teamwork on a typical team is difficult enough, but how is it done on a team without designated leaders?

Self-managed or self-organized teams—whether they’re temporarily without a leader or intentionally structured that way—are becoming increasingly more common in the modern workplace, especially in the tech sector.

There are self-managed teams that operate within conventional organizations that simply don’t have a direct leader for various reasons. On the other end of the spectrum, there are massive companies like Zappos and Valve that make it their goal to create truly leaderless organizations.

For the purposes of this article, when I talk about a self-managed or leaderless team, I mean a team or organization that’s a) without a direct people manager or any one person who’s in charge, and b) a team that makes decisions and delegates workload as a group.

Let’s look at some of the ways in which leaderless teams are able to foster teamwork.

The nature of self-management is teamwork

What’s the goal of a self-managed team? According to Andy Doyle, former Head of Operations at Medium, a self-management structure “aspires to empower individual voices and avoid the bureaucracy that often accompanies traditional organizational structures.”

Depending on a number of factors including its size and purpose, the way in which a self-managed team fosters teamwork is going to be vastly different and more involved than a team with a more traditional hierarchy. Why? Because a self-managed team’s greatest benefit, a more open approach to decision-making, can sometimes be its greatest detriment.

In a typical team structure, there’s generally one lead who ultimately has the final say on team decisions and overarching strategy. On a self-managed team, this isn’t always the case.

Rather, the floor is wide open for discussion on everything from day-to-day tasks, delegating work, keeping each other accountable, all the way up to making decisions on major projects and big picture strategy. As you can imagine, teamwork is essential for self-managed teams.

Because of this, teams with a decentralized, horizontal power structure by their very nature will require rigorous debate and an almost evangelical commitment to process.

Process, process, process

On a leaderless team, collaboration is key. A lot of collaboration. And because there’s a wider variety of opinions at play (each given equal weight, in theory anyway) there needs to be a robust decision-making process firmly in place to allow room for debate and discussion.

At Zappos, and other organizations that have adopted the Holacracy organizational structure model, that process takes the form of “tactical meetings." These meetings follow a rigid format that resembles the following:

1. The Facilitator asks: “What do you need?”
2. The agenda item owner engages others as needed.
3. The Secretary captures any Projects and Actions requested & accepted by any circle member.
4. The Facilitator asks: “Did you get what you need?” If yes, we move to the next item on the agenda.

At first glance, these meetings seem unnecessarily abstract and overly official—and they are—but they’re designed that way for a reason: to ensure that each attendee is given equal time and opportunity to voice concerns and participate without interruption. (There’s a more relaxed, though still regimented, discussion portion that takes place later on.)

Similar to scrum, which involves self-management to a large extent, tactical meetings are moderated by a facilitator who isn’t in a management role but is present to help remove obstacles in decision-making, fast-forward the meeting process, and ensure the rules of the format are adhered to by all parties.

Perhaps this makes sense at a company as large and complex as Zappos where other non-hierarchical process styles might be grossly inefficient. But what about companies whose size and organizational structure necessitates a different approach?

Diplomatic decision-making

At Jostle, the design team is a small self-managed team within a traditionally structured company. Each member of the design team is given the job title of UX Designer and there’s no official senior or lead designer (at the time this article was published).

I spoke with two members of the team, Elliot Mah and Justin Alm, to get a sense of how their self-managed team operates. I quickly learned that their process is less informal than the tactical meetings of Holacracy, but still relies heavily on direct communication and clear articulation of ownership and ideas.

“We have a fairly diplomatic process regarding decision-making, and our team is mature enough to do a cost-benefit analysis when we’re changing anything significant. But sometimes it takes some extra work to illustrate your arguments, which isn’t necessarily a bad thing, just very democratic and sometimes slower than what other teams might be used to.”

Justin Alm, another UX Designer and author of an internal document that outlines how the design team functions as a self-managed team, explains:

“We generally use the term co-creation to describe collaboration between coworkers and teams—our internal culture of design. Because the design team works at the intersection of many projects and teams, it’s important that we discuss our capacity for taking on work with the team when making decisions about who takes on which project.”