The top section of the document is similar to amazon's PR/FAQ process, which having been forced to use to speak to amazon folks, I've found to be pretty good fo

The top section of the document is similar to amazon's PR/FAQ process, which having been forced to use to speak to amazon folks, I've found to be pretty good for getting your thoughts and end customer defined. It's actually pretty good for junior to mid level engineers as well: it keeps them from focusing on the pure tech they want to deliver and focus more on the why. I find a lot of people get stuck on what/how they want to deliver, thus delivering the wrong solution. I know it helped me out personally.