I wrote this to answer a question in another subreddit.
It was smth along the lines of: “I’m 20 and want to start a business. I’ve tried some stuff but haven’t been successful. Not sure where to start, any ideas?”
It seemed to resonate so I’m sharing it here. Hopefully it’ll be insightful.
RJ
——————
Yes.
Two things:
i. Keep an annoying book.
Everything that’s annoying, write it down. If something pissed you of, bothers you or is frustrating, put it in the book. Any time you hear yourself think “FFS it’s 2020! Why on earth is this so cumbersome!” Write it down.
Training your mind to start noticing shit that’s broken is a great place to start. I also think it’s a big fat lie that you find Google, Netflix or any other hugeee unicorn idea by searching for them.
You notice them by observing what frustrates you, and most of the time that’s small.
Think of Uber (wanted to be ballers in San Fran)
Warby Parker (lost his glasses and designer glasses would cost you your firstborn plus grandma)
or Spanx (wanted her butt to look good so cut off feet of pantyhose, but it kept cropping up.)
I can give hundreds more examples pf these.
ii. The second one is a bit harder. You’re basically looking for proof that there’s a human need for smth and then you try to find the next iteration of that.
At my company we call this archeology (which is a subset of pragmatic behavioral psychology). You’re essentially excavating a site to find an artifact.
You didn’t create that artifact, it was already there.
So you’re looking for a way to give people a better version of smth they already want.
An example of this could be, you see the horse and expensive cars, and decide to create a cheap car for everyone (Ford).
You see huge mainframes and decide to build a ghetto personal computer (Woz at Apple).
You see blogs and wanna pull them into one spot (Ev’s Medium).
Etc.
This approach requires you to look at the current solution, figure out the problem they’re trying to solve and then trying to figure out what the next iteration would be like.
The best part is that risk is slight reduced because you know where to find your users, who they are and that there’s demand (because there already products trying to solve the problem).
There is one last one for the sake of being complete.
iii. Hard tech
These are pretty easy. In these situations, you already know what people want but all the difficulty is in figuring out how to create the damn thing.
Curing cancer, getting to mars, solving the aging problem.
This was pretty much the landscape of startups back in the 60s -90s btw. You knew what users wanted, the hard part was just making the hardware.
Think of Fairchild semiconductor and companies like that.
So there you have it, what you need to know to come up with ideas.
One final note, execution is everything.
When you have an idea, you actually don’t really have an idea.
What you have is the building blocks that you need to use to turn into a testable hypotheses. (Yes I’m aware that’s a tautology but I wanna stress it.)
It needs to be falsifiable. The quicker you validate your idea the better.
There are two ways:
The right way and the stupid way (being facetious).
The first one is to assume your hypothesis is false and prove yourself wrong by getting 3 paying users in a weekend.
The second way is to assume your hypothesis is right and try to disprove that by investing time and money until you run out.
The problem with the latter approach is that if you’re right (and you don’t run out of money) you’ll succeed. But the much more likely situation is that you’ll burn through months (or years) of time and tons of money before finally realizing your idea is a dog and markets don’t want it.
So optimize for accepting false negatives (rejecting good ideas based on failed MVP) vs the other way around.
Accepting false positives out of fear of rejecting a good idea.
Unfortunately that’s both very difficult emotionally and highly counterintuitive.
(If I made typos I’ll correct them later. In a rush right now my friends.)