Egil Østhus

Oh, I love this question. This is so difficult for everybody in product. I think we have, we spent quite a bit of time putting on kind of how do we kind of deal with that, this question, because this was one of the questions or trade-offs we sort of was starting to focus on early on. So in our case, I would say there is a few dimensions there because you bring in the kind of the technical depth.

Oh, I love this question. This is so difficult for everybody in product. I think we have, we spent quite a bit of time putting on kind of how do we kind of deal with that, this question, because this was one of the questions or trade-offs we sort of was starting to focus on early on. So in our case, I would say there is a few dimensions there because you bring in the kind of the technical depth.

Oh, I love this question. This is so difficult for everybody in product. I think we have, we spent quite a bit of time putting on kind of how do we kind of deal with that, this question, because this was one of the questions or trade-offs we sort of was starting to focus on early on. So in our case, I would say there is a few dimensions there because you bring in the kind of the technical depth.

Technical depth is very important to don't lose track of, obviously. But it's also what is the next feature you want to add to the product, right? Because Because eventually you want to gain more adoption to the product. And how do you kind of value that? So more than anything, we spent quite a bit of time deciding what is really the vision? Where do we want to take this product?

Technical depth is very important to don't lose track of, obviously. But it's also what is the next feature you want to add to the product, right? Because Because eventually you want to gain more adoption to the product. And how do you kind of value that? So more than anything, we spent quite a bit of time deciding what is really the vision? Where do we want to take this product?

Technical depth is very important to don't lose track of, obviously. But it's also what is the next feature you want to add to the product, right? Because Because eventually you want to gain more adoption to the product. And how do you kind of value that? So more than anything, we spent quite a bit of time deciding what is really the vision? Where do we want to take this product?

And why does this product exist, right? You need to understand what they're trying to solve, right? So more than anything, starting to really get the proper vision. So what we are focusing on, we are focusing on Making sure that developers have as much time as possible to do kind of what they love the most, solving difficult problems.

And why does this product exist, right? You need to understand what they're trying to solve, right? So more than anything, starting to really get the proper vision. So what we are focusing on, we are focusing on Making sure that developers have as much time as possible to do kind of what they love the most, solving difficult problems.

And why does this product exist, right? You need to understand what they're trying to solve, right? So more than anything, starting to really get the proper vision. So what we are focusing on, we are focusing on Making sure that developers have as much time as possible to do kind of what they love the most, solving difficult problems.

And secondly, we also started to evolve into saying, okay, when you create a software product, that is a team effort. So it's not like one single individual that is creating the great products. Great products is built by teams. At some point, I would imagine that you want to start monetizing on a product, right? So you need to have some thought around where and how do I monetize?

And secondly, we also started to evolve into saying, okay, when you create a software product, that is a team effort. So it's not like one single individual that is creating the great products. Great products is built by teams. At some point, I would imagine that you want to start monetizing on a product, right? So you need to have some thought around where and how do I monetize?

And secondly, we also started to evolve into saying, okay, when you create a software product, that is a team effort. So it's not like one single individual that is creating the great products. Great products is built by teams. At some point, I would imagine that you want to start monetizing on a product, right? So you need to have some thought around where and how do I monetize?

There is an open source version of the product, but it's also an enterprise version of the product. So how do we balance those two? We defined, then again, who is the user or the persona, the decision maker or the

There is an open source version of the product, but it's also an enterprise version of the product. So how do we balance those two? We defined, then again, who is the user or the persona, the decision maker or the

There is an open source version of the product, but it's also an enterprise version of the product. So how do we balance those two? We defined, then again, who is the user or the persona, the decision maker or the

key persona that is interacting with the open source versus the enterprise, and what is really the needs of this person for us to make this very, very attractive product for that persona. So when we have a feature request from a customer, does that feature request move the product towards the vision of where we want it to be? Does it really allow the developer to be more efficient?

key persona that is interacting with the open source versus the enterprise, and what is really the needs of this person for us to make this very, very attractive product for that persona. So when we have a feature request from a customer, does that feature request move the product towards the vision of where we want it to be? Does it really allow the developer to be more efficient?

key persona that is interacting with the open source versus the enterprise, and what is really the needs of this person for us to make this very, very attractive product for that persona. So when we have a feature request from a customer, does that feature request move the product towards the vision of where we want it to be? Does it really allow the developer to be more efficient?

Does it allow the developer to work more efficiently together with others? And secondly, also, it's about the commercial thinking. So does this really fit into the open source part or does it fit more into kind of the enterprise part? Is this something we should bundle this as a value add? So that's more the commercial conversation of everything.

Does it allow the developer to work more efficiently together with others? And secondly, also, it's about the commercial thinking. So does this really fit into the open source part or does it fit more into kind of the enterprise part? Is this something we should bundle this as a value add? So that's more the commercial conversation of everything.