Showing posts with label Organisational Change. Show all posts
Showing posts with label Organisational Change. Show all posts

Saturday, 8 October 2022

How to create a handover system in a sales team

If you work in sales, chances are, your CRM or funnel system is a fairy tale - stuck in the past with very little connection with the reality of the world. 

Handovers in sales teams are especially difficult. It is not the fault of organisations or individual employees. Nor is it that the sales team does not want to do handover to the new team members. 

So: 


Why are handovers in sales such a pain? 

1. Because sales is a personal thing. A client is dealing with a person, not a company. All salespeople use their personal charm and knowledge to create great solutions for clients. Sales Team member A is not replaceable with Sales Team member B. One does not write everything. Because one cannot. For instance, I know that the CIO at Firm A values cost cutting above all else. The CIO at Firm B loves Ayn Rand. These are not things that matter to a formal sales process. This is one individual interacting with another individual. 

2. A lot of communication (and commitment) in sales is oral and undocumented. Whether we like it or not, this is what it is. 

3. There is sometimes a gap between the exit of one team member and the joining of the replacement. So, the handover time is either too short or nonexistent. 
 
4. Some clients will leave with the salesperson. That is how it is. 

How to make handovers work? 

First things first, handovers and takeovers are a function of two things: 
A. Person to person (and their time and personality overlap) 
B. Documentation maturity. 

A is a function of how nice the two individuals are, how well they get along, and how much time they have with each other. 
But B is a function of organisational process maturity. An organisation with a culture of process documentation and audits at the right time will find that much of its pain of transitions and audits will vanish.  

But in sales, A is as important as B. 

What do we do then, to ensure smooth handovers in sales? 

Enter: The Magic of Shadow 

This solution requires: 
A. A camaraderie within the team 
B. A small reporting span for sales leaders - no more than 4-5 people per sales leaders. Not a pack of 15-20 sales professionals reporting to one. 

What we need to ensure is adequate information redundancy (i.e., the information should be with more than one person so that if one person is not available, another person should know whats going on). 

The format is that once a week, the sales leaders take individual calls on which the events of the week are discussed. The sales leaders are free to take notes etc. But they are the redundancy/backup. This is because in sales, it would be unfair for people to be backups of each other, given the intense competition in sales. 

Being the information back up of their team is on the KRAs of the sales leader. They are required to meet with clients and potential clients at least once every 5 visits by the team member. That is why a small span of control is vital for this model to work. 

When a team member resigns... 

If a replacement is ready, they are immediately assigned to shadow the outgoing team member. If the replacement is not ready, the sales leader can take a call and assign another colleague or act as a shadow themselves. The latter option is not the best idea but sometimes one may not have a choice. 

This shadow remains with the outgoing team member till their last working day. 

Signing off on Knowledge Transfer 

One week before exit, there is a joint meeting which includes the outgoing team member, the sales leader, and the shadow. This is the formal KT sign off meeting. In this meeting, the process is as under: 
A. The shadow goes over the list of clients being managed by the outgoing team member and specifically lists: 
    i. The Scope of work  
    ii. Important client stakeholders 
    iii. Current stage 
    iv. Other competitors in fray and their relative standing 
    v. Timeline of decision and delivery 
    vi. Internally, who are our stakeholders for delivery of order 

B. The sales leader compares this information with their own notes to ensure that: 
    i. All clients in the team member's charter are covered. 
    ii. All details are covered and are accurate. 
    iii. In case of some clients, the sales lead can ask additional questions to ensure that the shadow knows everything that they should know. 

If the sales leader is convinced that handover has happened, they can sign off on the process. 

If the shadow falters on any information, the person who is penalised is not the shadow but the outgoing employee. Their exit checklist can only begin with this handover signoff. 

Once this signoff as per the checklist is given, the outgoing employee and the sales leader cannot then question the shadow on why they did not ask the outgoing employee x or y. The responsibility for signoff therefore is with the original backup - the sales leader. 

If the Signoff fails 

If the first signoff at T-7 fails, a second sign off is scheduled anytime from T-3 to T-0 day, based on everyone's convenience. 

The second sign off is the final signoff. 

The same checklist is followed this time too. 

If the sign off is cleared, the outgoing team member can begin their exit checklist and other exit formalities. 

If the sign off is not cleared, the exit formalities cannot begin. 

