If you have a business idea, would you rather be a perfectionist or get things done and launch right away?

by adventph. Posted on Sep 13, 2020    35    23

Personally, I think getting things DONE is better than perfecting it. Perfecting a business idea can be done in the process of introducing your brand or product. And let's admit it, it doesn't happen in weeks. Sometimes, it could take months or years. So I'd rather implement and launch! And figure things out along the way.

There are lots of different ways to implement a project quickly like:

  1. Capitalizing on an existing model of the same idea you/I have
  2. Getting a project partner to launch immediately
  3. Utilizing resources that already exists

and so much more. Does anyone agree with me?

Well, here's a relevant article also. This one promotes staying agile and lean, especially for startup businesses. https://technologyrivers.com/blog/launch-quickly-7-ways-to-get-idea-to-app-store/



matthewfelgate 1

Minimum Viable Product as quick as possible → refine → repeat

Vickillah 2

I was trying to start my business off perfectly, and found that I was wasting too much time on the details before I even started. Spoke with my mentor and he said stop wasting your time get out there bust your knuckles, get your cuts and scrapes and learn from them. I’m one month in and have had some great success in my launching. If it wasn’t for my mentor I would probably still be figuring out the details of what programs to use how to track my income what kind of business account should I be opening. I am definitely a believer in get started and figure out the details as you go.

twocentcharlie 2

Imperfect action beats perfect inaction everyday.

  adventph 1

Agree 💯💯💯

Slowmaha 2

GETMO - Good enough to move on

then iterate...

sykikchimp 2

Get to cash flow as fast as possible. Refine as you learn what your actual customers are willing to pay for.

PotenciaMachina 2

My definition of perfect is "no mistakes." I consider not launching as quickly as possible to be a mistake, thus I often have my cake (near to perfection) and eat it (launch quickly). What do you think about that?

three29 4

I’d rather be a perfectionist and never launch a single product. It’s been working out for me my whole life so far.

You miss none of the shots you don’t take.

gmansoorpk 1

Good for you

  adventph 1

Appreciate this insight! I guess we can look at it at that angle also. :) Some people prefer taking it “slowly but surely”

sail_fast123 3

Every time I’ve tried to be a perfectionist I’ve waited so long to launch that I ended up going nowhere. It the past month I’ve started to just go full force into projects and ideas whether or not I have the resources and the results have only been good. Easier to learn from a mistake than it is to prepare for all the mistakes that could come.

UncomfortableMike52 3

Somewhere in the middle honestly, don’t produce crap, but keep moving forward and keep testing things out. The balance is hard to find! :) Simple sells

bbar97 3

I definitely think it depends on the nature of the product/business. In some cases you should spend time to get it right, while others it is better to just get it going. For example it wouldn't be wise to launch some new kind of amusement park without meticulously planning and preparing, while for most software/app projects its not as neccesary to get it perfect on launch.

loracph13 3

I agree! Launching quickly will also help you get feedback from users which you can use to improve your product. Getting an experienced project partner is also very advisable for first timers so they won't waste time figuring things out on their own. Great share!

animalsarebetter 1

Where do you recommend finding such a partner? 🤔

  adventph 2

You may want to check our website - https://technologyrivers.com. We are a software development company from Virginia.

AccidentalCEO82 7

Good enough. Perfect is an arbitrary feeling because what a business owner thinks is perfect probably isn't the case for everyone else that matters.

ILikeChangingMyMind 18

In Silicon Valley we agree so much with this idea that we have quirky acronyms and sayings which revolve around it :-)

  • "YAGNI" (You Ain't Going to Need It) - when you catch someone "perfecting" a product by adding bells and whistles that it doesn't actually need (or at least, not now)

  • "Yak Shaving" - when someone feels like they're polishing/perfecting their product, but they're blind to the fact that it's not a real improvement, and they're just wasting time

  • "MVP" - Minimum Viable Product - unlike the first two terms (which originated in tech), this one came from the venture capitalists who fund tech start-ups, so it's less quirky ... but probably the most relevant.

    Investors noticed a pattern: many of their companies would spend all the money given to them (their "runway to launch") on hiring people to build the perfect product.

    Then they would bring that product to market and ... it turns out it's really hard to predict exactly what the market wants. Many products wouldn't be successful right out of the gate ... but could still be made to succeed, if they could just fix or improve a few things. The problem was, because the company already "used up their runway" (spent their cash) to get there, the company would "crash".

    To avoid that, the idea of MVP is to build and release the:

    1. smallest possible (minimum) version of your product that you possibly can ...
    2. ... which still is complete enough to serve its purpose (viable)

      This gives you the "runway" to iterate, and release new and improved versions over time.
[deleted] 1


ILikeChangingMyMind 2

First off, this is just a principle, and no one principle isolation can guide all businesses.

But that being said, if you don't know that the framework you're building is what your business actually needs ... it may not be. It's certainly possible that you accurately anticipated your future needs, and saved time by addressing them now ... it's just, we humans in general are bad at doing that, so it's less likely you did. Only you know your particulars.

I just know that in general the "technician" in us will often want to do things, like build frameworks, that the business doesn't need. As a tech entrepreneur, it's important to let your side gig be fun to your inner technician ... but if you want your company to succeed, you also need to let your inner entrepreneur have their share of your time .... and that role needs data to make decisions about the future of your company.

To get that data you need an MVP, so the general principle here is to YAGNI as many pieces of your app as possible, get to market as quickly as possible, and then learn what you really need to be working on.

Govind_the_Great 2

Minimum viable product which is part of the reason Nvidia always releases better iterations down the line.

Somewhatinformed 3

For companies that raise pre-launch is there a general industry standard or limit to how much of the round should goes towards pre-launch?

My company is raising soon and we estimate we will spend 100K of the 350K raise by our launch. We have gone 8 months in development with no capital and would have 25 weeks between when we start raising and when we launch.

ILikeChangingMyMind 2

I don't know of any, but I'd imagine it's somewhat contextual to your product/industry.

In tech in general you can usually do multiple launches, releases, updates, etc. at (comparatively) low cost. On the web in particular, many even practice "continuous deployment", where every code update written goes live immediately (after passing a slew of software tests). In that sort of environment the mantra is "get started in the market ASAP, see what the market tells you, and then respond as quickly as you can".

The ideal of The Lean Startup in particular is that you're not even working on building a product, you're working on figuring out what your business should be. In that view what matters isn't producing anything ... except what you have to (your "MVP"), to learn what will work (ie. what the market wants). Practices like A/B testing (ie. make a change to your product and see if customers respond well), are critical to accomplishing this ... and they need customers.

But in other industries, eg. retail consumer goods, each round of iteration is very costly, so there can't be one standard ... just principles like "learn from the market as quickly as you can".

JPaulMora 7

Amen. It’s great for personal projects too