5
8 Comments

I can't launch

I have read everything about launching fast and launching lean. But I just can't do it. I know that I have a bad design & bad code because it's my first version. I know I can improve that thing if I give some time to it.

But I'm stuck between my obsession to make it right vs just launching. And I'm unable to do anything.

I know what I should do but I can't do it.

Why does it happen? Is it some kind of anxiety ? Does everyone launching have the same thing at some point or the other? Do have lots of expectation from this product?

on June 29, 2021
  1. 2

    All great points already. Heed them

    Launching (and failing fast) is super important for this very loop. It short circuits your perfectionist tendencies.

    Usually what happens is you launch and no one cares. That forces you to rethink if it's even worth it. What's the ultimate vision. Can you make it simpler/cleaner/faster/better. The more you iterate with those questions the faster you decide to find customers or find another project.

    Sometimes you launch by just putting the idea out there (no code/website/etc) and people start trying to pay you. You get advice on what features they really want, etc. All the interest directs you into 2 decisions: build what they want or stick to your vision - and again - changes the question from is it done yet...

    Good luck

  2. 1

    You should find the first Facebook design on the internets. That's what I call bad design. Some unicorns launched as Google sheets. PH launched like what, a mailing list? Dropbox launched as a 3-minute video. AirBnB's code wasn't bad just because they didn't have any code when they launched.

    1. 1

      Those are great words @uluhonolulu

  3. 1

    Hey mate,

    I think a lot of people are stuck in that "loop". Especially since it looks like you are a software developer. We developer take a lot of pride in our work. We wanna do it "right" event though "right" seems to be more like a spectrum instead of a singular point.

    I was initially a skeptic about "failing fast" and just releasing, because I've got it wrong for quite some time I believe. I interpreted "failing fast" with hacking something together with extreme poor quality, no security and gods forbid thinking about UX or scalability. With my newest try in the startup/indiehacker scene I'm not purposely trying to reduce any of that but rather I reduce scope and release. I might not have the product I've seen in my vision yet but I

    I'm happy with my results so far and looking forward for my release, even tough it is a far inferior product for now. It will be out and it will be mine. I'm looking forward to receiving feedback and try do adapt to it. If I succeed great, if I fail it will be a valuable lessen and I therefore wiser the next time.

    If you think your product can serve even 1 customer at it's current state, go for it!

    1. 1

      🔥So true what are the building @DodoTheDeveloper ?

      1. 1

        A set of tools helping with remote work. Currently I'm implementing the first component. Similar to a tool we use at work but I'm a bit frustrated in using it. You can think about a Trello board with a bit more functionality. If you are interested, I'm trying to build it in public.

  4. 1

    Hi @remidi,

    You launched Aurelio, so you did it right?

    1. 1

      Ya I did it but there's a lot that I feel like I'm not doing like writing more stuff. setting up more mails. Kinda stuck but yeah "something is better than nothing" is giving some weird freedom now I can do anything instead of waiting or searching for the most optimal thing.