A million things can go wrong when you deal with data or technology. Integrating business and technology requires ingenuity, discipline and fortitude. But most important is …
When you design for business intelligence (BI) or mobile BI, the response time (sometimes also referred to as load time ) will always come into question.
In mobile business intelligence (BI) design, the “case for small” stems from the need to effectively manage performance and response time for mobile experiences. The concept has nothing to do with smaller screens or device sizes. Instead, it deals with the delivery of the content onto those screens.
One of the common denominators of all mobile user experiences deals with what I call the “patience factor.” Mobile users tend to be less patient about performance and response time than PC users, since they’re on the go with less time to spare.
When it comes to defining successfor most technology projects with user rollouts, such as mobile business intelligence (BI), adoption is the key indicator of success. The degree to which users embrace the solution depends on a variety of factors. Some may be highly visible and easily measurable. Others may be less so and may require interpretation. Moreover, additional measurements such as cost reduction or productivity improvements contribute to the overall success criteria.
In business, better-informed decisions often start with a strong appetite for data, followed by a healthy dose of skepticism for it. If available, our collective insight becomes the guiding light for our decisions enhanced by data. In the absence of it—when we are left to decide by ourselves—we seek wisdom in our own experiences to fill the void where we can’t find or rely on data.
Proof of concepts (POC) specifically designed for business intelligence (BI) projects can be invaluable because they can help to mitigate or eliminate the risks associated with requirements whether we’re working with a new BI technology, asset, or data source.
When we discuss performance in mobile business intelligence (BI), we often talk about two components: response time and availability. I discussed the response time in detail in a previous blog. Today, I want to expand on availability.
Availability is sometimes referred to as “up time,” but it goes beyond that. We need to manage performance with a user focus to make sure our priorities support business execution, not hinder it.
Managing performance of any technical solution is a tricky business and mobile BI is no different. We primarily deal with two elements: What we can manage and what may be out of our control. To use a tennis analogy, we should always focus our energy on the former to make sure we can eliminate unforced errors.
When it comes to supporting mobile business intelligence (BI) implementations, what we do after we go live is as critical as what we do before. Technology support is art as much as it is science. If you add to the mix global deployments, remote access, language and cultural barriers, we face a daunting task especially when supported by virtual teams without on-site personnel. Two key elements should guide your approach: quickly identify the root cause for immediate relief and put in place safeguards to prevent future occurrences.
Fan insight is the Holy Grail of fan experience. Sports and entertainment organizations invest a lot of time and resources to better understand who their fans are, what they like and don’t like. Data is a key ingredient for gaining better and deeper fan insight. So it plays a critical role regardless of the sport, event or the size of the organization. Analyzing fan insight is like solving a jigsaw puzzle. Individual pieces (data sources or systems) in “disconnected” states won’t tell the whole story.
I joined a consulting firm just as I came out of the private sector where I was the customer of technology. In my new role, I found myself on the opposite side of the intersection of business and technology where I was looked to as the expert. I realized quickly that I had to be…