In "The Art of Project Management" (http://books.google.com/books?id=q1dJZv4Ycr8C&dq=the+art+of+project+managemente&pg=PP1&ots=_KlIPLlTqm&sig=b487NMWqqBfeCq_4-D

In "The Art of Project Management" (http://books.google.com/books?id=q1dJZv4Ycr8C&dq=the+art+of+project+managemente&pg=PP1&ots=_KlIPLlTqm&sig=b487NMWqqBfeCq_4-DWTROkJQrY&hl=en&sa=X&oi=book_result&resnum=1&ct=result http://books.google.com/books?id=q1dJZv4Ycr8C&dq=the+art...), Scott Berkun insists that a good PM write feature statements as they directly face the customer. "My software will save you tons of money" is a fine benefit statement, but the feature statement shouldn't be "My software uses closures" but rather "The order entry system will consist of a single screen." Perhaps this is because of some technical feat that only you can appreciate, but the feature statement wouldn't ever mention closures.