No sensible employee will want their exit formalities to be delayed. This process ensures that everyone is invested in ensuring a smooth and complete handover. 

When the replacement joins

When the replacement team member joins, they then work alongside the shadow for 1 month or more, and then the sign off process with the sales leader is repeated once again. Only after the handover sign off can the team member holding additional responsibility get off. 

But, shadowing is extra work! 

Yes, and this should not be ignored. The performance management framework needs to reward employees who act as shadows while a replacement is being hired. This can be in regular KRAs, or be noted as "Exceptional Contribution" based on how frequent this is. Sales is a stressful role as it is, and any extra work deserves to be acknowledged and rewarded in a structured framework.

Other linkages with PMS 

The other linkages that need to be established with the formal performance management system are: 
A. Sales Leader - Ensuring smooth handovers should be the KRA of the sales leader. Zero tolerance for client loss due to team attrition needs to be laid out. 
B. Incoming Employee - If the replacement is a new hire,their "Time to Productivity" and rampup roadmap should be in their KRAs. If process documentation and shadowing is in place, this rampup should not exceed 40-60 days. 







 

Tuesday, 5 January 2021

How to stop your KMS from being your MIS

This was a very interesting discussion. An organisation had just set up their KMS and were wondering about information structure. 

The project manager asked a very intelligent question - How do I ensure that my KMS does not become a document repository, and remains a knowledge warehouse? 

Here is, in brief, the answer: 

What goes into a KMS? 

To understand what goes into a KMS, we have to understand what a KMS is. The best way to understand what a KMS is, is to know what a KMS is NOT. KMS is not: 

MIS 

It is not meant to give you timely information on your operations and help you monitor business as usual. 

DMS

It is not a Document Management System. It is not where you dump all your reports, proposals, policy documents, etc. 

DSS

It is not a Decision Support System. All information in the KMS repository is, by and large, time agnostic. Like the Vedas and Amar Chitra Katha, the wisdom in it is for a long time, of course, updated with the times. But not time sensitive. That is the crucial aspect. 

A Knowledge Management System is just that - a system to manage the knowledge in the organisation. 

So, to be counted as knowledge, an artifact / document must be: 
A. Time agnostic
B. Be applicable in a wide variety of domains. If it is specific to that one project, that one report, and that one employee, its not KMS worthy. 
C. Be clear about the knowledge it imparts. 
D. Ideally, help a person connect the dots and lead to some business value.
E. Must not include any confidential information / company identifiable information.  

Some examples of good KMS usage 


Katy is looking for ways to quickly do effort estimate on her bids. Obviously, the information is incomplete, and she has to do her best. She finds out, over a period of time, that if she has some key data elements, she is able to give a bid that is very close to the actual costing + margin of the organisation. 
So, she prepares a questionnaire that has all these data elements. 

Now, whenever the bid team receives a RFP (request for proposal) , it sends this questionnaire as its standard list to the client. The bid team then has the info it needs to create a clear bid in a short amount of time. 


******************* 

Raghu, the Finance head, is sick of asking departmental heads for TCO (Total Cost of Ownership) before approving their capital procurements against Budget Line Items. 

Exasperated, he creates a TCO Calculation template that he just uploaded into the KMS. Now, before sending the proposal, everyone looks at the TCO calculation template. This has also helped other department heads identify the hidden costs in their procurements, which were earlier blind spots. 

************* 

How to ensure the success of your KMS

  1.  Keep a tight gate on what gets in. 
  2. Incentivise reuse of artifacts as much as possible. 
  3. Monitor usage at all times. Even plants atrophy without fresh air and anything left untouched starts to decay. KMS is not a dead system. It is a living, breathing system that supplies vital nutrients to your organisation. 
  4. Guard against plagiarism. It is unfortunate, but not rare, for employees to copy stellar documents written by someone else and submit them as their own KMS submissions. 
  5. Incentivise participation. If people are hesitant to create documents, give them sample documents and offer surprise prizes for lucky submissions. Hold a contest once a month every 6 months - for both submitting and using artifacts. The contest for using artifacts will also give you the case studies that you need to create emails about KMS use. 

How long does it take? 

6 months. This number is usually independent of the organisation size. It will take people about 6 months of consistent, persistent reminders to make a habit of using KMS as a regular part of their work. Plan your Change Management for 6 months, and keep plenty of budget. 

And Finally: 

What makes a good Knowledge Management System