Google Project Maven Ethics: A Stakeholder Analysis
This paper examines the ethical dilemma Google faced when employees protested the company's involvement in Project Maven, a Pentagon contract to develop AI analytics for drone technology. Using stakeholder analysis, the paper identifies the competing interests of employees, shareholders, the Pentagon, and affected civilian communities. It then evaluates Google's CEO decision to abandon the contract through utilitarian, rights, and justice ethical frameworks. All three frameworks support the conclusion that ending the contract was the right choice. The paper concludes with a lesson for managers on balancing corporate core values with business strategy and social responsibility.
- The Nature of the Ethical Dilemma: Google's Project Maven contract sparks internal ethical conflict
- Primary Stakeholders and Their Interests: Employees, CEO, Pentagon, shareholders, and communities examined
- Power Relations Among Stakeholders: Ranking stakeholders by influence over the CEO's decision
- Actions Taken in Response: CEO ends contract but visits Pentagon to preserve relationship
- Utilitarian, Rights, and Justice Perspectives: Three ethical frameworks all support abandoning the contract
- Key Lessons for Managers: Listen to stakeholders and uphold core company values
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- It applies three distinct ethical frameworks—utilitarian, rights, and justice—to a single real-world case, demonstrating how multiple lenses can converge on the same conclusion.
- The stakeholder analysis is thorough, distinguishing not only each party's interests but also their relative power in shaping the outcome.
- The paper maintains a clear argumentative thread from problem identification through ethical analysis to a practical managerial takeaway.
Key academic technique demonstrated
The paper models applied ethical reasoning by grounding abstract frameworks (utilitarianism, rights theory, justice) in concrete organizational decisions. Rather than treating these frameworks as separate exercises, the author uses each to reinforce a unified verdict, showing how multi-framework convergence strengthens an ethical argument.
Structure breakdown
The paper opens by defining the dilemma, then systematically identifies and ranks stakeholders by interest and power. It narrates the actions taken before turning to normative analysis through three ethical lenses. It closes with a practical lesson for managers, moving from description to evaluation to prescription—a structure well suited to applied ethics case studies.
The Nature of the Ethical Dilemma
At the heart of Google's culture is the motto "Do no evil." This motto is the motivating value for many of the company's workers, so it was no surprise when employees protested Google's contract with the Pentagon to provide AI analytics for drone technology as part of Project Maven. Employees were upset that their company appeared to be violating its core value — their reasoning was that Pentagon drones would likely be used in warfare and could lead to the killing of innocent men, women, and children, as various news reports had documented.
Google's CEO therefore faced a difficult choice: commit to the Pentagon contract and betray his workers' sense of the company's most important value, or abandon the partnership and satisfy employees. As the head of a public company, the CEO was also aware that shareholders had a stake in the equation. Government contracts can be lucrative and good for business, so turning one down would mean a loss of revenue that could hurt shareholder value. At the same time, if the company truly stood by its motto, the CEO also had to consider the stakeholders in places like the Middle East, where drones were often used to deliver explosive payloads. What if Google's work on Project Maven ultimately contributed to the killing or wounding of innocent civilians?
The CEO thus had multiple competing considerations: employees were unhappy about the contract, but maintaining a relationship with the Pentagon could be good for business; shareholders had to be kept in mind, but so did the real, life-or-death implications for people in other parts of the world. Should the CEO betray the company's culture and its employees' sense of its central value by abandoning "do no evil" in order to satisfy shareholders and develop a business relationship with the Pentagon?
Primary Stakeholders and Their Interests
The primary stakeholders in this issue were the employees, the CEO, the Pentagon, shareholders, and the communities that might be impacted by the use of drone technology in other parts of the world.
The employees' interest was straightforward: the decision to work with the Pentagon on Project Maven appeared to them to violate the code of ethics they had signed onto at Google — namely, to "do no evil." They felt the company was asking them to work against the very principle it sought to promote in its workplace culture.
The CEO's interest was that, as head of the company, he had to make the final decision. He could understand the employees' point of view, but he also had to consider business strategy, shareholders, and what the company's values genuinely required. This issue would set a precedent either way, making it essential to reach the right conclusion.
The Pentagon's interest was that it wanted to work with Google to get the project operational. Tasked with providing defense systems for the country, the Pentagon sought Google's analytics team to provide services that would support that mission. It was eager to work with the best, and Google was its first choice.
Shareholders are generally pleased when a company secures contracts that increase revenue, since more profit means a greater return on investment. Their interest in this issue was therefore primarily financial. If the contract were retained, it would likely boost returns; if it were abandoned, it could limit Google's revenue and potential for growth — particularly since the Pentagon consistently has significant resources to spend.
Civilian communities' interest in the issue was fundamental: anything that could potentially harm or kill them is a serious concern. If Google was helping develop technology that could be used to harm civilians, those communities had every reason to view the company as acting immorally. They could express their objections by turning away from Google products or by boycotting the company altogether.
Power Relations Among Stakeholders
In terms of power relative to this issue, the CEO held the most, since the decision about whether to continue or abandon the contract rested with him. Employees ranked next. Although they could not make the final call, they wielded real influence: they could stage walkouts, threaten to quit, use social media to fuel a public backlash, or engage in forms of sabotage. Unhappy employees represent a genuine risk for managers who are not attentive to their concerns.
Shareholders followed employees in terms of influence. While they could not "walk out," they could vote with their money. If shareholders were dissatisfied with the direction the CEO signaled, they could sell their shares and drive the stock price down, which would in turn limit the company's ability to raise capital in the future. The Pentagon, as a current and potentially long-term customer, also had leverage: it could make clear that if Google did not honor the contract, it would look elsewhere in the future, effectively excluding Google from preferred contractor status.
Finally, the affected civilian communities had the least power but faced the greatest vulnerability, since the end product of Project Maven would impact them most directly. Their primary avenue of influence was social media — raising awareness about the potential violation of Google's "do no evil" ethics and pressuring the company through public opinion.
Create your account
Always verify citation format against your institution’s current style guide requirements.