Design docs are about builds

A good way of thinking in GDD is to write down more details of what’s already in a build of some sort. With this I mean that if you design pages and pages of documentation regarding something not concrete, you are at risk of delivering something disconnected from reality.

Frame the problem, develop prototypes, align, and only after write down specs. That’s the way. You need less talk and more rock.