Ryan Hops discusses how to avoid antagonizing customers when launching changes to a product or website. He provides six steps: 1) Give warnings before changes, 2) Find power users and connect with them personally, 3) Show mockups of changes for feedback, 4) Invite users to test beta versions, 5) Give legacy options for those resistant to change, and 6) Recognize that customers are sometimes wrong and innovation requires risk. The case of Digg's failed redesign that lost users is presented as an example of not involving power users and implementing too many changes at once without communication.