My work life is made up of millions of pixels every day. My teams are distributed across the globe, and most times, my teammates are reduced to pixels in Zoom meetings, Slack chats, and emails. We bring different backgrounds, experiences, communication styles and collaboration preferences, and many more differences to the (virtual) table.

Over the last six years of my career, I’ve gotten to build and support distributed teams across the globe. While it’s been an opportunity that I’ll forever be grateful for and I got to work with fantastic people, it’s also challenged me as a leader and manager.

Much less happens organically through osmosis, or at the literal watercooler, but at the same time many of the challenges all teams face, like communication and collaboration, are exacerbated when we’re distributed across locations and time zones.

The common ways of building and leading teams just can’t be applied easily. That means as leaders, we often need to get much more creative.

At the same time, having to be much more intentional as a manager has helped me learn so much, and I’m thankful for how my teams have helped me improve. The main lesson I’ve learned is that despite not being co-located we can still create stronger, more deliberate distributed teams and produce the same, or even better results, than teams that share the same lunch table.

In this post, I’ll share what I’ve learned about improving teams based on three key “C” pillars: connection, communication, and collaboration. Whether you’re managing teams across the world or in the same building, these approaches can help you become more strategic, communicate better, and build highly aligned, well-connected teams that deliver great products.

Five factors that create high-performing distributed teams

How do you turn complicated, far-flung systems like our widely-distributed system of humans into teams? The research shows that there are five key factors that make teams high-performing:

  • Psychological safety. This means that we feel free to express our work-relevant thoughts and feelings to others, and we believe that they won’t think less of us if we make a well-intentioned mistake or ask for help.
  • Dependability. That means our teams are completing quality work, and doing it on time.
  • Structure & clarity. Everyone needs to understand their role, expectations, and plans.
  • Meaning. Being able to work on tasks that are meaningful to us.
  • Impact. We find a sense of purpose in our work or the output.

Now, the research about high-performing teams doesn’t say that everyone has to be in the same office, sharing the same fridge (based on everything I know about office fridges, that could actually be a good thing). But many of the practices that high-performing teams use are much easier to do when everyone is in the same room.

Team members need to feel free to express work-relevant thoughts and feelings to others, and believe people won’t think less of them if they make well-intentioned mistakes or ask for help.

If building teams is hard overall, then building distributed teams is even harder. Much less happens organically through osmosis, or at the literal watercooler. And many of the challenges that all teams face are exacerbated when we’re distributed across locations and time zones. The common ways of building and leading teams just can’t be applied easily. That means as leaders, we often need to get much more creative.

Three Cs for leading high-performance teams

Creating a high-performing distributed team is fundamentally about inclusion: making sure that everyone has equal opportunities to contribute by leveling the playing field and removing barriers to doing so. At the same time, I believe it’s impossible to replicate the exact same working experience for everyone – and I don’t think that should be the goal. Instead, we should make sure everyone is able to contribute in meaningful ways and do their best work.

So what does it mean to be a leader in a distributed team? We create structures to help people work together in such a way that everyone can do their best work. We provide building blocks for others to lean on and rely on.

As engineering leaders, we’re like the mortar between the bricks: We connect structures, teams, and people.

We hold them together. Our work as leaders isn’t supposed to be about us. It’s about the people and the teams that we support. We build the structures to help others shine.

In my work so far, I’ve been using different approaches to achieve this, focusing on building structures and supporting connection, communication, and collaboration in my teams. Let’s take a look at how you can utilise those to help your teams improve.

Connection: Working together with purpose

As humans, we strive to be connected with a larger purpose. But we also seek to feel connected with other people around us. When we’re in the same location as our teammates, we pick up small signals about them. We see their body language when they walk into the office in the morning. We know if people are tense or if they’re relaxed, or may recognize when they’re having more coffee than usual.

Use small actions to open doors to connections. The small signals get lost remotely, which means other things become much more important, like understanding people’s varying energy levels. When my colleagues in San Francisco start their work day, they’re high-energy and excited. But it’s 5pm or 6 pm for me in Berlin, and it might already be dark out if it’s winter. I’m tired and can’t pull my thoughts together on some days, but still want to be present and focused for my team. In cases like this, it helps if all of us in a conversation are sensitive to the other person’s state of mind, and where we are in our workday.

Make space for humanness. When I joined CircleCI in 2018, I met with everyone in our engineering organization because I wanted to get to know the people we were working with. During one of those conversations, one of our engineers said to me, “I need to meet my team in person every once in a while to remind myself that they’re actual people.” The sentiment struck a chord with me.

When we mostly interact with people in the shape of pixels in video calls or icons in chat apps, it’s easy to forget that there are humans at the other end of the screens.

When we center in on each other’s humanness, we go beyond teammates’ domain expertise. We need to be curious about who they are as people, and know what drives and motivates them.

Communication: Creating clearly defined expectations

