Previous Next

Articles

July 19, 2007

by Elizabeth M. Ferrarini

 

Rampant growth definitely describes Wipro Limited, the largest IT services firm outside of the United States. Based in Bangalore, India, Wipro has grown from 5,000 employees in 2000 to more than today's 65,000 employees, located in 22 countries around the world. Wipro services global companies in the areas of outsourcing, software application development and maintenance, research and development, and systems integration.

 

No one feels Wipro's 30 percent growth as much as Laksman Badiga, chief information officer. His IT group oversees the network infrastructure, software development and delivery, security and compliance, and governance to support a workforce that is exclusively comprised of IT professionals. With a background in driving large areas of customer systems, Badiga has the right background and proven experience at Wipro to head up the IT organization. He manages services teams with more than 3,000 employees who delivered solutions to multiple customers across the globe. He also has been involved in Wipro's human resources area, in which he was responsible for recruiting more than 20,000 people in three years.

 

Enterpriseleadership.org recently talked with Laksman Badiga about meeting the IT needs of a business with a dynamic growth rate.

 

EL: What are the biggest IT challenges you face, besides handling  growth?

 

LB: We need to keep on top of how to make processes consistent and maintain consistent delivery for a large system implementation. We need to balance the long-term approach of IT planning with managing the day-to-day tasks. We also serve as a "living laboratory" before we deploy any products or processes for customers. They like knowing that we've put things through their paces and have corrected any problems.

 

EL: What's your strategy for designing systems to support expected  growth?

 

LB: Our strategy has been to look ahead three, to five years, which is hard to do in our business. However, we've managed to do it. In 2000, we made a fundamental change in our system design. At the time, we had 5,000 employees. We said we should build systems and processes that would get us through 2005, with about 50,000 employees. In 2006, we started the process over again, but this time, we're looking at systems that would enable us to grow 10 times over during the next five years. By then, we should be at more than 200,000 people.

 

EL: How do you manage projects with so many people?

 

LB: We're very process oriented. We've built a system that enables all of our employees to follow the same process for project management. Because we are adding 15,000 new people a year, we had to bring in consistent processes and consistent delivery to our internal customers. We needed to have a systems-driven approach rather than a people-driven approach. This system encompasses the quality processes that enable us to drive our entire software development systems.

 

EL: Can you describe your governance model?

 

LB: We're concerned about several things -- how well we are aligning with the business, and how well we are demonstrating the value we are creating.

 

We've created a strong business ownership model for several years. At the lowest level, we have an owner for every function that goes on in the business. These people are responsible for propagating internally and understanding the business requirements. This group meets weekly with IT to make sure we're going in the right direction, both strategically and tactically. We also have a monthly, and quarterly review to make sure the business unit managers know what they are getting. Every six months, we look at the strategic direction of where the business is going, but we don't bring IT into this process.

 

EL:  How do you handle security, both internally and externally?

 

LB: Because we're connected to most of our customers, we make sure that we don't provide any crossover access to other customers. In fact, we try to segregate at our firewall each of the customers. We provide a way for those working on that customer account to get only to that customer. All of our offices are seamlessly connected to the network. In some cases, when we operate from our network in India, we have to go through our US network to come back into our network in India. We've also integrated many of our customers' security policies with our own.

 

We use a variety of Symantec products to run checks consistently on the flow of information inside and outside our company. About 90 percent of the email we get consists of spam, and we block all spam at the entry point. So, we allow about 10 percent of email to get through. We also have created an information audit group to make sure we stay current with our security practices. We also allow customer audits to take place, and they enable us to learn their best practices for security and to learn ours.

 

EL: How do you handle the influx of resumes you get each year?

 

LB: Six years ago, we created a recruitment system called Synergy, which ties into a people-allocation system. Every new project has its people requirements. These requirements are passed to our people-allocation system, which runs off our SAP HR system. The people-allocation system looks at the skill sets of our current employees and, in some cases, it flags those employees whose skills need to be updated with more training. If the people-allocation system can't find the appropriate internal employee matches, then it passes the project requirements to Synergy. Synergy, in turn, searches the resume databases for those who meet the project requirements, and then selects those resumes for the HR recruiter assigned to the project. The recruiter can automatically scan those resumes.

 

Anyone can place his or her resume in Synergy by entering it online at the Wipro Web site. The database has about 200,000 active resumes out of a total of about one million.

 

EL: What new technologies are you considering?

 

LB: We’re using service-oriented architecture (SOA) as a way to define our technology and to tie the processes together with that technology. We're also using a business-process-management rule engine to define how we can create unified systems. Our goal is to create systems that can be easily adapted to customers' needs. When it comes to SOA, we're debating between going with IBM or Oracle; we might wind up going in both directions.

 

