An overview of Engage
close
Engage is a Microsoft employee engagement platform built on the foundation of Yammer, designed to foster connection, community, and knowledge sharing within an organization.

It helps employees connect with colleagues, leaders, and communities, share stories and knowledge, and find a sense of belonging at work.
AI-powered awesomeness

Optimizing workflows with a communications dashboard

Designed for Microsoft's Engage app • 2024
Project Overview
I spearheaded (with my co-lead) a month long design sprint to help create a space dedicated to corporate communicators other power users to optimize their workflows within the Engage app.

The sprint involved getting stakeholder buy in to fund the project. Within a month, we researched, designed flows and produced videos to help tell the story of the communications dashboard.
But wait, what's Engage?
ROLE
Co-lead product designer
TIMEFRAME
3 months
IMPACT
46% of all corporate communicator MAU now from dashboard
Listening to our customers

What is life like as a corporate communicator?

Corporate communicators are what I would describe as the ultimate multitaskers: They're juggling content, people, tools all around to try and create the most optimal communications strategy...all in the name of ensuring employees are informed and engaged at the right time and place.

Hearing from various customers and user research sessions, there are a multitude of pain points they experience. Here are some of the top ones our team heard:

star

Which tool, when?

There is general friction with knowing not only which tool is appropriate, but when to use said tool to help generate and publicize communications content.

star

Fragmented workflows

The problem of "which tool, when?" also leads to team members not being able to coordinate more seamlessly between one another.

star

Manual (almost) everything

A lot of existing tools don't have automation nor AI integrated, so corporate communicators are left to their own devices to try and make things work on their own.

Listening to our customers

What is life like as a corporate communicator?

Corporate communicators are what I would describe as the ultimate multitaskers: They're juggling content, people, and tools all around to try and create the most optimal communications strategy...all in the name of ensuring employees are informed and engaged at the right time and place.

Hearing from various customers and user research sessions, there are a myriad of pain points they experience. Some notable ones I recall are the "which tool, when?" problem, the fragmentation of workflows and the level of manual work involved in daily tasks.

Which tool, when?

There is general friction with knowing not only which tool is appropriate, but when to use said tool to help generate and publicize communications content.

Fragmented workflows

The problem of "which tool, when?" also leads to team members not being able to coordinate more seamlessly between one another.

Manual (almost) everything

A lot of existing tools don't have automation nor AI integrated, so corporate communicators are left to their own devices to try and make things work on their own.

Okay, now about us...

How did our team approach this?

Given that our team's primary focus area was on innovation, we operated like a tiger team and could determine our own timelines, projects and priorities for the most part. As such, my co-lead and I commandeered the design sprint process and made our own.

We prepared everything for this sprint from scratch: from the schedule to preparing workshops for the team to help brainstorm and ideate.

Schedule of the process
Solutions

Bringing life to the ideas

With our brainstorming process, we wanted to ensure that we could focus on ideas with the communications lifecycle in mind.

After several workshops, with input from our data analysts, we prioritized on what we thought the solutions could be.

Last but not least, we also thought about how we could solve for the manual aspects of their jobs. Given the rise of AI and our own company's push towards exploring our own AI system's capabilities, we incorporated Copilot (Microsoft's AI engine) into this dashboard.

The challenges

Competitors and turmoil from within

Interestingly enough, there were two main challenges that our team faced as we were working on this initiative.

The first was that although our persona was a "corporate communicator" for this space, there were other personas that also kind of fit the bill as well (leaders, their delegates, etc.)

The second was that there was an existing app that was part of the same suite as our app, that tried to solve for some of the same pain points we had investigated.

How we determined who we were solving for
expand_more
Originally, the immediate thought was "oh, of course, corporate communicators", but there were other personas that fit the bill of a "communicator", just without the title. Leaders and their delegates for instance, also had to incorporate communications strategies into their work. Given that we wanted to optimize for power users, we decided to broaden our persona, so that we weren't just solving for one type of communicator.
How we addressed the internal competitor
expand_more
This was a bit of a unique opportunity for us as product designers to dive into more of the product strategy side of things. Despite the other app being part of the same suite as our app, their release timelines were slower, the tech stack they operated on had a multitude of limitations and the current experience was not at a good place for integration. Ultimately, we decided from a product standpoint to attempt to resolve the pain points with our own app, taking inspiration from what worked for them and also being mindful of the gaps within their experience.

The final product

My co-lead and I storyboarded, edited and produced two videos to showcase the designs in a relatively succinct way to various stakeholders.

Ending with...

The usual reflections and then some

Personally, this was a project I had a lot of mixed feelings about. The aspects I felt we could've approached differently were not just tied to the user experience, but also with the product strategy. Some parts of the information architecture I disagreed on with the product side of things, but agreed to disagree and commit with the team's decision. It's not that this was the wrong way to go about things, but looking back, I feel like I could've stood my ground a bit more.

All in all though, we had a lot of autonomy for many aspects of this initiative which empowered us to do a lot of great work together. I'll share some of the highlights:

  • It...worked? - our final videos and presentation resulted in leadership being fully on board and engineering resourcing for us to get started right away into figuring the actual implementation of the product.
  • Great teamwork - He'd likely brush this off, but Jose is one of the best design partners anyone could ask for. I always learn a tremendous amount from him; from facilitating workshops to building frameworks. (His website in case you're curious)
  • Maximum creative freedom - There was a lot of space we had to create; not only for the designs, but also for the processes and final deliverables. I thoroughly enjoyed being able to tailor a system that worked for our team.

Overall, still a great project with great people. Were there things I would've changed about the process? For sure, in hindsight, yes. But at the end of the day, progress is better than just standing still; done is better than perfect.