Skip to main content

"User Experience" - A Game Changer to make a Product Successful

User Experience is a game changer to make a product successful

[U]sability exists in the experience of the person. If the person experiences a system as usable, it is. A commitment to designing for people means that, at base, we must accept their judgement as the final criterion for usability […] The starting point for usability engineering must be the uncovering of user experience.

- Whiteside and Nixon, 1987 

(Understanding UX)


UI (User-Interface) design and UX (User Experience) in the software world is a hot market today, as gradually many organizations have started “experiencing” the need for it.

A few years back, when I was tasked to find and evaluate the best recruitment software by my team, it opened my eyes to this most amazing thing about ‘User Experience’. At the end of my task, the only software application I could recommend was with the ‘best’ user-experience. We had a constraint on how much we wanted to spend, but at the same time, we also wanted to save time of a team member – which became even more important. When we evaluated the value from a software with the best user experience, we were astounded by the outcomes. The savings on our precious team-members time for recruitment activity was huge!! This was apart from the frustrating experience they may have had to go through managing a large amount of candidate’s data.

Initially, I used to wonder… What’s the big deal with designing a software User-Interface? But now, after going in-depth in understanding this field, the implications to develop an application are exceptionally high!

So, what I am driving at… over here? The conclusion is very simple…

‘User Experience’ as a result of ‘UI and Workflow design’ is a game changer to make a product successful in this highly competitive market.

Let’s start with understanding… What is “User Experience (UX)”?

A very succinct definition of UX is given by the author of this blog – UX Definition as

User experience refers to the singular and accumulated experiences that occur for users because of them interacting with an object in a given context.

From the software development perspective; from my experience, the below pointers would help you to understand, how BIG UX impacts application development. For a user, a good experience with an application means…

  • Great UI Design: The pages designed are objective oriented, de-cluttered, have simple workflows, right colors (based on target audience type) and content is placed correctly at the right places.
  • Integrated Field Behavior: The fields on a page should be weaved along with each other using business rules. It should be easy to manage data across multiple features.
  • Modularity for Developers and Users: Page design should use widgets or modular features (plug and play), that allows for ease of application maintenance. This in-turn leads to less stress for the application users. 
  • Less is More (Simplicity): Well-designed pages should have limited fields with powerful features / functions.
  • Content Type: Better UI designs have special content at the right places, which enables more usability of the application.
  • Unique Insights: Well-designed pages also offer important & correctly phrased information that their target audience loves.

A lot of my own insights have come from my experience managing application development and my reference to this amazing site - https://goodui.org/. I highly recommend all the software developers to go through all the points here, given by its authors.

Why is UX so important?

UX has a far-reaching impact, as building an application user interface is a result of the user’s behavioral patterns. The below points would surmise this.
  • Pleasant User Experience: One of the important quality objectives for application development is “customer delight”. The most important of all to get to this is by giving a pleasant user experience, when using an application UI. This also ensures, that the user can stay or keep using the application for a longer period without getting stressed / frustrated.
  • Positive Impact on Memory: Users remember well-designed sites very well and for a long time in future. A unique design, that blends well with a pleasant experience can ensure this very well.
  • Less Stress for Mundane Work: A good UI design ensures less stress for users to perform mundane daily jobs, such as typing-in data, mouse-clicks, page-scrolling etc… A lot of research has already gone into reducing extra physical work for such jobs.
  • High Application Integrity: An important, but most often ignored aspect when building an application is to ensure, that the functions of a feature doesn’t break another feature due to non-existing constraints on data. A well-designed application UI always takes care of this aspect. Even bigger impact is on the user-experience, if user data is smartly auto-updated based on certain rules. For example, the sex of employee can be auto-defaulted to a female, if the first name entered by the user matches any existing female’s name in the database.

How can software engineers build better applications with a better UX?

