Users of a program found that sometimes, when they went to log in, they did not get a place to enter the username & password. Instead of the normal login prompt, they got a blank screen, and it was completely impossible to login. Sounds like a bad bug that needs to be fixed immediately, but the development team response was even more surprising: this was the user's fault!
The discussion came up of how to improve usability of the system. One position was to hire a usability expert to draw us a specification of a highly user friendly system, and then deliver that to the development team to implement it. There are several reasons why that will not work.
The image of being forced to jump through hoops is one of being required to take arbitrary actions in arbitrary orders just to satisfy some goals that are either unseen or at least not in the interest of the user. Some software is like that. You have to perform functions that you don't want to do, that you know you are going to get rid of, in order to satisfy some internal constraint of the software.
People talk about usability of software as if it was something separate from the software itself. Usability expert skills are distinct from those of programmers. And yet, usability is affected by many deep aspects of the software. It is essential that all programmers on a project be aware of the usability goals of the entire project.