EL: What are some of your best processes for IT?

 

LB: Our entire IT department uses all of the service delivery aspects of the IT Infrastructure Library (ITIL). We also help our customers to carry out ITIL internally. We also use Lean and Six Sigma. We're one of the first companies to apply Six Sigma and the Lean production model to software development and delivery, starting in 2002. Our goal is to use Lean to improve our software processes.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
393 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

The name "Ryder" means one thing to a lot of consumers and business owners -- it's the company you call when you want to lease or to rent a truck. However, that's just one part of Ryder System, Inc.'s business. Based in Miami, Florida, and with yearly revenues exceeding $5 billion, this global organization ranks as the leader in providing outsource services for supply chain management. For example, Visteon, a 1997 spin-off from Ford Motor Company, outsourced the logistics of its freight transportation system to Ryder, which includes everything from international oceans to airfreight.

 

IT has definitely helped Ryder distinguish its supply chain service, as well as fleet operations, from its competitors. This situation might run counter to some of the themes in Nicholas G. Carr's Harvard Business Review article (May 2003), "IT Doesn’t Matter." The article caught the attention of a lot of major IT executives, especially Robert E. Sanchez, CIO, of Ryder System.

 

Sanchez has kindly taken the time to answer some questions about how he runs his IT organization, what cost-cutting initiatives he's taken over the years, and, of course, what he has to say about the B-School article. Sanchez, who received a Master's in Business Administration from The Wharton School at The University of Pennsylvania, held several senior operational positions at Ryder, including president of the fleet management solutions area, before he was promoted to CIO.

 

EL: Can you describe the IT infrastructure that supports your supply chain  or transportation outsourcing business?

 

Our supply chain business unit has a series of logistical systems we have integrated with some homegrown software. That system can manage anything in the supply chain both inbound and outbound, including transportation, distribution centers, and interfaces with suppliers. Our platforms consist of UNIX, Windows, and AS400s.

 

EL: What cost-cutting, or improvement initiatives have you spearheaded  over the years?

 

RS: We outsourced all of our applications development and management to Accenture. In 1997, we decided to bring that piece in-house.The cost savings were significant. In 1995, we also designed an asset management system to improve the company's North American fleet of 150,000 truck rentals and truck leasing business unit. In addition to owning these vehicles, we have about 700 shops scattered across the country that maintain these vehicles. This system enabled us to have more accurate information about the status of these vehicles. As a result, we've made better use of our fleet across the country. The system was built on a client server called PowerBuilder. The data resides in an IBM DB2 database.

 

EL: What's the business model you have for IT?

 

RS: Our internal IT organization operates as a shared service with about 250 employees. We operate with a combination of cost allocation and also direct costs in some areas going to the business units. We also outsource the management of our infrastructure to IBM Global Services. Some IBM employees reside at our facility.

 

EL: How do you work with your business units?

 

RS: Having run one of the business units, I know what it's like to be sitting across from IT folks. I'm also a member of the company's leadership team, which consists of the nine top leaders. We make a lot of the strategic decisions for the company.

 

We also have a pretty structured IT steering committee and IT strategy process we go through. The process enables systems administrators to identify, document, and gain support for projects we need to work on. There is also a strategy team which works with each of the business units. Each team consists of a director level individual who helps prioritize the identified projects. Once a year, the strategy team meets with the leadership committee to decide which projects, based on the allocated budget, will be carried out in each business unit.

 

EL: Do you use any kind of best practices such as Six Sigma or  ITIL?

 

RS: During the past three years, we've spent a lot of time developing a process called ACE, or Analyze, Chart, and Execute. The idea of it is to develop standard processes across the company, not just for IT, mainly for our supply chain business. ACE entails documenting all the different processes we use in the supply chain.

 

EL: How do you measure your success?

 

RS: We tie our success to the success of the business units.We don't look at, "did we get our project done on time?" Instead, we consider how well that project translated into value for the organization.

 

EL: Did you build up the infrastructure during the dot.com era, and did  you have to deal with the aftershock of your purchases?

 

RS: Like many companies, we created the rate of spend by purchasing a lot of hardware and software during the dot.com period. We felt a lot of pressure not to fall behind. A lot of the software we bought didn’t turn out to be very useful. Today, we're really focused on the key technologies that add value and that work. For the supply chain, we selected a standard transportation management packaged and integrated into our homegrown system.

 

EL: What projects are you working on that are really important for the  next year or so?

 

RS: We're continuing to enhance our supply chain in terms of the in-house proprietary tools. We're working on fleet reporting and analysis tools for our truck leasing and maintenance side. We want to allow our shops to view their fleet information online and provide our technicians with tools that can make them more productive.

 

