close
Explore
Reading time = 3 min

3# Work flow to design a group chat

General infos

The client

MEGA is a global technology company focused on security, privacy and performance for storage and sharing since 2013. In 2016, Mega released its Chat end to end encryption product.

Background

After many updates and features added to the Chat product, research through user testings and interviews have been conducted in In Feb/March 2023, in order to receive feedback and identify pain points from users.

Timeframe
1 sprint
Rôle
UX/UI Designer
Team

1 Product Owner

1 Business Analyst
1 UX/UI Designers

Contribution

Research / Interview

Design thinking

Wireframes
Prototype
Testing

The Problem

Currently, the process of creating the group chat is confusing, which causes frustration and delays in communication. 

User story

As a User of chat/meeting application,
I want to be able to easily create a chat group,
So that I can communicate with specific participants and collaborate effectively.

Acceptence criteria

As a User, I expect to be able to do so easily and quickly. 

I also expect the application to provide clear instructions on how to
create a chat group, including information on how to add or remove participants, change the group name and customise group settings. 

The result

We cut the process of Creating a Group Chat by 5.

Comparing to current experience, 1 click allows user to access contacts and settings, then start the conversation.

The result

We cut the process of Creating a Group Chat by 5.

Comparing to current experience, 1 click allows user to access contacts and settings, then start the conversation.

Findings and insights from Users testing and interview report.

When tested on "Create a new group chat" task,

all users clicked on ‘Add participant’ to an existing chat as a way to create a group chat

instead of clicking on "New Chat’" then "New group chat"

When asked on why they clicked on ‘Add participant’, they said that “New Chat” implied creating a 1:1 chat while being asked to create a “Group Chat“

Findings and insights from Users testing and interview report.

When tested on "Create a new group chat" task,

all users clicked on ‘Add participant’ to an existing chat as a way to create a group chat

instead of clicking on "New Chat’" then "New group chat"

When asked on why they clicked on ‘Add participant’, they said that “New Chat” implied creating a 1:1 chat while being asked to create a “Group Chat“

Competitive analysis research

Do we have to re-invent a Group chat tool ?


“... By leveraging existing mental models, we can create superior user experiences in which the users can focus on their tasks rather than on learning new models.”

Based on Jakob’s Law, I decided to run a competitive analysis on similar desktop/web products : Microsoft Teams, Slack, Telegram and Google chat, and scoped usability, flows, user guidance and user entry...

There were good and bad in every product.

No items found.
Competitive analysis research

Do we have to re-invent a Group chat tool ?


“... By leveraging existing mental models, we can create superior user experiences in which the users can focus on their tasks rather than on learning new models.”

Based on Jakob’s Law, I decided to run a competitive analysis on similar desktop/web products : Microsoft Teams, Slack, Telegram and Google chat, and scoped usability, flows, user guidance and user entry...

There were good and bad in every product.

From competitive research and current experience Analysis

My thinking

1) Will creating a more visible "New group chat" button solve the issue and make 'adding more participants' easier & obvious for the user ?

2) Is the understanding of adding multiple participants the core of the problem ? as Chat & Group Chat are still Chat.

No items found.
From competitive research and current experience Analysis

My thinking

1) Will creating a more visible "New group chat" button solve the issue and make 'adding more participants' easier & obvious for the user ?

2) Is the understanding of adding multiple participants the core of the problem ? as Chat & Group Chat are still Chat.

Developing

Flows

Wireframe + Prototyping

After creating the basic layout and structure of the pages, for both versions and receiving feedback, I refined the wireframes into interactive prototypes that showcase the functionality and user flow of 2 versions of our group chat. These prototypes serve as support for the next steps to determine which design performs better in terms of user engagement and satisfaction.

No items found.
No items found.
No items found.
No items found.
Testing

To know which version perform better I conducted A/B user testing.

As we already have an established UI and Design, we set the current baseline result as defined by the research insights, and define conversion goal as per the User story and acceptance criteria. Completion of a group chat + add / remove participants and edit settings.

No items found.
No items found.
No items found.
Reiterations

To direct users, I decided to limit the options.

I kept the main CTA from prototype A " Start New Chat or group " and limit access to settings to right menu as per observation on first testing but transformed it as a main CTA support for Chat settings interface instead of list of shortcuts, and use icons and labels as shortcuts on central interface.

To keep users on track and help localise in their process, I embedded " Add / Remove participants" and " Chat Options " interfaces inside Lightboxes.

Next Steps

  • Submit to Product owner and Chat/Meeting team for feedback.
  • Conduct Testing on Prototype 3
  • Reiterate
  • Submit to devs
No items found.
No items found.
No items found.

Learning Points

Nothing wrong in doing Competitive research, is good way to identify and use exiting flow scheme - ( Jacob's law)
Question the problem in the brief in order to identify the real problem
Providing more options and shortcuts to users can lead to more confusions, curate the interactions.
Your product is not damned
There is always a solution
c      nsult the uxorcist