Succeed at Transformation

Despite the pomp and fanfare associated with launching corporate transformation programs, in reality very few of them succeed. According to a recent report by McKinsey the success rate is pegged below 40%. In addition, the same research indicates that defensive transformations – those undertaken as part of crisis management – have lower chances of success than progressive ones – those launched to streamline operations and foster growth. However, adopting certain strategies, like setting clear and high goals, and maintaining energy and engagement throughout the implementation phase, can really boost the project’s success rate. A key aspect of business transformation is IT transformation. This can be attributed to the fact that significant business change is either driven or influenced by technological change.

So what is IT Transformation?

IT transformation is basically a holistic reorganisation of the existing technological infrastructure that supports the company’s mission critical functions. In essence, IT transformation is not all about effecting change for the sake of change but involves systematic steps that align IT systems to business functions. To appreciate this approach, it is important to explore current trends in the business world where human resource, finance and IT transformations are being carried out in unison. This is being done to develop strong corporate centres that are leaner, agile and more productive that enhance greater synergies across all business functions.

IT transformation inevitably results in major changes of the information system’s technology, involving both hardware and software components of the system, the architecture of the system, the manner in which data is structured or accessed, IT control and command governance, and the components supporting the system. From this scope of works it is evident that IT transformation is a huge project that requires proper planning and implementation in order to succeed.

Tips to Improve Success in IT transformations Projects

1. Focus on Benefits not Functionality

The project plan should be more focused on benefits that can be accrued if the system is implemented successfully rather than system functionality. The benefits should be in line with business goals, for instance cost reduction and value addition. The emphasis should be on the envisaged benefits which are defined and outlined during the project authorisation. The business benefits outlined should be clear, feasible, compelling and quantifiable. Measures should be put in place to ensure that the benefits are clearly linked to the new system functionality.

2. Adopt a Multiple Release Approach

Typically most IT projects are planned with focus on a big launch date set in years to come. This approach is highly favoured because it simplifies stakeholder expectation management and avoids the complexity associated with multiple incremental releases. However, this approach misses the benefit of getting early critical feedback on functioning of the system. In addition, the long lead times often result in changes in project scope and loss of critical team members and stakeholders. IT transformation projects should be planned to deliver discrete portions of functionality in several releases. The benefit of multiple release approach is that it reduces project risks and most importantly allows earlier lessons learnt to be incorporated in future releases.

3. Capacity of the Organisation to confront Change

As pointed out, IT transformations result in significant changes in business operations and functions. Hence it is important that all business stakeholders should be reading from the same script in regards to changes expected. In addition, key stakeholders should be involved in crucial project stages and their feedback incorporated to ensure that the system is not only functional but business focused.

Check our similar posts

Field service and customer transparency

These days, a business is as good as it is transparent. Businesses are on unsteady ground because of the ever changing face of social media and a never-seen-before demand for information. With many sources of info on the internet, being credible is a sure way of building trust and loyalty among clients.

Here is an example. Customers will always believe what they see. If they see the work you put into furnishing their favourite products, you have a greater chance of getting their approval. They can invest more in what they see. The clothing merchandise Patagonia did this for their Footprint Chronicles line to show how their jackets are made and worked out fine for them.
Transparency is a must. Nowadays, customers never forget when they feel cheated. It is even harder to ensure transparency because many clients are also experts who scrutinise every detail. So, how can you keep transparency at the forefront?

Have transparent workforce management

Customers always look for new information and want to be in the know. There is nothing worse than not being able find a product manual or an easy way to set up appointments. By giving your clients a self-service option, they can pick the services they want. This leaves more time to get stuff done rather than answering unending service calls from dissatisfied customers.

For instance, you could have a field service customer self-service application that allows customers to look for personalised services, a machine manual, book appointments, or solve any other problem. Customers then get feedback anytime. This one-on-one approach can help customers feel like their questions are being answered. They?ll also not go through the hassle of long hold times to reach an available customer service representative.

Create transparency in field service repair projects

If field technicians have access to field service software, it allows technicians to be more open to customers. This gives them vital information like customer history and the ERP, so that they can explain changes that were made after past enquiries and what is being done in current products. Such information can be a guide for future updates or let the techs suggest products that suit a client’s taste. Unlike always staying offline and out of touch with your client, using field service software can allow entry of allowances and mileage, and also let the customer know the delivery time for their products.

Show customers what they’re paying for

