Where this started
Neowin, which covered the retrospective, sets the timeline: back in May 2026, Microsoft announced a major revamp of Teams meeting controls, and eventually began rolling them out in August 2026. The Microsoft 365 Message Center notice for the change, MC1317197, explains why. In Microsoft's words, Microsoft Teams is updating meeting controls and the share panel to simplify use, reduce accidental actions, and improve sharing confidence.
The crowding built up over several years. UC Today described it this way: every capability added over the years, from reactions and raised hands to Copilot, Whiteboard, and breakout rooms, landed in the same toolbar with no corresponding cleanup. The Leave button ended up next to Share, which ended up next to Raise Hand, and the more features Microsoft shipped, the worse the crowding got. Leaving a client call by accident when you meant to share a slide is the kind of problem that keeps a UX team busy.
Section summary: The redesign was meant to stop expensive misclicks, such as leaving a meeting or sharing the wrong thing, in a toolbar that had grown with every new feature.
Rejected design #1: spread everything out
Microsoft's first idea was simple. Its blog describes an early concept that spread the controls across more of the meeting window. The aims were to reduce crowding, form clearer groups, and put more distance between Share and Leave.
The first round of research went well. Microsoft says participants liked parts of the cleaner layout and the clearer grouping. Repeated use changed the picture. Microsoft's first longitudinal study, along with feedback from early users and customer sessions, found tradeoffs in control placement, discoverability and how Leave was separated. Microsoft summed it up in one line: the layout looked cleaner, but looking cleaner wasn't enough.
Microsoft's account is more cautious than some coverage. Neowin wrote that prolonged use showed the concept reduced operational efficiency because controls were harder to discover. Microsoft's post does not go that far. It names the tradeoff areas and gives no numbers. It also does not say that spacing alone was why the concept was dropped.
Rejected designs #2–4: three approaches tested at once
Microsoft then built three competing designs and tested them against each other:
| Concept | Idea | Fate |
|---|---|---|
| All centered | All controls in one predictable spot, with Leave off to the side | Closest to what shipped |
| Three columns | Groups of controls split apart to use more of the screen | Not shipped |
| Cleaned-up current | Less clutter while keeping the familiar layout | Not shipped |
Neowin described the centered option this way: one of them placed all controls in the center, and the Leave button on the side. This is very similar to the design we have today. For the three-column concept, Neowin noted that the notable aspect being the column on the left, which grouped audio, video, and sharing controls on the left.
Microsoft says a large cohort used the designs for a month and answered surveys twice a week. The team tracked findability, efficiency, confidence, effort, satisfaction and perceived value. It also tracked how opinions changed as people got used to each design. Microsoft does not give the cohort size, who took part, or comparative scores, so the post shows no statistically proven winner. Microsoft says outright that the lesson wasn't simply that one design "won."
Section summary: Microsoft tested a centered layout, a three-column layout and a cleaned-up version of the old toolbar side by side for a month. The centered layout became the starting point, but the bigger lesson concerned customization.
Why there is no single "perfect toolbar"
The research led Microsoft to separate visual simplicity from operational simplicity. Neowin summed up the reason: Teams' user personas utilized the software in different manner, depending upon how frequently they shared their screen, made notes, raised their hands, etc.
Microsoft's examples are familiar. A presenter needs different things than someone listening in a large discussion. A person who records often wants Record close at hand. Others care most about Notes, Copilot, People or reactions. Participants kept asking to customize the toolbar, so Microsoft stopped trying to find one ideal layout and built a system people can adjust.
Preferences also conflicted. Some testers wanted Raise hand visible at all times, while others liked it grouped with reactions. Some wanted fewer visible controls, while others wanted to use more of a large monitor. Feedback about controls that moved during use pushed Microsoft toward a second principle: simplicity also means predictability. Microsoft put it this way: people in meetings have better things to think about than where their interface went.
Problems found after the main design work
Microsoft says the design had mostly settled by early 2026. Before widening the rollout, the team ran a structured review built around nine meeting tasks. The post lists six of them: muting, adding and removing controls, taking notes, raising a hand, recording, and starting transcription without recording.
The transcription task exposed a real problem. The feature existed, but some participants could not reliably find it or understand it. The review also found two other issues. Right-click alone did not make customization discoverable enough, and the difference between temporarily shown controls and permanently pinned ones needed to be clearer. Microsoft says it also used aggregated usage telemetry, card sorting, diary studies, and feedback from testers who switched back to the old experience.
Microsoft's stated principles for the final design:
- Keep frequently needed actions easy to reach.
- Keep Leave apart from common controls.
- Make the larger set of tools easier to navigate.
- Let people personalize their controls.
- Build an information architecture that can change over time.
Section summary: Even after the layout was settled, structured testing found hard-to-find transcription, weak discoverability of right-click customization, and confusion between temporary and pinned controls.
How to use what shipped
Microsoft's support documentation describes the customization that came out of this work. Core controls such as camera, mic and screen sharing are fixed and stay available. Everything else can be moved around:
- Reorder: Select a control, then drag and drop it to a new position on the bar.
- Pin: Select More to open the overflow menu. Right-click an option and choose Pin, or drag it onto the control bar.
- Unpin: Right-click a control on the bar and choose Unpin, or drag it onto More.
- Pin Raise hand: Select React, right-click Raise hand, and choose Pin.
- Turn the new controls on or off: Go to Settings and more > Settings > General > Meeting and set the New meeting controls toggle.
The Raise hand step matters because the ability to raise your (digital) hand has not gone away, it's just been clubbed under the React menu. Neowin's earlier coverage explained the change: people would accidentally raise their hand when trying to send a reaction, interrupting the flow of the meeting.
If your layout seems to reset on another device, that is expected. At launch, meeting controls customization preferences (such as pinned controls) do not sync across devices. They do persist across meetings on the same client, and the Message Center notice lists cross-device sync as planned. If someone customizes the toolbar on a work laptop and then joins from the web, they will need to set it up again there.
Notes for IT admins
The Message Center notice covers Teams for Windows desktop, Teams for Mac desktop and Teams for the web. Not in scope: Teams (consumer), iOS, Android, Teams Rooms, Linux. Its September 23 update projected these general availability windows:
- Worldwide: mid-October through late October 2026
- GCC and GCC High: late October through mid-December 2026
- DoD: mid-December 2026 through early January 2027
These are Microsoft's forecasts, not a guarantee that every tenant has the new controls yet.
On control: Microsoft is switching the new experience on by default, with no tenant-level disable option. During rollout, individual users can temporarily revert via Teams settings, but that opt-out is a short-term adoption aid. App pinning policies also change. Existing meeting app pinning policies will continue to be honored. New meeting app pinning policies will support up to two apps pinned to the main meeting controls, with additional apps available in the More menu. Tenants that pin several meeting apps should check their policies now. Helpdesks should expect calls from users who can't find Raise hand or Record.
What to make of it
The retrospective is open about Microsoft's own mistakes. It is still Microsoft grading its own work, with no raw data, no participant counts and no outside validation. The rejected designs are only as Microsoft describes them. What can be checked is the shipped result: pinning, unpinning, reordering, a separate Leave button and fixed core controls, all confirmed in Microsoft's support and adoption materials.
The design lesson applies beyond Teams. Usability tests on day one tend to reward clean screenshots, while muscle memory only shows up weeks later. Microsoft says the transcription and right-click problems turned up in testing, not after release. Whether letting users customize the toolbar fixes the problem or just moves the work onto users will depend on adoption in large organizations. The end of the opt-out toggle is something to watch: Microsoft says it will retire the user-level opt-out in a future release and announce that in a separate Message Center post.
Microsoft is also asking for feedback. The post ends by inviting comments on what the team got right and what to simplify next, closing with "we're still listening."
References
- Here are the designs Microsoft rejected for Teams meeting controls revamp Neowin · 2026-11-19T21:54:01+00:00
- New meeting controls experience in Microsoft Teams – Microsoft Adoption adoption.microsoft.com
- The designs we didn't ship: How user feedback shaped the new Teams meeting controls | Microsoft Community Hub techcommunity.microsoft.com