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 »
Webcast: In the Google Apps Cloud: How to Achieve Your Business Objectives
Dec 3rd, '09, 1 - 2 pm US/Eastern (GMT-5)
Join Council member Brent Hoag, Director, Global IT, at JohnsonDiversey, as he discusses the adoption of Google Apps which has helped meet four corporate goals; sustainability, simplification, increased employee productivity and global collaboration.
Webcast: Collaboration Initiatives: Benchmarks & Best Practices
Dec 15th, '09, 4 - 5 pm US/Eastern (GMT-5)
Join Council members Ruth Thorpe, VP & CIO at the U.S. Pharmaceutical Operations of Sanofi-Aventis, and Gary Kuyper, CIO at Bethany Christian Services, as they speak about their collaboration initiatives and experiences in how and why they chose the social networking and collaboration tools they are using and their business goals for collaboration, and facing culture change challenges.
Data Overview: Collaboration Initiatives Field Guide: Benchmarks & Best Practices
This appendix to the Council Field Guide provides an analysis which discusses benchmarks for collaboration IT implementation costs, adoption rates and payoffs. The overview identifies top IT and business goals and satisfaction rates for collaboration initiatives as well as best practices and lessons learned for implementing collaboration IT.
Learn more about the CIO Executive Council »December 15, 2004 — CIO —
As a leading entertainment retailer with more than 800 stores, we're always looking for a competitive edge. And in the fall of 2000, we found one. Working with an outside software developer, we created our own "Listening-Viewing" system that lets customers see and hear clips from products in our stores just by scanning their bar codes.
Like many companies, we arranged to have the source code from the project put in escrow (in this case, with Iron Mountain) as a hedge against our vendor going out of business or failing to support a product we relied on. But our reason for pulling the code out of escrow was rather unique: We removed it not because we needed it, but because we acquired it; once you own the code, you don't need escrow anymore.
What happened was that our vendor was trying to market the system to our competitors. After the ensuing lawsuit (in which TWE prevailed), we took over the software company and the source code.
If you look at our investment in the system, the cost of putting the code in escrow was insignificant. I would definitely do it again.
As told to Christopher Lindquist