One roadmap for two rival platforms
How research reframed a turf war between Teams and Yammer as a single question about people — and shipped a design that respected how they actually work.
Two collaboration apps, one confused workflow
Early 2020. Lockdowns sent collaboration usage soaring — and exposed how little anyone agreed on where each app belonged. Teams was the productivity hub; Yammer was the company-wide social layer; the two overlapped in ways that confused users, and two product organizations each wanted to own the seam. Leadership wanted retention. Nobody could say, with evidence, what should live where.
Teams
The productivity hub — chats, channels, meetings. "Where the action is."
Yammer
The company-wide social layer — communities, discovery, belonging.
The overlap
Users wanted synergy; leadership wanted retention. Neither org owned the seam.
Turning a rivalry into a shared roadmap
The hardest part was never the users — it was getting two competing organizations to trust one set of findings. So the research was run in the open: Teams and Yammer leadership sat in the same sessions and heard the same users, live, at an evidence-first table. Design and engineering co-ran the capability-mapping and ideation workshops, so they owned the concepts rather than receiving a report. A shared timeline, mandatory attendance, and bi-weekly readouts kept everyone aligned as the insights formed — and findings packaged for the C-suite seeded a wider integration effort across the whole office suite.
A qual-to-quant loop across every stakeholder
Broad questions call for listening first, then structure — methods layered to converge on measurable themes, across a sample of information workers, communications admins, IT pros, and everyday end-users at twelve companies.
- Focus groups — 4 sessions with card-sorting to rank feature value
- Company case study — 8 in-depth interviews inside one organization
- Customer round table — 20 attendees across admin & IT roles
- Digital diary — 20 end-users logging a full week in-context
- Design-thinking — pre- & post-study synthesis workshops
- Feedback loop — bi-weekly readouts kept stakeholders in the data
From vocabulary to structure — the "circles of trust"
Unbundling the apps into the features people actually valued — chats, channels, communities — surfaced a single organizing axis: group size. The larger the audience, the more public and formal people became. That one variable explained which app people reached for, and where the real gaps were. Eight messy themes collapsed into a clear choice between three integration models.
Separate apps
Keep the apps distinct, respect the workflow that already existed.
One app, sections
Merge into a single app with separate sections.
Fully merged
One space, no distinction between the two.
Alignment that shipped — and scaled
The finding settled the debate and shipped the workflow-respecting design. In the year that followed, Teams grew +150% and Yammer/Viva +66%, with engagement KPIs up 12–20% across desktop, web, and mobile. Two feuding organizations aligned on a joint, user-grounded roadmap; the findings seeded a wider integration effort across the office suite; and the work legitimized a standing research seat — a new six-person team — in future M365 platform decisions.
The hardest part wasn't the users. It was getting two competing orgs to trust one set of findings. — the through-line of the study