I think but am not at all confident that you think the unhelpful munchkinry is so prevalent and multiple rejections are sufficiently common as to make this technique useless.
Pretty much.
If “true rejection” allows multiple reasons for rejection, not just one, and isn’t used as a gotcha, I have no real problem with it, but the difficulty of genie-proofing it and the ease of using it as a gotcha make it not work very well in practice.
This is also one reason I oppose bets.
I have some direct experience with
if the potential customer says, “It seems good, but you don’t have feature X,” that may not be the true rejection. Fixing it may, or may not, change anything.
But that sounds like the multiple reason case. If the customer has multiple reasons why he doesn’t like the product, and he’s only stated the biggest one, the customer may be unsatisfied after you fix it. Claiming “the customer didn’t state his true rejection” assumes that a true rejection can’t consist of multiple reasons. And even if the customer did phrase his rejection in some way that implies that it’s the only reason, I don’t think “failed to state all his reasons” is meaningfully like “didn’t give his true rejection”.
Pretty much.
If “true rejection” allows multiple reasons for rejection, not just one, and isn’t used as a gotcha, I have no real problem with it, but the difficulty of genie-proofing it and the ease of using it as a gotcha make it not work very well in practice.
This is also one reason I oppose bets.
But that sounds like the multiple reason case. If the customer has multiple reasons why he doesn’t like the product, and he’s only stated the biggest one, the customer may be unsatisfied after you fix it. Claiming “the customer didn’t state his true rejection” assumes that a true rejection can’t consist of multiple reasons. And even if the customer did phrase his rejection in some way that implies that it’s the only reason, I don’t think “failed to state all his reasons” is meaningfully like “didn’t give his true rejection”.