Define expectations, and surface what matters. As leaders, it’s our responsibility to make sure that our expectations are always clear to everyone on our team. That’s one of the many reasons why weekly one-on-one meetings are the backbone of our communication, as well as with our relationships with our teammates.

This is especially true when your organization is in high-growth mode. When I joined CircleCI in 2018, the engineering team had been growing by 50 percent year over year, and also increasing in terms of geographical distribution. Conversely, the management team was incredibly small. And after all this growth, we were running into challenges around evolving our engineering culture. We had a bunch of knowledge silos on teams. But at the same time, we had folks who were really keen on growing. What we needed was a way to build a pathway for all of this enthusiasm that would allow us to scale the business.

One of the things we did at CircleCI was create an engineering competency matrix, and communicate it to our teams. It’s our career-growth framework for engineers. This matrix is now woven into everything we do, from hiring, to structured feedback, to performance reviews. It helps us hold everyone to the same standards, and clarify expectations as we scale.

Once we’ve set expectations for growth and performance, the next thing we need to do is communicate these standards and hold each other to them. Praise is a really beautiful way to both connect and communicate as a team. In our company Slack, we have a channel called #gratitude in which people share their appreciation for others who have helped them. It allows us to see how small acts of kindness help us connect as a company.

Grow together. An even better way to connect and communicate as a team is by helping each other grow through constructive criticism. In distributed teams, this can be really difficult to do well. When we mostly see each other on screens, it becomes difficult to have harder conversations.

Feeedback-template.png

I have a template I co-opted from the book Feedback and Other Dirty Words by M. Tamra Chandler that I often use as a starting point. I’ll ask my team to discuss our feedback preferences in this format, then discuss the responses as a group. We use what we learned to give each other much more meaningful and specific feedback.

When we make space for each other’s humanness, we clarify expectations and we help each other grow. We build trust with our teammates, which provides the basis for our collaboration as a team.

Collaboration: Making space for others

We shape collaboration in large part with our own mindset. For example, we need to think often about power dynamics in teams and organizations. Many of us hold explicit or implicit power on our teams – through formal or informal leadership roles, domain expertise, seniority, or tenure. But all of us also carry biases and blind spots. We can set ourselves up for much better collaboration when we approach these biases with humbleness and an awareness of power dynamics.

Stay humble, and make space for others. Just as we try to connect in many small ways, there are small ways we can become better collaborators throughout the work day. For example, we can avoid dominating conversations, even when they are written communications. Think about the times when you’re sending teammates walls of text, or when you bury documents in comments. When we’re in meetings, or when we have discussions in chat, we need to ask ourselves, “How much space am I taking up right now?” It’s our responsibility to open up space for others and invite them into conversations by asking, “What’s your opinion on this? I’d like to hear your thoughts.”

Build foundational relationships. Collaboration is one of the best vehicles that distributed teams have for relationship-building. As leaders, relationships are foundational for us to be able to do our jobs well. But relationships are equally important for everyone on our team, because collaboration is not just about the output of work. Our engineering teams often use the pair programming technique, which helps them strengthen relationships with their teammates and makes teams more resilient. Pair programming also helps us avoid knowledge silos and distribute information – and it’s a really great tool for onboarding new teammates.

Combat hero culture and fix structural issues. “Hero culture” describes a culture where organizations reward very talented people who consistently go the extra mile to get seemingly impossible tasks done by themselves and under lots of pressure. Many companies reward this kind of heroism through promotions, or increasing influence, compensation, or visibility. Hero culture is still incredibly common in our industry, and I’ve seen it have disastrous effects on teams and organizations.

Hero culture is even more pervasive on distributed teams because of the disproportionately high visibility of this type of work compared to other work: “hero tasks” such as single-handedly fixing an issue at times that one normally wouldn’t work often come with high visibility, whereas the hard work around sustaining a team and supporting teammates in the background often goes more unnoticed.

Hero culture not only weakens teams, it also sets up the heroes for failure by putting pressure on them as the only people who can solve problems.

Hero culture is the result of organizational failure and very hard to combat, but it’s our responsibility as leaders to identify and fix it, and make things better for the people affected by it. As leaders, we have a responsibility to combat hero culture by making sure we build the support structures that help avoid or at least reduce the necessity for such acts of heroism. We also need to be mindful of the behaviours that we encourage, reward, and ask people for, even if implicitly or unintentionally.

Building our team continuously

There’s one more “C” pillar that’s important to note here: continuity. Building great teams is a lot of work – and the process is never done. We all constantly grow and change, and the organizations we work in are ever-evolving and full of surprises. This is one of the main reasons why I love working with people so much.

Building teams is a continuous process every single day. No matter where you are in your team’s development – and no matter if your closest teammate sits across the table or across an ocean from you – focus on strong connections, intentional collaborations, and conscious communication with your teammates. Continue building your team every single day, one pixel at a time.