Reminders for Everyone

Reminders in Flock only served tech-savvy users. To broader audience, the functionality was hidden and inefficient. I designed Reminders to cover extensive use-cases while chatting at workplace. The best part was that we were rethinking Reminders, [which meant designing ] and not looking at it as a redesign problem.

My Role

I was the only interaction designer throughout this project. Initially, I worked with a product manager to lay down the goals. Later on, I conceptualized the flows, created visual designs, and communicated the interactions to developers. This phase of design took two weeks. 

 

In the week-long second phase, I conducted the usability testing and studied the usage data to improvise the interactions.

Double Diamond Model. Source: https://www.designcouncil.org.uk/

This is asample quote lorem ipsum dolor sit amet This is asample quote lorem ipsum dolor sit amet but again testing it is This is asample quote lorem ipsum dolor sit amet

This is an insight. Use this when you want to highlight a finding or a problem statement.

Insights
Insights - This is a text heading to be used with in aparagraph. It can also be used to highlight a text

Wiki: A Need-finding Research

Preliminary research for chat-integrated Wiki at workplace

Reminders for co-workers

Reminders for co-workers

Reminders for co-workers

Reminders for co-workers

Food and learning

Solving reminding needs in Flock chat

Reminders for co-workers

Kick-starting  Flock Suite

Designing a suite of workplace tools from scratch

Part 4: Small fixes and experiments

Google Authentication

Some of the pain points in the previous sign-up flow were:

  1. Users do not understand that they need to use their work email address

  2. Users do not understand the notion of a team. It is hard for them to come up with a team name.

  3. Users get stuck at "Team url". They don't know what it means.

Password setup
Channel empty state

Some of the pain points in the previous sign-up flow were:

  1. Users do not understand that they need to use their work email address

  2. Users do not understand the notion of a team. It is hard for them to come up with a team name.

  3. Users get stuck at "Team url". They don't know what it means.

Part 5: Persona Building

Google Authentication

Some of the pain points in the previous sign-up flow were:

  1. Users do not understand that they need to use their work email address

  2. Users do not understand the notion of a team. It is hard for them to come up with a team name.

  3. Users get stuck at "Team url". They don't know what it means.

Password and SSO authentication

Until this time, we have been using OTP for email verification every time a user signs in. Delay in receiving OTP was the reason for user frustration. Thus, sign-in with password was one of the most requested features. Apart from this, medium sized enterprises were requesting an option of configuring SAML into Flock.

Use Cases

  • In companies where employees share workstations and sign out daily, it becomes repetitive and frustrating for them to wait for the OTP to login daily.

  • Users who use mobile devices primarily for work, when trying to use Flock on browsers have to repeatedly wait for the OTP every time they want to login.

I designed the flows for password and SSO authentication in Flock. The flows modified due to the upgrade were:

  1. Sign up flow for team creators

  2. Sign up flow for team joiners

  3. Sign in flow for existing users

  4. Sign in for new users

  5. Re-set password flows

  6. Password change options in Settings

  7. SSO and auth preferences in admin panel settings

I had to design such that the existing users verified by OTP can be moved to the new configuration.

Password setup in sign-up flow