學門類別
政大
哈佛
- General Management
- Marketing
- Entrepreneurship
- International Business
- Accounting
- Finance
- Operations Management
- Strategy
- Human Resource Management
- Social Enterprise
- Business Ethics
- Organizational Behavior
- Information Technology
- Negotiation
- Business & Government Relations
- Service Management
- Sales
- Economics
- Teaching & the Case Method
最新個案
- Leadership Imperatives in an AI World
- Vodafone Idea Merger - Unpacking IS Integration Strategies
- Predicting the Future Impacts of AI: McLuhan’s Tetrad Framework
- Snapchat’s Dilemma: Growth or Financial Sustainability
- V21 Landmarks Pvt. Ltd: Scaling Newer Heights in Real Estate Entrepreneurship
- Did I Just Cross the Line and Harass a Colleague?
- Winsol: An Opportunity For Solar Expansion
- Porsche Drive (B): Vehicle Subscription Strategy
- Porsche Drive (A) and (B): Student Spreadsheet
- TNT Assignment: Financial Ratio Code Cracker
-
Microsoft IT India
Raj Biyani faced tough challenges managing Microsoft IT India: leading a remote development organization in which key decisions were made in Redmond, and managing an organization that was perceived as less strategic than its sister Microsoft India Development Center with which it shared the Hyderabad, India site. The case follows Biyani's thought process in diagnosing the organization's problems, and poses the challenges of leading globally distributed operations. -
General Motors Technical Center India - Powertrain Engineering
Prabjot Nanua was proud of the growing capabilities of the General Motors Technical Center India Powertrain Engineering group that he oversaw. Since 2003 engineers there had expanded the center's capabilities, developing a reputation within GM for completing high-quality design and analysis projects for other Technical Centers at a substantially lower cost. In areas such as tolerance stacking analysis, GMTCI-Powertrain was now the only location in GM worldwide that performed this type of work. Nanua thought about the next stage of development for the center. Should they "go deep" and focus on more areas of technical competency where the center had developed a competitive advantage? GMTCI could become the center of expertise for a narrower set of methods and capabilities like they had done in tolerance stacking. Or should they "go broad" and continue to lobby headquarters for more complex assignments that might ultimately lead to program ownership for an entire vehicle? Each scenario had different implications for how GMTCI fit within the network of Technical Centers and corporate GM. If they did the former, they might be faced with the perception that GMTCI was limited to back-office analysis for GM's products. But when Nanua put on his headquarters "hat," he wondered if that shouldn't also be the corporation's priority for them.