This episode of Leadership Launchpad delves into the leadership principle known as "the line," a concept discussed by Travis Kalanick, founder of Uber, during his conversation on the David Senra podcast. The episode explains how leaders can find the balance between too few and too many rules within their teams and organizations. Drawing from real-world examples at companies like Uber, City Storage Systems (now Atoms), and Netflix, the discussion breaks down the dangers of both chaos and excessive control, and offers insights into how leaders can foster innovation while maintaining necessary structure. Listeners will also hear practical advice for technical managers on communicating expectations, building effective processes, and developing leadership skills that influence where "the line" is drawn in their teams.

Important Timestamps

  • 00:00: Introduction to "the line" leadership principle

  • 01:02: Background on Travis Kalanick and City Storage Systems

  • 02:25: The dangers of chaos in organizations

  • 03:10: Pitfalls of excessive rules and bureaucracy

  • 05:59: Defining the line: minimum viable rules

  • 08:35: The impact of hiring and team diversity on rules

  • 12:45: Three levels of skill and understanding organizational rules

  • 14:39: Uber’s city launch playbook and practical application of the line

  • 18:40: Multi-dimensional nature of the line in scaling organizations

  • 20:09: Setting clear expectations and the link between leadership and innovation

🤖 Automated Transcription

Matt Gjertsen [00:00:00]:

So what you want to find is that line, which is defined by the fewest number of rules that keeps you from tipping into chaos. That spot for where the line is is going to be different in every organization, on every team, and you as a leader have a lot to say with where that line gets drawn. The more you can act as a leader, the more you can get to understand people and figure out how to communicate with them in a way they want to be communicated with. Hello, and welcome to the Leadership Launchpad, where we help technical managers improve themselves, their teams, and their organizations. If you are a technical leader, an engineer or technician looking to become a leader, or someone who supports technical leaders, this is the show to get actionable insights from people who have been in the trenches to help improve your own performance and the performance of those around you. Today's show is going to be a solo episode where I am going to talk about a topic that came up on a recent David Senra podcast where he was interviewing Travis Kalanick. For anyone who doesn't know, Travis was the founder of Uber. After being ousted from Uber, his next job was as CEO of a company that I worked for called City Storage Systems, which was recently renamed Adams.

Matt Gjertsen [00:01:15]:

On the podcast, he talked about a principle called the line. And so today I will explain what the line is, why it is important, and how you can find it as a leader. But before we dive in, I do want to remind you that Minimum Viable Manager is now out. I spent 2 years of my life distilling down all the best leadership practices that I have learned over the last 20 years. So if you are a new leader or someone who wants to become a leader and you're looking for actionable steps to improve yourself, hop on over to Amazon where you can get the book as a paperback, an ebook, Or audio, which I narrated myself. I will put the link in the description below. So with that, what is the line? Now, this was a really interesting topic that though I had been at what was then CSS, now Atoms, I was there while Travis was building it from about 500 people to 2,500 people. It's now grown even more.

Matt Gjertsen [00:02:13]:

Though I never heard him mention the line, now that he talked about it, I know exactly what he's talking about. I saw him kind of building it in real time as the company grew. And so, so let me explain what this means. You have to start by thinking about kind of the, the end, the 2 potential end states of a company if it doesn't go very well. There's 2 different paths that companies go down that often lead them to failure. Path 1 is chaos, right? You never put any rules, you never put any processes. Young founders are saying, oh, we don't need any of that stuff. Why would, why would anybody create these rules? We don't need an employee handbook, yada yada.

Matt Gjertsen [00:02:53]:

And so nobody really knows what's going on. People start stepping over, over one another. People start stepping on each other, and it leads to just a lot of confusion. Things slow down, talent starts to leave. Everybody's sad. So that's, that's one side. The other side that can happen is too much control. We put in— we have a very extensive employee handbook that goes line by line of all the things that have to happen at the company, right? It tells you how much leave you can take.

Matt Gjertsen [00:03:23]:

It tells you, you know, how long a performance improvement plan is going to last. It mandates that every single manager at the company have one-on-ones every week, and they document them using this, this specific process. Over time, those processes, the documentation, the rules, they start to pile up. And just like on the other side, things start to slow down. It gets hard to make decisions. More committees get formed. Nothing can get done. The top talent gets frustrated.

Matt Gjertsen [00:03:51]:

