One thing Dan didn't mention (but perhaps alluded to), is that an objection does not immediately translate into a request to engineering to add feature X. For

One thing Dan didn't mention (but perhaps alluded to), is that an objection does not immediately translate into a request to engineering to add feature X. For example, in Dan's discussion of priority and severity, he didn't go running to the development team telling them they needed to add severity to FogBugz in order to nail a big client. This allows developers to focus on good long-term design decisions that hopefully make the product better. Granted, if you hear enough of the same objection, it may be something that you want to add to your product, but you want to keep that as part of an existing engineering workflow instead of treating every object as an urgent request to help get a sale.