I've had trouble putting into words how different mis-communications of mine have occurred, and this sums it up rather nicely. I think many developers I know do this: we're so excited about all of the sound reasoning we placed around our conclusions and the processes that got us there that the actual conclusion is an afterthought tacked onto the end (oddly enough, the conclusion of the communication).
But that's not why you're telling someone something. You're telling them so that they take away what you put all of that work into arriving at, not how you did it (unless they want details later, of course).