Take a miner spending his entire day excavating a complex tunnel system he’s become very familiar with. If you think of your enterprise application as a cave system, it is easy to understand what we mean by “deep” work. Simply put, deep work refers to all-day, everyday projects, while quick work refers to brief, less frequent actions within the same application-but both are equally required to move forward in the product cycle. Inevitably, you’ll lose these users if the application is too complex for their needs. While this is important, a vast majority of the users only need a subset of functionality. So why does user adoption so often fall short? Most enterprise applications are designed for a power-user experience. Of course, all of this effort is spent in anticipation of a significant ROI in not only the company’s profitability but in the improved experience for its users. This includes training business users, continuously pushing user engagement, and not to mention enduring a typically lengthy implementation cycle. This massive investment doesn’t just encompass cost, but also the considerable time, energy, and resources spent in making it successful for their business needs. When companies invest in a new enterprise application, especially one that overhauls a critical organization-wide process such as their product management, the ultimate KPI is user adoption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |