I've had to counsel (for lack of a better word) team members who got excessively demoralized and cynical about the product we were working on, because all they ever hear about is what is broken, who is pissed about it, and what deal fell through because of it, on what is largely a successful product making a decent number of people happy. Make sure that you don't just look up and check the global context sometimes, make sure your team members do too, and help them if you have to.
I am reminded of the 'Cool Cam' anecdote, in which morale was shifted from "Not only that, but everyone had grown tired enduring the stress of the weekly 'why-shouldn't-we-cancel-this-project' meetings with the executives" to "The weekly meetings got easier, more developers were brought on, and the team managed to put together one hell of a game."
I've been in that spot. Actually going to where users are using the product was a big lift. They liked it, despite the "code warts" that they are blissfully unaware of.
