this is pretty exciting news for me,<p>a university entrepreneurship club is doing an event to introduce entrepreneurship to students,<p>I was invited to talk since the founders of the club know that I code/create stuff,<p>I'm thinking about cutting through all the entrepreneurship porn and talk to ppl about real entrepreneurship<p>* finding a pain point<p>* coming up with a solution<p>* sticking to the process and doing the work it takes<p>* not to expect success in the first 1-2 years, neither from the first startup/project<p>* coding is not a required skill to be an entrepreneur<p>* you don't have to finish university to start doing something<p>this is what I'm thinking to talk about, do you think I should remove or add something?
I've got some slides from some talks I've done on this before. Happy to shoot them over and you can user stuff that's useful if you'd like?<p>Otherwise:<p>* Problems > Solutions: How you fix something is not as important as actually fixing it. People will pay you if you can actually fix things, even if it's not as sexy as you originally intended.<p>* Validate problems: Why * 5, don't reveal your ego "I'm building this...", get them to talk about the last time the problem occurred.<p>* Don't get married to a solution: There are 100's of ways to get from A-B. Come up with a bunch of "solutions" and note down the assumptions they are based on. Pick the one you feel aligns best with your vision of the future and go talk to the people you think have the problem<p>* Knowing when something isn't working.<p>* Knowing when something is working.<p>+ the things you listed above.<p>Potentially survey the students before hand, I've used this to find some super relevant problems that I can discuss based on real life. Make people way more engaged.
Depending on your location, paying (close) attention to your local labour laws ( since your first employee ) and all those extra-hours just before each release.