I’ve had thousands of conversations about beginning startup companies, selling services online, creating profit-generating web applications and putting up blogs. circumstantially, I began to see differences that I feel are coveted in order for your own project to succeed, and I present them here.
Don't be afraid to act:
If you’re agreeable with your current salary and you need the promise of eating at least one meal a day, why change it? If you can’t commit whole-heartedly to your act, things won’t come to pass, and you’ll always put your project second on your to-do list. In accrual, when you have other arrears that take up the majority of your day, you won’t be able to commit the time along with resources needed to get things rolling. Who wants to sit in front of their computer after work to design the UI interface of your application or draft a business proposal to pitch to a small-business venture investor when you’ve already used most of your thinking and creative energy at something else?
I’m not asking you to abdicate your day job , but you may have to consider (a) scaling down your project to something you can manage on a part-time basis, (b) adjusting your approach to other duties and duties, or (c) coming up with something else that you’re equally passionate about, but can manage do to in your spare time.
Before doing anything, set your goals:
Right on the onset of your project, there should first be a clear connotation of goals and what it is, accurately, you’re peddling. When you’re asked about your idea, you should be able to respond in a concise, clear, and marketable way. If it takes more than five minutes to describe your idea, it says that the concept is either (a) too complex — so you should consider simplifying, (b) you’re clueless as to what needs to come to pass — so you should develop your ideas further, or (c) a combination of both.
Hire well:
When your startup anticipates on other people (programmers, graphics designers), you have to pick the right people, and once you do, you have to keep them on the payroll. Being a cheapskate when it comes to human resources will cost you a lot in the long run. How would you expect employees to commit to developing your idea when you won’t commit to keeping them on board? When your employees jump ship, you’ll be stuck in the water. Your success hinges on the people working with and for you.
Be confident but listen to what other people are trying to say:
You have to believe in your idea, you should have the mindset of proving your naysayers wrong… but ceaselessly hear to what your peers have to say. Believe it or not, other people are smart, reasonable, and experienced too. Don’t miss out on an angle that you failed to see, or make a mistake that your super-PHP-expert friend warned you from the start about SQL injections — listen keenly and avoid the affinity to shut them out just due to they’re not saying what you want to hear. If you feel their criticisms or suggestions are wrong or won’t work in your case, simply say, “Thanks for the input, but I think I got it”. This says that even though you’re not going with their idea or suggestion — it still indicates that you appreciate their input and that you’re always open to any ideas they may have in the future. If you shut out these valuable resources, in the end, you’ll have no one to else to blame but yourself.
No comments:
Post a Comment