Amazon Alexa Enterprise • Ongoing
Redesigning Alexa's Enterprise Console
Lead Product Designer , 2024 - Present
2 PMs · 10+ Engineers · Solution Architects
Enterprise UX · Systems Design
TLDR;
Alexa Smart Properties gave enterprise partners the tools to deploy Alexa experiences across hotels and senior living communities — but the console was built for developers, not the non-technical staff who actually used it. Deployment timelines stretched 6–12 months. I redesigned the console from the ground up, introducing automation-driven workflows and no-code content management that reduced deployment from months to under 30 days and launched on schedule in October.
CHALLENGE
A powerful platform built for the wrong user.
Alexa Smart Properties was designed for enterprise scale — but the people managing it day-to-day weren't engineers. Hotel operations managers, senior living activity coordinators, and front desk staff were expected to configure and deploy Alexa experiences across thousands of devices using a console that assumed deep technical knowledge.
The result was a system with three compounding problems:
Long deployment timelines — onboarding a new property took 6–12 months, requiring solution architects at every step.
High operational friction — non-technical staff couldn't manage content without developer support, creating constant bottlenecks.
Limited scalability — every new property deployment required the same manual, resource-heavy process with no way to scale without adding headcount.
INSIGHTS & OPPORTUNITIES
We saw an opportunity to evolve Alexa Smart Properties into an enterprise-ready, off-the-shelf platform.
Research and stakeholder interviews revealed what properties actually needed: a system that felt as familiar as uploading a file, not configuring a server.
Key opportunity areas:
Reduce reliance on technical resources — properties needed to manage their own content without waiting on developers or solution architects.
Automate the complex parts — structured content like calendars, menus, and announcements could be transformed into device-ready experiences automatically, removing the manual configuration step entirely.
Build for scale from day one — the platform needed to support deployment across thousands of devices without the process breaking down at volume.
DESIGN STRATEGY
Reduce friction without sacrificing enterprise capability.
The strategy focused on three pillars:
Content-first workflows — instead of configuring devices directly, staff upload structured content and the system handles the rest. A calendar upload becomes a schedule of Alexa-readable events. A menu becomes a set of dining queries Alexa can answer.
Role-aware dashboards — different users needed different views. A property manager needed an overview of all devices and content status. An activity coordinator needed a focused view of just their content. The console had to serve both without overwhelming either.
Scalable by default — every design decision was evaluated against the question: does this work for 10 devices or 10,000? Anything that required manual intervention at scale was redesigned.
DESIGN PROCESS
Solo designer. Large-scale project. Structured approach.
Working as the sole designer across 2 PMs and 10+ engineers, I developed a centralized documentation system early — capturing design decisions, their rationale, and open questions in a format accessible to all stakeholders without requiring navigation through design tools.
This single source of truth reduced time spent re-explaining past decisions and accelerated cross-functional alignment significantly. The team moved from extended deliberation to committed decisions within days rather than weeks.
I ran prioritization exercises with both tech and product owners to sequence the work, developed design tenets that resolved competing stakeholder priorities, and presented complex design decisions confidently to senior leadership throughout the process.
The three design tenets that guided every decision:
Support existing workflows rather than replacing them
Maintain a purposefully lightweight interface
Prioritize clarity for the guest experience above all else
WHAT WE BUILT
A no-code console that makes enterprise deployment effortless.
The final console introduced five key capabilities:
Role-aware Dashboard — a single entry point that surfaced the right information for each user type, from property overview to content-specific views.
Enterprise-Ready No-Code Onboarding — properties could configure their Alexa experience through guided setup flows without engineering support.
AI-Powered Content — staff upload structured content and the system automatically transforms it into device-ready Alexa experiences across all deployed devices.
Assisted Flows — step-by-step guidance for complex configurations, reducing reliance on solution architects for routine tasks.
Random Check-In for Senior Living — a wellness feature designed specifically for senior living communities, enabling automatic resident check-ins through Alexa devices.
IMPACT
From months to under 30 days.
The redesigned console launched on schedule in October. Properties that previously required 6–12 months to deploy could now onboard in under 30 days. The centralized documentation system reduced re-explanation time significantly and improved cross-functional collaboration efficiency throughout the project.
Customers provided positive feedback during early usage, and the launch demonstrated the platform's ability to scale without adding operational overhead.
REFLECTION
What I learned.
Documentation is a design deliverable. Creating a centralized system for design decisions wasn't overhead — it was one of the highest-leverage things I did on this project. It kept 10+ engineers aligned without requiring my presence in every conversation.
Design tenets resolve stakeholder conflicts. When competing priorities created friction, the tenets gave the team a shared framework for making decisions without escalating every disagreement. They saved weeks of deliberation.
Invest in discovery before details. One thing I'd do differently is spending more time upfront deeply understanding customer goals before moving into design details. Getting to "what is the customer actually trying to accomplish?" earlier would have eliminated unnecessary features before they became scope.