Amazon Devices Product Pages Re-invisioned

Redesigned the most important transactional surface for Amazon Devices, simplifying a feature-heavy detail page around a single customer job—launching 14 improvements that drove 1.5M incremental unit sales and a 9-figure revenue lift.

The problem

Over time, the device detail page had accumulated features serving multiple business objectives — conversion, portfolio awareness, and cross-sell—without a clear hierarchy. Customers were bearing the cognitive cost of business complexity: upsell features interrupted product evaluation, accessories appeared in multiple places, and less critical information sat above the content customers needed most to make a purchase decision. The opportunity was to align the organization around a stack-ranked set of business priorities, then redesign the page to reflect that ranking—simplifying the experience around one primary job: getting the right customer to the right device.

My role

I led the I led the strategic and organizational work that made this redesign possible. That meant defining the problem framework before any design work began, aligning the design resourcing for this initiative, and ensuring design was operating as a strategic partner to product—not an order taker executing a brief.

From a people leadership standpoint, I made an early call to restructure how the team operated. Rather than maintaining a one-to-one PM-to-designer model, I elevated my senior detail page designer into a design lead role, extending his scope to direct two additional mid-level designers across the initiative. That freed him to focus on the hardest strategic and systems-level problems while the team covered the volume of feature-level execution work the project demanded.

I also prioritized building a research foundation rather than designing on instinct. I partnered with our principal UX researcher to develop a comprehensive, multi-step research program that ran in parallel with design—informing decisions as we made them and validating the direction before we committed. That gave us something to stand behind in every stakeholder conversation.

What I did

Defined the framework that unlocked alignment. The page had three competing business priorities with no agreed stack ranking. I named that problem explicitly and proposed adopting Amazon's central Zone Framework—grouping like information and customer actions together to reduce context switching—combined with progressive disclosure to reduce visual clutter without removing content some customers would need. Framing the design problem as a prioritization problem gave business and tech leaders something concrete to align on before a single pixel moved.

Pushed back on upsell and cross-sell placement. Stakeholders wanted accessories and companion products prominently featured throughout the page. I argued that asking customers to consider the ecosystem before they'd committed to the base device was hurting conversion—if they don't buy the device, they can't buy anything else. I proposed consolidating cross-sell into a sec tion below product information and in a focused experience triggered after a customer adds to cart. A/B testing proved the hypothesis: removing upsell features from the top of the page improved base device sales.

Restructured the team to match the scope of the work. I transitioned my senior designer into a design lead role directing two additional mid-level designers, then established a working rhythm where design and product arrived at decisions in tandem rather than sequentially. That model kept work moving without creating handoff bottlenecks and built design's credibility as a strategic partner rather than an execution function.

Built a bi-weekly alignment cadence that moved the org forward. Getting director-level buy-in was the biggest hurdle. I partnered with the product management leader to bring both a strategy document and design work to leadership on a bi-weekly cadence, breaking the design into themes for each session. Once we had director alignment, we moved to VP and business line executives—Alexa, Kindle, Fire TV, Ring—whose input further shaped the strategy. I then took the work to the SVP, where the goal was alignment on business priority ranking. The SVP shifted the conversation into an open dialogue early—I adapted, and we came out with alignment on priorities, actionable feedback on features, and a clear path forward.

Invented a new delivery model to ship on time. The volume of changes exceeded what our team could execute at the fidelity we were used to delivering. I worked with product and engineering leaders to establish a just-in-time design delivery process—sharing work in progress at whatever fidelity it was in so engineers could start building, with designers available to answer questions and resolve specifications in real time. I framed the entire project as experiment-based: we weren't trying to get every feature perfect before launch, we were getting the most important changes live for our Devices fall launch event and optimizing from there. That reframe gave the team permission to move—but it also papered over a problem that would catch up with us.

The outcome

Launched 14 improvements to the device detail page in time for the largest Fall launch event to date, driving 1.5M incremental unit sales and a 9-figure revenue lift. The redesigned pages became the foundation for how Amazon Devices presents products to customers, with the framework extending beyond the initial launch surfaces.

See key, high-impact changes to sections of the page below:

What this demonstrates

This project shows how I work when the problem isn't just a design problem—it's an organizational one. Defining the right framework, aligning competing stakeholders around a shared priority stack, restructuring a team to match the scope of the work, and reinventing how design delivers under pressure are the same moves I'd bring to a retail organization navigating a complex experience overhaul.

What I’d do differently

We invested heavily in the vision work and the SVP presentation—and that investment paid off in terms of alignment. But once executive leadership reviewed the work, the assumption was that we were ready to execute. We weren't. The designs were directionally right but not fully baked—edge cases hadn't been resolved, specs weren't written, and the work wasn't ready to hand to developers. We ended up scrambling through a post-vision gap that we hadn't planned for.

If I were doing this again, I'd set expectations with leadership earlier about what "vision alignment" actually means versus what execution-ready design looks like—and I'd have partnered with my product management counterpart sooner to build a realistic project plan that accounted for the work between those two phases. The lesson isn't to rush the vision—it's to be honest earlier about what comes next and how long it actually takes.