Leadership Principles for Remote Teams (and All) with Jason Warner, CTO @ Github #5

Leadership Principles for Remote Teams (and All) with Jason Warner, CTO @ Github #5

Uncover the leadership principles that drive success in remote teams, as shared by Jason Warner, CTO at Github. Delve into his insights and strategies, applicable not only to remote teams but to all, in our fifth installment of this series.

Don’t have relationships over there, start it

Have regular one-on-ones with your head of legal, head of infrastructure, or head of sales

What does the process of for hiring people in a fully remote process look like?

It’s not much different to what an in-person hiring process would look like.

The closing question for communication:

What’s your recommendation for choosing the right tool for the right scenario?

The way to scale

As companies are going to be scaling, not many people have seen it.

Most organizations look more like a horizontal line

The CEO never gets feedback on certain things or contexts

What I had learned over the last couple of years is a couple of things:

My glutes… what happened is my hamstrings and my lower back, the glutes sit in between them… and my glutes stopped working appropriately.

If there’s a 1B, it’s video just like this

everything else after that is a “super nice to have”

Jerry Li: And going back to all the pain points and challenges we talked about so far, I know you have a great analogy that incorporates all these elements into a very easy to relate to example.

Jason Warner shares an example of something very personal to him because over the last couple of years he’s developed a set of pains in his body.

Interesting cues to pay attention to

Jerry Li: Through this whole phone call, there’s been this image coming in my head of this… almost giant chessboard…

Two other things to keep in mind:

Never reward bad behavior.

How do you create smooth communication downwards, upwards, and lateral?

Ensure that lateral communication also happens in a healthy way

Have you read “The Subtle Art of Sabotage?”

Yes, it’s a book by Patrick Gallagher about how you can slow down the enemy in subtle ways.

The other is, when you timebox something, the natural reaction is for every engineering organization to say… “Can’t do this in that timeframe… Whatever this bit is, is too big to fit inside that box…”

In fact, you can’t have meaningful chunks broken down into small discrete units of time, which are one or two weeks.

What have you done to set up the relationship with the canaries to just be really straight with you about feedback?

Anyone can be a canary. I think of it as people whose feedback I genuinely trust and value because over time they’ve proven that they have the perspective that you want.

ProtoBus

Think of it as a ProtoBus – you send packages of information around the organization and you want them to be opened up and read

revisit decisions

You should be doing it intentionally

Jason Warner: Sure.

Communication pathways inside your organization that need to exist and the appropriate actions or responses that happen in each one of those levels

You’re talking about weeks and months before you’ve got that stuff tamped down.

You should have been investing in this stuff way before you needed it

When do you actually need that last 9% to become great?

We’ve never tried it the other way. Maybe my percentages are that in-person is actually 95%, in videos its 94% and I’m using the wrong percentage differences.

Bottom Line

You need to say something 4x-5x and you need to broadcast it. You don’t say something in Slack and then know the things.

If you can get 90% of the 90% with video, you can optimize the last 9%

You largely only need it in certain contexts. You don’t need it everywhere.

What does the role of in person interaction play in terms of creating engagement?

Video can play a role in that up to a point of 90%.

“Reopening of decisions made”

“We’ve made a decision, we’re going to go do this. The right people that communicate it to the right pathways have been done. Everyone’s on the same page… And then someone literally pops up from somewhere and says, “you know, I think we should revisit this decision. I just want to have the discussion again. I want to do that.” It’s not based on data. It’s more of wanting to have that discussion again, time to revisit it.”

You get the most viable decision if you’re looking for the fastest decision

Do two people in an interview with a candidate

When is the customer going to see this for the first time?

Project status is always a good one, which is… “All projects are green until one week before they’re due, and then they’re red.” That’s just the nature of the business.

What’s brought you the greatest joy as an engineering leader?

Seeing something that shouldn’t have existed in the first place, NOW EXISTS because you were able to go do something.

A good example of this is the original GitHub actions team at GitHub.

They put out a grand vision for what “GitHub Actions” was supposed to be in five years and then broke it down to what they wanted to see it get done in a two week sprint to show the world that GitHub was going to be something different.

Communication is so complex and the fidelity of it is so important, in that if you can use the higher fidelity forms, you’re able to better make it happen.

“Crisis” and “opportunity” are sort of represented with the same Chinese characters

If you could only choose one tool, choose the one that becomes your institutional memory

GitHub is a quintessential institutional memory tool

If you think about an organization, it has a large neural net.

You can train each node to make decisions that you would typically make, or better than you would, while you’re not in the room

Timebox everything

Everything should be timeboxed into one week sprints one week, two weeks, quarters, whatever. Figure out what those time boxes are.

Jason Warner: My biggest fear is that I’ve got blind spots as a leader

As I progress in my career as I have more responsibility or as my teams grow, people are going to filter information to me

Resources

Challenges with trust, communication, and engagement are NOT unique to remote teams.

Signs of mistrust

The easiest way to know there is mistrust is to hear things from others about others

Scaling leadership by applying the right tools and frameworks for effective communication

Jason Warner, Senior VP of Technology at GitHub, shares management principles fundamental to how he leads remote engineering teams.

Find out the canaries in your organization

Are people that are great examples of who your organization should be on its best days

How do you go about curating and building that out?

It all starts with you as a leader. You should be building these relationships with everyone in your organization or as many people as possible, from the beginning.

A pre-investment before you need it

Get in shape over a period of time. If you got out of shape over the course of 20 years, you’re not going to get in shape, in a matter of weeks.

You need to create the best organization that you can and know that you are going to be taking some of that burden on for your organization, but your organization itself will be much better running and smooth.

In a remote setting, if you ever think that you’re having a miscommunication with somebody, jump to video right away!

Engagement

Have some standing check-ins

CEO

Every leader in an organization should make the decisions that ONLY they can make and delegate all the other ones

Video calls

Being expressive through your hands and facial expressions are important

If you are taking your over communicative approach, figure out how everybody in your organization can absorb that for their context

If you’re small enough, you try to never work through layers even though layers are important for the execution of things

Most organizations will be remote first because remote is better access to talent

Focus on the first 90% to reach your goal

Source

Get in