學門類別
哈佛
- 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
Six IT Decisions Your IT People Shouldn't Make
內容大綱
Senior managers often feel frustration--even exasperation--toward information technology and their IT departments. The managers complain that they don't see much business value from the high-priced systems they install, but they don't understand the technology well enough to manage it in detail. So they often leave IT people to make, by default, choices that affect the company's business strategy. The frequent result? Too many projects, a demoralized IT unit, and disappointing returns on IT investments. What distinguishes companies that generate substantial value from their IT investments from those that don't? The leadership of senior managers in making six key IT decisions. The first three relate to strategy: How much should we spend on IT? Which business processes should receive our IT dollars? Which IT capabilities need to be companywide? The second three relate to execution: How good do our IT services really need to be? Which security and privacy risks will we accept? Whom do we blame if an IT initiative fails?