Cover_loop.png
Cover_vue_Slim.png

Loop Email

INSTANT MESSAGING PLATFORM | AI ASSISTANT | 2016

How might we revolutionise the way people work with emails to enhance collaboration and efficiency? 

intro.png

Company background

Loop Email (formally 4th Office) has a mission to revolutionise the use of email, driving teams to work together more effectively. Taking the opposite direction of Slack, the messaging app is reorganising content as an additional layer on the top of the existing email infrastructure.

The situation

As I joined the product team, the start-up had pivoted to focus on an AI Assistant for emails. The vision was to build a system able to give reminders for pending emails and provide contextual insights about the user's correspondents. My role was to conduct initial user research, explore new scenarios with prototypes and validate them with users.

onboarding.png

Brief & Objectives

As we launched the AI assistant in the app, we had to introduce it to our early set of users with an onboarding.

The key objectives of the onboarding were to:

  1. Use the conversational interface and associated visuals to explain the fundamentals and key advantages of the product.

  2. Highlight to users how to trigger the smart assistant.

  3. Demonstrate how the AI assistant would help using users’ real contacts and data.

First Wireflow

<-- Click to enlarge -->

Prototype & User Testing

After exploring various concepts and IA logics, we built prototypes and conducted user testing sessions, letting candidates go through the onboarding process and observing then their first steps using the app.

The results were encouraging, we could confirm that: 

  1. All users identified how to trigger the smart assistant

  2. Candidates understood Loop email’s proposition and USPs.

  3. They felt confident turning on notifications, as they understood the value of the insights they will later on get.

We learnt we needed to focus on:

  1. Explaining that the muted messages would still be accessible in a dedicated section.

  2. Clarifying the use of "follow ups" as it is a core functionality of the app.

We would need to fine-tune some interactions:

  1. Call to actions between the different kind of follow ups

  2. The copy to a shortest possible format

  3. The speed of the interaction during development

Final_loop.png

Position: UX Designer (Contract)

Start Date: Jan 2016 | Timeframe: 6 months

Chief Product Officer: Rags Vadali | Product Manager: Uros Zupan

- Other Projects -