3 ms·
There's a problem with expectations. A voice bot is a terrible CLI with no documentation. And it's intentionally that way. I suspect by avoiding a full docum
by hakfoo 4y ago
There's a problem with expectations.
A voice bot is a terrible CLI with no documentation. And it's intentionally that way. I suspect by avoiding a full documentation model, they hoped to curb user expectations. "It didn't understand when I asked it XYZ, perhaps it just couldn't" doesn't fly if XYZ is on a widely documented support list. Conversely, marketers probably figured people would find it "magical" if they were encouraged to babble at the box and some things actually worked.
This neglects the users. They'll try it out early on, and develop their own set of expectations. "This is what actually worked when I first tried the box in 2016, so I won't bother asking it anything outside that bound." In order to upset that, you need dramatic changes to visibility.
In that regard, I always thought the right form factor was something like an Echo Show. It had more opportunity to directly push command visibility, with an idle screen is a good place for "Now available: try command DEF". It also has opportunities to reduce the worst pain-points of voice UIs by showing lists of options or even just the current message, rather than waiting for the slow cadence of speech to get to the point you care about.
Part of the problem may also be conflicting incentives. I suspect there's a huge tug of war in these platforms between "how do we maximize customer experience and utility" and "how do we use these as portals to encourage vendor lock-in and take up of additional services." This might also conflict with the visibility directive: if they want to promote anything, it's going to be "Alexa, do blah-blah with Prime services" even if the user base would see more value in awareness of a new local-only feature or third-party integration.
If the platforms were more open-- to the level of ordinary users being able to evaluate the rules and set up custom macros and overrides-- that helps to neuter efforts that sacrifice the customer experience for growth hacking.
- PaulHoule 4y agoThat's what was so neat about Alexa as a demo was that it offered a few services such as playing music that were both possible to implement and possible for the user to feel like they understood what it was capable of doing. They never moved from that place, however, to anywhere better, either in terms of users perceiving it as a lot or better or being something that really makes money for AMZN.