Managing IT Politics in CRM System Implementation
This paper examines the successful implementation of a Customer Relationship Management (CRM) system within an organization, focusing on how political challenges were managed to ensure project success. The paper identifies data ownership conflicts and departmental power struggles as the primary threats to IT project success, and explores the strategies used to overcome them. Key factors discussed include establishing a compelling strategic vision, securing active CEO sponsorship, applying positive reinforcement to encourage data sharing, and driving a cultural shift away from data silos. The paper draws on relevant literature to support its analysis and offers practical insights into managing organizational politics during planned IT change initiatives.
- Introduction: CRM project context and strategic vision
- Anatomy of a CRM System Success: Overcoming data politics and departmental resistance
- Executive Sponsorship and Cultural Shift: CEO championing drives adoption and culture change
- Conclusion: Key lessons in managing IT politics
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- The paper uses a real-world case study format, grounding abstract organizational theory in a concrete CRM rollout experience that makes the argument immediately relatable and credible.
- It integrates peer-reviewed citations throughout the narrative rather than clustering them, demonstrating engagement with the literature at each analytical point.
- The argument builds logically from problem identification (data politics, silos) to solution (executive championing, positive reinforcement) to outcome (cultural shift), creating a satisfying analytical arc.
Key academic technique demonstrated
The paper demonstrates effective use of practitioner-scholar synthesis — combining firsthand organizational observation with citations from management and IT journals (e.g., MIT Sloan Management Review, IEEE Transactions on Engineering Management) to validate experiential claims. This technique strengthens credibility by showing that the observed outcomes align with documented research findings.
Structure breakdown
The paper opens with a framing introduction that establishes the strategic context and the central challenge. The main body section narrates the CRM project chronologically, weaving in citations to explain each managerial decision. A brief conclusion distills the key lessons into transferable principles. The structure is tight and appropriate for a short reflective case paper at the undergraduate or early graduate level.
Introduction
The development and launch of a Customer Relationship Management (CRM) system throughout our company had the potential to become highly political and mired in power struggles, as customer data sits at the center of such a system. What made this project successful was, first, the focus on the strategic goal of aligning every information asset to the purpose of retaining existing customers and acquiring new ones. IT projects that attain exceptionally high levels of success — from a financial, operational, and long-term strategic standpoint — share the common attribute of an exceptionally crisp, compelling, and passionate vision (Raimond & Eden, 1990). In the case of this CRM system implementation, the compelling vision was the ability to sell online more effectively than ever before and to sell more to existing customers. The urgency of achieving this vision was underscored by a series of new product introductions the firm was planning within six months of the new system going live.
References
Bernoff, J., & Li, C. (2008). Harnessing the power of the oh-so-social web. MIT Sloan Management Review, 49(3), 36–42.
Craine, K. (2007). Managing the cycle of change. Information Management Journal, 41(5), 44–46, 48, 50.
Lui, K., & Chan, K. (2008). Rescuing troubled software projects by team transformation: A case study with an ERP project. IEEE Transactions on Engineering Management, 55(1), 171.
Maurer, R. (2009). Get your team involved. The Journal for Quality and Participation, 32(1), 28–31.
Petouhoff, N. (2006, April). The scientific reason for CRM failure. Customer Relationship Management, 10(4), 48.
Raimond, P., & Eden, C. (1990). Making strategy work. Long-Range Planning, 23(5), 97.
Create your account
Always verify citation format against your institution’s current style guide requirements.