With field service automation, billing will also be transparent. By using the available information about your field service solution, the station can send updated service reports to the customer like mileage, allowances, parts, hours worked, and photos of broken parts from the service. After the customer authenticates the transaction with a signature, the field service agent can generate and sent to the customer an invoice based on the agreed upon services. In case allowances and mileage can be forwarded to the customer, it will be shown on the invoice.
Because you use field service automation, it means that the customer will receive the invoice really fast ? in days rather than weeks ? and transparency will skyrocket because the whole experience of the service will leave a permanent mark in their mind.

Mistaking information for transparency

Being honest with your customer is the one thing. Wasting their time with unnecessary information is another. Here is an experience I had with a small retailer. Tracking information is only useful if it has recent updates and is accurate. If the company want to use real time tracking, let them do so under one condition ? updates should be regular and on time so as not to leave the customer frustrated because they also make plans based on the same information. Late updates shed light on the nature of the service command. Everyone hates cooked-up real time information.

A company must not always have a one to one exchange of information with customers to maintain transparency..

Use simple language that all customers can understand
Don’t use abbreviations that only employees know
Never ever air your failures and flaws to your customers

It is interesting that most of the tools we use to keep in touch with our clients and servicing their requests can also be used to gather data and iron out possible errors to improve products and services. This is a good chance for service providers to evaluate and make necessary amendments.

There are some areas that will need improving while others will not, nevertheless, the client needs to always be informed and know why things are the way they are. Not all details should be told, so filter what you share.

5 ways field service supports customer service

Sales organisations are always in motion, working to deliver the right product to their customers. To keep customers smiling all times is hard and only needs close communication and fulfilling promises that were made to them. This is where the field service delivery team comes in. Field service can either meet this demand or fall short plummeting satisfaction rates.
This is a task that relies on right people using various parts and information to get the job done. No matter what, the customer always expects to get exceptional services whether it be over the phone, chats, in the field, online messaging, over email, or social media.

These five field service points are suitable for any business model and guarantee excellent company-client relations.

Proactive service

A proactive service gives more to the customer. More attention is given to the customer so that the right actions, deliveries and repairs are done. By getting everything right the first time, the customer has less to do ensuring that they are satisfied with the services.
However, the field service technician is flooded with a myriad of unpredictable situations; overheating equipment, stalled machines, and insufficient precaution. But through field management software, they get more data about the customer and type of service or parts expected and they easily ride through any storm and prevent future damage.

Transparency

Nothing frustrates a customer more than a schedule that delays repairs. They easily ditch you for better services elsewhere. By offering the customer a service where they book appointments based on their own availability, we can easily sync this to the technicians and manager?s calendar. This not only saves time but also money from otherwise idle equipment.

On-site and off-site collaboration

Having seamless communication between field and office technicians is vital. Field technicians need to know more about parts, repairs, client maintenance history, and predict what should be changed in the long run. The faster they do this the better.

There should be a system that creates and automates communication between field and office technicians. Let each have the upper hand when providing parts, products or services to the customer.

Flexibility

Information is key to field service agents. They make the first impression since they make the initial contact with clients. Regardless of the resources, the field technician must always be armed with mobile tools they will need to access online resources and be ready for any emergency.

Actionable performance improvements

Customers demand excellent service a company could offer. But as the game constantly shifts, the service management technicians must also come up with plans to stay up to par with competition. All these stems from coming up with KPIs, measuring them and turning them into a workable plan for the future.

The Matrix Management Structure

Organizations exploit matrix management in various ways. A company, for instance, that operates globally uses it at larger scale by giving consistent products to various countries internationally. A business entity, having many products, does not assign its people to each product full-time but assign those to different ones on a part time basis, instead. And when it comes to delivering high quality and low cost products, companies overcome industry pressures with the help of many overseeing managers. In a rapidly changing environment, organizations respond quickly by sharing information through a matrix model.

Understanding the Matrix Management Structure

A basic understanding of matrix management starts with the three key roles and responsibilities that applies in the structure.

Matrix Leader ? The common person above all the matrix bosses is the matrix leader. He ensures that the balance of power is maintained in the entire organization by delegating decisions and promoting collaboration among the people.
Matrix Managers ? The managers cooperate with each other by defining the respective activities that they are responsible for.

Matrix Employees – The employees have lesser direct authority but has more responsibilities. They resolve differing demands from more than one matrix managers while they work things out upwards. Their loyalty must be dual and their relationships with managers must be maintained.

Characteristics of a Matrix Structure

Here are some features that define the matrix management structure:

Hybrid Structure ?The matrix structure is a mix of functional and project organization. Since it is a combination of these two, matrix management is hybrid in nature.

