The devil may be in the details. If your team is excited to build a service (say, for the technical challenge or the potential reputation gain) that objectivel

The devil may be in the details. If your team is excited to build a service (say, for the technical challenge or the potential reputation gain) that objectively should be done by a different team (say, they have the right background, have already started, or whatever) -- do you put the teams interest first (and do it) or the company's (and don't). I've faced this situation a lot. I used to pick the former. If we have more impact, how can that be bad? Good for company & so on. It frequently did end up good for my team, but not always good for the company. Once I adopted the "good for company" mindset, I found I could often achieve what was good for both, but I did find value in putting the company first. To put another way: the local optimum is not always the global optimum. As a manager, you need to think about the global & favor that over the local. My two cents.