Usability Testing:

    Moderated Testing:

  • A facilitator guides the participant through the test, asks questions, and observes their behavior.
  • I select 5 participants per user group //Nielsen Norman Group recommends 5 users to uncover 85% of usability issues

    Friendliness Bias:

  • Most of the participants in the usability testing group were my colleagues. During the testing, I kept in mind the potential for friendliness bias, as they tended to provide overly positive feedback, such as saying, ‘Yes, I completed the task,’ to avoid offending me. To reduce this bias, I encouraged them to share honest feedback by asking open-ended questions like, ‘What challenges did you face while completing the task?’ or ‘How can we improve this process?’ This approach helped uncover hidden pain points and ensured more accurate and actionable insights."

Before >> After

Feedback One

At the managerial level, I receive too many tickets. If I want to share a specific ticket with a team member, there is no option to share or copy the link of that specific ticket.

This feedback highlights a usability issue in the system, specifically the lack of a feature to share or copy links to individual tickets. This can be addressed by adding a Share button or Copy Link option for each ticket, making it easier for managers to delegate tasks and collaborate with team members.

Feedback Two

While creating a task tree, there is a security issue where some users don’t have permission to open or view other tasks within the tree.

    To address this issue, I implemented active and inactive states for tasks:

  • Active Tasks: Tasks that the user has permission to access and interact with. These are fully visible and clickable.
  • Inactive Tasks: Tasks that the user does not have permission to access. These are displayed in a grayed-out or disabled state, making it clear that they cannot be interacted with.

Lessons Learned

I realized from the start that organization and attention to detail were critical, especially during the research phase. Every insight from user feedback, such as during usability testing, had to be carefully considered without dismissing anything as unimportant or common sense. This approach ensured that no critical pain points or opportunities for improvement were overlooked.

One key learning was the importance of visibility of system status. For example, by adding a progress indicator for task completion, I saw how such a simple feature could significantly enhance the user experience. It provided users with clear feedback on their actions, keeping them informed and confident as they navigated the ERP system.

Re-testing proved to be incredibly valuable. It uncovered additional usability issues that weren’t apparent during the early design phases. This taught me to never assume a design is perfect and highlighted the necessity of continuous testing and refinement to create a truly user-friendly product.