Skip to main content

Why UX is a Critical Component of Functionality

One of the biggest anti-patterns in software development is ignoring the design and appearance of software, focusing solely on “functionality.” In reality, “functionality” encompasses the entirety of a product, not just the parts that perform tasks like updating a database record. It’s unfortunate that final products often get released without the necessary polish that an experienced UX designer can provide, but it happens all the time. And, I get it—deadlines are tight, and things need to get shipped. But, by releasing something as an “MVP” without considering how users will interact with that base-level functionality, we are doing ourselves a disservice.

A Practical, Non-Software Example

A few weeks ago, I had the pleasure of traveling out west. While there, we stayed at a hotel that advertised a pool, gym, and other amenities you might expect. The online presentation looked good, so we booked it.

Now, a gym typically includes a section for cardio, weightlifting equipment like a set of dumbbells and a bench, and maybe a machine or two. There’s a wide variety of implementations within these requirements across various hotels—some better than others. Regardless, they all fulfill the basic function of being a gym.

However, what I found on my most recent stay was a missing component crucial to making gyms usable—the user experience. This particular hotel gym met the basic requirements: there was a bench, a set of dumbbells, and a treadmill. So, you could technically work out there. However, the layout and size of the space made it unusable. It was a narrow, galley-type space where all the necessary equipment was jammed together. Multiple people could fit in the space, but not comfortably or ideally. It would take time to reposition the bench to lift some dumbbells.

Essentially, the layout was so horrible that no one wanted to use it (nor did anyone use it while I was there). This is why the experience matters. Clearly, this space wasn’t designed by someone who actually uses a gym. Sure, the essential equipment was present, but a gym is more than just the equipment. It needed to be a space where people actually wanted to work out. The missing user experience created a literal waste of space.

Why UX Matters as Functionality

From the practical example above, we can learn that essential functionality includes the user experience (not just the widgets that work within an application). What good is your application if it appears so janky that no one wants to use it? UX is not an afterthought or a secondary implementation concern. Your new feature only gets to be rolled out once. It has one shot at making a good first impression. How you incorporate the user’s experience through empathy and good design standards will determine how hard you have to work at getting something new adopted.

So, ignore the user experience at your application’s peril.

If you found this helpful, please share it with your colleagues, friends, boss, etc. Also, feel free to start reading my Agile Laws series here.

Thanks for reading!

Agile ↑

David Bjarnson

David is an agile practitioner for 6 years in various capacities working specifically on software development for a number of different companies. David has his CSM, CSPO, CSP-PO, CSP-SM, and PMI-ACP certifications.

Leave a Reply