Things dramatically slow down. And again, everybody's sad. This is the description, basically, roughly, that Travis used in his conversation with David Senra. And I really like it because I do think it's true. One of the things that I often say say when talking about things like bureaucracy, the control side, is those who hate bureaucracy the most are the most likely to be eaten up by it, right? Because you ignore it, you think, oh, the processes aren't for us, like we're not going to do that thing. So you just fall into chaos, and then either the chaos becomes out of control and then, you know, the company falls apart because of that reason, or it gets so bad that you have to institute all these draconian rules. I often say that, you know, when you can't lead, poor leadership often becomes dictatorship, right? If you don't know how to lead people, if you don't know how to convince them of the right thing to do, inspire them to the mission, yada yada, then you just become someone who mandates everything and micromanages everything and become a dictator. This is— this kind of discussion is very similar to what you'll hear about the early days of Netflix in the book No Rules Rules, where they very deliberately said, They wanted to create as little process as possible.

Matt Gjertsen [00:05:07]:

They just wanted to hire really smart people so they knew the right thing to do. But I guarantee you, no matter who you hire, they're going to need some direction. They're going to need some kind of processes, if for no other reason than the great new engineer that you just hired shouldn't be trying to figure out from first principles the best way to submit an expense report. Like, that's just stupid. But you do need— so you, so you want some set of skills. The trick is to make sure, or some set of rules, the trick is to make sure those rules aren't so Byzantine and complex that your really smart engineer has trouble following them and they actually get in the way and slow him down. And so these are the 2 sides of the spectrum. And so the way Travis talks about the line, the line is where the sweet spot is.

Matt Gjertsen [00:05:59]:

The line is where innovation and speed of action happens, The line is what is the minimum number of rules that keeps you from falling into chaos, right? So we're trying to minimize rules, but there is a limit to that, right? As soon as people don't know what to do, as soon as people are having trouble, you know, having to spend their energy on things that they shouldn't have to be thinking about, as soon as people are get— you know, people are getting in their own way because everybody's inventing their own way to do this. Perfect, really common example I see of this is early on in a company, the very early stages of a company, documentation isn't a thing. Everybody just puts documentation wherever until you get a lot of documentation. That's like, where is that? Where is that? And that's why everybody has, you know, 800 Google Docs open in their browser at once because nobody knows where those documents are. And so sooner or later somebody says, hey, we need a document repository. We need a place where all of this goes. Which they do. Every company needs some kind of knowledge management process.

Matt Gjertsen [00:07:08]:

But if you don't have some kind of rules or guidance around it, then avionics has their own way they document, and production has their way they document, engineering has their way they document. And sometimes there are unique cases that allow for that or that warrant that. But the majority of the time, it's just 3 different people who decided 3 different ways to do it. And in my experience, you've tipped over a little bit into chaos because now there's all these different places and, and still nobody knows where to go to find the information that they actually need. So the line that Travis talks about is the minimum number of rules that you need to not tip into chaos. And he says that's the sweet spot. That is where innovation and speed of action happen. Just enough rules so everybody's clear what to do, but not so many rules that they're getting in the way of doing what actually matters.

Matt Gjertsen [00:08:07]:

So I love that description. I think it's fantastic. As a leader, the interesting thing to understand is that in every team, in every organization, where that line sits is going to be different. You as a leader have a lot of impact on whether or not that line is more towards control Or more towards chaos. And so I want to talk about some of the things that you need to be thinking about as a leader to influence that, right? One, the thing that everybody brings up, the thing that came up when we were talking about Netflix, is hiring. Who are you hiring, right? If you set and hold a really high bar for talent, then chances are You're gonna be able to lean a little bit more towards chaos. They'll need a little bit fewer rules, fewer processes, because everybody has a common understanding. But I think that misses a few things because high bar of talent, high bar of experience can mean that.

Matt Gjertsen [00:09:12]:

But there's an interesting way you can accidentally create a group that you think doesn't need a lot of rules because they're high talent, when actually it's not the talent piece that's doing it. And this is what happens very often in early startups, where who are you hiring? You're hiring your friends, you're hiring the people that you know, the people that you've worked with before. And so if everybody has a common background, it makes it really easy to skip over a lot of rules because there's a lot of assumptions that can be made that everybody understands. Everybody's in on the joke. Everybody understands the way things are supposed to go. Everybody's been out at restaurants and understands what a proper meal expense is. Everybody's traveled or they've seen their parents travel on business trips and they know that you don't just swipe your company credit card and get first class just because, right? There's lots of assumptions that when you start with a small group of people, where everybody has similar experiences. The place where all of a sudden a lot of struggle happens is you grow beyond that and you start to hire people with different backgrounds, which you need to because you need diversity of thought, diversity of experience if you want to make sure you're finding the right answer to things.

Matt Gjertsen [00:10:33]:

But with that different experience, you're going to bring on people on the team who don't have an automatic shared understanding of what's right and what's wrong in every situation. And so that's where slightly more processes tend to kick in. The place that gets people into trouble is where they treat it like whack-a-mole, right? Where it's like, oh, this was a mistake, let's do that. This was a mistake, let's solve that. This was a mistake, let's solve that. And all of a sudden you're creating all these one-off rules to handle these individual situations. And what you need to be doing instead is kind of pulling back and thinking a little bit bigger picture. of what don't people understand here.

Matt Gjertsen [00:11:14]:

Maybe they don't understand how their actions connect with the success of the company or the, the financial state of the company. Maybe somebody's never drawn that line for them before. As a, as a founder or somebody who's worked in startups, it's really easy to understand that. If somebody's never worked at a startup, for somebody who's coming from a large Fortune 500 corporation, if they don't have any rules like The concept of money might be completely foreign to them because the company had like infinite money. Like it was just like this crazy expense report that the sales team is spending millions and millions of dollars every single year putting on different events and stuff. And so what's my, you know, $500 upgrade for my airline ticket? And so all I mean to say is that you as a leader, when you feel like you're having to start putting a bunch of rules in place for a company or for your team, You wanna be thinking about what's the missing link here? What's the thing that people aren't understanding? Is there a way that I can get at the root cause of this to help understand the why a little bit more so that I don't have to have all these rules in place? I remember very clearly, so when I was in college, I used to do speech and debate. And after I did, I was really successful, went to nationals and all kinds of stuff. And then the year after I graduated, I came back and judged a couple of events.

Matt Gjertsen [00:12:45]:

And I remember watching a number of people and judging them and everything. And I kind of formed this framework that when you're learning something new, and I think this applies to anything, but in this context, I was thinking about speech and debate, there's really 3 levels of skill. And I generally think this is true. There's 3 levels of skill. Level 1 is learning the rules, right? Like you're a novice, you're figuring out how to do this thing. So in this case, what does a good speech look like? How do I hold myself? How quickly do I talk? What's the pacing, all that stuff. So you're learning the rules. Then level 2 is someone who knows the rules and they can execute within them.

Matt Gjertsen [00:13:25]:

And they, you know, make sure it's all, it's like 5-paragraph essay format where I say this thing and then I have my 3 supporting arguments and yada, yada. And so they know the rules and they can execute well within them. And then level 3 is someone who knows the rules. They know the reason for the rules. So now they can work outside of the rules. They don't have to follow the same structure in their speech because they know that that structure is meant to provide a clear roadmap for the listener to follow along. They can provide that roadmap in a different way, and it just, you know, lets them kind of do whatever they want and still be amazing. And so I think inside organizations, that's something that you need to be thinking about when you're thinking about setting up all these rules of Ask yourself, is there a simpler way? Is instead of putting in place all these rules, is there a why behind this that I can explain and, you know, really show people that makes it so I don't have to have a whole bunch of rules? So that's the final point I want to dig into here a little bit of what's some realistic advice for a leader who wants to think about how do I minimize the number of rules that I have on my team? And there was a fantastic example that Travis brought up in David Senra's podcast where they were talking about Uber, because Uber kind of famously was very on the, the chaos side of things, where something that they did to move really quickly is, at least from the outside point of view, it looked like Travis had empowered all of these general managers, right? Like, you're in charge of a city, you're in charge of a city, and they just went in and launched it themselves, and they had very little oversight It was very much survival of the fittest.

Matt Gjertsen [00:15:11]:

You go do your thing and check back in with us when the city's launched or something. That's kind of how it appeared from the outside. And that's how David kind of presented it on the show to ask Travis for his input. And Travis said, no, no, no, that's not it. Their goal was very much to define where is the minimum set of rules, because you can imagine a world where if you're a company that's like Uber is, you know, they're going global for the first time, they're moving out, and they— the way they launch in individual cities, you could have this really detailed list of requirements and things you have to do and meetings that you have to tick off and a whole committee that signs off and on on, on whether or not things are done correctly. And what it came down to, though, the, the rule, the one rule that they had to keep in place enforce is that you couldn't launch a city until you passed the pricing call. The pricing call was with Travis. He was there.

