Hannes Lenke

Tim was very vocal on Twitter about what he did and that attracted the first users really. And then we started beginning of 2020 to iterate very quickly on the user feedback that we got. and adding more features, adding a framework that is called Playwright for test automation, which is now our prime framework that we're using to enable our users really to create tests.

Tim was very vocal on Twitter about what he did and that attracted the first users really. And then we started beginning of 2020 to iterate very quickly on the user feedback that we got. and adding more features, adding a framework that is called Playwright for test automation, which is now our prime framework that we're using to enable our users really to create tests.

Building an MVP never stops, right? So you're building new features, etc. And what we try to achieve is always speed. Release features to customers fast and get their feedback really fast, right? So we always try to identify who's a potential early adopter of these features. What is the actual core problem that they want to solve? And can we make trade-offs there?

Building an MVP never stops, right? So you're building new features, etc. And what we try to achieve is always speed. Release features to customers fast and get their feedback really fast, right? So we always try to identify who's a potential early adopter of these features. What is the actual core problem that they want to solve? And can we make trade-offs there?

Building an MVP never stops, right? So you're building new features, etc. And what we try to achieve is always speed. Release features to customers fast and get their feedback really fast, right? So we always try to identify who's a potential early adopter of these features. What is the actual core problem that they want to solve? And can we make trade-offs there?

Are there a set of users that want to solve one problem with a subset of the whole feature set that we could potentially build? And once we understand that, we're going to release a minimal version of this feature set to users in an RFR with a feature flag. Then we're interviewing these users, trying to understand, okay, is that a potential fit for what they really need? Or is it maybe not?

Are there a set of users that want to solve one problem with a subset of the whole feature set that we could potentially build? And once we understand that, we're going to release a minimal version of this feature set to users in an RFR with a feature flag. Then we're interviewing these users, trying to understand, okay, is that a potential fit for what they really need? Or is it maybe not?

Are there a set of users that want to solve one problem with a subset of the whole feature set that we could potentially build? And once we understand that, we're going to release a minimal version of this feature set to users in an RFR with a feature flag. Then we're interviewing these users, trying to understand, okay, is that a potential fit for what they really need? Or is it maybe not?

Do we need to go back to the drawing board? And this iteration can happen, actually, and should happen in four weeks, sometimes eight weeks. So that we really fast try to understand, okay, is that what we're building here solving actual customer problems or maybe not.

Do we need to go back to the drawing board? And this iteration can happen, actually, and should happen in four weeks, sometimes eight weeks. So that we really fast try to understand, okay, is that what we're building here solving actual customer problems or maybe not.

Do we need to go back to the drawing board? And this iteration can happen, actually, and should happen in four weeks, sometimes eight weeks. So that we really fast try to understand, okay, is that what we're building here solving actual customer problems or maybe not.

Building out your roadmap is really hard because you constantly have to make trade-offs. Essentially, there are four lists or voices that are influencing the roadmap. First of all, what are customers asking for? We have a public roadmap for this where you can upvote and hand in special feature requests.

Building out your roadmap is really hard because you constantly have to make trade-offs. Essentially, there are four lists or voices that are influencing the roadmap. First of all, what are customers asking for? We have a public roadmap for this where you can upvote and hand in special feature requests.

Building out your roadmap is really hard because you constantly have to make trade-offs. Essentially, there are four lists or voices that are influencing the roadmap. First of all, what are customers asking for? We have a public roadmap for this where you can upvote and hand in special feature requests.

So we're constantly asking our customers to look at their public roadmap and if they require a certain feature, please submit it there. The second piece here is since we grew a lot and have quite some customers and have responsible salespeople for it, so what are our salespeople asking for? What are they hearing from customers, listening to customers?

So we're constantly asking our customers to look at their public roadmap and if they require a certain feature, please submit it there. The second piece here is since we grew a lot and have quite some customers and have responsible salespeople for it, so what are our salespeople asking for? What are they hearing from customers, listening to customers?

So we're constantly asking our customers to look at their public roadmap and if they require a certain feature, please submit it there. The second piece here is since we grew a lot and have quite some customers and have responsible salespeople for it, so what are our salespeople asking for? What are they hearing from customers, listening to customers?

I also try to be part of the customer conversations like daily to really understand, okay, what are my existing customers that are maybe using us on a larger volume really asking for, right? So that's the second piece of influence on our roadmap. There's another piece, which is what are our engineers asking for? Is there technical depth that we need to address?

I also try to be part of the customer conversations like daily to really understand, okay, what are my existing customers that are maybe using us on a larger volume really asking for, right? So that's the second piece of influence on our roadmap. There's another piece, which is what are our engineers asking for? Is there technical depth that we need to address?

I also try to be part of the customer conversations like daily to really understand, okay, what are my existing customers that are maybe using us on a larger volume really asking for, right? So that's the second piece of influence on our roadmap. There's another piece, which is what are our engineers asking for? Is there technical depth that we need to address?