This shows the difference between an engineer and an artist. An engineer want to see how a system works... what are it's limits... how efficient you can make it run. For what purpose? Doesn't matter or that will be determined later.

An artist on the other hand doesn't care about the system, they have something in mind. The "vision" you hear about. They will then seek out anything possible to get that vision made, irregardless of tech.

Applied to this situation, if you are making a game, you have to be both artist and engineer, of that there is no doubt. However, if you are making a game, this intrinsicly means that you have to start with the Artist side, the vision, what it is you want to DO. Then you can engineer the system to make it work but if you don't have vision, you are not making a game, you are merely "making levels".

Please don't take this as meaning your approach is not good. It is. For engineering. But not for a Game Design Document and not to make a game, for that requires more than just that line of thinking.