Search...

Type above and press Enter to search. Press Esc to cancel.

June 13, 2019 | 4 Mins Read

Five Things You Might Not Have Known About Decisions Behind IT Outsourcing

June 13, 2019 | 4 Mins Read

Five Things You Might Not Have Known About Decisions Behind IT Outsourcing

Share

By Dr. Marlene R. Kolodziej

Executive decision-makers cannot always anticipate and fully understand the implications of information technology outsourcing (ITO) decisions for the long-term processes, capabilities, and performance of their organization, especially when considering ITO for cloud-based services.  My doctoral research explored the decision-making process, and particularly the criteria used by executive decision-makers, for identifying and selecting organizational competencies when engaging in Information Technology Outsourcing (ITO) using cloud-based services. Findings indicate that executive decision-makers are unable to articulate decision-making criteria and to define processes used for identifying and selecting organizational competencies to consider as part of ITO engagements for cloud-based services.

While the study participants were asked a number of questions, the desire was to answer the question “How do executive decision-makers describe the process followed for the identification and selection of organizational competencies to consider as part of ITO engagements?”.  Of course, there were additional questions, such as a) “How do executive decision-makers describe the criteria used for selecting organizational competencies to consider as part of ITO engagements?”; b) “What methods do executive decision-makers use to anticipate the long-term impact of their ITO decisions on organizational processes, capabilities, and performance?”; and c) “How do observations on anticipated impact differ from realized impact on organizational processes, capabilities, and performance from ITO decisions?”. The good news is those questions helped identify these five things regarding executive decision-making when outsourcing to the cloud.

#1: Executive decision-makers identify competencies primarily using intuition. It’s not new news that executive decision-makers select organizational competencies to target for ITO for cloud-based services based on the need to fulfill application, security, regulatory, or compliance requirements; to fill a gap; and/or to increase capabilities not found within their organizations.  What is new is the research found executive decision-makers identified organizational competencies to outsource to the cloud through a process of intuitively understanding the gap or criteria in their applications, security, regulatory, or general requirements. These decision-makers also made sure those competencies were not a core part of their business.

#2: Executive decision-makers thought they used a formal decision-making processes (but not really). While executive decision-makers used their intuition to select organizational competencies to target for ITO for cloud-based services, they also believed a standard decision model was used. Executive decision-makers assumed they used a formal multi-criteria decision-model (MCDM) as part of their decision-making process, when in actuality, their decision was intuitive but happened to align with a formal MCDM.

#3: Executive decision-makers rely on external expertise (though they really used their intuition). While now know executive decision-makers intuitively identify competencies to outsource to the cloud prior to initiating the outsourcing process, but the researched also showed  executive decision-makers engaged in a formal request for proposal process with external vendors. Although some participants used the expertise of external vendors to identify competencies to reduce cost, the identification of organizational competencies is much more of an organic process. Executive decision-makers decided to retain core competencies such as customer-facing applications and business relationship management activities while moving noncore competencies such as internal corporate systems, architecture design, cloud operations, simple sales management, and support to an outsourcing provider.

#4: Executive decision-makers build in contingencies (and are flexible). Executive decision-makers retain some onsite infrastructure for business continuity but also construct their ITO using cloud-based services with the flexibility to move data to another cloud-based service provider or back in house. Executive decision-makers also avoided outsourcing core competencies and are willing to insource those previously outsourced competencies should those competencies change to core competencies and become strategic. Essentially, executive decision-makers identified their core competencies prior to engaging in outsourcing to the cloud; understood their internal strengths, what made them unique, and what competencies were missing; and used the cloud to strengthen internal competencies or add new competencies to remain competitive, and revisited those competencies they outsourced to make sure those competencies were where they should be.

