| Add You |
Hubs | Hubbers | Topics | Request |
| #1 in Business | Subscribe Email Print |
|
You are here: Home > Business > Management > The Key Reasons Why Cios Get Fired And What To Do About Them - Part 1 |
|
Add You - The Key Reasons Why Cios Get Fired And What To Do About Them - Part 1
Taking Charge Of Your Files umptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand.One of the first steps is to box up last years files. However, before you do that be sure to go through your files and clean them out. The files that can take up a lot of space during the year, can be easily tossed. For example, your correspondence file, newsletter files, chron files. You can also combine your completed client files for the year, both seller and tenant buyers. After you have gone through the paper file cabinet, be sure to do the same with your computer files. Years ago when computer memory was at a premium, people did not keep all the extraneous garbage on their computers, like people do today. Just like your paper files, move the files to disks or your zip drive if you need to, or just delete them. You don't need every letter you sent, every e-mail, or all the newsletters you've been meaning to read. Also go through your favorites and clean them out. Treat your computer like memory was at a pr You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 5 Medical Billing - Network Issues You're now CIO - welcome to the hot seat!Medical billing packages are extremely complex pieces of software. The reason for this, besides the number of things that the package itself has to do, is because of the number of people who usually work within the package itself.Medical billing agencies and companies are usually massive because they have to deal with a large number of providers and carriers. Because of this, most medical billing packages are created for networks so that more than one person can access the package at the same time. This is critical because all of the information stored by the package is time critical. To understand this, we'll present a brief example.John Doe is being billed for an oxygen concentrator. The patient file is already on the system so the medical biller pulls up the records and goes through the proper channels for billing the patient. An hour later, the patient calls and speaks to another biller. Turns out that The CIO is probably the hottest seat on the "C" suite in terms of pressure and demands and that gets reflected in terms of a short tenure in the job. As individuals, they are typically bright, intelligent, hard-working and committed - and yet when you visit the offices of their colleagues frequently they are demanding that their CIO needs to go and go soon. How long does a CIO last? In the bad old days around the turn of the millennium - in the times of the dot-com crazy years of explosion growth and sudden collapse the accepted wisdom (or should I say urban myth) a typical CIO could expect to last 18-24 months in the job. These days, they get a while longer at the helm some say around 3-4 years (Forrester poll) and others 4-5 years (Gartner poll). You've got to keep the lights on! The most obvious requirement for any CIO is to keep the core IT systems and basic infrastructure working. If they stop and the organisation ceases to function properly, then they are not going to stay around long. I guess in over 25 years of business experience, I've only seen these catastrophic failures happen 2 or 3 times and the CIO incumbent pay the price of failure. Business users and customers expect IT to work and by and large it does. I suspect expectations of reliability increase year-on-year and most CIOs are on top of this fundemental part of their game. Perhaps the big downside, is that the substantial time & efforts typical CIOs and their staffs spend "keeping the lights on" puts them under pressure in othe key strategic areas that can ultimately cost them their jobs. So why do senior executive colleagues want to fire their CIOs so much? I often reflect on a number of the CIOs I know well personally. I often struggle with the paradox that despite they are great people, dedicated to their jobs and achieve great things for their organisation with the frequent situation that many of their colleagues want to see them fired? How can such an uncomfortable situation arise? Perhaps at the heart of it is the relentless increase in the demand for IT to help a modern large-scale organisation function successfully with the constraints of time, resources and most of all money to fulfill these expectations. We all know that the units costs of technology is falling year-on-year, the problem is that the demand is increasing even faster. This means that left unchecked, the costs for IT would explode year-on-year - and if this happens every CIO knows that they will be out-the-door before the kickoff budget planning round has even finished. So every decent CIO attempts to control this ballooning budget overspend monster and it's here that is perhaps the root cause of the difficulties they experience. In the case of large organisations (particularly financial institutions) one endures a long drawn out and intensive budget setting process. At the end of which the overall budget for IT is determined and then the costs allocated (with different degrees of science depending on the organisation) to the individual business units and functions. The spending is based on a whole series of assumptions - which in practice turn out to be over optimistic. Business demand nearly always exceeds the assumptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand. You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 50 What to Do If...Help Your Cleaning Staff Know What to Do in Certain Situations 've got to keep the lights on!What to do if. . . You Find Money: If it's a few cents, put it on the nearest desk or table. If it's $5, $10 or more, put it in an envelope (if possible) with a note as to where it was found and leave it on the Receptionist desk. You Break Something: First clean it up, and then leave a note. ("I accidentally broke the _____ while dusting. Please call XYZ Company at 555-0123 so we can replace it,") . Then call your supervisor so they know what happened. If you own up to it right away, often-times people say "Oh, don't worry about it". Plus, they appreciate your honesty. You Get Locked Out: You set your keys down and get locked out of an office. Call your supervisor or someone with a key. Remember, ALWAYS keep the keys on you at all times - never set them down. You Find Something Personal Left Out: If you put it away, be sure to leave a The most obvious requirement for any CIO is to keep the core IT systems and basic infrastructure working. If they stop and the organisation ceases to function properly, then they are not going to stay around long. I guess in over 25 years of business experience, I've only seen these catastrophic failures happen 2 or 3 times and the CIO incumbent pay the price of failure. Business users and customers expect IT to work and by and large it does. I suspect expectations of reliability increase year-on-year and most CIOs are on top of this fundemental part of their game. Perhaps the big downside, is that the substantial time & efforts typical CIOs and their staffs spend "keeping the lights on" puts them under pressure in othe key strategic areas that can ultimately cost them their jobs. So why do senior executive colleagues want to fire their CIOs so much? I often reflect on a number of the CIOs I know well personally. I often struggle with the paradox that despite they are great people, dedicated to their jobs and achieve great things for their organisation with the frequent situation that many of their colleagues want to see them fired? How can such an uncomfortable situation arise? Perhaps at the heart of it is the relentless increase in the demand for IT to help a modern large-scale organisation function successfully with the constraints of time, resources and most of all money to fulfill these expectations. We all know that the units costs of technology is falling year-on-year, the problem is that the demand is increasing even faster. This means that left unchecked, the costs for IT would explode year-on-year - and if this happens every CIO knows that they will be out-the-door before the kickoff budget planning round has even finished. So every decent CIO attempts to control this ballooning budget overspend monster and it's here that is perhaps the root cause of the difficulties they experience. In the case of large organisations (particularly financial institutions) one endures a long drawn out and intensive budget setting process. At the end of which the overall budget for IT is determined and then the costs allocated (with different degrees of science depending on the organisation) to the individual business units and functions. The spending is based on a whole series of assumptions - which in practice turn out to be over optimistic. Business demand nearly always exceeds the assumptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand. You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 5 Banking - Inventory Collateral This segment will explain the essentials of how a bank evaluates the inventory that is offered as collateral for a business loan or an operating line of credit. As explained in the segment on equity, this is not supposed to be a text book course, but explains briefly what you will encounter in the real world of business finance.These comments are not for the retail business; they apply to wholesalers, importers and manufacturers.The amount of money the financial institution will be prepared to lend you will depend a great deal on the amount and ease of realization of the inventory collateral you can offer to cover the loan, in case there is a default in repayment.It is not just the amount of the collateral, but the quality of the collateral, and whether it would realize enough to repay the loan if there was a liquidation of the business.A typical example might be that your main collateral So why do senior executive colleagues want to fire their CIOs so much? I often reflect on a number of the CIOs I know well personally. I often struggle with the paradox that despite they are great people, dedicated to their jobs and achieve great things for their organisation with the frequent situation that many of their colleagues want to see them fired? How can such an uncomfortable situation arise? Perhaps at the heart of it is the relentless increase in the demand for IT to help a modern large-scale organisation function successfully with the constraints of time, resources and most of all money to fulfill these expectations. We all know that the units costs of technology is falling year-on-year, the problem is that the demand is increasing even faster. This means that left unchecked, the costs for IT would explode year-on-year - and if this happens every CIO knows that they will be out-the-door before the kickoff budget planning round has even finished. So every decent CIO attempts to control this ballooning budget overspend monster and it's here that is perhaps the root cause of the difficulties they experience. In the case of large organisations (particularly financial institutions) one endures a long drawn out and intensive budget setting process. At the end of which the overall budget for IT is determined and then the costs allocated (with different degrees of science depending on the organisation) to the individual business units and functions. The spending is based on a whole series of assumptions - which in practice turn out to be over optimistic. Business demand nearly always exceeds the assumptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand. You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 5 A Sane, Satisfying Working Life: How You Lost It And How To Get It Back for IT would explode year-on-year - and if this happens every CIO knows that they will be out-the-door before the kickoff budget planning round has even finished.Corporate ‘life’ is a nasty oxymoron.Jam-packed days, endless demands to do more with less, impossible goals, rally the troops, jump on a plane. Miss your kid’s birthday.You know these painful facts all too well. An existence? Yes. A path to a paycheck? Certainly. But, a life? A well-balanced, appropriately challenged life? No way.Is it any wonder that you are filled with dreams of escape? You’re not alone. Recent Conference Board surveys reveal that:• 40% of employees feel disconnected from their employers• Two-thirds of American workers do not feel motivated to drive their employers’ business goals• 25% of employees are just “showing up for a paycheck”These surveys validate the Gallup Employee Engagement Index Poll which finds that a majority, or 54% of workers are “not engaged” with the objectives of their organization. Even worse, 17% of employees are considered ac So every decent CIO attempts to control this ballooning budget overspend monster and it's here that is perhaps the root cause of the difficulties they experience. In the case of large organisations (particularly financial institutions) one endures a long drawn out and intensive budget setting process. At the end of which the overall budget for IT is determined and then the costs allocated (with different degrees of science depending on the organisation) to the individual business units and functions. The spending is based on a whole series of assumptions - which in practice turn out to be over optimistic. Business demand nearly always exceeds the assumptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand. You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 5 How To Write A Resume umptions in the budget (whether for infrastructure, desktop & communications or applications & projects - or all of them together) - the CIO is then sucked into a policing issue trying to enforce standardise solutions (to keep unit costs down), seek out and destroy skunkwork initiatives or suppress & defer and demand.To apply to any job, the candidate needs to write a resume. These are some tips on writing a solid, persuasive resume that will help the applicant get the position they’ve been dreaming of.The resume must be segregated into different sections to be easily understood by the company representative, in most instances Human Resources (HR) department personnel. There are many resume-builder sites available on the net. By searching and locating a proper description, the job applicant may model their resume on it, inserting their own qualifications. By deciding to design the resume in different sections, the job seeker makes it clear to the HR personnel that they know how to proceed with their career.First, the applicant must give details pertaining to their full identity, including address, phone number and email. Then the job seeker must give all the particulars about their education, place of study and grades achieve You can't keep the spending tide back Despite your best efforts in putting in place control systems to control spending, many CIOs ultimately fail to keep the overall IT costs under control. You might be able to keep those costs you have direct control over, but user departments find a way to fund the spending you try to suppress regardless. Eventually the CIO and Finance catch you out when they get around to aggregating all of the IT related spend going on in the organisation, that can be 50% to 100% higher than you think it is. You may have not been responsible, but you are judged to be accountable for this overspend :-( Business users hate the words NO & WAIT! All to frequently, the CIO and their teams are involved in saying no or never to business demands for more IT (from Blackberries to new CRM systems). Much of the demand can be simply status driven (I must have a Blackberry too as all the other senior managers have one). The CIO may try and put in prioritisation and approved processes in place - but to the business user these can seem to be bureaucratic roadblocks deliberately put in place to stop them getting what they want. Nobody loves you anymore :-( If you are not careful, as CIO you end up with a personal reputation as obstructive (insisting on standards), a conehead (asking colleagues to invest in major infrastructure investments they don't understand), ineffective (as new projects never get delivered fast enough) and pretty isolated. Setting aside the business & technology challenges, long tenured CIOs make a big effort to build their personal relationships with key colleagues outside of Technology. The service sucks! Sometimes the service just sucks. The root cause can be over aggressive negotiation and bidding of an outsourcing contract that forces the other party into dysfunctional behaviour in order to try and recoup their losses on the contract they signed with you. Sometimes it's down to an offshoring exercise (internal or external party) that doesn't work out to well. The cost savings turn out to be less than expected - but worst of all the delivered service is appalling. If poor service screws up the revenue numbers and increases customer churn for a key division of the company - then you are toast. The silver bullet doesn't work Many organizations end up signing up for a huge "Transformation Program" and these of course can take years (3-5 years to see through). You may of course have signed up a very convincing multi-billion partner organization to help you through this journey. At the outset, you can enjoy a lot of support from your CEO and the whole IT organization (and much of the business community too) can become heavily involved. The seasons come & go and slowly but surely the doubts begin to grow whether the Transformation program will ever be completed - or that the benefits so confidently predicted will ever be realized. I guess you should start to worry if you get to see the leaves falling from the trees a couple of times and the Transformation program is still running. The CFO and their team start to show ever closer interest in your budget spend and forecast - your outside partner tells you to have courage and keep going. The business senior executives start to jump ship and stop attending the key governance meetings, you know when your sponsor tells you that they feel someone else is better suited to take the helm that your time is up! So what do long tenured CIOs do differently to be successful? OK - if you want to learn the secrets of successful, respected CIOs and how they got to become one of the most respected members of their management teams. Then you can: - Ask one of them - they can be found ;-) - Read Part 2 of this article series<
HTTP = HTML link (for blogs, profiles,phorums):
Related Articles:Mobile Oil Change Vans and Packages Available How to Succeed as a Virtual Assistant Part 2
|