Hmm. Let's just say it was a little obtuse.
I've long been a believer and student of "What, not How" when it comes to requirements, design, and so on.
On this particular occasion, I realized the "Why" was really the most important, and missing!
So I now think we should:
- Document "Why, not What"
- Design for "What, now How"
- and hope no one ever looks at "How" (along with sausage and law)