@theandrewbailey -- regarding how much other team members devote to the project, the rest of us work 40 to 50 hours a week. This is to be expected since a 10 minute vision takes 100x the time to actually code out and make functional. But to be honest, we are all putting in less and less productive time, as the whole process seems so inefficient and wasteful.

@theandrewbailey yes, he does give feedback, about once every several days. However, three days of coding can be wiped out with one piece of feedback. This is frustrating since it could have been nipped earlier on during a design session. Is it common for people to code-to-vision rather than code-to-design?

It doesn't really matter the methodology used, but there is always (should be?) some written design, requirements, or specification somewhere. I've only ever been on "corporate" type projects where lots of stuff has been defined in advance. I find it really nice, because I can focus on implementing things, not designing, envisioning, or winging things. While malleable to some extent, it's not like a new concept could be inserted.

It might also help to know who this product is for. Is it a B2B/internal or B2C project?