As a Gmail user, I had grown so used to opening the drop-down box and tabbing down to the delete option that when I didn't see it, I thought something was broken.
You see, I had come to accept Gmail's "Thou Art an Ass if Thou Throwest Email Away" point of view, and had resigned myself to being the sort of ass who deleted stuff.
So when I finally looked to the left and saw the "delete" button, I wasn't quite prepared for it.
That said, I like it. It says something important about software - you never know how people will actually use your product until you let them. Google paid attention, and reacted correctly.
I've learned to recognize that the way I imagine customers using my products is often very different from how they actually use them. Here's an example of this, but turned around a little.
I've had a bunch of conversations with our sales team lately - they've been wondering, "Hey, Bob, you were the InstallShield PM, and you used Update Service with it, tell me what you liked about it." What blew them away wasn't that I used it to send updates (which, while cool, is rather prosaic) but that I relied on it to know how fast new versions were adopted, what my product mix was, and stuff like that.
Their point of view on the value of the product was "ISVs need to send software updates". My point of view (as a customer) was "I need to know what's going on." And as a customer, my point of view wins.
Just for giggles, I've asked our developers to sit down with our own setup authors to see what aggravates them about InstallShield. They are, after all, customers. It may make your brain hurt when you realize that we use InstallShield to build our installations for. . .InstallShield. We've been listening to external customers for a long time, but we haven't listened as well to our internal customers.
Maybe we'll create a delete button. I'd like to think we'd do something sensible like that too.