Adam Jacob

For us, the decision was, what we want is to build a transformative product that we believe people could use across the spectrum from giant banks to small companies, and that they could use this technology to really run the entirety of their infrastructure automation, but eventually the whole of the DevOps stack. So we had to make trade-offs on how much time are you willing to spend?

For us, the decision was, what we want is to build a transformative product that we believe people could use across the spectrum from giant banks to small companies, and that they could use this technology to really run the entirety of their infrastructure automation, but eventually the whole of the DevOps stack. So we had to make trade-offs on how much time are you willing to spend?

How much effort are you willing to expend? How difficult is it in order to get that vision to come into fruition? Where at each stage, there's an off-ramp where you could build a less powerful thing. You could decide to bring a version of it that is less functional, a version of it that maybe does a little less or is a little less valuable. And you have to decide, is that what you want to do?

How much effort are you willing to expend? How difficult is it in order to get that vision to come into fruition? Where at each stage, there's an off-ramp where you could build a less powerful thing. You could decide to bring a version of it that is less functional, a version of it that maybe does a little less or is a little less valuable. And you have to decide, is that what you want to do?

How much effort are you willing to expend? How difficult is it in order to get that vision to come into fruition? Where at each stage, there's an off-ramp where you could build a less powerful thing. You could decide to bring a version of it that is less functional, a version of it that maybe does a little less or is a little less valuable. And you have to decide, is that what you want to do?

Or do you want to keep building the more powerful thing that you really believe is transformative in the end? There's tons of smaller technical trade-offs. For example, we started out by modeling Kubernetes. We then learned that while there were plenty of people who had complaints about Kubernetes, overall, the market kind of still was a little in love with it.

Or do you want to keep building the more powerful thing that you really believe is transformative in the end? There's tons of smaller technical trade-offs. For example, we started out by modeling Kubernetes. We then learned that while there were plenty of people who had complaints about Kubernetes, overall, the market kind of still was a little in love with it.

Or do you want to keep building the more powerful thing that you really believe is transformative in the end? There's tons of smaller technical trade-offs. For example, we started out by modeling Kubernetes. We then learned that while there were plenty of people who had complaints about Kubernetes, overall, the market kind of still was a little in love with it.

People would be like, yeah, that bothers me, but it's fine. And there were other tools that we could focus on modeling more like the experience of putting together your infrastructure for AWS, for example, where people hated it. When you ask them, how do you feel about the tools that help you manage all your AWS infrastructure? It was like grudging respect was like a pretty good answer.

People would be like, yeah, that bothers me, but it's fine. And there were other tools that we could focus on modeling more like the experience of putting together your infrastructure for AWS, for example, where people hated it. When you ask them, how do you feel about the tools that help you manage all your AWS infrastructure? It was like grudging respect was like a pretty good answer.

People would be like, yeah, that bothers me, but it's fine. And there were other tools that we could focus on modeling more like the experience of putting together your infrastructure for AWS, for example, where people hated it. When you ask them, how do you feel about the tools that help you manage all your AWS infrastructure? It was like grudging respect was like a pretty good answer.

And so it made more sense to think about moving the product in that direction because A, it was easier to focus in on, but B, there was a little more discontent with the shape of the tooling that they already had.

And so it made more sense to think about moving the product in that direction because A, it was easier to focus in on, but B, there was a little more discontent with the shape of the tooling that they already had.

And so it made more sense to think about moving the product in that direction because A, it was easier to focus in on, but B, there was a little more discontent with the shape of the tooling that they already had.

Roadmaps are tricky, right? There's a comedian who had a quote. I wish I remember their name because I'm going to quote them now. I'm sorry that I don't. But when somebody comes to you with a problem, they're usually right about the problem and they're totally wrong about the solution. Conceptually, this is very true in products.

Roadmaps are tricky, right? There's a comedian who had a quote. I wish I remember their name because I'm going to quote them now. I'm sorry that I don't. But when somebody comes to you with a problem, they're usually right about the problem and they're totally wrong about the solution. Conceptually, this is very true in products.

Roadmaps are tricky, right? There's a comedian who had a quote. I wish I remember their name because I'm going to quote them now. I'm sorry that I don't. But when somebody comes to you with a problem, they're usually right about the problem and they're totally wrong about the solution. Conceptually, this is very true in products.

Like people will tell you if somebody comes, if you have a customer come and tell you what's wrong with your product, they probably come with an answer to what they think you should do. And that answer is usually the wrong thing because there's usually no delight to be found in it, right?

Like people will tell you if somebody comes, if you have a customer come and tell you what's wrong with your product, they probably come with an answer to what they think you should do. And that answer is usually the wrong thing because there's usually no delight to be found in it, right?

Like people will tell you if somebody comes, if you have a customer come and tell you what's wrong with your product, they probably come with an answer to what they think you should do. And that answer is usually the wrong thing because there's usually no delight to be found in it, right?