A streamlined experience for tracking and managing goals with clarity

Context and Scope


Viva Goals ensures employees understand strategies, manage goals effectively, and focus on priorities. It defines clear objectives, aligns them with roles, and provides resources. It sets measurable goals, tracks progress, and fosters transparency. Viva Goals drives clarity, alignment, and performance.

My role & Collaborations

As the Lead Product Designer, I was responsible for reimagining how users consume goal progress right from understanding status at a glance, to filtering by team, and making timely updates via check-ins. I led the design vision, strategy, and execution while collaborating with PMs, engineers, and data teams

Design process

Design Process.jpg

The Discovery


Primary Challenges of the Existing Viva Goals

<aside> 🤷🏽‍♂️

Unfamiliar With OKR Methodologies

A key obstacle to the widespread adoption of Viva Goals within organizations and teams is its reliance on the OKR framework. The OKR methodology is often perceived as complex and unfamiliar, making it difficult for organizations to implement effectively. Despite attempts to train team managers in OKR adoption, the success rate has been subpar. Moreover, some customers have begun requesting features that allow for the customization of OKR terminology to more straightforward goal-setting language.

</aside>

<aside> ☹️

Drop Offs

Heavy drop-offs at every stage post login. Go with Goals aims to fix drop-offs during the user journey post first login. This includes users who have logged in but not joined an org/team.

</aside>

<aside> 👩🏽‍💻

Engagement issues

We were seeing a clear decline of the engagement despite of the purchases of licenses of Viva Suite

</aside>

Echoes of Customer

Cone Health:

Customer does not use OKRs. They like the tool and the alignment it could provide but have concerns around terminology and changing the day to day of their users. This is just an example of an org who Goals could benefit, but we’ve got to work on messaging and how the tool supports non-OKR users.

Dolby: Customer has their own terminology; they want to be able to rename OKRs and projects within the tool.

HCA: Customized labelling allows greater VG adoption that reflects the terminology of HCA. Customer is requesting greater flexibility to change the terminology of OKRs, Initiatives, Projects, KPIs etc.

GTMotive: Somehow we set the idea in our teams that OKRs are quarterly defined … would it make sense to rename annual OKRs in some way or even all OKRs (user defined, for example we would call annual company OKRs “annual goals” and quarterly team goals “marketing quarterly team goals”).