學門類別
哈佛
- 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
Is Your Project Turning into a Black Hole?
內容大綱
Any seasoned executive knows that information technology (IT) projects have a high failure rate. Large IT projects can become the business equivalent of what astrophysicists know as black holes, absorbing large quantities of matter and energy. Resources get sucked in, but little or nothing ever emerges. Of course, projects do not become black holes overnight. They get there one day at a time through a process known as escalating commitment to a failing course of action. Without executive intervention, these projects almost inevitably turn into black holes. This article sheds light on the insidious process through which projects that devour resources, yet fail to produce business value, are created and gradually evolve into black holes. It presents a framework that explains the creation of black hole projects as a sequence of three phases: drifting, treating symptoms, and rationalizing continuation. The framework is illustrated through two cases: EuroBank and California DMV. The article then presents recommendations to prevent escalating projects from becoming black holes and provides a means for detecting problems at an early stage.