Articles

2 Posts tagged with the transformation tag

JanBertsch.jpg

 

As gas prices slowly crept up to the $4.00 mark this year, sales of new trucks and SUVs hit a record low sending some automobile makers on a hunt for ways to keep the bottom line from taking a nose drive. Three years ago, the $64 billion Chrysler LLC took take steps to deal with an impending downturn in the market by launching a recovery and transformation plan. In early 2007, the company began the corporate journey toward financial health and operational well-being. The plan includes changes throughout the entire enterprise and throughout all of the organizations with IT being one of them.

 

Jan Bertsch, Chrysler's senior vice president, and global CIO, says, "Our IT goal is operate more efficiently and more effectively. The business case specifically for IT was very clear. Because the competition continues to get stronger, IT really needed to focus on several things, one of them being the need to leverage global resources to support our growth initiatives."

 

Enterpriseleadership.org recently sat down with Bertsch, who is a also Chrysler's treasurer, to talk about the strategic changes and partnerships that will make IT more responsive to the global needs of all its constituents. Here is what she had to say:

 

EL. What can briefly describe your key responsibilities as CIO  at Chrysler?

 

JB. I'm responsible for the direction of our global systems' hardware strategy and planning. This comprises all of the company's systems application development, our data center operations, telecommunications, and network operations on a global basis. IT has the dual role of keeping our global operations running, but also being a key partner with our business. We try to use IT to help the enterprise respond to changing customer and business partner needs, as well as to help fuel our international growth. Our structure today combines centralized services as well as shared services.

 

EL. Can you describe how the current  structure of IT supports all of global business operations?

 

JB. Our applications group aligns with the main businesses of Chrysler, which includes our sales and our marketing systems, our after sales systems, our product development, our procurement and quality systems, as well as manufacturing and supply systems, and human resources, finance, tax, and legal. Our shared services group provides these standardized services and support to all of our applications across the organization. These applications include our applications architecture, and our IT compliance of our processes, such as Sarbanes Oxley. Databases and business intelligence belong to our shared services organization.

 

Our infrastructure group provides the foundation for all of the work, the hardware, the software, the data center, and the networks across the company. We operate and support all of our partners across the business, in all of the plants across the countries with all of our data centers. We interface with all of our suppliers and parts depots as well and our dealerships. That's our organization today.

 

EL. How is  the structure of your IT organization going to change because of the IT  transformation?

 

JB. Going forward, we want to focus on continuing to support the design, and the manufacturer, and the sales and the service of our vehicles. At the same time, we want to improve the business intelligence and operational excellence that goes along with that. We'll continue to focus on critical company initiatives. For example, we'll support the strategies of our business partners by carrying out the following strategic initiatives: determining the prioritization and the source of funding to speed delivery, and to enhance the quality of our services across the company; and also helping the company to improve its efficiencies, and to achieve its revenue goals through more innovative and more efficient use of technology.

 

EL. What's your enterprise architecture and does it  align with the overall business model?

 

JB. Our technology architecture goal is to provide the capability for the interoperability between our diverse platforms we have. We achieve this with a number of efforts, including a common development in infrastructure platform, a product strategy that includes simplification and a drive towards common IT services. Our applications architecture focuses on a consistent consistency of design.

 

We want to enable common processes and common business services, which span all of the areas, with a service oriented architecture approach to the development. We'll focus on service enabling many of our legacy systems, which have coding for a significant amount of business processes. We have the goal to improve upon the simplification of that and work with some of external service providers that we recently announced. These external partners will help us to combine those solutions in divergent areas to become agile solutions. There's a big focus on that aspect.

 

EL. What were some of the  signs that prompted the IT transformation?

 

JB. Because of the rapidly changing industry, changing marketing demand, and changing customer demand, we thought the need for IT capability could flex better with business demand if we had an alternative solution to how we work today. Of course, we all need the ever-increasing demand for innovation and technology improvement. Our IT transformation was one part of the corporate plan, but I see it as the next step in our continuous efforts to operate more efficiently and effectively. An IT transformation gave us the tools and the flexibility to drive business growth, not just to react to the situation.

 

