Marcel AIย Platform: Productivity Tools

Mobile phone displaying app interface that reads: "Hi! I'm Marcel. I'll connect you with 80,000 other Publicis Group employees and match you with new opportunities"

Overview

Designed and developed in partnership with Microsoft, Marcel is an AI platform aimed at shifting Publicis Groupe from an outdated holding company model to an open enterprise level platform that connects 80,000 talented employees, across 200 disciplines in 130 countries for more seamless communication and collaboration.

The initial outcome was to launch a mobile app to Publicis Groupe employees for both iOS and Android and a desktop component shortly after. The pilot app was scheduled to roll out to employees in the U.K. in the spring of 2019.

My role on this project

I lead product design and acted as the product owner for productivity tools in Marcel which included the integration of Microsoft Office 365 Email and Calendar, Oracle and Altair time-tracking systems, as well as Box and OneDrive cloud file management systems.

โ€

Problem statement

How can Marcel remove barriers to productivity from our existing tools and allow Publicis Group employees to spend less time completing mundane tasks and more time doing the work that they love?

โ€

User research

A survey was conducted among Publicis Groupe employees. Participants represented various sectors of Publicis, a mixture of seniority ranging from Junior Associate to Director & Above, and a variety of departments including creative, tech, human resources, business development, etc. Our research helped us understand:

  • Day to day usage of productivity tools
  • Tasks associated with these tools
  • Perceived levels of productivity throughout the day
  • Barriers to productivity
Bar chart titled 'Barriers to Productivity,' showing percentages for various barriers: attending meetings (65%), reading email (41%), environment (41%), internal processes* (33%), scheduling meetings (29%), responding to email (29%), and tech issues (24%). *Internal processes include tasks such as expense reporting, which are not supported by current productivity tools.
Bar chart titled 'Barriers to Productivity,' showing percentages for various barriers: attending meetings (65%), reading email (41%), environment (41%), internal processes* (33%), scheduling meetings (29%), responding to email (29%), and tech issues (24%). *Internal processes include tasks such as expense reporting, which are not supported by current productivity tools.

Goals for productivity tools in Marcel

The outcome of our user research helped refine a vision for these productivity tools and start to shape our product features as we moved into product design and development.

๐Ÿ“…

Calendar

Eliminate barriers when coordinating schedules and provide useful schedule insights.
๐Ÿ“จ

Email

Facilitate interpersonal connection between Publicis Groupe employees within the Marcel app.
๐Ÿ’ฌ

Cloud Storage

Reduce time spent locating files by augmenting capacity to find and share files by using natural language.
๐Ÿ•“

Timesheets

Provide employees with an option to save and submit timesheets from their mobile device.

Product design

Marcel is a platform that utilizes NLP (natural language processing). Our team started creating decision trees for primary use cases, or intents, to understand how we could extract relevant information from a userโ€™s dialogue to fulfill an intent. Once our decision trees were validated, we started introducing UI in the form of low-fidelity wireframes and prototypes โ€“ working closely with the our partner, Microsoft to define these product features.

Decision tree diagram illustrating a natural language processing (NLP) flow for handling the user intent: 'Where is the PowerPoint that Andy was working on yesterday?' The tree maps out steps to interpret the query, identify keywords such as 'PowerPoint,' 'Andy,' and 'yesterday,' and determine relevant actions or responses to locate the requested file.
Decision tree diagram illustrating a natural language processing (NLP) flow for handling the user intent: 'Where is the PowerPoint that Andy was working on yesterday?' The tree maps out steps to interpret the query, identify keywords such as 'PowerPoint,' 'Andy,' and 'yesterday,' and determine relevant actions or responses to locate the requested file.

Experience design principles

Our experience design principles informed the design of our product features.

โ˜•๏ธ

Keep it conversational

Be personable and maintain a balance between two modes of interaction, voice and UI.
๐Ÿ”ฎ

Be proactive

Predict the needs of a user and provide intelligent recommendations without direct user inputs.
๐Ÿ’†

Reduce friction

Remove barriers to productivity and reduce time spent completing tasks.

โ€

Task flow wireframes illustrating the process for fulfilling the voice input intent: 'Is Andy available for lunch this week?' The wireframes map out steps to interpret the query, check Andy's schedule, identify available lunch slots, present the options to the user, and send a meeting invite.
Task flow wireframes depicting the process of scheduling a meeting based on email context. The flow includes steps to interpret the email content, extract relevant details (e.g., participants, suggested times), check calendar availability, propose meeting options, and confirm the scheduling.
Task flow wireframes depicting the process of scheduling a meeting based on email context. The flow includes steps to interpret the email content, extract relevant details (e.g., participants, suggested times), check calendar availability, propose meeting options, and confirm the scheduling.

Project learnings

  1. Communicate effectively: Clear, consistent communication across teams and with stakeholders was absolutely necessary to save a lot of time doing re-work. This was especially true with having well articulated feature stories.
  2. Prioritization is crucial: You can do anything, but you cannot do everything. Prioritization and continuous refinement of the product backlog allowed our team to launch with a clear vision for an MVP that would deliver incremental value to our employees. It also helped manage out of scope requests and set reasonable expectations with our stakeholders.
  3. Data heavy projects are a lot of fun: This project challenged me creatively to think of novel ways to use data points to solve problems and create new, meaningful experiences within the constraints of our current productivity toolkit.
  4. Product design is never done: We continue to gain valuable insights from feedback received from our beta users. Our team has a very healthy product backlog that will only continue to grow as our users gradually change and Marcel is rolled out to new geographies.
@ Sapient Razorfish for Publicis Groupe
2018-2019