Skip to main content

Checklist for outsourcing

  1. Human resources - ensure fair and equitable treatment of all team members affected by the decision, provide a degree of certainty about the approach to be adopted so as to assist all relevant parties to make appropriate decisions in relation to staffing matters, seek to maximize a harmonious working environment and minimize the potential for dispute during the changeover to a different vendor, maintain the viability of functional areas during the outsourcing process, ensure that related processes are focused on achieving the best value for money, ensure that team members are aware of what constitutes ethical standards and behave ethically in relation to the outsourcing of operations
  2. Contracts - competitive tendering and contracting for delivery of the designated services, contract for services is actively managed with reference to performance and service delivery standards, risks and rewards of outsourcing especially with regard to accountability, final evaluations are performed at the end of the contract term which should be used to assess future tenders or extension of contracts.
  3. Planning - ensure proper planning procedures are in place which will allow outsourcing opportunities to be identified, plan iterative steps in service implementation
  4. Service - ensure performance and service standards have been separately identified for different functional areas, ensure that responsibilities for decision making on whether to outsource or not is with team leaders of appropriate competencies & who are sufficiently independent of the functional areas affected, maintain standards of access, equity and privacy, contract management procedures are in place with responsibilities allocated to team members with the appropriate competencies and experience, reporting structures established.
  5. Measurement - key performance indicators have been developed from performance & delivery standards established, ensure the costs of the functional areas are known & have been properly benchmarked with other enterprises where appropriate, ensure clear and measurable objectives have been developed, regular monitoring of performance indicators occurs and recommendations made for improvement where targets are not being achieved.
  6. Financial - detailed cost/benefit analysis is prepared before a final decision is made to outsource, consider of existing fixed assets if any held by the enterprise (sell or lease), termination and transition costs, future contract management costs, costs are monitored against agreed contract rates.
  7. Proposals - requests for proposals have sufficient technical detail as required by those tendering with regard to expenses, scope, guidelines to be adhered to, etc, proposal review committee established and is sufficiently competent and independent, term of the contract considered, evaluation criteria established and use made of weighting calculations, documentation of the final decision


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.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b