Raising the CX Bar for Lightsail
Transforming customer experience through strategic leadership and scalable mechanisms
Transforming customer experience through strategic leadership and scalable mechanisms
As an AWS employee, I adhere to company policies regarding data confidentiality. While I cannot share specific usage metrics or proprietary customer adoption data, I have provided qualitative insights and outcomes to demonstrate the impact of my contributions. These examples align with publicly available information and best practices while respecting internal guidelines.
As the design leader responsible for the customer experience of Amazon Lightsail, I was tasked with rebuilding the UX function, aligning it with AWS standards, and delivering measurable improvements in customer outcomes.
Lightsail serves small businesses and developers who want simple, reliable cloud hosting without the complexity of other AWS services. When I assumed leadership, the product faced significant challenges, including fragmented design systems, accumulated UX and accessibility debt, and the absence of a dedicated design team. My goal was to restore customer trust and build mechanisms for consistent, high-quality delivery.
I rebuilt the Lightsail UX function, establishing a new design vision and hiring core talent to lead both foundational and forward-looking initiatives. Together, we defined a UX strategy that balanced short-term delivery needs with long-term modernization. This structure created the foundation for reliable execution, faster iteration, and alignment with AWS bar-raising design principles.
A key strategic initiative was Lightsail for Research, developed in partnership with the AWS Public Sector team. The product provided pre-configured environments such as RStudio and Scilab for researchers who needed simple, ready-to-use computing resources.
My team engaged directly with academic institutions including Stanford and Duke University to gather feedback and refine the experience. Since there was limited prior research on this audience, UX led the end-to-end product definition. I also advocated for migrating Lightsail to the Cloudscape Design System, replacing a fragmented internal system. This migration improved accessibility, visual consistency, and design velocity. Lightsail for Research launched successfully in early 2023, broadening Lightsail’s customer base and demonstrating the impact of human-centered product leadership.
For the core Lightsail Virtual Private Server (VPS) product, customer data revealed high churn within the first six weeks of onboarding. Many small-business users struggled with WordPress setup, one of the most common use cases.
I directed the team to redesign the onboarding workflow, reducing setup steps from 54 to 13. This simplification reduced time to value, increased first-use success, and directly improved retention metrics. When AWS introduced a global IPv4 pricing change that affected Lightsail customers, we mitigated churn by introducing IPv6 support and improving educational content around pricing transparency.
An accessibility audit identified more than 250 issues within Lightsail’s legacy system. I used the migration to Cloudscape as an opportunity to prioritize and address these issues in partnership with engineering. By December 2024, all high-impact accessibility issues were resolved, aligning Lightsail with AWS standards and improving usability for all customers.
Beyond product delivery, I focused on building mechanisms that sustained quality, improved collaboration, and reduced accumulated design debt across the organization. Lightsail had limited product management support, which required UX and engineering to take shared ownership of improving the customer experience. This created a strong, collaborative culture where decisions were driven by customer insights and technical feasibility.
CX bar-raising reviews: Ensured every feature met AWS customer experience standards before release.
Pre-checks: Identified usability and workflow issues early in the design and development process, preventing late-stage rework.
CX education and leadership: Encouraged designers to participate in AWS CX programs and bar-raising activities to strengthen craft and decision-making.
Design debt hackathon: Created a recurring cross-functional mechanism to identify and resolve accumulated UX and accessibility debt. These sessions reduced backlog and promoted collaboration between design and engineering.
CX debt tracking: Introduced a framework to measure, prioritize, and track design and accessibility debt across releases, ensuring continuous improvement.
Cross-team syncs: Established regular meetings with engineering leaders to maintain alignment, transparency, and shared ownership of outcomes in the absence of dedicated product management.
Vision continuity: Provided ongoing direction through multiple team transitions, keeping the customer mental model at the center of every decision.
These leadership mechanisms established a culture of accountability, shared ownership, and continuous improvement. They enabled the Lightsail UX and engineering teams to operate with clarity, autonomy, and a consistently high bar for quality.
Expanded reach: Launched Lightsail for Research, adopted by universities such as Stanford and Duke.
Improved retention: Simplified onboarding reduced setup steps from 54 to 13 and improved customer satisfaction.
Enhanced accessibility: Resolved more than 250 accessibility issues, aligning Lightsail with AWS inclusion standards.
Built a high-performing UX organization: Re-established the function, hired key talent, and mentored designers who delivered both operational and strategic outcomes.
Institutionalized CX excellence: Embedded bar-raising reviews, pre-checks, hackathons, and design-debt tracking to sustain quality at scale.
Fig 1: Create Virtual Computer
Fig 2: Create Virtual Computer
Fig 3: Virtual Computers
Fig 4: Create Storage
Fig 5: Create Storage
Fig 6: Attach Disk
Fig 7: Dashboard
Fig 8: Setup Wordpress instance
Fig 9: Setup Wordpress instance
Fig 10: Setup Wordpress instance
Fig 11: Setup Wordpress instance
Fig 12: Setup Wordpress instance
Fig 13: Setup Wordpress instance
Fig 14: Setup Wordpress instance