<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ivan Galic on Medium]]></title>
        <description><![CDATA[Stories by Ivan Galic on Medium]]></description>
        <link>https://medium.com/@ivangalibug?source=rss-122c383efe9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HlPQHZD1ugwCELEi.jpg</url>
            <title>Stories by Ivan Galic on Medium</title>
            <link>https://medium.com/@ivangalibug?source=rss-122c383efe9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:57:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivangalibug/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to build a technical product, for non-technical founders. Part III: Getting to the MVP]]></title>
            <link>https://medium.com/@ivangalibug/how-to-build-a-technical-product-for-non-technical-founders-part-iii-getting-to-the-mvp-27719462d24a?source=rss-122c383efe9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/27719462d24a</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[non-technical]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Ivan Galic]]></dc:creator>
            <pubDate>Wed, 15 Mar 2017 11:44:36 GMT</pubDate>
            <atom:updated>2017-03-15T11:45:06.929Z</atom:updated>
            <content:encoded><![CDATA[<h3>Choose the easiest path</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUcPaODdBsnCEX1DE9kGlg.jpeg" /><figcaption>Don’t make your life unnecessarily difficult</figcaption></figure><p>After all the thinking and research, it’s finally time to get something built. As an engineer, I feel impatience just writing this. And that impatience often drove me directly into building a product, ignoring all the lessons I’ve talked about so far. Be better than me.</p><p>Roughly, there are three approaches you can take to getting an MVP out and validating it. Here they are in the order of preference as I suggest it.</p><h4>1. Mock the product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQGfduM4f0x00cUQNbWPDg.jpeg" /><figcaption>Mock the product if possible</figcaption></figure><p>What I mean here is getting to the point where you give your customers (now real instead of potential ones) a taste of the working product, without actually building it. While the “product” offered in this way won’t be as polished or as full-featured as you’d like it to be, it can be enough for a proof of concept. This is not applicable to all ideas, but it’s a viable approach more often than it seems.</p><p><a href="https://en.wikipedia.org/wiki/Aardvark_(search_engine)">Aardvark</a> was a social search engine that would let you ask a question, and then try to find an appropriate person in your social circle to answer that question.</p><p>From a technical perspective, this immediately evokes ideas of AI and machine learning, putting heavy algorithms to use to figure out who would be the best person to answer any given question.</p><p>That does make sense at scale, but is not necessary for an MVP as Aardvark’s founders showed. Initially, when a question was asked, one of them would immediately go off manually searching your social graph for a good match. This meant you could be waiting for a match for a long time which wasn’t ideal, but it was enough to show if people were interested. If you were willing to wait for a couple of hours for a match, you could only be happier with the service if the match was instant.</p><p>Another great example is Dan Norris and his company <a href="http://wpcurve.com/">WP Curve</a>. His idea was to provide flat-rate, unlimited fixes for Wordpress sites. This means you can purchase a subscription, and any time you have a problem with your WP site, you can turn to them for help and they’ll fix it for you, in the same day. If you look at their site right now, you’ll see that they offer this service 24/7/365 and have a team spread out all over the world.</p><p>Yet when they were starting, it was just Dan — even though the 24/7/365 promise was there even back then. Instead of blindly going out and hiring a bunch of people and setting up all the business operations first, Dan started offering the service immediately, with him as the only support person. This meant, in his own words, he slept with his phone on his pillow and would wake up in the middle of the night to fix a problem if a customer contacted him. Difficult for sure, but better than wasting a bunch of time and money to set everything up only to learn nobody wants it.</p><p>I hope it’s obvious what the benefits of this approach are, and if you can find a way to make it work it can be the easiest, cheapest and safest way to test the waters for your idea. Sometimes you will need some development help here if you are completely non-technical, but having to get a little bit of help is a lot better than having to get someone to build a full product.</p><h4>2. Off-the-shelf technology</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FKYH6gGeqYi-kMqvPAQFXQ.jpeg" /><figcaption>Off-the-shelf is better than build-your-own</figcaption></figure><p>If you can’t get away without a more significant amount of technology, perhaps you can use some off-the-shelf products. Often you can patch together a number of different apps and solutions to get a rudimentary version of your product going, without having to invest in actual development.</p><p>I met a guy who started a wine box subscription business with a combination of Shopify and excel spreadsheets. As a customer, you would fill in a questionnaire about things you like and dislike in a wine. Separately, he would source wine deals from wineries. Based on his inventory for the month and the database of users’ preferences, he would decide what to put in each box before packing them and sending them off.</p><p>This is another example where software could really help a lot. A custom website and interface for getting users’ feedback, an automatic matching engine and a lot more. But he built it all on Shopify, added 3rd-party forms which recorded data into an excel spreadsheet, and then he did all the matching manually.</p><p>Again, very tedious, but it worked. He is non-technical and he launched and grew his business without having to partner up or hire a developer. Later when he needed one, he had much more negotiating power and had people lining up to work with him.</p><h4>3. Build the technology</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qa-HO2uNKsBNa-hhS2u-Mg.jpeg" /><figcaption>Only build your own as the last resort</figcaption></figure><p>Since you are non-technical yourself, leave this as the absolute last resort. I believe you can learn practically anything if you want to, and that includes managing building a technical product (or coding for that matter). But doing that while building a business, possibly for the first time, and learning a zillion other things? You’d have way too much on your plate at once. It’s not impossible and it’s been done, but beware that in a lot of such stories many details have been left out or glossed over. For example, that the founder had a technical co-founder they’d known and mucked around with building stuff for years.</p><p>Depending on your idea, you may really need to build your technology. And maybe, the idea is so good it’s worth pursuing even though you’re not really the best person to be executing on it. If that’s the case, I’ll discuss building your MVP in the next article. But make that the last option; it should never be the first thing to try.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27719462d24a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build a tech product, for non-technical founders, Part II: the MVP]]></title>
            <link>https://medium.com/@ivangalibug/how-to-build-a-tech-product-for-non-technical-founders-part-ii-the-mvp-367de78b19f8?source=rss-122c383efe9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/367de78b19f8</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ivan Galic]]></dc:creator>
            <pubDate>Wed, 28 Sep 2016 21:51:01 GMT</pubDate>
            <atom:updated>2016-09-29T09:04:37.859Z</atom:updated>
            <content:encoded><![CDATA[<p>This is part 2 of the series. For <a href="https://medium.com/@ivangalibug/how-to-build-a-tech-product-for-non-technical-founders-part-i-the-idea-59cf577f9d2a#.46e83tej0">Part I, click here</a>. From here on, I assume you have decided your idea is worth your time and it’s the best one you have.</p><p>If you’ve been reading anything related to tech startups at all (and since you’re reading this, it’s fair to assume you have), you’ve read about the importance of building and shipping your MVP, then getting feedback from your customers as early as possible and steering your decisions accordingly.</p><p>However, I think there is a lot of confusion about the term, so let’s try to define it first.</p><p><em>MVP</em> stands for <em>Minimum Viable Product</em>. In my experience, the main challenge is to find the balance between <em>minimum</em> and <em>viable</em>, and people usually focus too much on either of these. Here is a definition I find useful.</p><p><em>Minimum</em> means minimum you can get away with. Since the goal is to launch your product and get feedback from real customers as quickly as possible, anything you build into your product is taking you away from this goal, because it takes time.</p><p>Trim away until there’s nothing you can reasonably trim, in order to spend as little money, time and other resources as possible to launch your product. The goal is simply to launch.</p><p>But this will lead you to releasing a crappy, unusable product if you don’t balance it with <em>viable</em>. Viable means it still needs to solve the problem you are trying to solve, it still has to be unique compared to competing products, it still has to be <em>valuable</em> to your customers. Where this balance line lies is something you need to figure out. Deciding what is not that important and what is essential is a really challenging task, especially for the founder who came up with the idea and vision in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yvw13zck4JCINSd5Wor3fg.jpeg" /><figcaption>MVP — bare-bones, but no less than that.</figcaption></figure><p>Naturally, you’ll tend to think everything is important and your product won’t work without feature <em>X</em> or <em>Y</em>. The truth is, if the whole premise of the idea is really something valuable, there aren’t that many <em>X</em>s and <em>Y</em>s that will make your product not work. If you are looking at competing products and their level of polish, and realise you have to have a large set of features and a very high degree of polish to be able to compete with them, then your product is not different enough. It may still be possible to compete, but that exercise is better left to large organisations with large stacks of cash, not someone trying to scrape bits and pieces to put everything together.</p><p>I’ve been in projects where we thought we just had to have every little feature any customer ever mentioned or our competitors had, without realising how futile that was, and how the main problem was that the core of the product was broken.</p><p>On the other hand, you may have the whole <em>lean startup</em> idea drilled into your mind so much you believe nothing is essential. I’ve seen that too, and it can be just as bad. It’s easy to end up with a product that simply doesn’t stand out in any way. I’ve done that myself and it doesn’t work.</p><p>Define what it is that makes your product unique and indispensable — that’s the <em>“how are you going to compete”</em> from the previous article. That’s what you need to ship with. And if that’s too many things, re-think your idea. Your first version of the product doesn’t have to solve every possible problem, it doesn’t have to be perfect. But it has to be enough to be useful.</p><h4>Why MVP?</h4><p>Why even take this route? Why ship with a small set of features and a less-than perfect product instead of building something amazing, and mesmerise the world? Because that’s not how it works. It goes back to discussion of visionary founders, and that quote by Steve Blank saying that no matter how fantastic your idea is, your customers will want something changed.</p><p>I’ve never been a part of a project that was envisioned in some perfect form, built and everybody thought it was great. Either it was built exactly the way it was originally envisioned and it sucked, or it changed along the way, often drastically.</p><p>While that doesn’t necessarily mean your original vision won’t work at all, why spend so much time building something only to discard large parts of it when you realise you were wrong? The whole idea behind lean startup and MVP is to minimise investment and prove something works before building it.</p><p>After you have that initial thing working, you can add, remove and make it better. Here is a short story.</p><p>An experiment was run with two groups of people learning pottery. The first group got the assignment to create one pot in 30 days, and make it the absolute best they can. Make it their masterpiece, or closest to one they could get within those 30 days.</p><p>The second group was given the task to create as many pots as possible within 30 days. No rules, nobody would judge how they looked or their quality, just the number.</p><p>The end result? The second group produced far better pots than the first. While people in the first group planned and thought long and hard about how to make an amazing pot, the others were just building. The first ones were really bad, but as they kept at it, the pots just got better and better and eventually surpassed the ones from the first group.</p><p>In practice (no pun intended), this translates into doing quick iterations. Push out something small, see what works and what doesn’t, what needs to be added (most urgently) and go off of that; then repeat.</p><h4>Talking to people</h4><p>This is also where talking to your customers comes in. <em>What customers</em>, if you haven’t even started building your product yet? Potential ones. Before you start building your product, and even before you plan what the product will be like, define who your customers will be. Like everything else, this may change as you go but you should have a clear idea of at least who you think your customers are.</p><p>Once you define who they are, try to figure out where you can reach them. General answers like “AppStore” or “Internet” or even “Facebook” are not good enough, because you don’t have the power to reach them there. Releasing your app into the AppStore or creating your page on Facebook is like splashing a mug of water into the ocean. Some passers-by might see it, but nobody will care.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sscGo6b8Feto5Vcu3eVOJg.jpeg" /><figcaption>You need to find your audience</figcaption></figure><p>Instead, you need to find a place where your customers gather in high concentrations, even if their number is small. You don’t need to sell your product to every possible customer, but you need to find a small group you can reach relatively easily and you can communicate with directly. You will also find it much easier if you spend some time getting to know this group of people and interact with them before asking for feedback on your product, but that’s a story for another time.</p><h4>Stick to your vision or listen to customers?</h4><p>Once you start talking to your potential customers, you will often find their opinions are different from yours. Sometimes they will tell you things you thought were the crown jewels of your product don’t matter that much, and sometimes they’ll care a lot about things you weren’t even sure you should include. Or they will simply want things done in a different way than you imagined. How do you know if you should listen to them or stick to your own idea?</p><p>There’s no single rule. You could easily be wrong — you are just one, possibly unique person — but you can’t blindly follow your customers either. My best advice is to talk to them and try to get to the bottom of what they are saying. What is it really that’s bothering them? What is it really they are objecting to? What is it really they need, that would solve their problem? You can often find more than one way to solve a particular problem, and sometimes the most obvious one (which your customers will most likely suggest) might not be the best.</p><p>I’ve often seen it first hand how doing exactly what a customer said turned out to be dead wrong. And also, how ignoring what they are saying turned out to be just plain stupid. It requires balance, like most things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LzylCRdJy4ZVvIGxE5FeGA.jpeg" /><figcaption>Balance… something like this.</figcaption></figure><p>Pay special attention to issues brought up by many different people. For every person that tells you something, be aware that there is a larger number that thinks the same but isn’t saying anything.</p><p>Then finally, listen to your gut — not as god’s word, but more like weather forecast. And if whatever you’re doing is not working, change and try again.</p><h4>It’s not good enough unless you can sell it</h4><p>When talking to customers and especially while your product is in early stages, you will often hear things like:</p><blockquote>“I’d use your product if it could only do X”<br>“I’ll buy it if you just add feature Y”<br>“It’s an amazing idea, but we can only use it once it’s more polished”</blockquote><p>All of these are very rarely the real truth, even if the person you’re talking to thinks they are. In reality, they are just excuses and they mean they don’t really <em>need</em> your product. Ultimately, your product will only succeed if you can sell it. And ideally, you can sell it before you even start building it. When you can’t, it usually means you need to refine the proposition — or completely change it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RL0_qd_XiQVajEdiYaY1Lg.jpeg" /><figcaption>Cash first, making the product second</figcaption></figure><p>Don’t think it can work? Take a look at Kickstarter, and the number of projects that got crazy amounts of funding based on a video showing the concept of the product. That’s what proves people really want it. When I’m willing to pull out my credit card and give you money for something you can only draw a sketch of, you’ve got a hit on your hands.</p><p>More broadly, you can see this in a lot of places. Companies will often order something and pay for it (at least in part) before it’s done. The key here is trust, and that can be tricky when you are starting out. If I asked you to give me $100m to build you a spaceship, and all I had to show were some ideas and sketches, you wouldn’t trust me enough to pay. Still, there are more cases when it can work than it appears at first, and investing some time to find them can be well worth it.</p><h4>Should you follow this approach?</h4><p>As I mentioned earlier, large parts of this are described by the <em>lean startup</em> methodology, based on a book by Eric Ries. It’s really caught on in the tech industry and has been trending for a number of years now, and if you haven’t read it you should. But is it the right choice?</p><p>Even though I’m obviously advocating it here, the question of whether it’s a good approach is in my opinion not asked enough. Like anything, it’s a framework. It fits some cases, and doesn’t fit others. That’s ok, as long as you think through whether it fits <em>your</em> case or not, and why so. Because if it does, there’s a lot of pain you can avoid following it. But the idea is not to blindly follow a set of rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p4atOfpL-McDpoO35R2Xdg.jpeg" /><figcaption>Don’t take anybody’s word as gospel</figcaption></figure><p>I think it’s a great framework, especially for first-time founders. The reason being simply that it gives a set of rules, and tries to eliminate unnecessary risk and avoid working on things that aren’t likely to succeed. That improves your odds of success and makes is less likely you’ll get lost along the way where you could have easily avoided it.</p><p>Yet when we look for role models and examples, we all look to the most successful ones. We all look up to companies like Google, Facebook, Apple, Microsoft… In many cases, it’s really hard to find evidence that they followed anything resembling the lean startup or customer development methodologies. We don’t really know. More importantly however, often the main premise seems wrong. What “painful problem” was/is Facebook trying to solve? How about Instagram? Sure, you can always stretch any idea to fit your theory, but in my mind that’s not what it is.</p><p>I’m happy with accepting such cases simply don’t fit the framework. Instead of trying to wrap Instagram’s journey around a methodology, I prefer to think of it as simply a case where it doesn’t work. I don’t know if there is another/better methodology for these one-in-a-million successes, but there probably isn’t just by definition.</p><p>Either way, it’s a harder path to take. Such ideas are not recognised by almost anyone until they (seemingly suddenly) take off. Chances of success are much lower, and although I didn’t think that way when I was dreaming up my own first project, I think they are better left for the next time, with more knowledge and hopefully some success under your belt.</p><p>In the next part, we’ll talk about how to approach building the MVP. Until then!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=367de78b19f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build a tech product for non-tech founders]]></title>
            <link>https://medium.com/@ivangalibug/how-to-build-a-tech-product-for-non-technical-founders-part-i-the-idea-59cf577f9d2a?source=rss-122c383efe9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/59cf577f9d2a</guid>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Ivan Galic]]></dc:creator>
            <pubDate>Tue, 26 Jul 2016 10:55:50 GMT</pubDate>
            <atom:updated>2016-07-26T10:55:50.882Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to build a tech product, for non-technical founders, Part I: The idea</h3><p>You are non-technical, and have a great idea for a tech product — but now what? How do you know if your idea is worth building? Even worse, what if you haven’t asked this question at all? Also, how do you get it built when you can’t code?</p><p>There are heaps of materials out there on startups and everything related, and I’m not a successful founder with a $100mm exit. What I have done is seen the process from the inside, as an engineer, many times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sxQEQLntjOn86tf0EPzWdA.jpeg" /><figcaption>…how the sausage is made</figcaption></figure><p>Over the past 8 years, I’ve worked with startups, big companies and on my own projects; built MVPs and worked on established products; as an employee, founder, consultant and employer (sort of — hiring other contractors). So what follows are some of my learnings and observations, and what I’ve tried to make an objective perspective on the whole process.</p><p>I’ve tried to avoid pretence and unnecessary buzzwords, but feel free to call me out where you feel I haven’t. With arguments, please.</p><p>This is my view of what works and what doesn’t, I hope it helps.</p><h4>Idea as the seed</h4><p>Every product, successful or not, is based on an idea. Idea for how to solve a problem; how to make our lives better, more interesting, more fun. I’ll assume here you’ve got that far and have an idea you want to work on. But an idea is just the beginning, and useless if that’s the all it remains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfI6Mk4wAJGtlMF2mnJH1g.jpeg" /><figcaption>It all starts with an idea — but it often also ends there.</figcaption></figure><p>So with idea in hand then, what’s the next step?</p><p>This article is for non-technical people with an idea for a tech product — meaning a web or mobile app in this case. The issue, obviously, is you can’t build it yourself. In the spirit of entrepreneurship, that may seem like a non-issue. Can’t you just have someone else build the product, and you do the rest? Isn’t that what entrepreneurs do all the time?</p><p>Yes, if you have a deep understanding of what you are building (and a bunch of cash laying around). But let’s look at it from a different angle. You wouldn’t go into developing a new drug with no experience in pharmaceuticals, for example. You wouldn’t go about building a better desktop CPU if you don’t know anything about electronics. And while apps are easier and more approachable than those two categories, the principle is the same.</p><p>That’s why my first suggestion is to carefully evaluate your idea and how well it fits you. We all know building companies is hard. Why make it harder by going into something you don’t understand? With everything else you’ll be struggling with, the last thing you need is not being able to get the product built at all. Tech is not the only area you can build a successful company or product in. Is there another idea that plays better to your own strengths and experiences?</p><p>I strongly believe an idea, founder(s) and a point in time all need to match in order to achieve success. A non-technical founder starting a tech-based company is a possible indication of a mismatch between the first two.</p><p>If we look at those three factors — idea, founder and point in time — idea is the only one you can change meaningfully and quickly. The other two can also change (and time obviously does), but much more slowly. Ideas you can change as much as you like — especially before you invest a lot into building them. So, even if your first one isn’t a great match for you and the current point in time, another one might be.</p><p>That’s why I think a process for finding an idea is much more important than the idea itself. One possible way consists of picking an idea and running it through a series of tests — first mentally, then in the real world — to figure out if it has a chance of succeeding at this point in time, and with you as a founder.</p><p>The mental part goes first because it’s easier and requires less work, but it’s very important and lays the foundation for further analysis. In my mind, there are a few important things to consider:</p><h4>Do you actually care about the idea or problem you are trying to solve?</h4><p>If you don’t, the idea is probably not a good match for you, even if it’s a great idea otherwise. I’ve made this mistake several times and it always ended badly.</p><p>The issue is, it will take time to build your product or company into something successful. Worse, you’ll be running into difficulties all the time — with any idea. This is hard enough to work through when you really care about something, and nearly impossible when you don’t.</p><p>Don’t be seduced by thinking something is easy. Unless it can really be done (and I mean <em>finished</em>) in a few days, it’s not easy.</p><p>It’s likely you are underestimating the difficulty anyway, and if you are only going for it because you think it will bring you easy success, you are in for a disappointment. Maybe worse, if you involve other people along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*is9PRYQWUCxRiRFl5RP36g.jpeg" /><figcaption>If there is such a thing as easy money, it’s not in building businesses.</figcaption></figure><p>You might get lucky, but if you are counting on that better play lotto (or Keno, <em>wink wink</em>).</p><h4>Do you have the required skills?</h4><p>Here I don’t mean strictly being able to build it yourself. But as I wrote above, you need to know enough to be able to manage the project.</p><p>Many things can be learned, and you can’t be afraid of learning if you want to build a company. However, your time is limited, and even with best effort you can’t learn everything at once.</p><p>So, while you can build an app even if you are not a coder, it will be much harder if you also don’t know anything about development in general, and haven’t been through the process before. Double so if you also don’t know anything about the industry you’re getting into (i.e. the one whose problem you are trying to solve).</p><p>Try to achieve a balance here and be realistic about how much new stuff you can take on. As an entrepreneur you have to do something new and explore, and it’s great to challenge yourself, but there’s no point in getting in the middle of something you just can’t manage.</p><h4>Can the idea succeed?</h4><p>In your opinion, at least. What’s the ideal outcome? Is it achievable? If you are trying to solve a problem, do you think it really is a problem someone needs solved and is willing to pay for? Is the technical realisation of the idea going to be good enough for people to use the product?</p><p>All these questions are best answered by talking to potential customers as I’ll discuss below, but thinking through them before hand can give you a feeling of whether the idea is something worth pursuing or not.</p><h4>How are you going to compete?</h4><p>It’s a bad idea to constantly focus on competition. When you do, you just end up chasing them — it almost goes by definition. You are constantly watching what others are doing, and thinking about how you can do it better and outcompete them.</p><p>But we are talking about innovation industry here. Anything you see them doing, you’re already late for. By the time they release feature X, you’re behind. If you try to chase them, by the time you finish feature X they will have already released feature Y, and so on.</p><p>Additionally, it’s a recipe for burning out yourself and your team, because you will constantly be running with the finish line moving further every time before you reach it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21LegpRD_AYUEHa3A2n6rQ.jpeg" /><figcaption>Try to avoid chasing competition if you can.</figcaption></figure><p>This is something big companies can (and sometimes do) succeed in, especially when competing with smaller companies. When you have more resources than your competitors you can sometimes replicate what they are doing in a better, bigger way. If along the way you can also do some innovation, you can leapfrog whatever you competitors did before you and get ahead.</p><p>The key there is having more resources though, and if you are just starting out that’s one thing you don’t have. Instead, you have to work in parallel to your competitors — not after them — and try to come up with solutions that solve your customers’ needs better than anybody else. It takes practice, but here is what I’ve seen work.</p><p>If you can find a segment of the market, a specific type of customer you can focus on, then you can serve their needs better. This is especially effective if you are working against bigger, established companies. Because of their size, they have to try to capture a large segment of the market and try to cater to all of the customers in it.</p><p>You don’t have that problem. You can start small, be perfect for a small number of customers and not that good for the others. It’s ok, and will give you an advantage. If you do it right, your customers will feel like you are talking to them personally.</p><p>Try to think of ways to solve your customers’ problems not by improving current solutions, but by doing it differently. That sets you on a different path from your competitors and one they are unlikely to follow.</p><p>Of course, it’s also dangerous because you could be going in a completely wrong direction. But I think it’s the only way to break the pattern of just following what others are doing and instead make your own path. Besides, if you are just starting out you don’t have that much to lose (unlike existing companies, which is the reason they might not try to do the same thing you are doing until it’s too late).</p><p>All this is much easier said than done. As is giving advice compared to following it (<em>ahem)</em>. But how exactly do you go about doing things <em>differently</em>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKCejbTcRlCx698iXFOlIQ.jpeg" /><figcaption>Think outside of the box… much easier said than done.</figcaption></figure><p>Honestly, it’s really, really hard, at least for me. The best advice I’ve received is to forget about how things are currently done (<em>hard</em>), focus on the problem and customer and imagine (<em>also hard</em>).</p><p>Imagine what would be the ideal way to solve that problem for that customer. Forget about limitations for a moment and try to think of an ideal world. Once you are happy with the image, try to work backwards towards what you actually can do, but stay as close as possible to the idea. This is an exercise in creativity, and doesn’t come equally easily to everyone. There’s no scientific process that I know of (I wish did), so I’ll just leave it at that.</p><p>Going back to my original point though, you shouldn’t be overly focused on what your competitors are doing, but you <em>do</em> need to know how you are different (and better).</p><p>You are going to be compared to your competitors, and you better have an answer to why your potential customers should choose you. If you can’t answer that question, I bet they can’t either, and then you’re just doing all the work in vain because nobody will care.</p><p>When you have other people working with you, they will also be expecting an answer to that question from you. Nobody likes doing copycat work.</p><h4>Unique ideas</h4><p>What if you have an idea that doesn’t have competition? What if it’s so new and unique that nobody has ever done it?</p><p>Three options.</p><p>One, you have a massive opportunity and a billion-dollar idea — either because nobody ever thought of the idea before or because before wasn’t the right time and now is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkINNMyVpgwrSHJW0n8s3Q.jpeg" /><figcaption>Are you sure you’re the first one to think of the idea?</figcaption></figure><p>Two, you have a horrible idea nobody ever did because it’s horrible and stupid (or somebody did and failed).</p><p>And three, you only <em>think</em> your idea is original but actually there are others doing it already (which could mean you’re already late, or it could mean that the idea is not good enough to be big).</p><p>Needless to say, options two and three are more likely. You could say it’s a cynical view, and maybe it is in a way. Maybe it’s just because I’ve never been a part of huge success, and that’s fair to call out.</p><p>But I have seen many unique and new ideas people thought were brilliant that turned out not to be.</p><p>Don’t get me wrong, I’m not saying you should discount ideas you think are unique, that would be really stupid. You should appreciate and cultivate such ideas and hope with time you get more.</p><p>What I am saying is, not every silly idea that crosses your mind is going to change the world. Some might, but you only get a chance to work on a handful in your lifetime, so be aware of that. If you think your idea really is one in a million and that standard rules don’t apply to it, just <em>stop reading and go with it</em>. I mean it, I honestly wish you the best of luck.</p><h4>Be ready to change your idea</h4><blockquote>No business plan survives first contact with the customer — Steve Blank</blockquote><p>By now, you’ve hopefully spent some time building your vision. You started with your idea, thought about why people would care, what kind of problem you are trying to solve and how you are going to compete. And vision is important, that’s the first thing you develop after the initial idea. But you also need to listen, especially to your customers.</p><p>Not listening is probably the most common mistake I’ve seen.</p><p>A lot goes into building a successful product, and unless you’re just incredibly lucky to get everything right the first time, you will make a lot of mistakes.</p><p>That’s fine, as long as you are adapting and willing to change. Your customers will often be your guiding light, even when you don’t like what they are telling you. But you are building the product for them, so better make sure they are happy with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TN81mvHe1rLmBGSBPE5lmg.jpeg" /><figcaption>You can’t avoid mistakes. Better to accept that than pretend it’s not true.</figcaption></figure><p>Sometimes they will be wrong, but more often than not, it will be you.</p><p>Ignore media’s glorification of visionary founders. Media wants attention, it thrives on good stories. And stories about brilliant people who came up with a glorious vision and worked hard to achieve it are very enticing.</p><p>We all love to hear and read those stories. The trouble is, they are like myths. You take a sliver of truth, mould it the way that fits your story and massage and discard everything you dislike to make it into something beautiful — and far removed from the truth.</p><p>What you don’t read about are all the mistakes those same founders made, wrong decisions they made and how their amazing products actually became the way they they are today. The devil is in the details, and breadcrumbs to success too.</p><p>The most dangerous thing to think is you have an unmistakable <em>gut</em>, that whatever hunch takes you over in a moment is the right thing to do. Sure, sometimes you need to listen to it, but be smarter (and more humble) than that.</p><p>Until your gut really <em>proves</em> to you it makes great decisions most of the time, use your head more. And no, the fact you guessed (sorry, <em>your gut told you</em>) something correctly once doesn’t constitute proof. Also, making stupid decisions based on your gut is the easiest way to have people you’re working with leave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bmMFBAW3BS7p6cC9KXh84Q.jpeg" /><figcaption>Use your head more. Even if it’s just the monkey mind.</figcaption></figure><p>Ok, enough thinking. Time to start doing something. Next we’ll talk about proving your idea (in a more substantial way than just in your head).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59cf577f9d2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>