The most important aspect of building an “amazing” software application is understand the “Core Need” of users. The best way to understand this is – to think of the below “user perspectives” first.

  1. Time Spent using the Application: Is the user going to do his / her primary job “using” the application or his / her core work-area is something else?
  2. License Fees for the Application: Is the user “interested” to pay a hefty amount to acquire the application? Many target audiences of an app are rich to ‘afford’ the application, but they would still never put the money, since the “value” they expected is not there. Understanding the value first and then pricing it right is very important here.
  3. Efforts for Data Entry Jobs: Is the user ok for “spending time” doing data-entry in order to use the application. If yes, then having long forms is okay, but even after this, an analysis of the most basic required fields is of the utmost importance.
  4. Online / Offline Use: Is the user required to work offline sometimes or most of the times? Even in today’s world, this aspect remains relevant and is extremely important.
After understanding the above perspectives, below are some of tried and tested ways to build amazing applications because of a good UI design –

  • Learn simple UI design tricks (for example, de-cluttering a page by smart grouping of fields etc…)
  • Strictly ‘Plan and Design a Prototype’ before jumping into module designs and core development.
  • Segregate the ‘basic’ UI features as modular components, which are always required for any application. For example – Login pages, User management, validations etc… Make these into best practices for your organization by including requirements management, design, development and testing for such components as a separate activity.
  • Incorporate User Experience practices as part of software process engineering. This allows for re-use, optimization and enhancing knowledge of many more teams across the organization and benefits galore!
- Written by Anand Nanavati (SupraDigit Solutions)

Comments

Popular posts from this blog

Reduce Your App Development Costs by More than 50% by "Simply Preventing Bugs"!

"Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”— Steve Jobs Everybody loves to avoid a disaster, but there is a “proactive” effort to do activities that can prevent a disaster from happening. Most of the executives do not want to “get involved” in such “proactive” efforts, simply due to the love of fixing urgencies Or having a mindset that it’s not important.   I remember, when once I was working with the Quality Assurance team on a product. The development team simply refused to spend efforts on the most essential “unit testing” for their developed components! The intent was to release the software to the QA team as soon as possible and focus more on so-called “core development”. Over the years, looking at multitude of projects failing in-spite of highly experienced resources, reasonable time and the intent, I have uncovered that, prevention is the “Most Important” and “Ignored” part of software development. Why should we

Change the World by Keeping Your Inner Fire Ignited

A decade back, when I was working on a huge enterprise program (with multiple projects) along with a big team (of close to 300 people), we were a group of managers who were evaluated and pushed by the senior management to “proactively” deal with issues and to work on finding new solutions. I used to think of how - we can become “proactive”, when we were already focusing our efforts on fighting our daily “fires” or urgencies of our project work. When I delved deeper into our daily work habits, it struck me that till the time we are not excited about “getting things done”, the willingness to explore more out of our comfort zone just doesn’t happen. The innate human behaviour is to follow a routine and establish a comfort zone over a period. The 1st factor – “an external stimulus” can upset us and force us to think or act out of our comfort zone.  The 2nd factor that can make us “move” out of our comfort zones is about having an excitement of a future or coming up with a vision th

The Confusion Between Software “Metrics” Vs “Matrix”

When I was studying in class 10 th , I asked my English teacher a very basic question about why two words in English sound the same but mean different. That time, we never had a separate subject on “phonetics” and I was quite unaware of this part of the English subject then. She smiled and very smartly told me that – “English is a ‘funny’ language” and went away! I was amused by her answer the whole time. Only later I learnt that in English there are so many words with a spelling, that are used “as per the context” to mean different than their similar sounding words with a different spelling. In quality assurance and in general in project management, many testers and project managers make the same mistake with a misunderstanding and confusing these 2 words – “Metrics” and “Matrix”. They use them interchangeably! Metrics in the quality management context means “to measure” (check its meaning here - https://www.dictionary.com/browse/metric) and … Matrix has different meanings based o