Arm

What that means is you really want a team who can own a problem and not be matrixed across 10 different things where they have to coordinate a bunch. In some ways, I think about it like a computer program, where when you have a big monolithic computer program, it's very efficient as long as that monolithic computer program is small.

What that means is you really want a team who can own a problem and not be matrixed across 10 different things where they have to coordinate a bunch. In some ways, I think about it like a computer program, where when you have a big monolithic computer program, it's very efficient as long as that monolithic computer program is small.

What that means is you really want a team who can own a problem and not be matrixed across 10 different things where they have to coordinate a bunch. In some ways, I think about it like a computer program, where when you have a big monolithic computer program, it's very efficient as long as that monolithic computer program is small.

As it gets bigger and then you have multiple people working on that program, then you get a mainframe and it's very slow and you can't iterate on it and you can't move fast. So what you do is you decouple. You then build services and they talk to each other through well-defined APIs. Then you continue to decouple those programs, you continue to refactor.

As it gets bigger and then you have multiple people working on that program, then you get a mainframe and it's very slow and you can't iterate on it and you can't move fast. So what you do is you decouple. You then build services and they talk to each other through well-defined APIs. Then you continue to decouple those programs, you continue to refactor.

As it gets bigger and then you have multiple people working on that program, then you get a mainframe and it's very slow and you can't iterate on it and you can't move fast. So what you do is you decouple. You then build services and they talk to each other through well-defined APIs. Then you continue to decouple those programs, you continue to refactor.

That's how you build modern technology systems. You can think about containers as the current way of doing that, which is really small, independently running systems that can talk to each other through APIs. Now, if you think about org structure, it's not that dissimilar from that.

That's how you build modern technology systems. You can think about containers as the current way of doing that, which is really small, independently running systems that can talk to each other through APIs. Now, if you think about org structure, it's not that dissimilar from that.

That's how you build modern technology systems. You can think about containers as the current way of doing that, which is really small, independently running systems that can talk to each other through APIs. Now, if you think about org structure, it's not that dissimilar from that.

If you think about how do you have teams that can run really fast and there is going to be coordination, but what you want to do is minimize that coordination tax as much as possible. So if you have a well-defined API between them effectively, which is like I build a service over here, you build a service over here, we can go innovate.

If you think about how do you have teams that can run really fast and there is going to be coordination, but what you want to do is minimize that coordination tax as much as possible. So if you have a well-defined API between them effectively, which is like I build a service over here, you build a service over here, we can go innovate.

If you think about how do you have teams that can run really fast and there is going to be coordination, but what you want to do is minimize that coordination tax as much as possible. So if you have a well-defined API between them effectively, which is like I build a service over here, you build a service over here, we can go innovate.

Occasionally, our teams will get together and make sure that we broadly know what our vision is. We want to know what the thing is that we're running towards. But then I can go and in particular, my service or my organization or whatever it is or my feature can run independently and not have to

Occasionally, our teams will get together and make sure that we broadly know what our vision is. We want to know what the thing is that we're running towards. But then I can go and in particular, my service or my organization or whatever it is or my feature can run independently and not have to

Occasionally, our teams will get together and make sure that we broadly know what our vision is. We want to know what the thing is that we're running towards. But then I can go and in particular, my service or my organization or whatever it is or my feature can run independently and not have to

have a coordination like if high-level, if the EC2 team and the S3 team had to talk every time they were going to go launch a feature to make sure it worked together, we would move really, really slow. But we don't and so the teams can move really fast and then we make sure like we have, it's part of the leadership and the product leadership team to get together and say, okay,

have a coordination like if high-level, if the EC2 team and the S3 team had to talk every time they were going to go launch a feature to make sure it worked together, we would move really, really slow. But we don't and so the teams can move really fast and then we make sure like we have, it's part of the leadership and the product leadership team to get together and say, okay,

have a coordination like if high-level, if the EC2 team and the S3 team had to talk every time they were going to go launch a feature to make sure it worked together, we would move really, really slow. But we don't and so the teams can move really fast and then we make sure like we have, it's part of the leadership and the product leadership team to get together and say, okay,

We think going after this space is super important. And some of that is customers are going to want this use case. And so broadly, we're going to have to go after this thing. But we can still then have the teams go out and run fast. That is the organizing principle. And then there's other parts of the organization where we have teams that run kind of the data centers and other global.

We think going after this space is super important. And some of that is customers are going to want this use case. And so broadly, we're going to have to go after this thing. But we can still then have the teams go out and run fast. That is the organizing principle. And then there's other parts of the organization where we have teams that run kind of the data centers and other global.