Some of the most important product decisions we've made weren't about what to ship.
They were about what not to ship.
When we began rethinking the meeting controls in Microsoft Teams, the challenge was clear. Meetings had become more capable, and the interface had grown along with them. As Teams meetings became more capable, we saw an opportunity to make controls simpler to navigate and easier to adapt to different meeting needs. And simply adding another button every time Teams gained a capability wasn’t the experience we wanted to carry forward.
So we started with a question:
Could we make meeting controls simpler today while creating room for Teams to become more capable tomorrow?
It took more than one attempt to answer it.
First idea: Spread things out
An early concept divided the controls across more of the meeting window.
The idea made sense on paper: reduce crowding, establish clearer groups, and create additional separation between actions such as Share and Leave.
Initial research gave us reasons to keep exploring it. Participants responded positively to aspects of the cleaner layout and clearer grouping.
But repeated use revealed tradeoffs.
In our first longitudinal study, supplemented by feedback from early users and customer sessions, we identified tradeoffs in control placement, discoverability, and Leave separation that informed the next iteration.
It looked cleaner.
But looking cleaner wasn't enough.
A meeting toolbar isn't something people simply look at. It's something they operate quickly while concentrating on a conversation, presentation, or task.
So we kept going.
Next, we tested very different answers
Instead of debating design philosophies, we decided to test them.
We developed three approaches:
All centered: Put controls together in one predictable place.
Three columns: Separate families of controls and use more of the available screen.
Cleaned-up current: Reduce clutter while preserving more of the familiar structure.
We gave those experiences to for a large cohort for a month, with participants responding to surveys twice a week.
We looked at signals including findability, efficiency, confidence, effort, satisfaction, and perceived value. Just as importantly, we looked at how participants' reactions developed as they became familiar with each design.
The findings exposed an important tradeoff.
The lesson wasn't simply that one design had "won."
It was that visual simplicity and operational simplicity aren't necessarily the same thing.
Then users challenged the idea of a perfect toolbar
We had been approaching the toolbar partly as an optimization problem: determine which controls belong there, identify the best order, and create the right default.
What we learned from participants led us to reconsider that assumption.
People use Teams differently.
A presenter may have different priorities from someone participating in a large group discussion. Someone who records frequently may want Record immediately accessible. Another person may prioritize Notes, Copilot, People, reactions, or something else.
Across the research, we heard a clear desire for more control over that experience.
Let me customize it.
That changed our thinking.
Instead of trying to create one perfect toolbar, we focused on creating a system people could adapt.
Pin.
Unpin.
Rearrange.
Bring forward the controls that matter to you.
The goal became a simpler starting point without assuming that everyone's definition of "simple" is the same.
Finding the problems that still remained
By early 2026, the design had converged substantially. But before expanding the rollout, we conducted a structured review around nine meeting tasks.
Could participants mute?
Add and remove controls?
Take notes?
Raise their hand?
Record?
Start transcription without recording?
That final task exposed an issue we needed to fix. The capability existed, but some participants weren't reliably finding or understanding it.
That's an important distinction in product design:
A capability delivers the most value when people can easily discover and use it.
The review surfaced other opportunities too. Relying on right-click wasn't enough to make customization discoverable for everyone, and the difference between temporary and permanently pinned controls needed to be clearer.
So we iterated again.
Listening to more than one signal
There wasn't a single metric that could tell us whether we had the design right.
We combined what people told us through research and surveys with aggregated product usage insights.
We looked at questions such as whether participants could find what they needed, how confident they felt, and how they perceived different designs.
We also examined how early users interacted with controls and menus, and we listened closely to people who chose to return to the previous experience during testing.
When someone told us a control was difficult to find, an interaction took too long, or a change disrupted something familiar, that feedback helped us understand where the design still needed work.
Predictability matters
As more people tried the experience, their preferences weren't always the same.
Some participants wanted Raise hand visible at all times. Others liked its association with reactions.
Some preferred fewer visible controls. Others wanted to make fuller use of a large display.
Some appreciated additional separation between Leave and Share. Others noticed even small changes to locations they knew well.
One particularly useful lesson came from feedback about dynamic controls.
A toolbar can become harder to operate when controls move unexpectedly during an interaction.
That reinforced a design principle that stayed with us:
Simplicity isn't only about reducing clutter. It's also about predictability.
People in meetings have better things to think about than where their interface went.
Where we landed
After the prototypes, longitudinal research, surveys, experience reviews, telemetry, card sorting, diary studies, and a lot of iteration, the principles behind the final direction became relatively straightforward:
Keep frequently needed actions accessible.
Separate Leave from common controls.
Make the broader toolbox easier to navigate.
Let people personalize their controls.
And build an information architecture with room to evolve.
The finished experience can make those decisions seem obvious.
What you don't see are the designs that didn't survive the research.
That's the part of this work I'm most proud of.
We didn't need to have the right answer on the first try because we built a process that allowed users to help us find a better one.
Shipping is another beginning
The new Microsoft Teams meeting controls are becoming broadly available. Learn more about how to set up and use.
That gives us something our prototypes and studies couldn't: feedback from a much broader range of real-world meetings and ways of working.
So if you've tried the new controls, tell us what you think in the blog comments.
What did we get right?
What could we make even better?
And what's the next thing we should simplify?
Some of the most valuable moments in this journey began when user feedback challenged our assumptions.
We're still listening.