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.
The road to 2 million

Skyrocketing premium value with campaigns

Designed for Microsoft's Engage app • 2021 - 2023
Project Overview
I helped to envision and execute on a new feature set, Campaigns, for the Engage app in hopes of generating premium value revenue and more monthly active users.

The core principle that our team operated on was: build fast, iterate fast. Within three months, we delivered the first version of Campaigns out to customers. We gathered feedback, iterated and iterated and...now we've hit 2 million monthly active users.
But wait, what's Engage?
ROLE
Lead product designer
TIMEFRAME
3 months for initial MVP, 3 years for a mature product
IMPACT
0 to 2mil MAU (Monthly active users) within 3 years
The origin story

So, how did this all come about?

Well, let’s dive first into why the need for premium features even came about. Strategically, there was a shift in our app’s direction - going from an app that was a free add-on in the Microsoft 365 app suite to being part of a suite of premium apps. And thus began the journey of each team setting out to create premium value.

A comic of the change in company strategy
The first step

How did we land on campaigns?

Great question! Our team’s primary set of users were corporate communicators, meaning they’re the ones who plan, coordinate and even create all the communications that are sent out to the company internally. After diving deep into customer calls and secondary research, we were able to gather that they had a formula for their success - something we affectionately call, “The Communications Lifecycle”.

The communications lifecycle for corporate communicators

Upon further analysis, a gap that we identified was this: our lovely corporate communicator friends were unable to consolidate employee engagement into one place. There was no mechanism to allow anything to be “viral” intentionally. Looking into other social media apps, we observed the sheer power of hashtags for social media campaigns. We took that idea and ran with it.

The next bits

Execution and all that good stuff

We didn't want to simply copy and paste the technology of hashtags and call it a day. We wanted to empower corporate communicators to be able to aggregate all of the employee energy and engagement, gather metrics and be able to improve on their communications plans. Given that there was a need for speed, a core principle that our team operated on was: build fast, iterate fast.

We identified the most fundamental things that corporate communicators would need to successfully run a campaign and built on that.
I spearheaded many design iterations of how a campaign page could look like, how the flows would come to life within the existing app's ecosystem. The product manager and I would try and test our hypotheses quickly with customers and user testing sessions.

Within a month, with the input of the team, I put together a deck to showcase not only how campaigns could exist in Engage, but how customers could leverage it in their internal comms strategies. Needless to say, leadership buy-in was probably the smoothest part of this entire process.

Within three months, we delivered the first version of Campaigns out to customers.

We gathered more feedback, iterated and iterated and through years of hard work and great team work, we were able to create a version of campaigns that helped us reach 2 million monthly active users.

Some sappy reflections

For my own learning

Campaigns wasn't an overnight success by any means. If I were to summarize what led to the success of this feature, I'd highlight the following:

  • Great teamwork - not to sound cheesy, but having team members you can truly lean on can really enable you to do your best work.
  • Starting simple and iterating quickly - our team adopted a more "start-up" mentality and tried to ship fast with the foundations, then gather feedback and continue improving our feature set.
  • Played the long game - of course, our first version was delivered within 3 months, but it wasn't till years down the road that we could truly see the fruits of our labour. So, we kept working at improving our experience and it paid dividends.