While listening to Pandora Radio the other day, I had a minor epiphany. For those who don't know, Pandora is a 10-year-old Internet radio service that allows its users to create their own "radio stations" based on their individual musical tastes.
After offering up a couple of your favorite musicians, the music starts to flow. Every so often, Pandora throws in a new artist that the service thinks you'll like. You can say yes or no to the new artist's song. If you don't like the artist, then Pandora will play a song from an artist that it knows you'll like, that you'll feel comfortable about.
The service eases you into the new by never veering too far from the familiar. And it's so darn easy to use that "change" doesn't feel like "change" at all. Even though change is, indeed, happening.
How does Pandora Radio do all of this? It's called the Music Genome Project, a serious undertaking to analyze, deconstruct and capture all the details that make a song a song. Pandora, according to its website, is able to "scan its entire world of analyzed music, almost a century of popular recordings—new and old, well known and completely obscure—to find songs with interesting musical similarities to your choice."
Back to the minor epiphany: Everything about using Pandora makes me contrast it with how companies roll out enterprise software to their users today (especially in traditional on-premise software deployments).
Just look at the troubling experience of Lumber Liquidators, a $500 million discount flooring chain, as it rolled out SAP's ERP software. The software, though complex, worked fine; the problem was with those Lumber Liquidators employees tasked with using the software.
CEO Jeffrey Griffiths noted on a conference call that employees' difficulties adjusting to the new software—they had previously used manual processes and spreadsheets—caused a "weak" third quarter: lower productivity led to an estimated $12 million to $14 million in unrealized net sales, reported Chris Kanaracus, in an IDG News Service article.
Now, I don't mean to single out SAP; this situation could happen (and has) with scores of other enterprise software vendors. And, of course, Lumber Liquidators would not be the first company to flub change-management processes and user training when rolling out an ERP system.
But just think of how different a user's experience would be if ERP software could work like Pandora Radio: A user inputs his role on an easy-to-consume GUI page; the system then walks the user through one or two core software processes and gets them familiar with those pages; "What else do you work on?" asks the system; the user inputs a new process related to, say, invoicing, and the system introduces him to the new process and page; the user works on that, then goes back to the core process pages that he's familiar with to see how the new process dovetails with the already learned ones; when the system offers a pre-built process or task that the user doesn't need to know about, the ERP system can remove that view from the user's tasks list.
In addition, pre-defined user roles and tasks could also help steer users through all the tasks and pages they need to know, again removing the extra software functionality "noise" that can overwhelm anyone. Users could also explore new features once they become familiar with their core tasks, with the help of the software guiding it through the training.