Frustration: the feeling of being upset or annoyed, especially because of inability to change or achieve something.
It’s a feeling we all have experienced at one time or another, whether it was because of something as big as a delayed flight that strands you at the airport, or something as small as when the burger you ordered without pickles comes with pickles. It’s natural to find yourself in frustrating situations throughout the normal course of life. But these were personal examples. What frustrating situations do you find yourself in at work? Perhaps it’s an ineffective teammate, or a broken coffee maker, or an important piece of software that is just plain hard to use.
In a perfect world, end users would get to select the software that they have to use on a daily basis in the course of their work, but alas we don’t live in a perfect world. In our imperfect world, the typical approach to dealing with software that is ‘hard to use’ is to try to somehow improve the end user. We write extensive training guides, we attend weeks-long training classes, and we cover our desks with hand-written sticky note reminders, all in efforts to make the end user more proficient at using the software.
But what if this notion was flipped on its head? What if instead of focusing on improving the end user, we focused on improving the software itself? What if instead of forcing users into the mold of software that is not a natural fit, we fit the software to the way the user does his or her job? And what if there was software out there that enabled us to do so without custom code, without ripping out the existing system, and to do so in weeks, not years?
That world would probably be a lot less frustrating.
In this blog series, we’ll examine frustrating situations where a change in software could relieve a whole lot of stress for the people involved. We hope you’ll come along for the conversation!
Note: This is the first post in Clear Software’s “Frustration” series. Check out the other posts in the series below!