He wasn’t actually giving a blanket directive. The article was suggesting that you think about whether 98% is actually good in your use case by doing the math and thinking.

Yeah, but the guy writing the article seems to be bad at math and thinking.

Can I imagine a venue kicking out 2% of their former clients on some criteria? Absolutely yes.

Kicking out 2% of website visitors may still be totally reasonable if the cost to serve them is meaningful, or if they are less than 2% of revenue.

His defense for 98% being bad is that some CSS thing people were arguing about only had 70% coverage on his website.

Our b2b dashboard didn't support Safari for a while at all and it was entirely not an issue because everyone had a simple workaround to just use Chrome and the dashboard wasn't really the main product.

Except there was 0 analysis of the cost/benefit of supporting the end of the long tail, instead it was just economics-free shaming. Of course, you want to see who those 2% of users actually are. But nowhere in this article did I find any advice I'd actually want to use in a really business scenario.

I mean the name was "98% isn't much" and the article made it sound like 98% isn't good enough