Matt Gjertsen [00:16:11]:

And it was basically a brief of the situation of these are the kind of cars that we're gonna have. These are the kinds of pricing we're expecting. These are the limits that, you know, it's a run-through of all the things that the general manager had thought about, regulation, local regulations, how they're gonna comply with them, what ones they think they can avoid, all that, right? That ultimately results in this is the price that we're going to be charging so that we can expand and make money. And the way he described it, so that's the only rule. You don't launch until you pass the pricing call. Early cities, they had 8 pricing calls, right? Where Travis would ask a question, they didn't have an answer. He said, well, go figure it out. And they'd go figure it out and they'd come back.

Matt Gjertsen [00:16:57]:

And then every time they ran into one of these situations, where Travis asks a question and they don't have an answer or they don't know what they're going to do, they would put it in a playbook. They would document it. It's not a rule of something you have to follow. It's a playbook of something that you just make sure you're thinking about, right? And so the first city they launched, you know, maybe the first 5 cities they launched, it took 8 pricing calls, and then eventually it took 5, and then it took 3, and eventually it got to the point where there was only 1 pricing call. Where the people knew enough about the background, about what was going on in Travis's head, the why behind all the questions that he was asking. The documented playbook truly wasn't just a list of boxes to check, it was a list of this is how you need to be thinking about launching a city, right? So it taught them how to think about it. It taught them Travis's process of how he was thinking about it. And so by those later cities, somebody follows the playbook, they're an experienced GM, they just run the one pricing call and they learn everything, right? And, and he— they answer all the questions and Travis is like, okay, you can go, you can go launch.

Matt Gjertsen [00:18:11]:

So I thought that was a great example of it wasn't about creating a bunch of boxes to check, it was a process for how do I get people thinking the way I want them to be thinking about these problems, 'cause then the only rule is that one final rule, right? And so that's just what I think is such an amazing example is of a way to find that line, 'cause Travis was very clear, is this isn't a one-dimensional line. There's 80 different dimensions in where this line is drawn. There's the financial dimension, the quality dimension, the time dimension, how we treat people dimension. There's so many different dimensions. And so that's why it's a really complex problem. But if we— to summarize this, the challenge of getting larger and larger groups of people to work together is that everybody is coming together with different experiences, different assumptions, different values, and you're trying to bring all those people together, get them oriented going towards the same common goal. And if you don't put any rules in place, Then all those different assumptions and experiences are gonna create a lot of variation in how people decide to act, and people are gonna start getting in each other's way. It's gonna slow people down, and people are gonna be sad.

Matt Gjertsen [00:19:28]:

On the other hand, if you put all these rules in place to make sure no one can act out of turn because there are rules in place to make sure they don't act out of turn, everything slows down and everybody's really sad. And so what you wanna find is that line which is defined by the fewest number of rules that keeps you from tipping into chaos. That spot for where the line is, is gonna be different in every organization, on every team, and you as a leader have a lot to say with where that line gets drawn. The more you can act as a leader, the more you can get to understand people and figure out how to communicate with them in a way they wanna be communicated with. The more you can learn to set clear expectations for your team that includes the why, right? Why are we here? What are we trying to do? And the more you can build in natural feedback so that people learn the reason— not only how to follow the rules, but the reason behind the rules— doing those things, doing those basic leadership principles allows you to push that line closer and closer to the chaos side, because that's where the speed happens. That's where initiative and inventiveness exist. If you look at SpaceX, I can, I can tell you from the inside, not just from the outside, SpaceX is very chaotic. These— if you're trying to create a really innovative team, get control of everything, it's not going to work out very well.

Matt Gjertsen [00:21:00]:

This is not So if you want a reason, I'll end with this. If you want a reason to become a better leader, it is this. Your ability to lead will directly influence how close to the chaos side you can be and how much innovation and performance you can expect from your team. I hope you found this helpful. We got some more guests next week, and I'm thinking pretty soon I'm just gonna do a deep dive in Minimum Viable Manager. Kind of, there's 4 parts to it. I'll just go through one part at a time. per episode, really, you know, dive into it so that people can get a sense of what's in the book.

Matt Gjertsen [00:21:37]:

But until then, I hope you found this helpful, and I look forward to seeing you next time on the Leadership Launchpad.

Subscribe to listen to your favorite episodes!

Listen on

Spotify

Listen on

YouTube

You may be interested in