The following video transcript is generated automatically by a computer algorithm that learns and gets better on a daily basis. Please accept our apologies if some content below doesn’t make sense:

Next up is a tweet, which is which is somewhat related to that kind of topic. And this tweet is talking about from a guy called Suhail and he’s talking about the difference. But to all having the experience as an engineer to know when to sort of release a product into the wild or to release some of a feature or something that I’ve been working on. And he writes, A big part of being a great engineer is the difference between, OK. It works and I’ve done and it works. I fix the most common edge cases. I’m aware of more user experience issues. But let’s put them in the backlog for now. Let’s shift. I know there’s more work to make this great. Now, that seems sort of quite specific to sort of programming and engineering and product management. But I think it’s more generally applicable than that. I think it’s more applicable to sort of business in general, particularly early stage growth stage businesses. And what are you saying there is this over time you kind of learn this lesson of you. The only time that you actually learn anything about what it is that you’re doing as a business or in terms of the product you’re trying to put into the market is by exposing it to the market. And the right time to expose it to the market is not when you spend a lot of time smoothing off the rough edges and perfecting all the various moving parts and making sure it’s perfect from the idealised utopian plan that you’ve planned, either in your head or on paper or wherever it is, the best time to get feedback is as early as possible, but not too soon, which sounds like a really sort of fluffy. Well, how on earth do you know when it’s not too soon? Not too late. It’s just writes the Goldilocks problem. Right. But you get a feel for that over time. And various people over the years are sort of weighed in when that when that sort of time is best. I can’t remember exactly who said it, but it was probably Marc-Andre Eastern, the Venerates and Horowitz, you know, you want to I was pretty programme, actually. Y Combinator said, you know, the best time to release something is when you feel slightly embarrassed about it. Because then you then, you know, for a fact that you haven’t put in too much work. But you also know that it’s not completely non-functioning horrendous. And the only response you’re going to get from the market is is like, well, that’s just a steaming pile of whatever. That’s not going to work. And. I think so. I think what’s a house down here is actually so hit on a very specific part of that calculus that you should sort of pay attention to when you’re doing that. So. And the thing that he sort of pulled out there, which is important, is, is that. There’s an 80 20 to all of this, right? You know, there’s always an 80 20 parade. I was a genius. There’s always an 80 20, an 80 20 is is what’s the most common use case or the your customers are your market. What’s the most common way that they’re going to be interacting with this thing or using this thing or experiencing this thing? Spend a little time making sure the most common case is case of full. But in those cases, which are the outliers or, you know, the one in 10 or two in 10, I get to experience don’t worry about those so much because, of course, like you will probably get some feedback from your customers saying, well, this edge case over here doesn’t work. And it’s like, no fine cheque. I know that doesn’t work. What I’m most concerned about is what is that the cool thing that I’m trying to test or I’m trying to find out about? Does that work? Because you can always, always go back and flesh out something, flesh out the remaining 20 percent. You can always get someone to do that or do it yourself. But you don’t really know this yet. You want to learn stuff in the sort of core, core area of the product or service. And because that’s the thing that’s gonna be make or break. Right. You know, like that you’re going to have a certain sort of profit margins or certain gross margins and they are going to be influenced by the core of the thing, not so much by the edge case of the thing. So in your sort of previous businesses and the businesses that you run it, you sort of come across any of these kind of cases where you like you released too early or too late or when they passed was just right. Yeah.

So I think it’s one of their most, most difficult questions for entrepreneurs. And I agree with you that it applies not only to engineers, but actually to any company building approach, because eventually it does. You can hire engineers, but you still need to make us. He shows us entrepreneur when is good enough to go to market. How much should you spend on drug development? So I think also it depends on the industry. So financial services, you cannot release an unfinished product or broked with bugs because I could be regulated, you know, and you are managing other third parties money. So I would say, yeah, on financial services, it’s a tough industry for innovation because he’s arguably the most regulated one, but also. Yeah.

You carve out like a high bar on standards and you need to meet lots of stuff on security, soil and records and this and that. But I mean, there there are other industries as well that you cannot launch an unfinished product for sure, like rockets. But any form of transportation? I would say so. Any form of that transport industry in general. Like a car. Like anything. Like a bike. Because any mom is functioning, you know, on any of those products could hurt someone. You could get sued or whatever. So also, I mean, of course, far industry or the doesn’t need to even farm. It could be an even in the in the food industry. You know, you need suka certain quality, so you cannot just take it out. But when it comes to tech products, usually you can I treat probably not with high end gadget like phone or computer, but especially with software. You can deafen, you shoot actually released a simplified version. And if you don’t know when it’s good enough, just as you were pointing out before, and I think it’s important to understand that it needs to be simple in order to escape. So you need you do need to concentrate on your core single feature or single features, single most important features. Ideally, if it’s one is better. So you just need to make sure that it is good enough for that feature. And then other features are probably not well attended, but that’s fine. And then see or validate if that scales.

And if it does, then you can go on and know build all the ecosystems surrounding that core feature. Because, you know, that’s gonna take you. That’s going to be at the heart of your business. So, yeah, you better make sure that works on you. You should try to out with the less possible budget on that script as possible because you know, you have competitors. Yeah. So. Yassa will always come back to a lean Start-Up. I think that’s an unquestionable. Yeah. Business method or method methodology or approach that it’s mandatory for. Unless your industry is not, you know, fit for that, but otherwise, you should find a market fit with a lean Start-Up approach. Yeah.

Share This