學門類別
哈佛
- 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 That an Order?
內容大綱
In August 2022, a student pursuing his master of business administration degree in Mumbai at one of India's top business schools found himself in a despondent situation as he prepared his curriculum vitae (CV) to apply for an internship position at Golden Tobacco Company. He had written an email to his former project supervisor (a senior fellow of the MIT Media Lab at the Indian Institute of Technology Bombay), requesting him to approve the project the student had worked on under his supervision as relevant experience for the internship position. In response, the student received an email from his supervisor with one terse line: "Is this an order?" With a deadline that very evening to submit the CV, the student was in a tizzy. Where had he gone wrong in his email to prompt the terse reply from his former supervisor? How could he fix the situation? And how could he prevent such a situation when writing emails in the future?