Mobile BI Mistakes: Know Your Organization
In my first book, Why New Systems Fail, I write about the perils of IT projects. Clocking in at over 350 pages, it’s certainly not a short book. In a nutshell, projects fail because of people, organizations, communications, and culture more than purely technological issues.
I began writing that book in mid-2008, long before apps and mobile BI had reached critical mass. While I know that technologies always change, when I leaf through my first text, I find that the book’s lessons are still very relevant today.
For instance, consider mobile BI. In an Information Management piece on the ten most common mobile BI mistakes, Lalitha Chikkatur writes
- Assuming mobile BI implementation is a project, like a traditional BI implementation
- Underestimating mobile BI security concerns
- Rolling out mobile BI for all users
- Believing that return on mobile BI investment cannot be derived
- Implementing mobile BI only for operational data
- Assuming that mobile BI is appropriate for all kinds of data
- Designing mobile BI similar to traditional BI design
- Assuming that BI is the only data source for mobile BI
- Believing mobile BI implementation is a one-time activity
- Claiming that any device is good for the mobile BI app
It’s an interesting list and I encourage you to check ou the entire post.
The Good, the Bad, and the Ugly
I’d argue that you could pretty much substitute ‘mobile BI’ for just about any contemporary enterprise technology, but let’s talk for a minute about the actual devices upon which mobile applications run.
With any technology, there have always been technological laggards and mobile BI is no exception to that rule. Think about the potential success of mobile BI in a typical large healthcare organization vs. a typical retail outlet.
In a very real way, mobile BI is quite similar to electronic medical records (EMRs). The technology behind EMRs has existed for quite some time, yet its low penetration rate is often criticized, especially in the United States. Why? The reasons are multifaceted, but user adoption is certainly at or near the top of the list. (For more on this, check out this HIMSS white paper.)
Generally speaking, many senior doctors have (at least in their view) been doing just fine for decades without having to mess around with smartphones, tablets, and other doohickeys. Old school doctors rely exclusively upon paper charts and pens. Technology just gets in the way and man of them just plain don’t get it.
Does this mean that the successful deployment of mobile BI is impossible at a hospital? Of course not. Just understand that many users will be detractors and naysayers, not advocates.
Retail, on the other hand, is quite a different animal on many levels (read: margins, employee turnover, elasticity of demand for the product, tax implications). Here, though, let’s focus on the end user.
Go into just about any retail store and I’ll bet you a steak vs. Saab that most of its employees aren’t much older than 30. Translation: they grew up on computers and the Internet. As such, they’ll all too willing to experiment with tablets, app, and mobile BI. The fear factor is gone and that fundamental willingness to experiment cannot be overstated.
Technology progresses faster than most users can embrace it–or, at least, want to embrace it. Like any technology, mobile BI can only be successful if your employees allow it to be.
What say you?
Method for an Integrated Knowledge Environment (MIKE2.0) is an open source delivery framework for Enterprise Information Management. The MIKE2.0 Methodology has been built to support our belief that information really is one of the most crucial assets of a business. We believe meaningful, cost-effective Business and Technology processes can only be achieved with a successful approach for ...
Other Posts by MIKE20 Governance Association
The moderated business community for business intelligence, predictive analytics, and data professionals.
|How do you innovate effectively and maintain a competive edge?|
Learn how in our exlcusive ebook, "Bad Data Need Not Apply: Designing the Modern Data Warehouse Environment."