> I think you're missing a few steps in your development process, or at least one. Normally it goes like this: problem->solution->implementation->testing. Ther

> I think you're missing a few steps in your development process, or at least one. Normally it goes like this: problem->solution->implementation->testing. There should actually be testing associated with every step: Is X a real problem worth solving (severity or cost x frequency)? Would Y be an appropriate solution (test a mockup, prototype, or stub UI)? Does the Z implementation work (as in, not just does the problem get solved when Z is used, but does Z actually get used to solve the problem)?