Home > User Experience > Lightsome — Declutter your Institute Mailbox: A UI/UX Case Study | by Soham Mitra | Dec, 2020

Lightsome — Declutter your Institute Mailbox: A UI/UX Case Study | by Soham Mitra | Dec, 2020

Lightsome — Declutter your Institute Mailbox: A UI/UX Case Study | by Soham Mitra | Dec, 2020

How Might We’s :

Based on the inputs gained and analysed, here is a list of How Might We’s that can be solved,

How might we help the user create separate sections for communications of different purposes, sources and deadlines ?

How might we help the user segregate unsolicited communications such as “Questionnaire fill-up”, “Lost-found”, “Thank You”, “Gentle reminders”, “Monthly Newsletters” etc?

How might we help the user reduce junk space in the mailbox by auto deleting or removing such unsolicited communications after a set timeframe?

How might we help a moderator send reminders to a particular individual or a selective target group?

How might we simplify the idea of creating quick polls, surveys for several purposes and to take the same to a desired audience easily?

Task Exploration / Goal :

Ideating on all the inputs and analysing the key needs, I now have a rough idea about the main tasks that my application needs to solve.

Task 1: Segregating communications into different categories so that it is easier for the recipient to visually differentiate them amidst a barrage of incoming communications; and it is easier for the sender to send follow-up mails to only a particular set of people, rather than sending it to the entire group ( especially for reminders about an already sent communication requesting action )

Task 2: Giving an option to the user and sender to select if he/she wants to delete the post after a specific set of time, in case it is known that it will not be of any future use after a dead-line. Also, feature to auto-archive the posts after a specific time frame (3 months, or configurable) to keep the existing communication space clutter-free.

Task 3: To keep templates ready for creating several known formats of posts, which gives an ease of access in creating posts and also makes it easier in segregating different types of posts. The segregation also helps in creating a dashboard for the incoming posts inside the application, which gives the user an overall view about the unread posts of different categories.

Defining application terminologies :

To solve these aforesaid tasks, I finalised these main terminologies which will help me achieve the targets of this application.

  • Post: I am naming each communication here in the form of ‘Post’. Each user can post content and segregate them based on different post types.
  • Post Type: Based on the research, posts can be broadly divided into these types/categories; Newsletter, Admin Notice, Lecture Notice, Other Notice, Survey, Assignment, Lost-found, Opinion Poll and Miscellaneous. I am naming this category as ‘Post Type’. This will help me to differentiate the posts to declutter the communication channel.
  • Group: In each institution, the students are part of different sections and subsections in which the communication happens. I have segregated them here as ‘Groups’. A group can be a class, a community club, admin groups which can include all the members, a project group with a few mates etc.
  • Admin and Member of a Group: Each group can have admins and the non-admins will be termed as members. An admin is someone who is there to moderate the group and hence, will have greater privileges.

Information Architecture :

Based on the inputs received and after segregating the different tasks that the application should solve, I prepared an information architecture of all the possible flows and solutions; which helped me to further iterate the prototypes.

Source link