How I work, 1 of 3: Building for AI
First, recognize expertise.
Curiosity about voice-driven interfaces drew me from AWS to Alexa in late 2022. I joined at the advent of a new product, Alexa Themes, that aligned to my background as a high-volume studio builder. I inherited a team that was in crisis, overloaded and under-appreciated, so I made a plan: gather insights via 1:1 interviews, then redefine roles and the model via team meetings. A few people left, and the few who stayed bought into the new model as co-owners. We delivered proof of concept to SVP leadership, then 4 Themes in 60 days—meeting the goal while raising standards and morale.
Then, reinforce roles.
A sudden management change in early 2023 added to my scope: 9 new contributors and their projects, plus relationship management across three groups of engineering, science, and product leads. My plan to increase Themes efficiency accelerated. I re-defined the agency role in consultation with my team, interviewed existing and new agencies, and then chose a new vendor that empowered my team while transforming time and cost metrics. With the Themes standard properly set at over-delivery, I dove into roles, standards, and career support for the new team members.
Value process and outcomes.
Alexa’s transformation to generative AI overlapped existing 2023-24 goals. When an executive mandate reduced my team but not my scope, I reset roles with each of my three remaining heroes. Through borrowed designers, cross-team alliances, and my own contributions, I met iterative goals while protecting Alexa Themes as the standard for customer delight. While a late hiring round made Alexa+ timelines possible, Alexa Themes remained the example of clear goals and process as essential ingredients for creative exploration and innovation.