學門類別
哈佛
- 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
最新個案
- A practical guide to SEC ï¬nancial reporting and disclosures for successful regulatory crowdfunding
- Quality shareholders versus transient investors: The alarming case of product recalls
- The Health Equity Accelerator at Boston Medical Center
- Monosha Biotech: Growth Challenges of a Social Enterprise Brand
- Assessing the Value of Unifying and De-duplicating Customer Data, Spreadsheet Supplement
- Building an AI First Snack Company: A Hands-on Generative AI Exercise, Data Supplement
- Building an AI First Snack Company: A Hands-on Generative AI Exercise
- Board Director Dilemmas: The Tradeoffs of Board Selection
- Barbie: Reviving a Cultural Icon at Mattel (Abridged)
- Happiness Capital: A Hundred-Year-Old Family Business's Quest to Create Happiness
BP's Office of the Chief Technology Officer: Driving Open Innovation through an Advocate Team
內容大綱
The case describes the evolution between 1999 and 2005 of an unusual innovation team within the office of the Chief Information Officer of BP. The team leader, Vice President and Chief Technology Officer (CTO) Phiroz Darukhanavala ("Daru"), eschewed a large group and a venture budget in favor of a small, lean team intimately engaged with BP's business units. The case described several mechanisms created by the CTO office during its early evolution, aimed at expanding executives' appreciation of emerging technology capabilities, building a network of relationships through which emerging technologies are scouted and vetted, and providing structured mechanisms for technology transfer. In late 2005 the CIO's Advisory Group challenged the CTO office to "keep reinventing yourselves." Students are asked to assume Daru's role and suggest new processes and structures to continue the evolution of the CTO office. The teaching note describes what the team actually did, and addresses questions raised at the end of the case.