EL. Who are the IT partners and what do they bring to the  table?

 

JB. We decided to look at those areas within IT that had the biggest opportunity for improvement. We took time to assess where we felt we were market leaders and where we weren't. For example, we've operated our mainframe and server support areas efficiently with third-party resources. However, we manufacture automobiles, not provide IT services to major corporations. We knew that other technology companies in the industry could probably service us better in those areas because of their scale of business.

 

We first identified some areas where we felt we could drive improvement in the organization. We went out and market tested those areas. We also market tested some global players that had the capability to handle a company Chrysler's size, and that we felt would be good business partners with us. Based on our market test, we found that where we thought we had opportunities, we did have opportunities. At that point in time, we did due diligence and settled on suppliers. We awarded business on the applications side of our services to Tata Consultancy Services, and also to Covancys, a part of Computer Sciences Corp. We awarded our infrastructure business to Computer Sciences Corp. We're now in the process of transferring our internal business processes to our new business partners.

 

EL. What is involved in  the handoff of business processes from IT to the partners?

 

JB. For example, Tata will handle some of the applications maintenance work. We identified what work will go to them, and then we'll work with them on transferring business processes and the know-how. Because we're in the middle of this, I don't want to go into too much detail. On the applications side, some of the work will take place in other locations and might not require as many people. Tata might provide offers to some people to work locally. On the infrastructure side, Computer Sciences Corp. has provided interviews to our on-roll people and has made offers to some of those people to work either on the Chrysler account and perhaps later on to work on another account. We also have contract houses who've elected to work with our business partners.

 

EL. How will the transformation change your governance  process?

 

JB. There will be a reasonably large change in that area when we transfer the business. This transformation allows us to better focus on identifying internally the strategic business processes we could benefit from, and we could improve some of our innovative solutions. We'll be less involved with the day-to-day operations, and we'll be more involved in the strategic processes going forward. We'll further collaborate with our business partners. We'll gain a better understanding of their pain points, their desires, and the way the business moves. As a result, we'll be able to better leverage our global service providers' wealth of experiences in these new technologies, and to identify quickly projects that will have the greatest payback and the surest ROI. We'll have more time and more ability to improve our governance process, to improve the prioritization of our projects, and to improve the quality of the innovative solutions we can bring to our business partners.

 

EL. Do you have any strategic business processes where  IT can make big improvements?

 

JB. Sales and marketing is an area where there is some capability to improve our volume planning operations. This is area also works very closely with our logistics and purchasing operations to improve our forecasting techniques for what we should be building and, therefore, what we should be buying. We always seem to have many good ideas. However, we're somewhat precluded from being able to participate all of them because of capital requirements. Because we're going to be working with partners that have the capacity to invest in those new technologies, our revised governance structure will enable us to better prioritize these business processes.

 

EL. Does your financial  background enable you to see things differently than a CIO who has grown up in  IT?

 

JB. Having a finance background helps me to dive into the business case to analyze each of the improvements or projects we're looking at. I've always professed that changing IT or anything for the sake of changing it doesn't make any sense. You need to have a sound business case to justify it or else we shouldn't be doing it.

 

I don't imagine that being in finance really differs from the experiences of most CIOs today. I see more CIOs with a strategic background, usually in finance or in business management. To be successful in a CIO role, you have to know the entire business, and you can't be a successful CIO just being a good technology person. You have to understand the strategy. You have to have a good financial sense about you. I see more people with those some skills taking on this role in many industries.

 

EL. What process improvements you are making to  become more responsive to customers' needs?

 

JB. We're in the process redefining our IT landscape for the new delivery model we're talking about in the future. Both IT facing and the customer facing processes will focus more on becoming customer friendly. At Chrysler, we know that the perception of the customer is everything. We spend a lot of time with our dealers, with our systems, and with our processes to try to enhance the customer's experience with the dealership -- either online or in person. I think one of the key changes will be in the level of participation that we to target in the alignment of our IT strategy with the business strategy. We don't like reacting to business requests. Instead, we like to be an integral part of the solution to our issues and our goals. We'll measure our contribution in the future, not only in terms of our IT delivery metrics, but also as an innovative and cross-functional partner of our business.

 

EL. Have done any previous outsourcing?

 

JB. In the past, we told the partner what we wanted them to do. Now we're saying: 'Listen, we have something to deliver. Let's work with you to figure out the best way to deliver it. We're open to suggestions.' We're doing this a much larger scale now. We're also looking at doing that with certain functions within our organization. However, we're still maintaining relationships with the suppliers, and maintaining the governance, the compliance, and much of product planning up front in house. I know that many people who outsourced in the past might've outsourced too much and now they're bringing a portion of it inside. We tried to be cautious about that as we go to our next steps -- making sure that we transfer those parts of the business that our partner is best at and maintaining those parts we know we are the best at managing.

 

EL. What is your timeline for the IT  transformation?

 

JB. Last year we started in earnest right after the separation of Daimler and Chrysler. We determined what we were going to do to by year end. We selected our partners early in 2008. We should be completely done with this portion of the transformation by late summer. It's a quick timeline, but we felt it was important both for the respect of the people and to maintain our business knowledge transfer as much as possible. Our new business partners agreed with that.

 

It's not going to stop there. We're relying on our relationship with our new business partners to continue to identify opportunities. Already in the process, our partners are now coming to us, identifying some things that we had either not thought of, or hoped would happen shortly after the transformation. Some of those are based on best practices that the business partners see. Other ones may be based on pure scale -- where we might be able to reduce the requirements for hardware because we're now dealing with companies that have a larger base that we had. Together we'll pursue more good opportunities as we continue down this path.

 

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

| More
2,098 Views 0 Comments 0 References Permalink Tags: article, governance, it_strategy, outsourcing, transformation

ZackHicks.jpg

 

If you want to know why people buy Toyota, just ask someone who drives one. Some people have put as many as 300,000 miles of their vehicles. That emphasis on quality comes through in every commercial about Toyota. However, quality resonates through just about every function, especially IT, at a Toyota company. But this hasn't always been the case. In 2002, executives at Toyota Motors Sales, USA, Inc. complained about how IT was unresponsive, and about where all of the money spent on IT projects went. Barbra Cooper, the CIO, undertook a massive restructuring of IT to better align strategically to better align with the needs of the business units and to better align with the company's culture of quality and continuous improvement.

 

Recently, enterpriseleadership.org sat down with Zackery Hicks, a corporate manager from the Office of the CIO at Toyota Motor Sales, USA to talk about how IT meets project goals, innovates, maintains quality, and develops talent. Here's what he had to say:

 

EL: Can you provide an overview of your IT organization?

 

ZH: Barbra Cooper, our CIO, also oversees the University of Toyota, which is a global responsibility. Our IT organization has a federated model, consisting of about 400 employees. The office of the CIO oversees the transparency, governance, and the business enablement. We have aligned a divisional information officer or DIO with each of our business units. Each DIO has a staff of direct IT reports. Each DIO sits with his/her business line and attends that business unit's staff meetings. At review time and throughout the year, the business executives provide feedback on DIO performance to the CIOs. DIOs have a dotted line to their divisional executives.

 

Within my domain, I have IT strategy, finance, governance, resource management, and vendor management. I also have security, privacy and compliance.

 

EL: Is that structure a model for all of IT within Toyota?

 

ZH: For some divisions of Toyota, IT has the same structure as us. The manufacturing divisions have a flatter IT structure than ours because of their
specialized business needs.

EL: Did Barbara Cooper develop this structure for the IT organization?

 

ZH: She did. Barbara likes to say she called the police on herself. Before joining Toyota, she has been a change agent CIO, transforming new companies and then moving on. Her longest tenure as a CIO has been at Toyota. Several years ago, she felt that it was time to transform IT here because people perceived IT as more of an order taker. Cooper wanted us to be thought of as a respected strategic partner. She took us on the journey to achieve this goal.

 

EL: Where does the Toyota Motor Sales IT organization fit into the global Toyota IT?

 

ZH: We are a separate company from Toyota Motor Corp in Japan. However, all the supply chains interconnect with each other. In fact, all of our systems connect with those of our other affiliated companies. We have
a close relationship with the other IT organizations within Toyota.

 

EL: Can you describe the governance structure by which the DIOs operate?

 

ZH: The Office of the CIO facilitates the executive steering committee. We have many project portfolios recommended by each division for committee approval and for provisioning.  Each division and each DIO has his/her own local governance. You can liken it to state and federal government.

 

We decided to empower DIOs with all of the resources needed to meet their business units' needs.  We did this because we didn't want DIOs turning into relationship managers.  Furthermore, we wanted them to strive to be successful. As a result, we empower them to respond quickly to their evolving business units' needs. We have a threshold for what they can decide
locally.  Beyond that local approval level, they have to rise up to enterprise governance.

 

EL: Do the DIOs have to reach project objectives before funds are released?

 

ZH: We have a business case for each project. We look at the ROI and the total cost of ownership. We also want to have a portfolio view so it isn't just only based on ROI. Some projects that might help us with innovation or help us in our continual quest for better quality might have a lower threshold. In the overall picture of the company, these projects have value. We take more of a portfolio view, but we absolutely do look at securing a return. In the Toyota Way of Plan-Do-Check-Act, we ask each project team to come back after completion to verify whether or not the project reached its objectives.

 

EL: Can you describe the metrics or methodology the business units can judge the success of IT projects?

 

ZH: The business case at the initial start states these objectives. At the beginning of the year, we do an annual plan. We agree upon what the enterprise goals are going to be. What does each DIO or direct report have in common with the things we agreed upon? What are our targets? What things are going to be done locally? What are the local plans that we are going to achieve that year? The annual plan must address all of these questions.

 

By the time the business case comes forward, we already have awareness on what projects we can expect. We do have funding gates at appropriate phases of the project. Before we begin construction, we look to have a completed ROI analysis and a full cost of ownership for a five-year plan. We want ideas to get off the ground. We make it very easy for the different
business sponsors who have ideas for something new. We'll fund the idea, give the team a pre-determined amount of time to go off and think about the idea, and to vent the idea out with IT and any other affected groups to see if the idea has some legs. If it does and the team comes back, then we'll give them more seed money to get through high level requirements. We continue down this path before they get to construction. We want to encourage good ideas that help the business. We also want to limit our exposure by investing in the wrong things. Before we give them money to begin construction, we want to make sure all of the risks and the returns are vented out.

 

EL: Toyota is known for being a leader in sustainable innovation and breakthrough innovation. Can you give me one or two examples of how IT has contributed to innovation?

 

ZH: We're proud of our dealer extranet. Two disparate systems used to burden most of our dealerships. They used to enter their factory order requests in with their factory system and then run their office via their dealer management system. The interface we created enables our dealerships to work on either the factory system or the dealer management system without
ever rekeying any input. A vehicle entered as sold in the factory system would automatically update their inventory systems as purchased on their own. This innovation tore down the silos between the automation that existed. The extranet provided the dealerships with more flexibility. They now could see the vehicles to them in their pipeline, and can trade with other dealerships before the vehicle arrive to the dealership. This capability gives dealers the ability to get the right car, to the right place, and at the right time for the right customer.

 

Quality is another aspect of innovation for us. It's part of our focus on and part of our culture. Quality shouldn't be limited to our vehicles. Our systems should also have that quality. We've been innovating by providing our engineers, regardless of where they are in the world, the ability to view any part of a vehicle that is not performing as designed. Our Toyota dealerships have this capability for servicing vehicles.

 

EL: What quality practices are you using in IT?

 

ZH: Toyota is Lean. We have our own culture on Lean thinking and continuous improvement. Cooper made them a big priority when she reorganized IT. We wanted to better align IT with the Toyota culture. Our mantra says that we're not a public corporate IT shop; we're a corporate in-house IT department which knows what our business wants and mirror that. We needed to move upstream and to understand our business better. We achieved this posture through Lean thinking and the continuous improvement or Kaizen. We absolutely incorporate these quality practices in everything we do in IT.

EL: How does IT meet the objectives of the Toyota Production System?

 

