| I ran Product Engineering at a competing startup (hundreds of millions of MAUs) that tested/employed similar flows. And yes, they work in the short-term, and unless you are very principled, it's hard to avoid them. I'm glad you heavily protested them. But I'd like to further the argument for why they should be avoided. First, yes they do work in the short-term. You run an A/B test with some adversarial flow that blocks mobile web traffic users from doing certain things. Most of them get pissed, but enough of them download the mobile app (which allows you to build up their engagement via phone presence and notifications) that the A/B test is positive. Rinse and repeat. A few dozen experiments later, and now these patterns are pervasive across your product. Apart from whether they work (in the short-term), there are three other questions readers of this thread should think about because I'd hate for people to walk away thinking "these patterns are normalized and they work so, sigh, i should just do them too". One is whether they work in the long-term. Yes, you can juice your metrics in the short-term, and sometimes that translates to long-term growth, but it's harder to measure secondary effects. Can you accurately measure product brand damage and quantify the long-term impact? Second, and as an EM you should appreciate this, can you measure secondary brand damage like _recruiting brand_ damage? Dark patterns (and threads like this with hundreds of passionate engineers talking about how much they hate those dark patterns) _will_ damage your ability to hire the type of engineers you want to help you build your product. Finally, there's some subjective ethical question in here. Even if these patterns work in the short and long term, do you _want_ to spend your life, your intellectual energy, your time turning the internet into this? Do you want to go out and hire smart, passionate people and get _them_ to spend their time and intellectual energy turning the internet into this? (side note: I have no affiliation with the author of this post, but I wrote the original Disrespectful Design post he links to in his first paragraph) |
We also worked with growth consultants (read: Bay Area B2C product leads) in scoping out some of these ideas. We accrued what I call "product debt" where we launch the MVP but never followed up to polish the feature[0] as they don't improve KPIs.
I assume this is the same with Growth teams everywhere but am happy to be corrected.
Regarding long term impact, we measured this through various dimensions in marketing, recruiting, and user research. The outcomes are largely positive.
______
0: One feature I argued for was an opt out of the mobile app interstitial. It makes sense to show it once or twice, but users aren't going to download the app just because they saw it 50x.