EL: Did you read the Harvard Business Review article?

 

RS: Yes. However, I didn't agree with everything he [Nick Carr] says. First of all, he limits his definition of IT infrastructure to servers, LANs, WANs, and some components of ERP, such as general ledger. Based on this definition, I would agree with his comment that this type of an IT structure would not help an organization strategically differentiate itself from the competition.

 

The author refers to a lot of proprietary technology as being outside the IT domain. I don't agree with this. For example, the systems we have to manage our supply chain and fleet business, according to the author, are not part of IT. By developing these systems, we can continue to gain a competitive edge.

 

Our scenario is similar to FedEx. Where would it be without its tracking systems? That technology enabled FedEx to grow and distinguish itself from the competition. The supply side of our business is really about selling IT. The supply chain is really interesting because we mostly sell IT. If you come to us and want to outsource all of the components of your supply chain, we'll bring you the people, the process, and the technology. Many of our customers have tried to handle their supply chains, but failed.

 

EL: What are you looking for in your manpower requirements?

 

RS: We're considering technical expertise, expertise in the Web development area. We also have a need for individuals who have combined their technical skills with a business background, perhaps an MBA.

 

EL: Your leadership team decides on the projects IT will carry out. How do you handle the day-to-day management of these projects?

 

RS: My group has directors that are aligned with each business unit. These directors, in turn, have program managers who carry out these projects. The program managers report to the IT organization, but they sit with the business unit. The co-locating arrangement, which began in early 2003, provides us the best of both worlds. On one hand, we decentralize IT by enabling individuals to sit close to the groups they support. On the other hand, everyone in IT works under the same IT umbrella. No one has a dotted line to a business unit.

 

We also have programs managers who oversee that IBM Global Services meets its  service level agreements.

 

EL: Has you role changed since you became CIO?

 

RS: We're focusing more intensely on the value of IT and making sure that the money being invested in technology provides the appropriate return on the appropriate value. These things have become a big part of what the CIO needs to be able to provide. He or she needs to know when to veto decisions if the IT value doesn't translate to business value. I say "no" to technology daily. For example, I said no to installing an ERP system for general ledger and finance. The cost was out of line for the organization.

 

EL: Your leadership team decides on the projects IT will carry out. How do you handle the day-to-day management of these projects?

 

RS: The supply side of our business is really about selling IT.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer  based outside of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
454 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Robert Mitchell jumped into "fire-chief mode" three weeks after he was promoted from senior director of strategic business analysis and strategic business implementation to CIO and vice president of operations at GTSI in Chantilly, Virginia. The go-live deployment of a $10 million PeopleSoft supply chain system, integrated into the company's current PeopleSoft HR system, disrupted operations at GTSI, a $1 billion provider of IT infrastructure solutions to government agencies. Because the first three months of the troubled deployment kept GTSI from delivering products and services to customers, the revenues for the publicly held company were jeopardized. Meanwhile, the company shelled out $1 million to fix the PeopleSoft problems.

 

Mitchell sat down with enterpriseleadership.org to discuss candidly how he perceives his leadership role, how he was able to get his arms about a negative situation, contributing  factors to what went wrong, and what he learned from the experience.

 

EL: You moved up from senior director of strategic business analysis into the role you have now. How did all of this prepare you for the CIO role?

 

RM: The CIO role is about being a business leader who adds value to the company, not about being an IT project manager. Looking at it from this perspective, my past job at GTSI and my previous positions were critical to my success as a CIO. They were about understanding the strategy, understanding the financials, and understanding the business process. They were almost always about having good relationships throughout the business and being able to know who to go to.

 

Most people associate PeopleSoft with human resources. We use PeopleSoft for all of our internal business operations, everything from human resources to our entire supply chain. Even our sales people use PeopleSoft to generate sales quotes.

 

EL: Several trade press articles talked about the major operational problems you had with a PeopleSoft supply chain deployment. What went wrong?

 

RM: As CIO, I inherited the PeopleSoft supply chain deployment, which had been run as an isolated IT project, not as process improvement for the company. IT was unsuccessful at getting the business involved in the deployment. It slowed everyone down and certain departments ground almost to a halt. The problems ranged from training in general, to this specific implementation. In addition, we brought in too many contractors. We should've hired employees to fill functions that required passing knowledge on to other employees. We didn't think through some of the required test plans and business acceptance issues associated with it.

 

The momentum to go live with the system by a certain date meant no turning back. I knew it was going to be very problematic when we went live. However, I also had a clear idea of how we were going to fix the problems, and how I was going to minimize them. If I hadn't jumped in and did some of the things I did on the business side, it would taken longer than 90 days to fix the problems.

 

