Those actually are valid points, but he could have clarified it a bit. If people despise it and either A) start publicly berating the IT organization or escalating to the C-suite or B) stop being productive because they can't stand the software, it's a problem.
Formatting is a problem, especially when collaborating on complex Word or PowerPoint documents. Excel & Calc are the most interoperable. Also interestingly, OO.o (I'm basing this post on the OO.o v3.3 beta) is more compatible with MS Office 2007 than MS Office 2003 is, so your mileage may vary depending on the status quo.
Training is a problem, period. A lot of the menus -- and menu icons -- in OO.o are not logical, and it is extremely obvious that Microsoft invested mountains of cash in UX research. Not that MS Office is perfect, but since most people have been using it for a decade or more the incremental changes across versions make it much easier for them to familiarize themselves with subsequent updates. In a lot of ways, I'd compare the UX of the two like this: OO.o:MS Office::GIMP:Photoshop. The GIMP works great but is missing some functionality that a small subset of users find critical, and the multi-window UI is confusing.
extremely obvious that Microsoft invested mountains of cash in UX research
Maybe, but they also benefitted from being there first. When organizations made the switch, they realized they were going to have to train everybody (I was with a huge organization in the '90s when all of this went down). They were only going to train on one system. In our case, we picked MS Office. Thus, good UX or bad UX, that's the UX that everybody learned. Organizations were dumping huge resources just into training, and all of that went into learning how to use MS Office.
Formatting is a problem, especially when collaborating on complex Word or PowerPoint documents. Excel & Calc are the most interoperable. Also interestingly, OO.o (I'm basing this post on the OO.o v3.3 beta) is more compatible with MS Office 2007 than MS Office 2003 is, so your mileage may vary depending on the status quo.
Training is a problem, period. A lot of the menus -- and menu icons -- in OO.o are not logical, and it is extremely obvious that Microsoft invested mountains of cash in UX research. Not that MS Office is perfect, but since most people have been using it for a decade or more the incremental changes across versions make it much easier for them to familiarize themselves with subsequent updates. In a lot of ways, I'd compare the UX of the two like this: OO.o:MS Office::GIMP:Photoshop. The GIMP works great but is missing some functionality that a small subset of users find critical, and the multi-window UI is confusing.
I could go on....