4 ms·
I think a major factor for you guys, which davidw referenced as a motivational engine, is rapid development cycles, if you release SOMETHING quickly you are not
by nextmoveone 19y ago
I think a major factor for you guys, which davidw referenced as a motivational engine, is rapid development cycles, if you release SOMETHING quickly you are not discouraged so easily.
4-6 weeks is generally my max. time for spitting something out, otherwise I get bored and slowly stray away and eventually leave the project/app alone. Like if it's 12, 16, 24, or 3 months etc. to get something out, by that time my attention has been moved elsewhere.
My answers to your questions should definitely not to be considered as advice(except for 2 and 3), but:
1. I make them the way I want, or very close too it. Or I leave.
2. After I get feedback from people other than the ones involved in the development of the product, or after you release for use and there is no/a negative response from your users.
3. Once again, after you release and it doesn't work, try to fix it. Ask your users what they want, can you give it to them? No? Call it quits. Yes? Keep on going!