EL: What did you do first?

 

RM: I had to engage the business in what was going on. They needed to understand that IT is basically a set of mechanics and a custodian of the system. They had to take ownership of the system and to learn how it works for them.

 

On my second day on the job, I got representatives from every department in the company to come to our board room, to sit down in front of the CEO, and to give him an overview of what the system meant to them. We built a council of people, our version of a governance board, to make decisions about system changes.

 

We set up a war room where IT people would come and get answers immediately, and we could prioritize and enter change tickets right away. We really made sure we had a clean process for addressing the most critical issues first.

 

EL: Was this the most challenging IT initiative of your career?

 

RM: Absolutely. There was an interesting twist to it. While it was challenging on one level, I found it easy to resolve because I knew what to do. Think about it for a minute. If the executive team thinks they need to make big changes to gain efficiencies, you have tremendous amounts of resistance throughout the company. On the other hand, if a badly designed system doesn't allow people to do their job, then everyone supports changing the system.

 

Creating a forum of people who were willing to take responsibility for their  system made the situation easier to manage.

 

EL: What other things did you learn?

 

RM: You have to deal with many aspects of change management. Specifically, you have to work through a variety of communications levels -- everything from executive, down to user community -- at the same time. You have to be very clear about who own the business process and who owns the IT automation process. Many people like to start with, "What does this system do for me?" If you don't change that attitude from the start, you're going to run into problems.

 

EL: As result of this experience, what formal IT best practices have you put in place, and how have you improved alignment with the business?

 

RM: We have a well documented, disciplined software lifecycle process. As a publicly held company, we have processes compliant with Sarbanes-Oxley. We've used many different sources to document, and to develop, these very processes.

 

As for alignment, we've created a synergistic environment in which the skillsets overlap between business analysts and IT functional analysts. For example, in IT, I have functional analysts with extensive PeopleSoft expertise who understand functions such as purchasing. Likewise, I have people indirectly reporting to me who manage the process and who also report to the functional department head. These people work hand-in-hand with their IT counterparts to make sure the proper implementation and requirements get done.

 

EL: What was your relationship like with PeopleSoft during your troubled  deployment?

 

RM: We didn't have a good relationship with PeopleSoft at that time. Both parties were at fault. Because it was trying to fend off acquisition attempts from Oracle, PeopleSoft didn't want to have negative press about a bad deployment. I made sure we kept focused on solving the problem rather than complaining to the trade press. This strategy helped to improve our relationship and gain access to some good people within PeopleSoft.

 

EL: Now that PeopleSoft is part of Oracle, what is your relationship like  with Oracle?

 

RM: Large companies, such as PeopleSoft, don't do a good job of being held accountable for what happens. You have to find a method to protect your interests. I started building relationships and getting conduits to certain Oracle vice presidents who can smooth out any problems. In turn, we've provided Oracle with architects who served on a leadership committee to define the future of PeopleSoft.

 

EL: Why did you eventually go public with the trouble PeopleSoft  deployment?

 

RM: We were approached by a reporter who heard about the situation. Because we had just come through the toughest part of the deployment, we thought it would be a good chance to talk about how we got our hands around the problem. After all, we took a beating on this. Out customers had experienced negative delivery ramification. We also had to satisfy our shareholders.

 

EL: Undoubtedly, you've reflected on this deployment. What conclusions  have you come to?

 

RM: Because I took over the deployment a few weeks before in went live, I had no trouble taking the high road and not pointing fingers at any one. If I had been spearheading the project right along, then everyone would have been pointing fingers at me.

 

Our president believes in being forthright. From the start, he acknowledged that we were having a problem with the deployment and talked openly about it. I operate the same way. I've pulled all of the skeletons out of the closet so they can be fixed. That's why it's important to leverage all the relationship you have.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
394 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Ben Salzmann is proof that a CIO can have a career as a C-level executive. After eight years as a CIO at Acuity, a property and casualty insurer that operates in 15 states, Salzmann was promoted to CEO. His leadership has brought a plethora of outstanding achievements to Acuity, which manages $1.8 billion in assets and writes $800 million in premiums. For three straight years in a row, the company has made the Great Place to Work Institute's list of the top mid-size companies to work for, and InformationWeek magazine's list of the top 500 most innovative users of IT in the U.S. That's not all: Acuity has received about 32 technology awards from ACORD, an insurance industry association. AARP also has named Acuity one of the best places for people over 50 to work.

 

Enterpriseleadership.org sat down with Salzmann to get his view of what it takes to prepare for the CEO spot, how he has created a great place to work, and how he has made smart decisions about using leading-edge technology. Here's what he had to say.

 

EL: As a former CIO, what helped you the most to take over the helm  at Acuity?

 

BS: As a CIO and a company officer, you see and interact with just about every department. You have a chance to develop a broad perspective about the business. However, you need to have the business inclination and an interest in becoming a CEO.

 

Some CIOs say "no" every time managers suggest a new way of doing something. From day one, the CIO has to listen to managers, to come up with  approaches that work, and then to provide them as plausible solutions. The CIO has to continue to find ways to make things work better.

 

A CIO who has come up the IT ranks has both a profession and an occupation. You're profession is as a technologist, be it systems or applications. The organization you work for determines your occupation within a certain industry. To climb the corporate ladder, you need to make a commitment to the organization, and to master both the organization's industry and business.

 

EL: If you're going to move up to become a CEO, you can't have a lot of adversaries. How does the CIO transition to being more of a colleague or business manager?

 

BS: First, the CIO needs to get him-, or herself, invited to important business meetings. For example, every time our underwriting field force comes to our headquarters, we make sure the CIO is present. He's viewed as part of the organization and can speak with underwriters during breaks and at lunch. If a CIO wants to earn recognition and get a sense  of ownership, he or she needs to demonstrate knowledge about what's going on in the business unit. Managers need to see this.

 

Also, CIOs should sit in on financial department meetings to hear everything that is coming. It gives them more ammunition for developing strategies about how to get things done.

 

EL: What is the biggest mistake some CIOs make during their  careers?

 

BS: Some of them take on massive mountains to climb, not realizing how long it takes to get to the top. A mountain climber goes up the mountain one step at a time. So, if you're constantly under a tremendous number of project deadlines, perhaps that's because your projects were poorly designed to begin with. Even if you have a large project, you're better off taking a baby-step approach and having a constant stream of deliverables you can provide on time and on budget. This approach might prolong the project a little; on the other hand, the IT team learns as they install smaller pieces.

 

EL: Does it matter to whom a CIO reports?

 

BS: It certainly does. I hope all of my competitors have their CIOs report to someone who isn't a company officer. This is a good way to hamstring the entire IT department. The CIO should report to the CEO and should be considered a company officer.

 

EL: How do you feel about outsourcing IT?

 

BS: Likewise, I hope all of my competitors outsource a major part of their IT organization. Our technologists built our claims system, our underwriting system, and our policy processing system. We wouldn't want to outsource a commercial underwriter. Yet, some insurance companies will turn around and outsource the development of their major systems. How many outsourcing firms really know the in's and out's of all phases of insurance? When you outsource IT, you pay them a small fortune to develop a moderate knowledge of your business, to use this knowledge to build a mediocre system, and then to move on to the next project!

 

EL: Should the CIO role be designed as a temporary, rotational  role?

 

BS: No. That type of model is an extreme belittlement of the  technology deployed in the organization. It's like having a  CIO-de-jour. Again, not employing this type of model helps my organization be more competitive. Good CIOs needs to have a technology background and business acumen. Their jobs aren't to explain the difference between a mainframe system and a network-based system, but to look at the organization and know how it fits into an enterprise technology model.

 

EL: For three years in a row, your company has been named as a great place to work. What are doing to make it such a great place?

 

BS: You have to first meet employees' basic needs; next, to listen to and communicate with your employees; and then, to provide them with a great working environment.

 

For example, since 2001, we haven't increased the health insurance premiums our employees pay, but we've improved their health insurance benefits each year. We contribute eight percent to their 401K plans, even if they don't put in a dime. We give them an additional 401K bonus so they will hit 10 percent of their annual income, even if they don't put in a dime.

 

We have an awesome suggestion committee, which goes over each suggestion submitted by employees. They can get a bonus for a suggestion. And, we hold town hall meetings where we bring in all the employees so they can get updates from the company officers.

 

Then we have our fun side. We've done everything from mechanical bull contests to chocolate fountains to Acuity's version of "American Idol." We hold our Christmas Party at a five-diamond establishment.

 

EL: You are one of the first companies in the insurance industry to  go paperless. Can you discuss the process?

 

BS: We started going paperless 16 years ago. We began with our personal lines, which insures houses and cars. As the file retention dates passed, we didn't have any paper to file. We worked with regulators and governmental bodies on how they can audit a paperless insurance company. Next, we went paperless in our commercial business lines, and in our claims systems. The advantages have been outstanding.

 

Wherever employees are in the world, they can use the Internet to not only check their email, but to go right into the personal lines system, the  commercial lines system, or claims system. They can read what's going on for a specific account, and then turn things around. For example, we can have 40 people at a time looking at the same system in 40 different locations. They all can be deciding on how to handle a multimillion-dollar business account.

 

By harnessing this technology, things happen fast, and we have no linear flow. Our work management system orchestrates all of the various reports we need to give to an underwriter. This way, the underwriter sees the entire picture at once and can make a better decision than if he or she were seeing bits and pieces over a few weeks.

 

EL: What's the biggest mistake insurance companies make when they go  paperless?

 

BS: Installing a workflow system at the same time as an imaging system can spell trouble for an organization. You end up imaging too many documents and making paper into intangible paper. For example, your computer can't calculate rates for an image of an insurance application: you need stored data. Many insurance companies have carried out their work management system in parallel with their imaging system.

 

In contrast, we did our work management system with our data collection systems and then brought in our expert system. We needed to put in the expert system before we put in our imaging system. If you put in the imaging system first, you're data-starving your expert system because your expert system can't read intangible paper or images.

 

EL: Because of your paperless environment, how have you improved the  quality of your transactions?

 

BS: We have world-class service levels based on rapid processing and very high quality ratios. We track every transaction for an entire year, and we announced that we have a 99.7 percent accuracy rate in a given transaction.

 

EL: You've won dozens of technology awards from ACORD --  can you  explain the significance of these awards?

 

BS: We've received more ACORD awards than any other insurance company in the country. ACORD is an insurance industry association vital to accelerating and advancing technology and setting standards for it. ACORD promotes the interface between insurance agents and insurance companies by standardizing  data and by promoting technology. The awards are to recognize technology leaders our industry.

 

At the ACORD LOMA Insurance Systems Forum in May 2006, we received seven national technology awards, including the Business Integration Enable award, the Early Adopter award, and the Greatest Number of Transaction Implementations award. For example, we received an ACCORD award for the way we download policy changes to our agencies' computer system, which automatically trigger the databases to update.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
570 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

CIOs in corporate America worry about how IT is going to make their organizations more competitive. In healthcare, demographics, not IT, help hospitals to, for example, expand into new markets. To this end, healthcare CIOs view IT as a critical underpinning for process improvements that can help patient care and safety.

 

Dennis L'Heureux has firsthand experience finding the right technology to fit a hospital's strategic initiatives, as well as its tight budgets. He wears two hats as both CIO and vice president of planning hat at Rockford Health System, a 400-bed tertiary healthcare provider and the second largest specialty health care group in Illinois. His exemplary technology leadership has earned him a place on Computerworld's list of Premier 100 IT leaders.

 

Enterpriseleadership recently sat down with L'Heureux to talk about some of the ways technology has improved some key functions and to discuss how he's dealt with an influx of new C-level peers.

 

EL: How do you deal with the challenges of spending on technology while  keeping the cost of healthcare down?

 

DL: I can't draw a direct line between those. There's always an incentive to keep the cost of healthcare down. We struggle with this all the time because of the new government mandate for more price transparency.

 

Our business is very complicated. For example, each insurance company we do business with might reimburse us differently for the same procedure. If someone wants to pay cash, the price will be different, to. This entire situation continues to vector downward as the government and insurance companies want to pay less. Meanwhile, the cash consumer wants to pay less.

 

We have constant pressure to provide the same types of services with better  quality and safety for less and less money.

 

EL: Can you talk about situations where IT has helped the hospital saved  money?

 

DL: A basic assumption in healthcare is that the use of IT over the long run will reduce costs. This is very hard to quantify across the board; however, I can cite some tangible cost savings. Because we've put in electronic medical records system, we've saved on file room clerks and don't have film expenses anymore.

 

And, I can say that technology is helping a radiologist come up with a diagnosis in less time than he or she did before, for example.

 

EL: What process improvements have you made at Rockford Health  System?

 

DL: We've eliminated the need to go looking through old film files trying to compare a patient's X-rays taken today with those taken three weeks ago.

 

We also centralized the scheduling of outpatient routines. Previously, physicians had to call a specific lab to make an appointment for an outpatient. The new system now allows physicians to call one number for all of these procedures. It also allows physicians to identify where any combination of those tests can be done for the patient. That's a pretty significant process improvement.

 

Finally, each year, our employees have to select their medical coverage for the following year. At one time, we mailed each employee a thick paper packet. Now, we have all of the information online.

 

EL: How automated are your medical records?

 

DL: We've automated a significant part of the records, including histories, physicals, all lab tests, all EKGs, all radiology tests, all surgical notes, all mammograms, and all cardiology tests. We haven't automated our nursing notes. That a big project.

 

EL: What are some of the best practices you have put in place for  IT?

 

DL: For the past 12 years, we've had a decent governance structure for how we use IT and the investments we make in it. Our Information Management Services Advisory Council consists of representatives from the physicians practice, nursing, administration, finance, and IT. This is a key best practice.

 

We also see our technology resource center as a best practice. If we'd had to outsource it, we wouldn't have pulled off the service levels that we now provide. We are proud of that.

 

EL: In some healthcare organizations, the CIO reports to the CFO. How do  you feel about that?

 

DL: The data suggests that if you report to a CFO, you have less flexibility and less investment in IT than if you reported to a CEO. You have the challenge of making sure you invest in the right things.

 

I'm fortunate to report to the CEO. In fact, I have survived five CFOs.

 

EL: How do you deal with the changing of the guard in C-level peer  positions?

 

DL: A new CFO may come in and ask questions -- why don't you do this and why didn't you do that? The answers can be simple. However, a lot of times, solutions and decisions have been made along a very complicated set of criteria. It's difficult to explain all that.

 

You have to retell your story constantly, not recreate history. You need to get the new CFO to understand where you are today and why. I like to sit down with the new person and go through all of my governance structure. Then, I list out all of the inventory of things we have, and talk about the investments we have made and what I think is still deficient. This tactic has worked very well for me.

 

You need to build good relationships with your C-level peers. These relationships help you to have an amicable conversation about crucial topics. If you don't have these good relationships, you'll cross swords every time you meet to discuss an important topic.

 

EL: How do you align IT with the hospital's business objectives?

 

DL: Because I was promoted to senior vice president, I am also in charge of strategic planning. It's easy for me to connect those dots. When we created our strategic plan for our company, we had six drivers. My schematic charts shows IT as the foundation for each one of them; IT doesn't sit as the seventh driver. We view IT as a support function, not as a way to create new markets.

 

New markets in healthcare come about by things such as demographics, unemployment, and employment. As we try to capture the market share for good paying customers, we try to leverage IT.

 

EL: What's the most pressing priority you have right now as far as a  project goes?

 

DL: Right now I'm working on using technology to provide better patient safety between the pharmacy and the nursing departments, which order, confirm, and dispense medications. We've mislabeled it as a "bar coding project," but it has many more components and processes than just bar coding.

 

At the time, the vendor we purchased the product from didn't have RFID. We're still months ahead of this implementation, so we've delegated someone to look into RFID and to see if it makes sense for us. I wrote the contract for bar coding, but if RFID is the way to do, then I'll have to reopen the contract and say I'd prefer RFID.

 

Prototyping often leads to two separate processes. That can be dangerous. We want to play it save and to stick with standard processes.

 

EL: What professional organizations help you to network with other  CIOs?

 

DL: I participate actively with the College for Healthcare Information Management or CHIME. About three times each time, I check with my CHIME colleagues to see how they are doing things, and what issues they are having.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
472 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Dr. B. Joseph White has studied and practiced leadership for more than 30 years. Since January 2005, he has been president of the University of Illinois, an academic institution with 28,000 faculty members and staff, 70,000 students, 21 Nobel laureates, and an operating budget of $4 billion per year. Dr. White has also gotten to know notable leaders, including Steve Jobs, Madeleine Albright, and Archbishop Desmond Tutu. In his new book, The Nature of  Leadership: Reptiles, Mammals, and the Challenge of Becoming a Great  Leader, Dr. White shares what he has learned about the blend of capabilities it takes to lead successfully -- and the secret to truly great leadership.

 

The Nature of Leadership reveals the dichotomy at the core of every effective leader: being part reptile -- analytical, rational, and tough as nails -- and part mammal -- nurturing, participative, and warm as toast. The book also has a leadership pyramid that shows the traits of a great leadership at the summit, and the traits of the reptile and mammal next to each other.

 

Enterpriseleadership.org recently talked with Dr. White about his book and his views about how CIOs, especially, can become great leaders.

 

EL: How would you rate the leadership abilities of most CEOs of the  Fortune 1000 companies?

 

BJW: Today, executives are under a lot of pressure to achieve high performance; to deliver top-line growth and bottom-line growth; to provide strong returns on investment, and most importantly, to grow the share value of their companies. Such performance includes a combination of good leadership and good luck.

 

Unfortunately, CEOs often don't have a lot of time to turn weak performance around or to improve on good performance. Their abilities to do so are extremely varied. The average tenure of CEOs has gone down to less than six years. Many boards and owners figure that if the CEO hasn't achieved strong performance after a couple of years, he or she isn't going to do it. Some CEOs have 18 to 24 months to prove themselves. To this end, CEOs need to have great leadership abilities and the wind at their back, too.

 

EL: Most of the executives profiled on Enterpriseleadership.org represent technology leaders in large organizations. These people are usually chief information officers (CIOs). What would you recommend they focus on if they want to become CEO of a company?

 

