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.
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.
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.
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.
In retrospect, this CRM implementation succeeded because it immediately challenged the single greatest culprit of failed IT projects: the political infighting over who owns the data and whose department will be asked to sacrifice the most in terms of process change (Petouhoff, 2006). Wisely, the project managers cultivated a mindset centered on the entire company needing to fight for its survival by better serving customers. This was to be achieved through the use of more complete customer records, more effective application of analytics to measure marketing strategy effectiveness, and the use of web-based analytics to evaluate multi-channel management strategies. For the first time, it would also be possible to measure the effectiveness of social media strategies on platforms such as Facebook and Twitter (Bernoff & Li, 2008).
The team asked the CEO to serve as executive champion and to attend each project review. They also asked him to be one of the first users of the system, providing data on customer visits he had personally conducted. Reliance on a senior executive to champion a new IT program increases the probability of success, especially when that executive visibly changes how they do their own job — altering their daily routine to use the new system or process (Maurer, 2009). Because the CEO was known for being technology-savvy, when he began using the new CRM in pilot mode on his laptop and delivering presentations based on analytics applications still in testing, it quickly became commonplace to see Vice Presidents, Directors, and managers conducting briefings using analytics drawn from the new CRM system. The CEO had effectively squelched negative politics by making the use of analytics data a mark of forward-thinking leadership.
The CEO also praised individuals and departments he found freely sharing data to make the new CRM system function more efficiently. In doing so, he employed a positive reinforcement strategy to unify potentially conflicting teams (Lui & Chan, 2008). This proved highly effective: Vice Presidents soon sent organization-wide emails encouraging staff to look for opportunities to collaborate with other divisions and to consider how the data they held could benefit others. This shift made the task of systems analysis and design — one of the most challenging aspects of project management, as many employees feared their roles were being redesigned or automated away (Petouhoff, 2006) — considerably easier to accomplish. Because silos of customer data had led to the development of small fiefdoms, concentrating on the need to serve customers better in order to remain competitive, combined with the CEO's visible commitment to the system and to data sharing, changed the organizational culture. Nothing short of a cultural shift is necessary for any IT system to attain or exceed its objectives (Craine, 2007).
Data and information are political currency in every organization. It takes foresight on the part of project managers and a deliberate strategy for overcoming the political issues inherent in any company. Having a CEO or other senior management sponsor who actively changes their own behavior to contribute to and participate in a new process is invaluable. As the research supports, the most effective strategy for reducing political infighting during IT implementations is the active involvement of C-level champions who can arbitrate challenges and model the desired behavior (Lui & Chan, 2008).
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.
You’re 88% through this paper. Sign up to read the remaining 1 section.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.