I hear you, zhawks. And I agree where there's one, there's more. In this case, there are likely several HD customers who would return or up their number of teams if the price were lowered. I think you and I disagree as to how many, but we agree that it is a factor, and we also agree that engine/design issues are ultimately a better fix for customer retention than price, and that they are months away from those fixes (even if thoses fixes are actually what the doctor ordered).
Now that I think of it, if I'm WIS, my thinking might be: 1) we want to get customers back, and once they're back, we want to keep them; 2) let's get the design/engine fixed up to make most existing customers happy 3) if our current customer base reacts negatively to our fixes, we'll get the fixes right BEFORE we put forth other efforts to grow our customer base 4) once we have our current customer base relatively happy (our customers LIKE our product), we'll see what we need to do to increase customers further (price drops, reward points, etc.) 5) What we do NOT want to do is do #4 first, then alienate many of our customers with new and/or more teams with poorly-implemented fixes (as we've done in the past).
You think maybe they're approaching it like so?