Timeline: 2023–2026 | Role: Design Program Manager, Alexa Devices & Services
Amazon was launching Alexa+, the most significant evolution of Alexa since the Echo's debut—domesticating generative AI for everyday home use. The effort required coordinating UX across new conversational paradigms, multiple device types (headless smart speakers, Echo Show 8 & 11"), and parallel beta and hardware organizations operating under compressed timelines.
My role was to ensure UX readiness across this complex, fast-moving ecosystem—serving as connective tissue between design, engineering, product, legal, privacy, compliance, and localization teams.
PRFAQ development, core UX paradigms for new conversational model, design systems for conversation design (forms, flows, patterns), consistency across voice and visual experiences
OOBE (Out of Box Experience), FTUX (First Time User Experience), Settings and core interaction flows, coordination across headless speakers and Echo Show devices, UX readiness tracking and go/no-go recommendations
Echo Show 8 & 11" (November 2025), cross-org alignment between beta and hardware organizations, Design QA execution under hardware lock constraints
Identified and resolved a system-level visual transition defect that had no clear owner—a background rendering "flash/blip" during screen transitions. Triggered cross-team investigation between design and engineering, leading to resolution before hardware lock. This prevented a subtle but brand-eroding defect from shipping on consumer hardware.
Stabilized Design QA execution under hardware lock constraints. Acted as de facto Design QA orchestrator while covering for another UX PM. Built trust and working rhythm with unfamiliar design and engineering partners (including across time zones in India). Kept UX issues visible, prioritized, and actionable despite compressed timelines and lack of formal authority.
Introduced Day 0/30/60 triage framework that materially reduced late-stage UX churn. Surfaced systemic risks earlier through DesignOps director reviews, cross-org UX forums, and executive launch-readiness briefings. This accelerated decision-making and prevented critical launch-blocking issues.
Built durable UX operating mechanisms including intake models, review cadences, designer workflow tooling, sprint alignment, and Jira/Confluence executive reporting. These mechanisms improved transparency and reduced critical late-stage UX escalations by a meaningful margin.
Served as primary source of truth for UX readiness across onboarding, settings, and core interaction flows. Presented risk-based tradeoffs and go/no-go recommendations to Director- and VP-level leadership throughout the launch cycle.
Navigated PM/TPM attrition by stepping into gaps, establishing clear escalation paths, and framing clear options and recommendations. This unblocked resourcing and prioritization decisions during critical periods.
Established working relationships with new engineering leadership under time pressure. Coordinated with TPMs in India and multiple engineering managers across time zones, navigating constraints to keep design QA moving rather than stalled.
This program reinforced that great design program management isn't about process for process's sake—it's about creating clarity in ambiguity and protecting quality without slowing velocity. The most impactful moments came from identifying system-level gaps (like the visual transition defect) that fell between teams, and having the conviction to escalate and drive resolution even without formal authority.
Operating across parallel organizations taught me the importance of being deliberate about escalation mechanisms—knowing when to work laterally versus when to surface issues to leadership, and always framing decisions with clear options and recommendations rather than just raising problems.
← Back to Home