This proclivity towards cannibalization is a real tragedy of we the human species, and it of course has its effects on software. Often times one might find a c

This proclivity towards cannibalization is a real tragedy of we the human species, and it of course has its effects on software. Often times one might find a customer of software who simply doesn't understand the way the system works, or is to be constructed, and they become suspicious of what they are being sold. Other times, its quite possible to 'eat ones own dog-food' and be fed back a refactored version of an asset they already owned, if not controlled properly, albeit slightly cooked up. From the customers perspective, it is perfectly reasonable to experience a plethora of these kinds of cannibalistic effects. If you get it on your plate, to save the project: invite the customer to the table. Software system implementation and usage, constructed though a meat pie, are key factors in success, its true, but if your customer does not at least have one finger in the tray, they won't know how fine it tastes. Educate your customer on software systems and why things are, not just that they are, take care of the bad smells with thorough enlightenment, and voila .. dinnertime.