Skip to main content

Why one size fits all Channel Incentives Design fails? How I used Gray's BAS/BIS behavioral traits help in designing a multi-pronged Channel Partner Incentives program.

When designing channel incentives, I always keep in mind that at the end of the day I am dealing with a human being. Incentive design, therefore, must be aimed at both the rational and emotional side of the account manager or channel partner.
Neuro-scientific and other studies have for some time now established that human beings are swayed by BOTH rational and emotional rewards. In 1970, Jeffrey Alan Gray, a behavioral psychologist, created the BAS and BIS system of behavioral traits. BAS is the Behavioral Approach System and BIS is the Behavioral Inhibition System. Someone with a BAS prefers to acquire more gains so they can be rewarded further. They play to reach for more and want to get rewarded for getting more. They embrace the risk-reward paradigm. On the other hand the BIS folks tend to want to stay put at a certain level and have a fear of losing their status. They fear being downgraded to a lower status level by not meeting their targets.
Taking the same channel incentive design approach for both BAS and BIS behavioral channel partners or account managers therefore is a sub-optimal design. When I designed Channel Incentives for a large Value Added Reseller, I deployed this understanding to good effect. When I started out, I had designed only one channel incentive of paying an additional SPIFF based on volume or revenue targets achieved. When we asked for feedback from the partner, we found that 60% of the partner's reps were not motivated. We researched more and found that not all reps were motivated by reaching for more. That is only some reps exhibited the BAS behavior. Other reps had voiced confidence in their ability to retain an account more and a less behavioral trait toward winning new accounts for volume bonuses. That is, they exhibited more of a BIS behavior.
With the above research in hand I, therefore, designed a second incentive called churn bonus aimed at reps who prioritized keeping the account churn low. After a pilot roll out, we found that 80% of the partner's reps now were motivated and were clear in their incentives design and targets to be achieved to win.
By rolling out both a volume/revenue target bonus aimed at the BAS reps and a Churn/Base Revenue retention bonus for the BIS reps, we found that the reps were selling to set behaviors that not only maximized our business targets for the partner but also the channel partner's targets for their reps.

Comments

Popular posts from this blog

Using Issue Trees to investigate Product Cycle and Launch Challenges is an important arsenal in a product manager's armory

Most of the times, as a product manager, I solve complex problems under constraints within a short 2 to 3 weeks time, while not sacrificing creative thinking. The actual work shown here below demonstrates how I use a technique called Issue Tree Analysis (that I learnt from McKinsey Academy's problem Solving Leadership Program that I was nominated to attend by my company GE Digital) to investigate in a structured yet creative way. Structuring the issue as a SMART (Specific, Measurable, Actionable, Relevant, Timely) problem  and ensuring the identified issues were MECE (Mutually exclusive, completely exhaustive) were the most significant challenges I faced. On the positive side, such issue trees helped me capture a 360 degree view of the impacts solving the problem would have and help cover any unexpected failures due to major risk items not being identified for mitigation.

Quantum Cloud Computing (QC) and Killer Apps built on it can help create products with life-changing feature experiences. So, what's happening?

I have always wanted to write an article that explained why I chose the Q-bits background image for my LinkedIn profile. For those who follow the evolution of quantum computing and know its intricate evolution path, they will readily see the disruptions a quantum cloud compute environment is all set to produce in the near-future. Others- mainly the skeptics, the curious and the uninitiated, please read on. I may end up changing your world view on Quantum Computing and what is can do for us, homo sapiens and the planet we inhabit. Of course, I am not saying we have the first Quantum Computer available for sale on an e-commerce site and SW vendors are shipping applications that run on Quantum computers. There is still the issue of non-availability of a taxonomy-defined instruction set needed to actually program Quantum Compute (QC) machines, even if the hardware could be prototyped. But, to think that articulating a quantum processor instruction architecture set is...

Are you weaving human beings' 3 basic behavioral cravings (Competence, Autonomy, Connectedness) into the very fabric of your product design, UX, marketing, support, the entire launch cycle? If no, you should.

Think about Maslow's hierarchy of needs (see Maslow's hierarchy of needs ) and the basic needs he espouses: his pyramidal hierarchy of needs meets our physical existential requirements. But there is also the behavioral cravings that humans have and that also has a hierarchy of needs. For a product, there is also the need to meet a customer's psychometric or behavioral needs. And, again, there are basic behavioral needs that are at the bottom of the pyramid. As a product manager, ask yourself, if your product appeals to the 3 basic behavioral needs that each of us exhibit in our lives and how the product addresses those needs. Psychologists have identified 3 basic needs that most of us want to have a grip on: Competence, Autonomy, and Connectedness. Are you doing A/B testing where you are taking into account a customer's behavioral needs? Are you incorporating these basic cravings of ours into the UX design? Behavioral need 1: Competence - Human beings have a...