Skip to main content

User Experience (UX) Design


Understanding UX Design as a Product Manager.

User experience

The international standard on ergonomics of human-system interaction, ISO 9241-210, defines user experience as "a person's perceptions and responses that result from the use or anticipated use of a product, system or service". According to the ISO definition, user experience includes all the users' emotions, beliefs, preferences, perceptions, physical and psychological responses, behaviours and accomplishments that occur before, during and after use. The ISO also list three factors that influence user experience: the system, the user and the context of use.

User Experience (UX) Design

User experience (UX) design is the process design teams use to create products that provide meaningful and relevant experiences to users. 

  1. Research
    • Understanding: Conducting user interviews to identify their Requirements.
    • User Personas: Represents a typical user to identify their goals, frustrations, etc.
    • Use Cases: How might different people use this product or service?
    • Journey Maps: How a user might start and finish the experience.
  2. Brainstorming
    • User flows: Diagrams that outline the steps a user might take during the experience as they go from step to step in the UI.
    • Wireframes: A rough skeleton representation of the UI and the various components that make up the UI.
  3. Implement
    • Prototypes: UI Designers create low or high fidelity prototypes, which may or may not be interactive.
    • Frontend & Backend Development: Once prototypes are approved, developers make the prototype a working product.
  4. Reporting
    • Usability Reporting: Observe real users using the product through a variety of means.
    • Split Testing: Testing the effectiveness of one design iteration over another.
    • Analytics Reporting: Gaining additional insights such as time spent on pages, bounce rates and more.






Comments

Popular posts from this blog

Ethnographic Research: Unlocking Deeper Insights in Early Adoption Programs

Why Ethnography Matters in Early Adoption Ethnographic research immerses product teams in the real-world environments where users interact with prototypes or new features. Rather than relying solely on surveys or lab tests, ethnography emphasizes observing and engaging with participants “in the wild.” In early adoption programs—where a small cohort of power users tries out pre-release software or hardware—this approach yields rich, context-driven feedback that accelerates refinement and fosters genuine user advocacy. Advantages of Ethnographic Research Ethnography offers three primary benefits in early adoption contexts: Uncovering Tacit Knowledge Users often perform workarounds or subtle habits that they cannot articulate in interviews. By shadowing them, researchers see instinctive gestures—menu sequences skipped, custom keyboard shortcuts invented, or sticky notes left on physical dashboards—that reveal hidden pain points and unexpected value drivers. Contextual Understan...

Aim to be Understood and Respected

As a product manager we deal with different stakeholders of the organization; like marketers, tech support guys, designers, developers, HRs, SMEs and even C-level executives. Most of our interactions aim at- Getting approval for proposals or work orders. Getting acceptance for solutions/work arounds. Requesting budget or resource availability. Resolving conflicts. In my opinion - being assertive is the key to succeed in such conversations. Assertive Communication is the art of expressing our thoughts, feelings, and opinions in a way that makes our views and needs clearly understood by others, without putting down others thoughts, feelings, or opinions. It is an effective tool for constructively resolving conflicts and achieving results. Following are some tips to communicate assertively with Stakeholders: Be clear on what you want and why you want something Quantify impact of not getting it Know all your alternative options  Be honest and direct in your communication Hold on to you...

Competitive analysis

As a product manager we aim to build a product, that meets the customer need, better than any other product in the market. We aim to not just satisfy the customer, but to delight him or her with our offerings; and while doing so we gain a competitive distance/advantage.  To maintain this competitive distance we need to monitor and analyze our competitors. This activity needs to be done religiously basis a predefined schedule and predefined format to record the findings. I have been using the below competitive analysis matrix and updating the same on a quarterly basis.  As it can be seen every row monitors a feature and compares it along the top contenders in the market. Analytical findings of this study is recorded in the last column. Product Roadmap can be updated accordingly. Conclusion:  Product Manager needs to be aware that the same activity of 'competitive analysis' is being done by the Product Managers of the contender products too. Thus, it is important to build '...