#5 jump chump how to
#5 jump chump software

The CHUMP’s project limped along until it was eventually canceled.īig penalties can result from violations of the Sarbanes-Oxley Act and other regulations, such as records retention, privacy and e-waste mandates. Since the DIOs didn’t want the project to succeed, many of the assigned staffers were either incompetent or had other (higher) priorities. Each business unit was directed to contribute money and staff to this effort, coordinated by the CHUMP.

One company decided to standardize desktop and communication functions globally. Although the organization acknowledges that some shared services (enabled by IT) would reduce costs, these efforts typically get bogged down in politics. Multidivision projects are practically impossibleĬHUMPs are typically found in organizations that have strong business units and weak central staffs. Given budget constraints and time zone complications, she was told to limit meetings to one per year, making collaborative strategy development nearly impossible and virtually ensuring failure. The new CHUMP at one global organization wanted to involve DIOs in a collaborative strategy-development process.

#5 jump chump how to

But CHUMPs are told to develop a corporatewide IT strategy and “tell” the business units how to comply. Allowing people to participate in shaping the new strategy improves buy-in and long-term support. In large organizations, implementing a new IT strategy requires many people to change their actions. Vision and strategy are best developed collaboratively rather than presented and imposed from on high. Individuals are less likely to support plans that they didn’t help develop (Except for CIOs of outsourced organizations, who usually have the outsourcer’s staff to solve problems.) As the organization learns that the CIO is unable to help, divisions stop calling, making the CHUMP irrelevant. With limited resources, CHUMPs are unable to provide new IT capabilities or address complex business problems. Here are some of the reasons why this happens:ĬIOs build creditability by solving problems for their customers. It is normally filled by a CHUMP (a CIO hired for undoable management and planning) who is fired and replaced within a few years. They are given a small staff, a small budget and many dotted-line reporting relationships with divisional information officers (DIO), who manage operational activities in the business units.īeware! This job is usually designed for failure. These CIOs have no operational responsibilities (or resources) or infrastructure or applications to deliver. They create a corporate CIO position for someone whose sole purpose will be to develop and communicate long-term IT vision and strategy.

Some companies recognize that day-to-day IT activities often make it difficult to undertake long-term planning.

#5 jump chump software

Artificial Intelligence (252) Auto Tech (7) Blockchain (62) CanadianCIO (15) Careers & Education (601) Channel (59) Cloud (1062) Communications & Telecom (74) Companies (60) Data & Analytics (169) Development (22) Digital Transformation (757) Distribution (9) Diversity & Inclusion (25) eCommerce (133) Emerging Tech (35) End User Hardware (65) Engineering (1286) Financial (783) Fintech (95) Future of Work (16) Governance (17) Government & Public Sector (106) Human Resources (2075) Infrastructure (30) IoT (108) ITWC Morning Briefing (4) Leadership (2677) Legal (305) Legislation (99) Managed Services & Outsourcing (45) Marketing (1951) MarTech (6) Medical (339) Mobility (4993) Not For Profit (3) Open Source (139) Operations (5424) People (12) Podcasts (1290) Posts (4121) Privacy (772) Project Management (76) Security (2972) Service (892) Smart Home (49) smart-home (1) SMB (489) Social Networks (416) Software (77) Supply Chain (21) Sustainability (17) Tech in Sports (246) Technology (7111) Women in Tech (74)