Control Scope Creep in Google Meet

Project Background

Google Meet is redesigning the in-call host controls experience to reduce moderator errors during large meetings and livestreams. You are the UX/UI Designer leading execution for a 12-week redesign covering desktop web, Android, and iOS, working with 1 UX researcher, 2 visual designers, 6 engineers, 1 product manager, and 1 content designer. The launch is tied to a Workspace quarterly release, so the date is fixed.

Key Stakeholders

The Group Product Manager wants visible improvements to host confidence and fewer support tickets this quarter. Engineering wants to limit changes to the existing control architecture to avoid regressions. Legal and Accessibility reviewers require approval before launch. Sales and customer success are pushing to add late requests from two large enterprise customers, including custom moderator presets and more granular participant permissions.

Constraints

• Timeline: 12 weeks total, with design sign-off by Week 5 and engineering code freeze in Week 10
• Budget: No additional headcount or agency support
• Surfaces: Desktop web must launch; mobile can ship only if parity work fits within the same timeline
• Dependencies: Accessibility review takes 7 business days; legal/privacy review takes 5 business days; user validation requires recruiting 12 Workspace admins
• Success target: Reduce host-control related support tickets by 15% within 30 days of launch

Complications

1. In Week 3, Sales escalates a request from a top Workspace customer for custom moderator presets, claiming it is required for renewal.
2. In Week 4, Android engineering reports that one proposed interaction pattern will add 2 extra weeks unless the design is simplified.
3. Research findings show that admins strongly want audit visibility, which was not in the original scope.

Your Task

1. Define how you would evaluate and contain scope creep while protecting the launch date.
2. Produce a prioritized execution plan for design, reviews, prototyping, and handoff.
3. Recommend what stays in MVP, what moves post-launch, and how you would communicate those trade-offs.
4. Identify the top risks, mitigation steps, and decision points for escalation.
5. Specify launch success criteria and a rollback or fallback plan if critical approvals slip.