Skip to main content
Case Study Undergraduate 759 words

Selling Executives on Project Management: A Case Study

~4 min read 5 sections Business · Project Management
Abstract

This paper presents a case study analysis of the Levon Corporation, whose declining revenues were linked to its lack of project management capability in an industry increasingly awarding contracts on a merit-points basis. The paper examines why company executives rejected employee recommendations but remained open to an external consultant, exploring the objectivity and fresh perspective consultants bring. It further analyzes why executives remained unconvinced even after the consultant's presentation, arguing that the consultant's approach was more critical than persuasive, and proposes alternative strategies — such as comparative revenue analysis and real-world implementation examples — that could have more effectively secured executive buy-in.

Key Takeaways
  • Introduction: Levon Corporation's Revenue Decline: Background on Levon's revenue loss and employee proposal
  • Why Executives Listened to the Consultant but Not Their Employees: Consultant objectivity, fresh perspective, and advisory value
  • Why Executives Remained Apprehensive After the Consultant's Presentation: Consultant's critical tone failed to persuade executives
  • Strategies to Secure Executive Support for Project Management: Comparative data and real examples as persuasion tools
  • Conclusion: Summary of how better strategies would have worked
✍️ How to write this paper — guide, tools & examples

What makes this paper effective

  • The paper directly addresses each case study question in a logical sequence, making the argument easy to follow and evaluating each issue on its own terms before connecting them.
  • It goes beyond description by critically evaluating the consultant's presentation strategy, identifying specific weaknesses and proposing concrete alternatives — demonstrating analytical depth rather than mere summary.
  • The use of multiple scholarly sources to support claims about consultant objectivity and organizational dynamics strengthens the credibility of the analysis.

Key academic technique demonstrated

The paper demonstrates effective case-based reasoning: the student grounds each argument in the specific details of the Levon Corporation scenario while connecting those details to broader principles drawn from project management literature. This moves the analysis from anecdote to generalizable insight, a key skill in business and management case studies.

Structure breakdown

The paper opens with a summary of the case facts, then addresses two distinct analytical questions in separate sections. Each section begins with a direct answer and follows with supporting reasoning and evidence. The paper closes with a brief synthesis. This Q&A-driven structure suits the case study format and ensures all prompt elements are addressed systematically.

Essay 759 words

Introduction: Levon Corporation's Revenue Decline

Levon Corporation executives were concerned about the company's declining revenues (Kerzner, 2013). The company's employees argued that the decline was due to changing industry trends: contracts were increasingly being awarded on the basis of merit points rather than the lowest-bidder mechanism. Because the company had no project management capability, it kept missing out on key contracts, which affected its revenue stream (Kerzner, 2013). The employees suggested that a project management function be incorporated into the business framework to increase the company's competitiveness. The executives were, however, reluctant to consider this proposal because they believed such a move would disrupt the organization's balance of power (Kerzner, 2013). They reluctantly hired a project management consultant to evaluate the employees' suggestion, but even after the consultant openly demonstrated that the organization was in dire need of a project management department, the executives remained apprehensive (Kerzner, 2013).

Why Executives Listened to the Consultant but Not Their Employees

There are several possible explanations for this. To begin with, since consultants are not part of the organization, they are less likely to be influenced by organizational culture and company politics. As such, they are more likely to give an objective opinion on the issue at hand compared to employees who work within the organization and may have other vested interests (Lientz & Rea, 2003; Russell & McGovern, 2012).

Moreover, a consultant enters as a new member with fresh ideas and fresh perspectives that can be applied to improve other areas of the organization — areas that may also be contributing to the decline in revenues (Lientz & Rea, 2003). In this regard, the consultant plays more than just an advisory role. In addition to giving an informed opinion on whether project management is the best path forward, the consultant draws on their expertise and past experience with other companies to advise management on how responsibilities and duties should be structured under any new arrangement. This ensures there are no overlaps, that lines of authority are clearly defined, and that power-related conflicts among executives and departments are minimized (Lientz & Rea, 2003).

Why Executives Remained Apprehensive After the Consultant's Presentation

The consultant was not sufficiently convincing given the executives' degree of reluctance. He began his presentation by highlighting how misinformed the company executives were about its financial performance, which immediately created a disconnect between himself and his audience. He then compounded this problem by failing to address the executives' most pressing concern: demonstrating how project management could be implemented effectively without disrupting normal business processes. Instead, he focused on what the executives had done wrong.

As a result, the executives remained apprehensive because they were not persuaded that project management would solve the problems the consultant had outlined. The consultant criticized more than he informed or persuaded, and he did not clearly show how project management adoption would resolve the organization's revenue problems.

1 Section Hidden · 175 words
Strategies to Secure Executive Support for Project Management175 words
There are a number of strategies the consultant could have employed to avoid this outcome. First, he could have begun by acknowledging the company's positive performance…

Conclusion

These strategies would have gone a long way in convincing executives that project management is not only necessary, but also entirely achievable in a manner that does not disrupt normal business operations. By leading with positive evidence and grounding recommendations in comparable real-world cases, the consultant could have shifted the executives from apprehension to active support.

References

Kerzner, H. R. (2013). Project management: A systems approach to planning, scheduling, and controlling (11th ed.). John Wiley & Sons.

Lientz, B. P., & Rea, K. P. (2003). International project management. Routledge.

Russell, D., & McGovern, M. (2012). A new brand of expertise. Butterworth-Heinemann.

Key Concepts in This Paper
Executive Buy-In Project Management Consultant Objectivity Organizational Change Revenue Decline Stakeholder Persuasion Business Strategy Change Resistance Case Study Analysis Contract Competitiveness
Cite This Paper
PaperDue. (2026). Selling Executives on Project Management: A Case Study. PaperDue. https://www.paperdue.com/study-guide/selling-executives-on-project-management-case-study-2148823

Always verify citation format against your institution’s current style guide requirements.