In this short post, I wanted to share some metrics that I have recommended to my own team as well as consolidate some views from experts that I have been exposed to. One key area is the participation rates. Participation rate is defined at a sales team level and is calculated typically as the number of reps in a team that attain 100% or higher of the set quota levels. For example, in a 4-person sales team, Rep A attained 60% of Quota, Rep B attained 120% of Quota, Rep C attained 30% of quota, and Rep D attained 90% of quota. This sales team then has 1 rep out of the 4 reps attaining at 100% and above, or a 25% participation rate. Note that the average attainment is 75% for the team but the bulk of it came from 1 or 2 reps, an untenable situation. A 25% participation rate is considered a poor participation rate and sales leaders have to understand the root causes of why certain team members are not able to achieve at their quota levels. Rep C at 30% attainment most likely won't be paid any variable commissions and therefore is likely to leave the company. A good rule of thumb is to expect 80% of your team to attain 100% and above and the remaining 20% to attain at least 80%. This would generally ensure an 80% participation rate and the average attainment of the team would likely be between 95% and 100%, a position no sales leader is going to begrudge. Every situation requires a different approach but an efficient sales leader's goal should be to maintain not only a high attainment but also a high participation rate for their teams. Happy selling!
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.
Comments
Post a Comment
Please be responsible with your comments. No cursing or derogatory words please.