Skip to main content

Checklist for IT Critical Success Factors


  1. Business User Interaction - Retention as a low-cost methods to increase revenue (retention is cheaper than acquisition), Voluntary, Long-term relationships, Referrals and testimonials as powerful tools that result from Business User satisfaction or dissatisfaction (referral Business Unit users are already sold, before they even call you.)
  2. Management engagement and support - Visible & consistent support, Active role in communication & reward, Assuring linkage of information technology to corporate strategies, Clear prioritization (relative to other initiatives, programs & priorities), Use facts & data to support actions at all levels of decision-making, Creating accountability's, expectations, roles & responsibilities for the enterprise, Conducting and attending regular reviews to assure & verify progress.
  3. Projects -Establish a documented project inventory (refresh regularly), Assure linkage of projects to critical enterprise & Business Unit user needs, Establish projects of appropriate scope and size (significant savings & achievable), Assign a Champion and Black Belt to each project (and hold them accountable), Implement a project tracking system to facilitate replication & reuse, Review previous projects.
  4. Continuous improvement -Training, Skills analysis, Compelling need for change.
  5. Realistic goals and strategies - Plans & road maps, Budget forecasts, Measurable goals.
  6. Effectiveness - Empower team members so that they may deal with mistakes as they occur, Decisions are based on the best available cost, benefit & risk information, Broad based participation.
  7. Communications - Creation & communication of a human resources plan, Regular written communications on news & successes, Development & dissemination of communication aids to management, Attempt to understand the Business Unit user, commitment & communication, Business Unit users should call only once, after that they should be proactively called.
  8. Compliance/adherence to architecture & standards - Standards, Methodologies, Processes, Legal aspects.
https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels/

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi