Previous Next

Articles

October 2008

MarkDLutchen.jpg

 

Mark D. Lutchen knows what it takes to unleash the full potential of IT so that organizations can derive the maximum benefit from it. As the former global CIO at PricewaterhouseCoopers (PwC), one of the largest professional business services firms in the world, Lutchen oversaw an IT organization of more than 2,500 professionals serving more than 120,000 employees in 144 countries. Today, Lutchen is a senior practices partner in PwC's IT Effectiveness Practice, where he helps clients get more value from their IT investments and their IT strategies. In 2004, he wrote Managing IT as a Business - A Survival Guide for CEO's. Many graduate school professors have used his book in MBA courses on IT management. Lutchen says that the basics IT management principles in his book haven't changed much since it was published.

 

Enterpriseleadership.org recently spoke with Lutchen, for the second time, to discuss what disciplines CIOs must put in place if they want to run IT like a successful company. This is what he had to say:

EL: Why did you write the book in the first place?

 

ML: I wrote the book because the IT clients I worked with seemed to have similar issues. It became clear that technology wasn't the problem. Instead, it was about managing IT and being disciplined about doing it. If you look at the failures that have occurred, you start to see some of the patterns. People have not instilled within IT the disciplines we use in other parts of the business. If you're a CIO running a billion dollar IT organization or even a half billion IT organization, that's the equivalent of running a business. To this end, you need all of the kinds of things in place for running a business. The book was to put this idea into context.

 

EL: Why did you decide to title the book as A Survival Guide for CEOs and not CIOs?

 

ML: The book is really for the C-level executives. I wrote it from a business orientation. If you look at the role of the CIO five years to 10 years from now, you'll find the CIO of a major corporation acting more like a CEO of a business around IT.

 

Many of the IT books that have come out in the past two years have redefined the CIOs role. That's what I did, except I redefined the CIO role as that of a CEO. I also wanted other people in the business, such as the CFO and the COO, to understand what happens in an IT organization from both the IT and the business side.

 

EL: Since your book came out, have CIOs become better at developing IT strategies that meld with the overall corporate strategy, as well as the needs of the business units? If not, how can they be doing a better job.

 

ML: Some of them have been trying to do that. Upfront in the book I address the issue that IT doesn't provide the one process or the one tool to take care of everything. Instead, if you want to do things right, you always need to be working on about 13 or 14 competency areas. All of competencies have to be at the right level for your organization. If you have the world's greatest technology but you don't have the ability to motivate your skilled people, then you're going to have an imbalance, and the technology won't perform the way you want it to. On the other hand, you have the technology spirit and the people with the right skills but you don't interact with the business units effectively. In other words, you don't set goals, prioritize things, or make sure you're linked to the business strategy. If this's the case, the technology you have, the way you put it in, and the skills you use to support it might be completely off target for the business units.

 

EL: So how do you get all of this to balance?

 

ML: People have had a desire to do it, but they have to work hard at it. In some cases, it requires ripping up what's there, and dramatically changing the culture. It also requires having a good base of quality and credible data, visibility, and transparency around what's going in the IT organization. You really need to look at the how the IT spend and IT performance support the business. People tend to work on parts of the problem. They really need a program to work on all the parts. It never ends. People have tried to make progress. It's been expensive.

 

The tighter money becomes, people begin to say that they don't need the disciplines they put in place, and thus start to cut costs here. For example, they might say no to rolling out an IT dashboard because they have the perception that it won't add value. Of course, an IT dashboard will add value much the same way, as you need a CFO to run a billion dollar business.

 

EL: What are some of the effective criteria processes C-level executives, including CIOs, and other business leaders or other constituents should consider in deciding on the mix of IT investments?

 

ML: People can't look at these as just IT investments or just IT spend. The companies making good progress have begun to understand that other than certain specific things, such as infrastructure, these aren't IT projects any more, but business projects with strong IT components. You need to approach things differently by saying that we, as an organization, need to decide on the mix of the total investments. Before you start making any decisions, you need a set of criteria for determining if the investment is a mandatory item, or if it is a regulatory item. Once you get that criteria agreed with by the business unit, then you can start to define the IT components, and to lay them in place. You also need to have a business measurement.

 

If the project has many business components and one IT component, then the business should unit own the entire project. Once you have structured the process and have agreed upon the criteria, you can start to have an intelligent discussion about which business projects must take priority over others. This discussion drives the platform of the portfolio of business projects you're going to do, and defines the IT components needed to support each project.

 

When the project gets going, you need to have a way to assess the results and to measure the benefits. At certain intervals, you need to stop and to make sure you can meet the targeted benefits. You can't wait a year or two years to see if there is any benefit. If you can't reach the first set of benefits in the first time interval, why would you let the project go forward?

 

EL: Where are companies falling short in finding IT dollars to invest in areas such as innovation?

 

ML: Companies that understand the activities what drive their costs, and make the effort to reduce unnecessary costs are more prone to have a mix of IT investments. On the other hand, if a company understands that 90 percent of its spend is tied up in legacy systems, then it's playing a zero sum game by having to spend money on maintaining these systems. If the company doesn't shift gears, it's costs will increase. You can't stand still. The older your systems get, the more they cost to maintain. People view this spend as a water faucet that they can turn off and turn on as needed. This saw tooth approach adds to the capital expenditure.

 

You need to understand how you spend capital to reduce costs to keep rolling forward. That translates to how do I free up cash if I'm not going to get any more money to be able to fund innovation? It gets back to perception. Do you have a group that just focuses on innovative things or innovative uses of technology for the rest of the organization or within anyone business unit? Many people view that has a luxury. It's a necessity. You don't always have to be on the leading edge, but you have to be on the edge of certain things, and to understand how these things would help the business to do something better, or to help the IT organization lowers its costs.

 

EL: What are the hot IT areas your clients are investing?

 

ML: This's an area where I'm going to tread lightly on. If you think back over the last couple of years, everyone was pushing service-oriented architecture. It was perceived as a major breakthrough in Web-based delivery of IT services. I haven't seen much about that lately. I lot of it was hype as opposed to the basic set of blocking and tackling you need when a new technology comes out.

 

Several years ago, we saw many companies heavily investing in customer relationship management systems. CRM had the same problems ERP had. People charged ahead and put in very large, global standardized systems to accomplish some objective. Many of these systems failed because of other factors. Some people, still to this day. haven't dealt with certain infrastructure issues that could remove large pockets of costs and make things more efficient. Using a tool as simple as virtual asset management, you can cut costs and improve efficiencies. If you don't understand your asset base, how are you going to understand how to move within a different direction?

 

Within the business itself, the use of things on the Internet and the Web have reached a certain plateau. We're doing more wireless activities. To this end, we need to have better wireless security and a better way to keep these wireless systems running.

 

EL: How should a company go about seeing if it can benefit from a new technology?

 

ML: You need to work with parties that help you to experiment with new technologies so you can evaluate how you can apply them in your organization.

 

Let me turn back the clock to 1995 when PriceWaterhouseCoopers had 100,000 of PCs and 1,000s of employees traveling all over the world each day. These people used to connect to the office via phone lines to get their Lotus Notes email. Broadband didn't exist at the time. Their calls would go from a server to a modem bank in the office. This service was expensive and the security wasn't where it should've been.

 

We decided to look at how we could provide connectivity that wouldn't drop calls, would require just a local call or a local connection, and would provide more security. We essentially laid the groundwork for our virtual private network. We asked MCI if it would work with us to develop the VPN. We needed a partner to help us to keep our costs in line. Our need to reduce the costs and to improve the security drove this innovation.

 

Today VPN is a staple. There are many other things like that out there. We couldn't have done that ourselves. The communications companies didn't understand what we were talking about when we first started speaking with them. You have to work collaboratively with other parties to get some of that innovation going.

--

Additional Reading - Sponsor Link:
Unlock the Hidden IT Opportunities in Troubled Economic Times


Author: Elizabeth M. Ferrarini - She is a technology writer from Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
447 Views 0 Comments 0 References Permalink Tags: article, innovation, it_investment, it_strategy

EvanRosen.jpg

 

Today, companies must maximize their time, their talent, and their tools to create value in the global economy. To better leverage these things, many companies have begun to design new business models and new workplace models based on one concept -- collaboration. However, too often companies say they have a highly collaborative environment because they've encouraged employees to use specific tools, such as Microsoft's SharePoint. Evan Rosen, collaboration strategist and author of the award-winning book, The Culture of Collaboration, says, that there's a hidden danger in making this type of statement. He says, "You need the culture to support the tools. Just introducing tools into an organization doesn't create collaboration."

 

Using examples from some of American's top collaborative companies, such as Boeing and Toyota, Rosen, in his book, explores how organizations of all sizes and types can adopt a collaborative culture to create value. Rosen, a former television news reporter and news anchor, spent much time visiting with all of the companies. He is the chief strategist for Impact Video Communications in San Francisco, California.

 

Enterpriseleadership.org recently sat down with Evan Rosen to discuss the benefits of collaboration, the trend toward real-time collaboration, and the essential elements that go into effective collaboration. Here's what he had to say:

 

EL: What prompted you to write this book?

 

ER: I've been involved with collaboration for many years. I planted the seed for the book back in 1999. At that time, I was in Munich, Germany, where BMW was preparing to launch the X5 Sports Activity Vehicle. It was using a highly collaborative process to do so. BMW created what I call mirror organizations between the manufacturing plant in Spartanburg, South Carolina, and the design and engineering center in Munich. By extending the workday and using the workday in both places, BMW wanted to shorten product development time from 60 months to 35 months. I realized as time went on that this type of collaboration could apply across major businesses. That was the genesis of the book

 

EL: How does collaboration benefit the bottom line both in hard dollars and in soft dollars?

 

ER: First off, I define collaboration as working together to create value while sharing virtual space or physical space. If you're not creating any value, what's the point of the collaboration? Value can be in hard or soft dollars. Hard-dollar benefits include reducing product development time, reducing time to a decision, and innovating a production process. Soft dollars really are hard dollars that are difficult to quantify. Soft dollar benefits include engaging people throughout the organization, recruiting and retaining the best people regardless of geography, and having better relationships with business partners.

 

Collaboration involves breaking down barriers among levels, functions, business units, and regions; and getting broader input into decisions. For example, people feel more engaged if they know their input counts, rather than if they're just handed instructions and told what to do. A highly engaged workforce results in a soft dollar asset. Responding effectively to customers' concerns can result in the soft dollar benefit of enhanced customer relationships.

 

BMW did accomplish its goal of reduced product cycle time, which resulted in a hard dollar benefit. BMW assembled the vehicle at its South Carolina plant, but engineers in both places collaborated to design the X5 and to support the product. The engineering teams used both synchronous collaboration tools, such as video conferencing, and asynchronous collaboration tools, such as video mail, to leverage both time zones. BMW realized that collaboration wasn't about tools, but about changing the nature of work and the culture of the organization.

 

EL: What company would you say has done an outstanding job of collaboration besides BMW?

 

ER: I'd say Boeing because it's an excellent example of what I call a global collaborative enterprise or an extended enterprise. It consists of a collection of independent companies that engage in a shared creation of value, often in real time. Boeing collaborates closely with global design partners, suppliers, and customers.

 

For the new 787 Dreamliner, Boeing has moved away from designing and manufacturing planes by itself and, instead, has transformed itself into a large-scale systems integrator. The move from linear design to concurrent design supports this shift. Take the linear design of the Boeing 777, the first digitally designed airplane. Boeing's engineers first designed the aircraft; then the sub-systems followed by the assemblies, the sub-assemblies, and the parts; and lastly they designed the manufacturing processes. For the 787, Boeing's engineers designed the parts, plans, tools and processes plus the assemblies, the sub-assemblies, and sub-systems all at the same time. To design and to produce the 787, Boeing had engineers in Everett, Washington, working with contract engineers at the Moscow Design Center. This shift mirrors what happens today in other industries. We're moving from the pass-along approach to work and interaction to do it now together through real-time collaboration.

 

