How well is your User Experience Defined?

No Comments

In the ever more digitally transforming world where users have begun to interact with each other and the businesses on a customized integrated dynamic platform, improving user experiences has become pivotal in adding business value. The emphasis here is on Usability, Performance, Capacity, Reliability, Availability and Security of the applications. Quantifying these qualitative factors will lead to defining, improving and managing user experiences. Though each is an extensive study within itself, I would like to prod my understanding with a few fundamental questions. Please apply them to the application environment you are working on and feel free to share your insights.


  1. Has the psychology of the users been captured well enough to suitably build the mockups, prototypes and wireframes inorder to get buy-in?
  2. To what extent have the human factors been considered?
  3. How broadly was the heuristic evaluation and feasibility study done?
  4. What is the ease of use and integration with the other applications?
  5. Does the interface appeal to the users and reflect their needs?


  1. How is your application behaving in terms of speed?
  2. Is your application exceeding the budgeted service level agreements?
  3. What are the industry performance standards for these transactions?
  4. What are your management’s acceptable thresholds towards latencies?


  1. What are your sizing parameters?
  2. What factors constitute the sizing parameters?
  3. How will you compute the values for each of these parameters?
  4. Are the systems capable of handling unexpected variations in workloads?
  5. How much variation can the existing systems gracefully handle?
  6. What is your projection for future trends?


  1. What is the rate of pass and fail of your transactions (include transactions, sub transactions across all the systems and sub systems)?
  2. Do the total count of all the transactions within a user’s single transaction match with the transaction delivery process defined for that particular transaction?
  3. What factors constitute reliability?
  4. What exactly qualifies a transaction as successful?


  1. What percentage of the time is application available?
  2. What are the industry standards for downtime?
  3. What are your contingency plans for downtime?


  1. Why is security important?
  2. Are you conforming to the security standards?
  3. What is the cost of non-conformance?

User satisfaction is the Key. I am sure these questions forced you to think about your stakeholders satisfaction?

Leave a Reply

Your email address will not be published. Required fields are marked *