Functional Manager ? When it comes to the technical phases of the project, the functional manager assumes responsibility. The manager decides on how to get the project done, delegates the tasks to the subordinates and oversees the operational parts of the organization.

Project Manager ? The project manager has full authority in the administrative phases, including the physical and financial resources needed to complete the project. The responsibilities of a project manager comprise deciding on what to do, scheduling the work, coordinating the activities to diverse functions and evaluating over-all project performance.

Specialization ?As the functional managers concentrate on the technical factors, the project managers focus on administrative ones. Thus, in matrix management, there is specialization.

Challenge in Unity of Command ? Companies that employs matrix management usually experience a problem when it comes to the unity of command. This is largely due to the conflicting orders from the functional and project managers.

Types of Matrix Structure

The matrix management structure can be classified according to the level of power of the project manager. Here are three distinct types of matrix structures that are widely used by organizations.

Weak Matrix ? The project manager has limited authority and power as the functional manager controls the budget of the project. His role is only part-time and more like a coordinator.

Strong Matrix ? Here, the project manager has almost all the authority and power. He controls the budget, holds the full time administrative project management and has a full time role.

Balanced Matrix ? In this structure type, both the project and functional managers control the budget of the project. The authority and power is shared by the two as well. Although the project manager has a full time role, he only has a part time authority for the administrative staff to report under his leadership.

Successful companies of today venture more on enhancing the abilities, skills, behavior and performances of their managers than the pursuit of finding the best physical structure. Indeed, learning the fundamentals of the matrix structure is essential to maximize its efficiency. A senior executive pointed out that one of the challenges in matrix management is not more of building a structure but in creating the matrix to the mind of the managers. This comes to say that matrix management is not just about the structure, it is a frame in the mind.

What Heijunka is & How it Smooths Call Centre Production

The Japanese word Heijunka, pronounced hi-JUNE-kuh means ?levelling? in the sense of balancing workflows. It helps lean organizations shift priorities in the face of fluctuating customer demand. The goal is to have the entire operation working at the same pace throughout, by continuously adjusting the balance between predictability, flexibility, and stability to level out demand.

Henry Ford turned the American motor manufacturing industry upside down by mass-producing his iconic black motor cars on two separate production lines. In this photograph, body shells manufactured upstairs come down a ramp and drop onto a procession of cars almost ready to roll in 1913.

Smoothing Production in the Call Centre Industry

Call Centres work best in small teams, each with a supervisor to take over complex conversations. In the past, these tended to operate in silos with each group in semi-isolation representing a different set of clients. Calls came through to operators the instant the previous ones concluded. By the law of averages, inevitably one had more workload than the rest at a particular point in time as per this example.

Modern telecoms technology makes it possible to switch incoming lines to different call centre teams, provided these are multi-skilled. A central operator controls this manually by observing imbalanced workflows on a visual system called a Heijunka Box. The following example comes from a different industry, and highlights how eight teams share uneven demand for six products.

This departure from building handmade automobiles allowed Henry to move his workforce around to eliminate bottlenecks. For example, if rolls of seat leather arrived late he could send extra hands upstairs to speed up the work there, while simultaneously slowing chassis production. Ford had the further advantage of a virtual monopoly in the affordable car market. He made his cars at the rate that suited him best, with waiting lists extending for months.

A Modern, More Flexible Approach

Forces of open competition and the Six Sigma drive for as-close-to-zero defects dictates a more flexible approach, as embodied in this image published by the Six Sigma organisation. This represents an ideal state. In reality, one force usually has greater influence, for example decreasing stability enforces a more flexible approach.

Years ago, Japanese car manufacturer Toyota moved away from batching in favour of a more customer-centric approach, whereby buyers could customise orders from options held in stock for different variations of the same basic model. The most effective approach lies somewhere between Henry Ford?s inflexibility and Toyota?s openness, subject to the circumstances at the moment.

A Worked Factory Example

The following diagram suggests a practical Heijunka application in a factory producing three colours of identical hats. There are two machines for each option, one or both of which may be running. In the event of a large order for say blue hats, the company has the option of shifting some blue raw material to the red and green lines so to have the entire operation working at a similar rate.

Predictability, Flexibility, and Stability at Call Centre Service

The rate of incoming calls is a moving average characterised by spikes in demand. Since the caller has no knowledge whether high activity advisories are genuine, it is important to service them as quickly as possible. Lean process engineering provides technology to facilitate flexibility. Depending on individual circumstances, each call centre may have its own definition of what constitutes an acceptably stable situation.

Contact Us

(+353)(0)1-443-3807 – IRL
(+44)(0)20-7193-9751 – UK