I think he was right - technical people apparently have a hard time explaining themselves. I think the point of the article is that you need to be able to incl

I think he was right - technical people apparently have a hard time explaining themselves. I think the point of the article is that you need to be able to include actual benefit information, which isn't necessarily straight forward to gather or develop, rather than just short term stuff. Benefits are not just inverted consequences, in other words. What it comes off as saying, is that who cares, just buy what ever you want, I mean, a developer might get upset that it takes more time to purchase equipment than to write some code. I can't imagine there being anything remotely close to a catch-all rule for this kind of thing - buying new hardware at a Fortune 50 vs. buying hardware at Facebook/Google vs. buying hardware at small, agile, cash-rich web startup are all going to be radically different, as they should be.