Michael Seibel "About Business"

자기확언 및 감사일기

There is a common misconception that your idea has to be great in order to start a company.

 

 

And the first i want to do is destory that misconception.

 

 

Personally, i was one of the co-founders of a company called Justin TV

 

 

It later became a company called Twitch.

 

 

And sold to Amazon for almost a billion dollars.

 

 

Our original idea was to create an online reality TV show.

 

 

Clearly it's hard to draw a line between that.

 

 

And creating a live video site

 

 

And where people watch video gamers

 

 

And chat with their friends.

 

 

But that's exactly what it became.

 

 

And so don't fall into the trap of thinking that your intial idea has to be great

 

 

By any definition

 

 

This is what you should think about instead.

 

 

My first advice is to start with 'a problem'

 

 

I think starting with 'ideas' is tricky

 

 

Because immediately people want to grade your idea.

 

 

It's a lot easier to start with a problem

 

 

And to think about how to grade a problem.

 

 

When you think about the problem.

 

 

You shoud be asking yourself

 

 

"Do i have any relationship with this probelm personally?"

 

 

Is this a problem that i have?

 

 

Is it a problem that my friends have?

 

 

Is it a problem that my family has?

 

 

Is it a problem that exists through the work?

 

 

Is it a problem that's in my community?

 

 

Often times having a personal connection to the problem is really helpful for two reasons.

 

 

One, you can tell whether the solution is even within the ballpark of solving the problem because you got some connection with the problem. 

<ballpark : not exact but close in number or amount, approximately correct>

 

 

And two, when you're feeling discouraged and the solutions that you're building aren't working,

 

 

You still have some personal connection to the problem that sees you through untill you find a solution that does work.

<see sth thorugh : to continue doing a job or activity until it is finished, especially when it is difficult>

 

 

So that's the first place, i would start thinking about problems.

 

 

And i think a lot of people keep little idea books with start-up ideas.

 

 

I think they'd have a lot more success, if they kept little problem books

 

 

And wrote down notes on the problem that they encounter on a daily basis

 

 

Or that their friends complain about their family complain about.

 

 

Once you find a problem, that's interesting enough to start pursuing further,

 

 

the next question I ask myself is "Why are you uniquely qualified to work on this problem?"

 

 

By 'qualified' i don't mean in the classical resume sense like "Oh, you've had 25 years of experience in this area" or something like that.

 

 

But what i do mean is that like "Is there some angle on the problem you understand that you don't think others understand?"

 

 

Is there some way of attacking the problem?

 

 

Is there some perspective on the problem is some personal experience with the problem that you have

 

 

That you don't feel is generally used or understood in other solution to the problem.

 

 

In this phase, it is often helpful if you're solving a common problem

 

 

To look at some of the people who tried to solve the problem before

 

 

And look at some of the products that are trying to solve the problem or failed to solve the problem

 

 

just so you can get a basic understanding of what other people thought their unique insight was

 

 

and whether it was the same or different than yours.

 

 

This is kind of your gut check.

 

 

"Hey, is this a right fit for me?"

 

 

The next step is to start thinking about how do you want to build your MVP

 

 

Your Minimum Viable Product.

 

 

What's the first product

 

 

What's the first solution you are gonna build and release to your users to see

 

 

if maybe you can try to help them solve this problem.

 

 

The most important thing to think about your MVP is don't fall in love with it.

 

 

Your MVP is most likely not going to solve the problem or is gonna solve the problem very poorly.

 

 

And it really is the first step in the learning process of whether this problem is solvable at all.

 

 

Let alone whether you can solve it.

 

 

A lot of people fall in love with their product.

 

 

And are not in love with their problem or their customer.

 

 

I advised the opposite.

 

 

Be in love with your problem.

 

 

Be in love with the customer.

 

 

and treat your product in a way that you can change.

 

 

It can develop. It can improve.

 

 

Don't be too in love with your inital product.

 

 

The most important thing to not fall too in love with your initial product is to release it quickly.

 

 

Oftentimes an MVP can be built and released in days or weeks.

 

 

it's not going to be perfect.

 

 

It might not be something you're proud of.

 

 

But it can be the beginning of learning about whether or not you can actually solve the problem.

 

 

느낀점

1. 제품을 사랑하지 말고, 문제와 고객을 사랑해라.

2. 그렇게 하기 위해서 최대한 빠르게 제품을 내놓고 개선해라.

 

 

 

너무 내 제품을 오래 고민하지 말고, 빨리 사람들에게 보여주고, 시장의 반응을 보는게 더 좋은 경험이 될것이다.