BJW: Information executives who want to become CEOs should focus on three areas: make sure their financial ability is first rate, make sure their people skills are excellent, and make sure they know how to develop a track record of making substantial consequential change.

 

The ability to change sits at the top my great leadership pyramid. A leader's success today depends on his or her ability to make consequential change, such as turning around an under-performing company. For CIOs, this type of change usually means leading the migration from one major system to another without missing a beat. For CEOs, it means doing things to foster internal growth, containing costs, and making smart acquisitions. All of these things will help to grow the market value of the company.

 

Most CIOs have strong change-making leadership skills. They've acquired years of experience taking their organization through generation after generation of new technology.

 

On the other hand, CIOs need to develop their financial skills. Often, CIOs function as budget managers, lacking first-hand experience dealing with the corporate profit-and-loss, and cash flow. And, some CIOs who are very good technically might also need to hone their people skills.

 

EL: In your book, you define five qualities you define for great leaders, and you mention having a "helicopter view" of the past, future, and current events. How can executives, especially CIOs, develop this helicopter view so they don't get a cloudy picture?

 

BJW: They need to learn all of the business's dimensions. CIOs who want to become CEOs need to be able to go from being professional heads of an organization to being general managers. GMs have a broad perspective, or, the helicopter view, which is knowledge of the business's past, its present, its future, and its functions, and how they fit. This view is also called strategic thinking. This is what boards look for.

 

EL: How do you feel about rotating CIOs through the business so they  can develop a helicopter view?

 

BJW: I first saw that being done 30 years ago with big Japanese companies. Executives in Japanese companies often rotate through operational areas such as finance, manufacturing. This is how you learn about the business and all of its dimensions. CIOs would get a lot from the experience. For example, going into the corporate planning function would help a CIO become more of a strategic planner.

 

CIOs, as well as CEOs, should never stop learning by reading good business  books. Tom Friedman, the author of The World is Flat, has become very  popular with executives because the book helps them to develop a helicopter view  of things.

 

EL: Some companies have programs to encourage innovation. How should  these programs be structured?

 

BJW: Because leaders are responsible for making change successfully, they need to have a great interest in new ideas. This applies to everyone from CEOs down to managers of small workgroups. Innovation begins with the process of turning these ideas into reality.

 

In my book, I share some of my experiences leading innovation efforts. I developed a concept called "the presumption of yes." lf someone comes forward with a new idea, there is the presumption of yes that we will carry it out.

 

Leaders need to have creative ways to encourage employees to come forward with good ideas about doing things better. Often, employees hear everything from "it's too expensive," to "we've tried that before and it didn't work." "The presumption of yes" helps a leader promote the value of innovation in an organization.

 

EL: Your "great leadership pyramid" ranks risk-taking at the top. What happens when a leader takes a risk that doesn't benefit the organization?

 

BJW: Every leader needs to understand that risk-taking involves a batting average. No one always bats 1000 -- not in baseball, and not in leadership. If you're batting 1000, you're probably not taking enough risk. If you're batting 250, you're probably taking too much risk, or you're not managing your risks very well. If what you try fails, there's nothing inherently wrong with that; you need to look at your batting average over time. A good leader should be batting about 650. In other words, one out of the three things you back, or attempt to back, ought to end up being successful.

 

EL: Some great leaders, like Steve Jobs of Apple and Larry Ellison of Oracle, are known to be tough on their employees. Should you admire a great leader, but avoid working for one?

 

BJW: You have to distinguish between great leaders and people whom you would personally select to work for. Keep in mind, there are a lot of paths to success in businesses. Some executives advocate that, you either  perform, or you're out of here. Some of us might not want to work in that kind of culture. It doesn't mean the organization won't be successful. Executives like Ellison and Jobs rate high at the top of the pyramid skills. They're very innovative, like to take risks, have the helicopter view, and sizzle with a lot of sparkle. They also attract the most talented people. They're also very good on the reptile side of the pyramid. However, they aren't very good on the mammal side of the pyramid, which explains why you might not want to work for them. Because I've spent some time consulting with Steve Jobs, I saw up close how he gets great people to work for him, even though he is rough on them: He makes them rich. It's the same with Ellison. A lot of us would opt to work for more nurturing leaders, but that's not the only way to be successful.

 

EL: Where does governance belong in a company?

 

BJW: The number one task of a board of directors -- the chief governance committee -- is to select a person to lead the organization. This person is either a great leader, or is someone who has the ability to become a great leader in a short period of time. If a governance committee does just that, things will go just fine. If they don't, they can do everything else, and the organization will not perform very well.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer  based outside of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
439 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

Actions