Offering regional and national programs, CIO (and CSO) events bring together some of the most respected names and thought leaders in information technology and security. Presented by CIOs and other senior level executives, these invitation-only programs offer timely topics and strong networking. Learn More »
June 17, 11:30 AM - 12:30 PM U.S./ET (GMT-4)
Larry Bonfante, CIO of the U.S. Tennis Association, will discuss the skills and approaches that your rising IT leaders must learn to be effective in an executive capacity.
How to Handle Your New CEO: Managing Turnover at the Top
June 18, 11:00 AM - 12:00 PM U.S./Eastern (GMT-4)
Turbulent times have increased turnover at the top. Find out what Council CIOs have done to "break in" new CEOs—build relationships, set expectations, educate on the role of IT.
Mid-Market CIO Panel: Tips and Techniques for Improving Vendor Relationships
July 15, 4:00 PM - 5:00 PM U.S./Eastern (GMT-4)
We'll highlight relationship priorities and best practices identified in a Council study, and we'll interact with a CIO panel on the approaches they've used to improve strategic vendor partnerships.
Executive Competencies Assessment Tool
Assess Your Business Leadership Skills with the Council's new benchmarking tool. Rate yourself in change leadership, strategy, customer focus and more.
Learn more about the CIO Executive Council »Apply today for a FREE subscription to CIO Magazine!
August 22, 2007 — CIO —
Most large IT shops have a discretionary budget in which to invest in high-risk projects with a potentially big but unpredictable payoff. But in small and mid-market companies, smaller budgets often make justifying the cost of a speculative project an insurmountable obstacle.
That's because the rules of project funding are the same, no matter what size your company is. To properly evaluate any project's feasibility, we must be able to compare the expected cost of the project against the expected value to the organization. With most IT projects, the future value of an investment is easy to predict by considering savings, efficiency gains or the reuse of existing resources. Simple forecasting methodology can then be used to calculate a potential return on investment (ROI) to determine a course of action. It's a tried-and-true method, and one the CFO understands. In a small organization, there's more to lose if you bet wrong.
I was faced with the task of justifying a business intelligence (BI) project for which the rewards were potentially high, but so were the risks. Traditional project planning and ROI measurements are ineffective in calculating the value of BI because calculating the potential value of unknown information is similar to a prospector digging for gold. We know there is something of value there; we have a rough idea what we're looking for, but how much of it, and how valuable it is, cannot be determined until after the investment is complete.
Therefore, although I'm not suggesting that BI tools are the junk bonds of IT investments, the rules of risk and reward that CFOs can relate to put these applications in that same high-risk category. And yet, I had to make the case for them anyway. I am the technical lead for a large medical practice in the Midwest (I can not disclose its name due to restrictions on non-medical press coverage). I oversee technology used in 17 locations by a staff of more than 380 (including 45 physicians). One of our key management challenges has been to standardize enough of the practice to gain the same efficiencies achieved by a larger organization.
Solving this challenge has so far eluded us, but it's the only way for us to improve our fiscal position. The bulk of our services are paid for by insurers or the federal government, through Medicare and Medicaid. Unlike most practices our size, we are not affiliated with a hospital or university. To grow our patient base, we rely on a network of physicians who refer their patients to us. And so, we must do more with less. Much of this year's strategic work plan relies on performance measurement. But the practice has limited tools to obtain meaningful metrics. We needed BI to get a better handle on our productivity. Here's how we got the project funded: We snuck it in.