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.

▶️ Check out its initial reveal at Viva Tech 2018 (product demo starts at 9:50)

Horizontal timeline showing key milestones for the development and launch of Marcel, an AI platform. The timeline starts with ‘Product Start’ in January 2018, followed by ‘1st Public Demo’ in May 2018, ‘Beta Begins’ in July 2018, ‘Design Freeze’ in October 2018, ‘Web Dev Begins’ in December 2018, and concludes with ‘Public Launch’ in May 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. Activities included: 

  • Backlog refinement and prioritization
  • Story writing
  • Dialog trees
  • Task flow diagrams
  • Wireframes
  • Visual design
  • System design
  • Concept testing
  • Usability testing

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?

Mobile app interface displaying a welcome message on a dark background. The text at the bottom greets the user: ‘Hi, Jeffrey! What can I help you with this morning?’ Navigation icons for keyboard and home are visible at the bottom of the screen, along with two pulsing dots in the center indicate that the app is in voice mode, actively listening to the user.
Mobile app interface with a conversational AI interaction. The screen greets the user, ‘Hi, Jeffrey! What can I help you with this morning?’ The user asks, ‘Show me my timesheet,’ and the response displays a card titled ‘Total Hours Saved’ for the week ending May 6. It shows 20 hours logged, with a bar chart visualizing hours saved across Monday through Friday, where Monday and Wednesday have the highest bars. Navigation icons for keyboard and home are visible at the bottom of the screen, along with two pulsing dots in the center indicate that the app is in voice mode, actively listening to the user.
Mobile app interface displaying a timesheet summary for the week ending May 6. The total hours logged are 40, with a breakdown of project allocation. The project ‘Blue Cross Blue Shield of Massachusetts’ is shown with 24 hours allocated to project work and 16 hours marked as a public holiday. There is an ‘Add Time’ button below the summary. Navigation icons for keyboard and home are visible at the bottom of the screen, along with two pulsing dots in the center indicate that the app is in voice mode, actively listening to the user.

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.
Whiteboard sketch illustrating early explorations of a file search and sharing workflow for Marcel. The flow begins with a conversational interface greeting the user (‘Hey M’) and progresses through various steps, including selecting a project, viewing matching files, previewing file details, choosing a recipient (‘Which Barry?’), and confirming the file share. Notes on the whiteboard include labels for interactions, file metadata details (e.g., user, last modified date, file type, size, location, and file name), and annotations clarifying functionality like ‘Show me PDFs’ and ‘Open Drive.’ The sketch combines text, arrows, and rough UI wireframes to map out the user journey.
Early-stage whiteboard sketch exploring functionality and UI patterns for file search feature in Marcel.
Whiteboard sketch exploring a workflow for managing meetings and emails within Marcel. The flow includes several screens: (1) A notification summarizing a meeting at 9 AM and important emails, with options to ‘Snooze’ or ‘View.’ (2) A detailed email view showing a message from Derek, with a ‘Reply’ button at the bottom. (3) A draft reply message stating, ‘Hey Derek, I have a meeting this morning, but I’ll take a look first thing after. How does an 11 AM review sound?’ with options to ‘Send as Meeting Invite’ or ‘Send as Reply.’ (4) A confirmation screen showing the message has been sent, with a summary card of the interaction. Notes on the whiteboard include annotations such as ‘Add in-between screen with message in writing state’ to refine the flow.
Early-stage whiteboard sketch exploring functionality and UI patterns for the email and calendar features in Marcel.

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. Data-driven design is incredibly rewarding: This project challenged me to creatively leverage data points to solve problems and design meaningful experiences within the constraints of our existing productivity tools.
  2. Designing for voice interfaces brings new challenges: Creating conversational flows for voice interactions required a deep understanding of natural language patterns, user expectations, and the constraints of voice technology and designing without a visual interface. This experience helped me think differently about simplicity and the nuances of user interaction.
  3. Effective communication: Clear and consistent communication across teams and stakeholders was essential to avoid unnecessary rework. This was especially true when crafting well-articulated feature stories, which provided clarity and alignment throughout the project.
  4. Maintain focus by prioritizing with intention: You can do anything, but you cannot do everything. Prioritizing and continuously refining the product backlog allowed us to launch with a focused MVP that delivered meaningful, incremental value to Publicis Group employees. This approach also helped us manage out-of-scope requests and set realistic expectations with stakeholders.
  5. Product design is never done: Feedback from beta users continues to provide invaluable insights. Our team maintains a healthy and growing product backlog that evolves as our users’ needs shift and as Marcel expands to new geographies.
@ Sapient Razorfish for Publicis Groupe
2018-2019