ZH: We're the sales and manufacturing arm of that. IT uses the same principles used in manufacturing. The methodology is the same. You can't see everything that IT does. On the other hand, if you walk by a vehicle assembly line, you can observe how much wasted time is expended. We mirror our production system by using dashboard and process documentation to visualize and to enable people to see what's doing on in it and to improve upon it. This visualization is all part of our continuous improvement.

 

EL: What types of IT career development programs do?

 

ZH: At my previous companies, you were labeled either an IT person or a business person. At Toyota, you have opportunity rotate through different areas of the business.  I started at Toyota in corporate services. Because I had IT experience, I had the opportunity to move into IT. However, people have to demonstrate the talent to move to another functional area, as well as to have the desire to do so.

 

EL: Is there a formal leadership program at Toyota?

 

ZH: It's based on different levels. Our University of Toyota functions as a center for dealers and for our employees to learn business skills, communication skills, to uplift the organization's abilities, and to prepare for the future. This center is also open to IT people. In addition, while working with the University of Toyota, we developed our own career path within IT based on the changes occurring in this industry. In the 1980s, a good programmer could count on becoming a manager. Today, a lot of programming happens offshore. An IT manager today needs to oversee relationships with disparate vendors, and a disparate workforce across the globe. 

EL: Can you describe the performance goals set for senior IT people?

 

ZH: We focus a lot on achieving our goals by building employee performance incentives into our plans. We establish goals at the beginning of each year.
Throughout the year, we make sure we honor these goals, unless business conditions change. It's easy to get distracted because of all the complexity which comes with IT. Having objectives, having goals, and tracking our performance of those goals becomes important for keeping everyone on track.

 

The Office of the CIO has been successful in managing not only the day-to-day operations of IT, but enabling the CIO to have optimal business engagements and worry less about tactical part of IT.

 

EL: How have you handled the execution of IT strategy?

 

ZH: We put the portfolio of our current applications on one axis. On another axis, we looked at what business conditions are likely to occur. We wanted to see what would happen at the intersection of these two things. What would happen to our systems if we need to support more or less dealerships? Would our systems support the increasing variation of our vehicles? What affect does business complexity have on our systems? This process helped us to have a better dialogue with our business customers. We were able to go upstream by our increased ability to have a dialogue about changing business conditions and the potential impact of our application portfolio. Instead of being an order taker, we could anticipate if we needed to invest in new systems. This awareness helped us more in strategic planning.

 

Through the Office of the CIO we ensure that these potential projects or projects that support the business strategy rise to the top and get the needed funding, and get all of the executive support they need. We make sure they are tracked monthly through that visualization. We want everyone to have the same understanding of what is going on with the projects, to be able to help the projects as they are coming off the tracks, and to get projects back on track based on early warning signs.

 

EL: Can you describe some of your IT innovation programs?

 

ZH: We have several formal programs around innovation.  In fact, one of our top goals for 2006 and 2007 included innovation. I mentioned our annual planning process helps keep our associates focused on those areas where we want to make progress. Innovation was an area that's taking center state in our annual plans. We don't care if the submitted idea was actually carried out. We're more interested in how many ideas each executive brings forward from their team. We want to provide a clear path for any idea to rise to the top. We also have some local groups compete similar to a science fair. Their ideas don't have to be about Toyota per se.  Perhaps a submitted idea might be the muse for another associate in how it could benefit Toyota. We don't want to limit innovation. We hope to bring in some ideas that could drive some foothold here at Toyota. Each quarter we give out awards for innovation and continuous improvement. In fact, in 2007, IT allocated 100 percent of its continuous improvement fund to innovative ideas.

 

Note: Since this interview took place, Zack Hicks is now corporate manager of administrative services.

--

Additional Reading - Sponsor Links:
Managing the Business of IT: Maximizing the Power of Service Resource Planning, the Next Step in Business Service Management
Understanding ITIL® Service Portfolio Management and the Service Catalog


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

| More
2,147 Views 0 Comments 0 References Permalink Tags: article, career_development, governance, innovation, strategy, transformation


Actions