What I get from the article, the author doesn't actually suggest less buttons or less control over the product - quite the opposite actually. Also, music playe

What I get from the article, the author doesn't actually suggest less buttons or less control over the product - quite the opposite actually. Also, music players are quite a bad example of something to disrupt - the iPod has pretty much shown 12 years ago what's the easiest possible interface that still does what 99% of users need. I think he's rather talking about cloud services that automate some of of your task where he proposes to actually add more steps / buttons / messages in the middle that help the user understand what's going on. To quote the article: > Put your user in the middle of your flow. Make them press an extra button, make them provide some inputs, let them be part of the service-providing, rather than a bystander to it. If they are part of the flow, they have a better vantage point to see what’s going on. Automation is great, but it’s a layer of cognitive complexity that should be used carefully. (Bump puts the user in the middle of the flow quite physically. While there were other ways to build a scalable solution without the physical bump, it’s very effective for helping people internalize exactly what’s going on.)