Many such cases - Lemmy.ca

I think most of the complaints are that Microsoft Office doesn’t work. Which is true. The web version of Microsoft Office is honestly kinda terrible.

And no, people don’t want to use a product that does the same thing as Microsoft Office, they want to use a product called “Microsoft Office”. No, it’s not logical, and doesn’t make any sense at all but it’s how people are.

The only sense it makes is that M$ hasn’t followed the spec, and so things done in office display fine I’m say libreOffice, but not the other way around. So if you’re company is willing to transition, but everyone you deal with outside the company is still on Office, there’s a bit of a communication issue. That’s M$'s biggest strength, homogenous work environments.
That’s why my business only uses pure, crisp .txt files. If I can’t open it in notepad, I don’t want it!
I have unironically been preaching the powers of text and JSON, and have some converts. Universal compatibility is great.
Json is a garbage format for anything that’s meant to ever be touched by a human. At least use yaml or json5.

In the first paragraph of JSON5’s site:

It is not intended to be used for machine-to-machine communication.

YAML is not supported by a lot of enterprise software (example: Azure pipelines supports it but Power Automate does not). JSON, XML, CSV, or failing that Text are the safe bets. We use a few options for reading or building presentation layers quickly.

It’s absolutely trivial to convert either format to json if necessary. The real killer for me with json is the lack of comments. Human-maintained files absolutely need comments.
With markdown or asciidoctor or restext or … you get both worlds.