#5: Executive decision-makers built muscle memory (practice, practice, practice). Executive decision-makers experienced negative outcomes when engaging in their first cloud-based outsourcing, but subsequent cloud-based outsourcing engagement were perceived as having more successful outcomes. The an initial outsourcing engagement requires creating new frameworks and processes, whereas subsequent outsourcing engagements rely on the previous structure and lessons learned from prior engagements, thereby reducing the negative impact. Essentially, the more outsourcing you complete, the more successful each engagement will be. Previous research suggests the decision to outsource is an organizational strategy considered by many organizational leaders a requirement for staying competitive in the marketplace, given its potential for reducing costs, increasing profits, or developing competitive advantage. Executive decision-makers agreed that decision-making regarding ITO for cloud-based services commonly ignores the effort required to integrate applications into the infrastructure and underestimates the people, effort, and cost implied. Essentially, executive decision-makers are intuitive in their decision-making for ITO using cloud-based services, do not purposefully use a formal MCDM, rely on external expertise when needed, ensure they have contingency plans and are flexible, and are more successful as they outsource more.

Stay Connected

Subscribe to The INSIDER, our exclusive monthly newsletter, and get a first look at what’s new, what’s next, and what’s only shared with our inner circle.

June 10, 2019 | 5 Mins Read

7 Tried-and-True Tips for Successful Merged Reality Adoption

June 10, 2019 | 5 Mins Read

7 Tried-and-True Tips for Successful Merged Reality Adoption

Share

By Evans A. Manolis

This much is certain: Merged Reality has become an increasingly important part of the service delivery process for many companies over the past two years. Remote Assistance has moved from a “cool to have” technology to a “must have” for service organizations that are looking to increase productivity and drive operational efficiencies.

Service organizations who have invested in Merged Reality technology are able to see a great impact on measurable service KPIs. Those include reduction of truck rolls/on-site service visits, increased first- time fix rates, decreased call handle times, improved remote resolution rates, maximized product uptime and perhaps most importantly, a positive impact on the customer experience. While service leaders understand the value that Merged Reality and Remote Assistance bring to both their customers and employees, they are faced with a challenge. How do they drive adoption and use of this technology among their front-line service teams? Over the past 24 months, I have worked with over 50 service organizations to help them address this challenge. What has become clear to me is that Merged Reality is no longer a technology play. Rather, Merged Reality is much more about change management and behavior change than it is about technology. It requires organizations to change the mindsets of service professionals. To change service processes. It means getting out of a comfort zone and committing to deliver service in a new way. And the reality is that none of these changes are easy. In order to help service leaders who are in the process of deploying a Merged Reality solution or for those who are struggling to successfully get one off the ground, I wanted to share 7 Best Practices For Merged Reality Adoption that I’ve seen proven to drive change and adoption.

  1. Build A Compelling Business Case. Start here. Make sure everyone knows what you are hoping to accomplish through the use of a Merged Reality solution and why you are launching this initiative now. Has there been a compelling event that pushed this initiative to the forefront? Be clear as to the reason this initiative is being put in place. Focus on the what and why of the program.
  2. Put Leadership in Place. All successful programs have three types of leaders. First there is the executive sponsor who has the vision for the program. Then you have the project leader, who has responsibility for the day to day operation of the program. This person is vitally important and without their full attention to the program, it is destined to fail, or at the very least, not yield the results you were hoping to accomplish. And finally, there are the change champions who are influential service employees who help drive the program to their co-workers.
  3. What’s in It For Me? This requires some thinking. Put yourself in the shoes of the service technicians who you want to use this technology. Why should they care about adopting and using a Merged Reality tool? Chances are they are very comfortable servicing their customers the way they have for the past five, 10, 15 or more years. What is in it for them personally? Forget about what is in it for the company or for you as the service leader. They generally don’t care about that but they do care about themselves. How will this solution benefit and be of value to them personally? Will it eliminate a plane ride and trip to service a customer in another country? Will it allow them to be more efficient in serving their customers thus allowing them to have more time with their family and friends? Will it make their job easier and less stressful? Will they be compensated for successfully using the technology? Communicate your message from their perspective and not yours. Get in their shoes!
  4. Start Small to Get Big. When service leaders see Merged Reality they think big picture, which over time is fine. But initially, focus on one or two high value, high visibility, critical use cases to get your program started. Where in your service organization can you use this technology and see the fastest time to value? Is there a specific challenge or problem you can initially focus on? Start there and then grow as the program takes root and becomes successful.
  5. Look for Short Term Wins. Gathering early program success stories is directly tied to the future success of the program. Be sure to communicate early successes to all those who are expected to use the solution. This is especially important for those service techs who may have used the solution once or twice but aren’t sure of the value of it. The “hedgers or fence-sitters.” Once they see that others on their team are having success, they will be more inclined to use the technology again.
  6. Analyze and Make Changes. Talk to your employees who have adopted and are using the technology (adopters) as well as those who are not (resistors). Look for root causes of both adoption and resistance. Understand why each has chosen their position. Let them know that their voices are being heard and you genuinely care about them. Don’t be afraid to make changes based on the feedback you gather from your employees. Your program is not cast in concrete.
  7. Publicize and Market. Once your program has started to bear fruit, make sure that all organizations within your company are aware of your Merged Reality initiative. Get it out of the service silo and communicate its success and impact to both internal and external customers. Make sure sales is aware of the program, as they can use it to win deals by differentiating you from your competitors. Conduct internal webinars to ensure that all employees are aware of the program.