EL: Did Boeing have to make any internal culture shifts to support the concurrent design workplace model?

 

ER: Every successful collaboration model always involves culture. To support the global collaborative enterprise, companies including Boeing have leveraged what mirror zones, which are time zones that are opposite or nearly opposite with some overlap in the workday. They allow for a nearly 24-hour production environment. People in different continents may share a job. When one time zone is sleeping, the other is working. Collaboration occurs in real time during the shift overlap and asynchronously at other times. The real-time collaboration involves, not only the ability to see and to hear one another, but to design everything from airplanes to 3D animation, regardless of geography.

 

EL: When it comes to collaboration or social networking, how do you deal across boundaries of managers and supervisors without someone getting their nose bent out of joint?

 

ER: It gets back to culture and the degree of transparency, or how well people are informed on business matters. Transparency can frighten a command-and-control oriented organization. The culture needs to support the kind of behavior such social networking tools allow and encourage. A company that has already embraced some attributes of information democracy will have an easier time with social networking. For example, one manufacturing company I've worked with provides all employees with key business information, such as the day's sales and the amount of inventory. In many companies, only key managers get that kind of financial information. If the depot person loading the product on railroad cars knows how much inventory awaits shipment, then this person can do his or her work more effectively and can contribute to decisions. Information flows both ways. Leaders can quickly gain insight from people anywhere in the company so everyone has a voice into decisions.

 

EL: What is the one element that can make or break how well people in an organization collaborate with each other?

 

ER: Collaboration tends to fail when the organization lacks common goals and when culture doesn't support the kinds of tools being forced into the organization. Before you can effectively collaborative, you need to build trust into the organization. It means moving away from a culture of internal competition that prevails in too many organizations. These organizations will pit the so-called star employees against other employees. Some competitive cultures don't encourage a lot of trust among employees. In this type of an environment, collaboration becomes fragmented. A good collaborative organization understands the values of long-term strategic relationships and that all partners must have a stake.

 

EL: IT people often get accused of not speaking the language of business, and business people don't always understand what IT is all about.

ER: How do you start overcoming barriers like this?

 

A company's survival, especially in tough economic times, requires breaking down barriers among functions, business units, levels, and regions. IT people who work for highly collaborative companies often get involved in decisions made by the business units. Likewise, these companies often engage sales, marketing, and engineering, as well as IT, in their key decisions. Organizations have many interrelated and interdependent parts. For example, redesigning the workplace environment involves facilities, IT, HR, corporate communications, and business units. Companies need to get these cross-functional groups engaged early in the decision-making process so that everyone has a stake in the outcome.

 

EL: How are companies redesigning the workplace to improve collaboration?

 

ER: Good collaboration consists of three components: -- culture, environment, and tools. The interplay of these three things determines effective collaboration. When it comes to physical environment, some companies have replaced cubicles with more flexible workspaces. Likewise, some organizations have created dedicated collaborative spaces that are designed to bring cross-functional teams together and to encourage them to brainstorm. The typical meeting room and conference room aren't necessarily equipped to encourage collaboration.

 

Mayo Clinic's dedicated collaborative space is part of its SPARC program, or See Plan Act Refine Communicate. The program's purpose is to do prototyping with new patient services by involving many different functions, ranging from doctors to marketing specialists to facilities people. Mayo Clinic has created an informal environment optimized for cross-functional brainstorming where people can relax and share ideas.

 

EL: When should an organization bring in an expert to improve collaboration?

 

ER: The answer depends on a company's background in collaboration. Some companies have built a collaborative culture from day one and have the knowledge and resources internally to extend collaborative culture. On the other hand, companies with less collaborative cultures that want to become more collaborative may need to bring in experts from the outside.

 

EL: What problem does an emerging company have with collaboration?

 

ER: A company's age doesn't determine how well employees collaborate. The Mayo Clinic, which is about 125 years old, has always had a collaborative culture. In fact, Mayo was founded on principles of collaboration. Many organizations view collaboration as a division between younger workers and older workers. Sometimes older people who've been with a company longer than younger workers view collaboration as a challenge to their authority and to their expertise. It's a destructive perception. On the other hand, some people who've been with the organization longer than others can collaborate more than people starting in the workforce can.

 

EL: How do companies measure the degree of collaboration?

 

ER: I'm going to address that topic in my next book.

--

Additional Reading - Sponsor Link:
Practical Lessons for Speeding ITIL Adoption: Leveraging Educational Services to Achieve Your ITIL and Business Objectives More Quickly

 

Author: Elizabeth M. Ferrarini - She is a technology writer from Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
339 Views 0 Comments 0 References Permalink Tags: article, best_practices, strategy

JeanneLieb.jpg

 

In 1987, the 42 separate insurance companies that comprised Factory Mutual Engineering & Research (FM), an industrial property insurer, and engineering-driven underwriter, consolidated their operations into three FM companies: Allendale Mutual Insurance Company, Arkwright Mutual Insurance Company and Protection Mutual Insurance Company. The three separate mutual insurance companies found it difficult to deliver reasonably priced, value-added engineering services in a marketplace driven by increasing competition and a demand for more challenging property protection. To reduce costs and to eliminate competition for the same customers, the three FM companies in 1999 merged to create one company, FM Global.

 

Today FM Global is an international property insurance and loss prevention engineering company with $4.7 billion in premiums and $9.7 billion in investments for 2007. The company's research group conducts tests in fire and explosion hazards, hazard detection and protection technology, natural disasters, and electrical hazards.

 

Enterpriseleadership.org spoke with Jeanne Lieb, senior vice president of information services (CIO) of FM Global at the MIT Sloan CIO Symposium 2008 where she spoke about managing a corporate business transformation. In this interview, Lieb talks about how executive commitment helped to make the merger go smoothly, and how standard processes, strong governance, effective leadership practices, and a good understanding of the business have helped IT deliver value to the business. Here's what she had to say:

 

EL. You can describe your organization's key responsibilities to  support the business? 

JL. We centrally manage all of our infrastructure, our systems development, and our enterprise architecture. Because our business model is unique in our marketplace, we had to build the majority of applications we require to run our business. These applications aren't available off the shelf. We're in the midst of a major six-year initiative to update our entire platform. 

On the infrastructure side, we're upgrading our internal voice network to voice over IP. From a server management, we're trying to gain efficiencies for using virtualization technology. 

EL. What other IT changes have you  made to operate both locally and globally? 

JL. Because of our presence in 50 countries, we had to standardize our global operations across the enterprise. As such, we use the same North American custom software in all of the countries where we operate. The software is centrally developed and centrally managed. This arrangement enables us to bring key information assets on the standard platform and use these assets in other parts of our business process. We drive economies of scale by doing that. 

Some of my CIO peers face the challenge of how to bring all of the financials together for doing business in several foreign countries. At FM Global, we don’t face this issue because we rely on this consistent platform. Because everything is centralized, we've been able to develop standardized business processes. As a result, we can focus on providing value back to the core business as opposed to worrying about how to handle financial reporting. 

EL. Can you describe why the merger went as well as  it did? 

JL. The three insurance companies that owned Factory Mutual were three equally matched companies. It was a merger of equals coming together to form a new company, namely, FM Global. This's important to understand. Because the merger didn't affect our clients, we quickly had to make some critical decisions at the beginning of the merger. For example, we had to decide which business-operating platform we wanted to use for FM Global. We didn't allow ourselves to say, 'Let's take a bit here and a bit there.' All of the insurance companies had valid platforms. Within three hours, four individuals, including me, made the decision to select one platform. We then worked with the executive committee on our rationale for our decision. During the 15-month merger period, the executive team continued to validate that we made the right decision for FM Global. No one challenged the platform decision. During this period, we also removed all of the system redundancy, and had all of the operations using a common platform. We couldn't have accomplished all of this if we didn't have full executive commitment. 

