A two-day design sprint by Hanna Shevelova and colleagues has yielded a provocative prototype for Microsoft Teams: an anonymous “End Meeting” button that lets participants collectively vote to close a meeting early. The concept, which transforms a long-running internet meme into a functional tool, has ignited fresh conversations about meeting culture, power dynamics, and the ethics of anonymous digital interventions in the workplace. While it remains an independent experiment, the prototype underscores a widespread frustration with meeting bloat and a growing appetite for more democratic meeting governance tools.

The Meme Becomes Reality: A Two-Day Design Sprint

UX/UI and product designer Hanna Shevelova announced the prototype in a social media post that quickly caught the attention of the design community. Built over just two days, the demo embeds a simple voting mechanism directly into the Microsoft Teams meeting interface. The button, labeled “End meeting,” is visible to all participants. Once clicked, it triggers an anonymous poll asking whether the meeting should continue. If a critical mass votes to conclude, the meeting is terminated for everyone—no host override required.

The project started not as a formal Microsoft initiative but as a creative exploration of a feature that many remote workers have jokingly requested for years. The idea of an “end meeting early” button has circulated as a Twitter meme and Reddit wish for so long that it has almost become a shorthand for existential meeting dread. Shevelova and her team took the meme seriously, treating it as a signal of genuine user pain. By compressing the design cycle into two days, they forced themselves to focus on core functionality and rapid validation, a approach that often surfaces insights which longer processes might miss.

How the Anonymous “End Meeting” Button Works

In the prototype, the button appears persistently in the Teams meeting toolbar, alongside familiar controls for mute, camera, and share. Tapping it immediately surfaces a simple, binary question: “End this meeting?” Participants see a live counter of anonymous votes. Once the tally crosses a predetermined threshold—say, 70% of attendees—the meeting ends abruptly, dismissing all participants back to their chat or calendar. The host is not notified of who voted, preserving anonymity.

Crucially, the threshold is configurable. In some versions of the prototype, the organizer can set the percentage before the meeting begins, choosing from options like simple majority (51%), supermajority (67%), or consensus (100%). This flexibility aims to balance group empowerment with host control. The team also experimented with a cooldown timer to prevent rapid-fire voting, ensuring that the feature cannot be used impulsively within the first few minutes of a meeting.

Breaking Down Psychological Barriers: Anonymity in the Workplace

The deliberate choice of anonymity directly tackles a known workplace problem: the bystander effect. In traditional meetings, even when multiple participants feel a session has run its course, few speak up. Power imbalances, fear of offending the host, or simply not wanting to be the first to voice dissent keep people silent. An anonymous vote lowers the social cost of expressing that desire, potentially unlocking more honest, efficient meeting outcomes.

This design mirrors anonymous feedback tools already used in enterprises—employee engagement surveys, 360-degree reviews, and whistleblower hotlines. In those contexts, anonymity encourages candor. Applying the same principle to real-time meeting management could fundamentally shift who controls the clock. It transforms meeting endings from a unilateral host decision into a collective, private gesture, which may reduce the resentment that builds up in overscheduled teams.

The Design Philosophy: Empowerment Without Chaos

Shevelova’s prototype is not simply about cutting meetings short—it is a lesson in designing for collective agency. The interface avoids gamification and keeps the interaction serious: no emojis, no sound effects, no rewards for early closures. The visual design uses Teams’ native components, making the button feel like a natural part of the app rather than a playful add-on.

The team considered edge cases carefully. For example, what if the organizer is sharing their screen and the meeting ends abruptly? The prototype triggers a soft dismissal that saves any shared notes and seamlessly redirects users back to their pre-meeting context. Additionally, the threshold can be set to 100% to effectively disable the feature for meetings where absolute control is required, such as all-hands announcements or sensitive HR discussions.

Technical and Ethical Feasibility within Microsoft Teams

While the prototype was built as a standalone demo, integrating such a feature directly into Microsoft Teams would require significant engineering and policy considerations. Teams already supports polls and surveys via the Forms integration, and its extensible app model could theoretically host a third-party voting command. But a native “end meeting” action that overrides the host would need deep operating system-level hooks and careful security modeling to prevent abuse.

Microsoft has historically been cautious about features that could be co-opted for trolling or harassment. A button that lets a group forcibly end a meeting could be weaponized by a coordinated majority to silence minority voices or derail critical discussions. Any real-world implementation would likely need safeguards like: a visible cooling-off period after a vote, clear audit trails (even if anonymized), and the ability for the host to override in emergencies. These guardrails would be as critical as the feature itself.

Could This Actually Ship? The Road from Prototype to Product

Though this is an independent project, Microsoft has a track record of monitoring community prototypes and incorporating user-driven ideas into its roadmap. Live reactions, fluid components, and Together Mode all evolved from experiments and public feedback. A Microsoft spokesperson did not comment on whether the “End meeting” button is under consideration, but the prototype’s viral reception suggests strong latent demand.

Product managers often use such external prototypes as “provotypes”—provocative prototypes—to gauge reaction before committing resources. The overwhelmingly positive design community response could accelerate internal conversations. However, the leap from two-day demo to polished feature is vast; it would require rigorous usability testing, accessibility audits, and cross-team coordination with calendar, chat, and compliance systems.

Lessons for Product Designers: Prototyping as a Catalyst for Change

Shevelova’s exercise offers three core lessons for product teams. First, constraints breed creativity: the two-day limit forced ruthless prioritization and produced a single, testable interaction. Second, memes are unsolicited user research: when the same pain point is repeated across internet culture, it is often worth investigating. Third, anonymity in collaborative tools is underexplored; while it introduces risks, it can also unlock efficiencies by removing social friction.

The prototype also highlights a broader trend in workplace software: the shift from top-down control to distributed empowerment. Features like delayed sending in email, silent partnership in Zoom, and collaborative agendas in Loop all chip away at the host’s unilateral power. The “End meeting” button sits squarely in this lineage, asking what would happen if meeting participants, not just organizers, were trusted to manage time.

The Future of Meeting Governance: More Than a Button

Beyond the specific feature, the prototype challenges us to rethink meeting culture. The real innovation may not be the button itself but the conversation it starts about consent and collective decision-making in always-on video environments. Could future meetings begin with a shared, visible agenda and a pre-agreed “done” condition? Could AI detect when a meeting has achieved its stated goals and nudge participants toward a vote? Could organizations adopt “hard stops” that require unanimous consent to extend past scheduled end times?

These questions suggest a next frontier for meeting design, one where software actively shapes group behavior instead of merely enabling it. While an anonymous end button is a blunt instrument, it opens the door to more nuanced interventions. As hybrid work cements itself, the tools that help us exit meetings gracefully may become as important as those that help us join them.

For now, Shevelova’s demo stands as proof that even a two-day prototype can resonate deeply with a global audience. It captures a collective frustration and turns it into a tangible design object—one that may not ship, but will undoubtedly inspire future experiments in workplace democracy.