As mentioned before, change is not easy — but is achievable. Keep working hard on it. It does not happen overnight, but the results you will get from your program are well worth the effort you will put in it to make it successful.

Stay Connected

Subscribe to The INSIDER, our exclusive monthly newsletter, and get a first look at what’s new, what’s next, and what’s only shared with our inner circle.

Most Recent

June 6, 2019 | 2 Mins Read

Take the quiz: What is Your ‘New IT’ IQ?

June 6, 2019 | 2 Mins Read

Take the quiz: What is Your ‘New IT’ IQ?

Share

By Tom Paquin

Here at the Future of Field Service, we love talking about new product implementation, integration, and rollout, but we realize that represents a very small percentage of the day-to-day life of service IT. The meat of IT interactions happen in the moments in between those large scale implementations; Maintenance, onboarding, and off-boarding of employees onto the various systems that run your service practice. Right alongside those big implementations, these day-to-day operations are changing too. 

The Dawn of New IT

With the many technical advancements disrupting every area of service, it’s easy to forget about how technology impacts some of those top-level areas of IT, as well. These technical advancements, along with changing perspectives about the role of IT holistically, have led to the coining and conceptualization of what we like to call New IT. So—what is New IT, and how does it differ from, uh, old IT?In short, the way that I like to think about New IT is as the democratization of Information Technology. While traditional IT forces a top-down approach to the way maintenance is handled, New IT puts the power, and expectations of onborading and maintenance into the hands of the user. With the advent of cloud, fast connections, and remote device management, IT professionals should be interacting with end users as little as possible. In field operations, where employees should be remote 99% of the time, this is even more imperative. This allows and IT staff to focus on bigger, broader strategic initiatives that are more worthy of their time.Let's use onboarding as an example. Ideally, IT should not even have to unwrap the packaging on a new employee’s devices in order to get them up and running. Modern device management starts at the OEM, and is visible in a cloud-controlled database, so the computer leaves the assembly line with the employee's credentials ready to be configured. This logic invariably extends to your FSM software, which should be managed and deployed in the cloud for ease of integration into a New IT workflow. Moreover, a solution should be chosen that is configurable, modular, and frictionless for updates, maintenance, and management. If you're an IT professional, you might be wondering how you stack up, so we've created a short quiz to test your "New IT" IQ. It'll help you see how you stack up against the most mature of Field Service firms. Check it out below: