Bringing Copilot to life across Viva by designing for the suite, not a single product.
01 — Context
I helped bring powerful, relevant Copilot experiences to products across Microsoft Viva. Rather than optimize one surface in isolation, we looked across the suite to understand where AI, discoverability, and reach could reinforce one another inside the flow of work.
So what
The opportunity was bigger than one feature: make Copilot feel findable and useful wherever work already happens.
02 — Framework
Where does the user already have intent? What is the smallest useful Copilot moment? How can the experience travel with people across products? And what makes the value legible without teaching another system? Together, these questions turned a collection of surfaces into one platform opportunity.
So what
The horizontal view made the seams visible—and gave us a better place to design from.
03 — Proof
We mapped the moments where people were already looking for help, then explored how Copilot could appear with enough context to feel relevant—not like another destination competing for attention.
See the work in the deck ↗So what
Discoverability is a product behavior, not a navigation problem.
03 — Proof
We looked for connective tissue across Viva and the wider Microsoft 365 ecosystem: shared signals, familiar language, and clear handoffs that could help Copilot reach people without asking them to start over.
See the work in the deck ↗So what
Reach is less about adding entry points and more about removing dead ends.
03 — Proof
The work explored how Copilot could be embedded within M365 in ways that respected the surrounding experience: visible enough to invite use, quiet enough to preserve focus, and consistent enough to build trust across the suite.
See the work in the deck ↗So what
Embedding Copilot well means designing the relationship, not just the feature.
04 — Guardrails
A horizontal strategy can easily become a generic layer pasted everywhere. The guardrail was to preserve the distinct job of each Viva product while giving Copilot a recognizable point of view: useful context, familiar language, and a clear reason to appear.
So what
Shared patterns create trust only when they leave room for product-specific meaning.
05 — Craft
We moved between customer needs, platform constraints, and emerging Copilot capabilities. That back-and-forth helped us find opportunities that were both meaningful to people and plausible within the Microsoft 365 ecosystem.
So what
The strongest concepts came from holding human need and technical reality in the same frame.
06 — Reflection
Looking horizontally changed the question from “where should Copilot live?” to “how should Copilot connect the work people already do?” That shift opened up better opportunities for discoverability, reach, and useful embedded moments—without asking any one product to carry the whole experience.