The behavior of OOo is often non-compliant with basic ergonomy this way. The
ergonomy says, that if program does some kind of long operation, it _should_
notice user about it, and preferably displays some estimate, how long will the
task take to perform.

In contrast, many users complained about OOo's two main problems with that:

1, Starting the OOo. Even on better-than-average machine, it takes several
seconds for OOo to open at least the splash screen so that user is noticed that
OOo is opening. During that significant period of time, nobody knows what's
happening and whether anything is happening either -user is not shure whether
OOo is starting or not. This leads to confusion, multi-starting that even
prolonges the start because more instances are starting simultaneously.
Users are extremely unhappy with that and consider OOo lower-quality program.
User likes and desires to know, what's happening, and specially whether
"computer" obeys his commands.

OOo should display the splash screen from the very beginning of startup so that
user knows it is starting. And the "thermometer" should be more verbose instead
of five jumps until opening. It should display opening status more smoothly.

2, Opening a file, saving file. There are many "vacuum" seconds when user also
cannot figure out, if OOo is doing something, or is frozen, or whatever. Even
with small files, it takes several seconds to display "thermometer" in bottom
line of OOo, and even that one dosen't run smoothly. Typically: first no signs
of life for long time, then thermometer appears, again nothing happening, and
then it jumps to the end, again period of undefined time, and woala file is
open. User is irritated and feared because he dosen't know in any moment during
opening, whether OOo is still alive. For him the behavior looks like dying
heart's EKG.