|
Nothing to see here. Ammon has tried a bold move to chase big money, used a few common tricks (release on Friday night, opt-out and other dark patterns), it didn't pan out and now he's doing damage control. When the dust settles, he'll give this idea another try. This is all from a corporate playbook, but it seems Ammon hasn't read the entire book. There's a chapter there that tells how to systematically manufacture situations where all the blame flows downwards while all the rewards flow upwards, so when a bold move like this pans out, credit for it would go to the top, and if it fails, blame goes to the bottom. Basically, he should've created a clueless VP of business relations or something of that sort, manufacture the situation where the only way that VP can get a fat bonus is by implementing this shady move (the idea should be delivered via another channel to have plausible deniability later) and watch the action from his armchair. And when it's failed, blame that VP for too much eagerness and fire him with a golden parachute. |
Consider the fact that if Ammon had fully considered this rollout, it would be very obvious to him that this would be the response. The legal ramifications would also have been obvious.
I think the only reasonable explanation is that it wasn’t fully thought through. I think his business being hit hard by the pandemic is a reasonable explanation for that. There’s no way TripleByte isn’t hit hard by this. Rushing a major feature out is exactly the kind of thing he’s supposed to be doing right now. It seems he just thought too much on making the business and tech side of the feature successful, and didn’t give enough time to the human and legal side of it.
Personally I thought his email was way more introspective and revealing than it even needed to be, and I think he’s being genuine.