EL.  How are you providing value to the business units that translate to  profitability and to competitiveness? 

JL. I can approach that in several different ways. We've developed those business applications that run our business. Applications, such as engineering, underwriting, and claims, have an intrinsic value in ensuring that people have the tools, the technologies, and the infrastructure to respond efficiently and immediately to our clients' needs. 

As a developer of products for FM Global, we return a lot of value back to the company. As an insurance company with a foundation in engineering, we think of the information that comes from our visits to clients' facilities as the raw material for a manufacturing process. We have data management practices in place so that we then derive value from our product development, our underwriting, and other process supported by all of that information flow. 

EL. What initiatives have you  developed to become more customer centric? 

JL. We focused an important initiative on the core business roles, which include client-servicing departments, such as underwriting, claims, engineering, and sales. Using that portal technology, we knew we could provide ready access to all the client information and client content our employees needed, depending on their role. We then took a step forward by integrating our business applications into that portal. It presents employees with a list of their associated clients. After they've selected the client of interest, then all of the underlying applications then operate off that client. This streamlined interface helps employees to understand our working relationship with the client by providing information such as policies, terms and conditions, inspections completed, and other services. Essentially, we have one place where we go to find what we need. 

Sometimes business processes get lost; no one knows who owns what. We've worked to provide a clear understanding of which parts of the business own what components. It's important to know which sponsoring part of the organization drives any change or innovation. These things need to evolve over time. Because of our role and our integration of technology into our core business, we play a key role in every aspect of the business. Planning activities, for example, help us to ensure that we put together an annual plan we can respond to. 

EL. Can you  describe your governance process? 

JL. We have a cross-functional technology steering committee comprised of senior management, along with representatives from marketing, underwriting, and engineering. We ensure that we have the appropriate targets on the plan, and we deal with allocating resources appropriately. Our efficient process to resolve issues helps us to break down barriers as they arise. Usually, a team working on an initiative might have issues they can't resolve efficiently. Our resolution forum helps to resolve the team's issues. For example, we might try to resolve how far a certain application might go, or how the scope of a project needs to change. 

EL. How do you make investment decisions? 

JL. Working with the technology steering committee, we come up with a plan. Once the plan is agreed upon, I work with the CEO of on an appropriate budget to support the plan. The board gets involved as needed. Many of our decisions focus on defining the needs of the core business, and looking at what things are in our clients’ best interest.

 

EL. What steps do you take to address your clients' needs? 

JL. The business organization, not IT, talks with clients directly.  We call them our risk management executive councils, which foster a direct exchange between local management with clients. We also have advisory boards represented by CFOs at our clients’ organizations. 

EL. Do you assign IT people to be the liaison with the  business units? 

JL. I don't have people in the specific role of relationship manager. A good IT professional needs to understand the business. You're always going to need people who are good at coding or managing the infrastructure. Because our business model relies on technology, I require my entire management team, as well as business analysts, to connect directly with the business and have sound relationships with their business peers and understand the plan, the objectives, and the way we leverage technology to best meet those objectives. 

EL. Many people say there is often a disconnection between management and IT. So, when you hire someone, how do you know they speak the language of the business? 

JL. I can't point to a specific methodology we use to ensure that. I've seen many technologists who provide great value, but they do a mediocre job of speaking to business peers about solving business problems. In these cases, you need to have a liaison or a translator in the middle. This person could sit in the business unit or sit in IT.

 

EL. What are you doing to minimize the personal risk for employees to  understand and to embrace change?

 

JL. Management experts will say you need to layout and to articulate to an individual what success means to their organization. You need to communicate early in the relationship about your expectation for how employees can contribute and positively influence the changes they want to affect. When it comes to asking employees to accept major changes, you need to take a step back and to understand what obstacles would prevent employees from embracing the change. If you believe, as I do, that people want to do what's in the interest of the company, then you need to look at those other personal factors that define success for those employees.

| More
164 Views 0 Comments 0 References Permalink Tags: article, best_practices, it_management