Dear Arun,
All thanks to Jacob for sharing the post. I read the post. Here's my take on it; it's a real-life experience.
There was an IT firm that had an Operations vertical and a Product Development vertical. The Operations Team had to use the products developed by the Product Development team. This was a result of an organization policy to use the products developed internally first and then market them to the clients. These products were one of the key strengths of the company. The Operations delivered a much higher volume of work. The revenue generation was higher by the Ops team, although the Products made the company an industry leader. This was the first bone of contention. The Ops team knew that they were the rulers, yet had lower visibility. The conflicts deepened each time a new product was developed by the PD Team and had to be used by the Ops team. Generally, the pilot phase wouldn't reveal all the bugs. It's only the go-live phase where the bugs would surface and slow down the production in Operation. This would become a major cause of concern as any slowdown would significantly affect the operation.
The management within the firm showed biased attention towards these verticals. The top tier had all its support for the PD Team, whereas Tier 2 was operation-oriented. As you suggested, the game theory worked best there with a Nash equilibrium at Ops refusing, but Product supporting quadrant. Here, the product team has a dominant strategy as they have the support from the top bosses.
Here's another article on Game theory in Biblical Times [Games strategy in Biblical Times](http://freakonomics.blogs.nytimes.com/2010/10/22/game-strategy-in-biblical-times).
Regards,
(Cite Contribution)