Tobey Hatch, Senior Product Marketing Director at Oracle interviews Jacques Vigeant, Product Strategy Manager for Oracle Business Intelligence and Enterprise Performance Management about how our mobile devices and business scorecards are enabling us to be more accountable and keep a watchful eye on business – even while on the golf course
Business scorecards have been around for many years – so I asked Jacques if he felt they had changed significantly due to technology. His answer was, “Yes, and no.” Jacques agreed that scorecard enthusiasts are still passionate about executing the company strategy and monitoring Key Performance Indicators (KPIs), but scorecards and Business Intelligence (BI) as a whole have changed. He explained that five to six years ago, people did BI work at the office and, for the most part, disconnected from their computer and workplace when they went home – with the exception of checking email and making a phone call or two. But now, that is no longer the case. People are virtually always connected with work and, more importantly, expect their BI and scorecards to be ‘always on,’ regardless of whether they are at their desk or somewhere else.
Basically, the BI paradigm has changed from a ‘pull’ model, where employees are at their desks querying or pulling information from the system, to a ‘push’ model where employees expect their BI and scorecard systems to reach out (or push information) to them when there is something of note to learn or something on which they need to take action.
I found this very interesting. However mobile devices do have their limitations with respect to screen sizes – does it really make sense to look at your strategy/scorecard on tiny devices? What kind of scorecard activities can you really expect to be able to do? Jacques’ answer was very logical. “When you think of a scorecard, it is really comprised of an organization of KPIs that are aligned with the strategic objectives of your company. KPIs are the heart of how you will execute your strategy. So, if you decompose that a little more, each KPI is well defined with the thresholds that you should keep an eye on and who is responsible for them. When we talk about scorecarding on a phone, we aren’t talking about surfing the strategy and exploring the strategy map like we do on the desktop. In a scorecarding context, we use the phone more as an alerting mechanism or simple monitoring device for your KPIs.”
Jacques gave a great example of an inventory manager who took part of an afternoon off to go golfing before winter finally hit, and while on the front nine holes, his phone vibrated. His scorecard was alerting him that the inventory levels for one of the products was below some threshold that he had set. From his phone, he had set up three options within Oracle Scorecard and Strategy Management (OSSM) for this type of situation:
1. Contact the warehouse manager directly by phone and work it out (standard phone function)
2. Tap/hold the KPI and add an annotation to the KPI in OSSM using the dictation capabilities of the phone and deal with it more fully when he gets back to the office
3. Tap/hold the KPI and invoke a business process from OSSM to transfer product from another warehouse with higher stock levels to the one that needs it
Being on a phone should still give you options to quickly deal with situations as needed, but mobile phones are not designed for nor should try to replicate the full desktop experience.
We covered other interesting subjects in the interview, including how Oracle is keeping pace with mobile innovation and new devices such as Google Glasses, Galaxy Gear, Pebble Watches and more, and how Oracle is handling mobile security– which is great news for our mobile workforce.
To listen to the entire Podcast, go to http://streaming.oracle.com/ebn/podcasts/media/20149746_EPM_SSM_10_2013_Taking-business-scorecards-golfing.mp3.
To learn more about Oracle Scorecard and Strategy Management, visit http://www.oracle.com/us/solutions/business-analytics/business-intelligence/strategy-management/overview/index.html.