Technology

Why Amazon's Gadget Boss Says It's OK to Fail

Martin HollowayPublished 4w ago2 min readBased on 6 sources
Reading level
Why Amazon's Gadget Boss Says It's OK to Fail
Image by finnhart from Pixabay

Panos Panay, Amazon SVP of Devices, Alexa, and Leo, told startup founders they have to be willing to fail and learn from failure. He spoke onstage at TechCrunch Disrupt in San Francisco, an event held Oct. 13-15 in San Francisco. TechCrunch

The session was billed in advance as a talk about what comes after the smartphone, with Panay making the case for Amazon's direction. TechCrunch He leads Amazon's devices, Alexa, and Leo groups.

Panay worked at Microsoft for more than 19 years before joining Amazon. He pointed to Surface RT, Microsoft's first tablet computer, as a significant failure from his time there. It led to a write-down of nearly $1 billion.

His advice was not to give up on the idea after that kind of miss. Panay said founders should keep their vision and change the plan, not drop it. Keep the goal, change how you build it.

The comments come in the middle of a longer move for Panay. Amazon was set to hire Microsoft's departing product chief in September 2023. Reuters Since then his work has focused on connected devices and voice assistants. In February 2025 he talked about rebuilding Alexa with AI, and in a Sept. 30, 2025 interview he talked about Amazon's hardware overhaul involving Echo and Kindle devices. Bloomberg

Hardware is less forgiving than software. Think of software like editing a document. Hardware is like building a house. Once the tools are made and parts are ordered, a mistake shows up as lost money, not a simple undo.

The broader context here is why gadget makers talk about failure in a different way. An online service can test a new feature with a few users and turn it off if it fails. A tablet, speaker, or e-reader locks in chip choices, battery limits, antenna strength, heat limits, and supplier deals that cannot be undone after millions ship. Testing has to happen early, in EVT and user testing, and sometimes lessons still come in public.

In my view, Panay's split between vision and implementation is the most useful part. Keeping the vision does not mean keeping the same parts list or the same controls. It means keeping the same user problem in mind while changing the design. The hard part is figuring out what failed, the idea or how it was built, without perfect data.

Looking at what this means for teams working beyond the phone, comfort with public trial and error may matter more than any one device. Home systems mix room-listening microphones, smart processing on the device, larger AI models online, and tight budgets. Makers will have to trade off speed, accuracy, or battery life, learn which tradeoff users will not accept, and fix it. Panay's point is that fixing it is the job.