8 steps needed to change an idea into $$
Just read this on a leading website and had to share this with you all
8 steps needed to change an idea into $$
This guide is aimed at software lauches - but the steps are valid for any idea you may wish to lauch into space as the next $$$$ machine
1. Define the problem - If you look around, the real money makers are those who solve problems other people have ... Define to problem and how your product will fix it - This is basic USP - Unique selling position
2. High level overview specifications and mockups - demostrates the power of visualisation - helps you get the idea into a clear and concise picture - something to work with - visual tools (like those power point presentations you see in all those meetings you attend)
3. Initial customer feedback and validation - This is a really crucial step and it might be a really depressing or exciting step. At this point you now have something that you can show potential customers to have them say: "This is interesting, I would use it and/or would pay you for it."
4. Be an axe murderer - Start killing off things you don't need right away and leave them to Version 1.1,etc., but also make sure the really important ones have a very high priority. By doing this, your app will be left to the most core and essential features. This will make it easier to get the product in the hands of your customers AND it will also make you laser focused on the things that truly matter to your customers.
5. Detailed specifications - Detailed specs are like your blueprint for the app, and shouldn't be rushed. You can't think of every scenario until you start building + testing it, but you can certainly try.
6. Build it - This is the fun part as things start getting built. From here, it should be pretty straight forward as you know what the app looks like and what all of the functionality looks like. The goal at this point is to have the war won before you ever fight/code it.
Yes, yes-- there are things you cannot foresee, but for the most part, you will know what to do. You've also spent so much time thinking and noodling on how to build the app, that a lot of pseudo-code is subconsciously in your brain.
7. Test for critical mishaps internally and with confidants - There are bugs, then there are "**** this is a critical error"! It's the difference between handing in a paper to your teacher with a spelling mistake or two and leaving out the answer to 2 out of 5 questions.
Find people you trust as well as your internal team to give the app a good run for critical bugs.
8. Launch it - This is where the T's get crossed and the I's get dotted. Make sure all the documentation is there, support is setup, and the marketing front end is good to go.
Step 3 was all about customer feedback and validation. You should have been keeping in touch with your customers throughout re: pricing and updates.
Make sure you have the merchant processing in place too. Also be ready to transition from what is most likely a development server to a production server. For more press, marketing, sales,etc. launch related/non-product stuff.
8 steps needed to change an idea into $$
This guide is aimed at software lauches - but the steps are valid for any idea you may wish to lauch into space as the next $$$$ machine
1. Define the problem - If you look around, the real money makers are those who solve problems other people have ... Define to problem and how your product will fix it - This is basic USP - Unique selling position
2. High level overview specifications and mockups - demostrates the power of visualisation - helps you get the idea into a clear and concise picture - something to work with - visual tools (like those power point presentations you see in all those meetings you attend)
3. Initial customer feedback and validation - This is a really crucial step and it might be a really depressing or exciting step. At this point you now have something that you can show potential customers to have them say: "This is interesting, I would use it and/or would pay you for it."
4. Be an axe murderer - Start killing off things you don't need right away and leave them to Version 1.1,etc., but also make sure the really important ones have a very high priority. By doing this, your app will be left to the most core and essential features. This will make it easier to get the product in the hands of your customers AND it will also make you laser focused on the things that truly matter to your customers.
5. Detailed specifications - Detailed specs are like your blueprint for the app, and shouldn't be rushed. You can't think of every scenario until you start building + testing it, but you can certainly try.
6. Build it - This is the fun part as things start getting built. From here, it should be pretty straight forward as you know what the app looks like and what all of the functionality looks like. The goal at this point is to have the war won before you ever fight/code it.
Yes, yes-- there are things you cannot foresee, but for the most part, you will know what to do. You've also spent so much time thinking and noodling on how to build the app, that a lot of pseudo-code is subconsciously in your brain.
7. Test for critical mishaps internally and with confidants - There are bugs, then there are "**** this is a critical error"! It's the difference between handing in a paper to your teacher with a spelling mistake or two and leaving out the answer to 2 out of 5 questions.
Find people you trust as well as your internal team to give the app a good run for critical bugs.
8. Launch it - This is where the T's get crossed and the I's get dotted. Make sure all the documentation is there, support is setup, and the marketing front end is good to go.
Step 3 was all about customer feedback and validation. You should have been keeping in touch with your customers throughout re: pricing and updates.
Make sure you have the merchant processing in place too. Also be ready to transition from what is most likely a development server to a production server. For more press, marketing, sales,etc. launch related/non-product stuff.