Showing posts with label Enterprise Mobility. Show all posts
Showing posts with label Enterprise Mobility. Show all posts

Friday, January 8, 2016

Enterprise Mobile News (0116)

Google news results for Enterprise Mobile (December 2015)
Welcome to this month's round-up of the hottest topics in mobile computing. All the hard work was done by Google & Wordle with findings massaged through my unregulated and completely unsanctioned ETD (extract, transform, and display) process.

Microsoft and Apps continue to feature prominently this month along with a larger showing by IBM. Also a number of announcements stemmed from the Forrester Wave Enterprise Mobile Management.The key topics in Enterprise Mobility this month are:
  • Apps, apps, apps - if you are interested in mobile then apps typically feature top of all searches, news, and marketing efforts. Some specific topics this month include Apple & IBM announced their 100 app milestone and Microsoft's PowerApps,
  • Microsoft & Windows - in this month a new version release and associated articles have helped  maintain the high ranking in the word cloud.
  • Management & security - when it comes to Enterprise Mobility these topics continue to be at the forefront.
Now on to the top of the top, that is the top vendors & solution providers in the area of Enterprise Mobile. Please let me know if you would like to see additional organisations in this list:
  • Adobe - Flash and Animate CC news, 
  • Apple - enterprise apps partnership with IBM, Open Sourcing Swift, and plenty of IOT / connectivity articles with Apple connecting to Ford Sync, Sonos, and the like.
  • Blackberry - Android, PRIV, and company results dominate in the last month.
  • Google (Alphabet) - Glass 2.0, Ventures, AI Messaging are getting the headlines
  • HP & HPE - Cloud partnership with Microsoft, Aruba, HP Falcon
  • IBM - app partnership with Apple along with announcements relating to the Forrester Wave dominate this month. 
  • Kony - Mobile Field Service for SAP.
  • Microsoft - Project Astoria, partnerships, updates, and results feature heavily.
  • MobileIron - Forrester Wave announcements, and investment/share price news feature heavily.
  • Oracle -  primarily partner and analyst articles.
  • Samsung - new Mobile Chief, settlement with Apple, 
  • SAP - mostly partner and analyst articles.
Disclaimer: Adam works for SAP, his opinions are his own, and all data in this article is sourced from the public domain, thanks Google and Wordle.

Wednesday, November 11, 2015

Mobile Enterprise News (1115)

Google news results for Enterprise Mobile (Oct 2015)
Welcome to this month's round-up of the hottest topics in mobile computing. All the hard work was done by Google & Wordle with findings massaged through my unregulated and completely unsanctioned process.

Last month Apple stood out with a big share of news articles. In this month's word cloud you can see that Android has grown with many Marshmallow mentions. Speaking of cloud, and mentions, the term Cloud itself is featuring more prominently than in previous months. Not unusually the key topics in Enterprise Mobility are:

  • Security & Management - these days your modern day Bonnie & Clyde are more likely to be sporting a Mac Book Pro than a Tommy Gun. They say fear sells so I'm sure that these topics will remain in the top spot for the foreseeable future.
  • Apps - feature in plenty of Enterprise Mobile news articles, surveys, and blogs. Most everyone says apps are great but not everyone has got around to buying or implementing them for everything yet. I guess I'll keep using my laptop and coming into the office for a bit longer.
  • Cloud - much buzz in the cloud security space this month with articles featuring Sencha, IBM & AT&T, Synchronoss, Mitel and many more.
Now on to the top of the top, that is the top vendors & solution providers in the area of Enterprise Mobile. Please let me know if you would like to see additional organisations in this list:

  • Adobe - eSign announcements & new mobile apps feature strongly this month.
  • Apple - iPad Pro continues to write articles with roll-outs across geographies and PR regarding a partnership with Telogis hits the news
  • Blackberry - Enterprise Server 12, rumors suggest a move away from hardware.
  • Google (Alphabet) - Pixel Tablet, Mobile Search revenue is up, Marshmallow.
  • HP - The company split grabbed the headlines this month with Hewlett Packard Enterprise and HP Inc the two new entities. 
  • IBM - partners with AT&T for cloud mobile security, big deals with Etihad & EVRY announced.
  • Kony - new LATAM leader, partnership with Exicon, 
  • Microsoft - Cloud & Enterprise team changes, struggles with Windows phone, 
  • MobileIron - Cooperation announcement by Fraunhofer Institute for Secure Information Technology + a number of revenue and stock price announcements
  • Oracle - Cloud & Mobile announcements including Sencha, Xamarin, & VMware
  • Samsung - Leveraging Oracle to rival the Apple + IBM enterprise partnership, Samsung Pay roll-out, 
  • SAP - SAP Vehicles Network, KeyNote testing, openSAP courses, & HANA Cloud Platform announcements.
  • Xamarin - added this month due to the number of announcements in relation to RoboVM & Oracle.

Monday, September 7, 2015

Mobile Enterprise News (0915)

Google news results for Enterprise Mobile (Aug 2015)
The weather bureau and financial analysts are particularly good at telling you what happened in the past and not always as flash at telling you what will happen next month. So I thought I’d use the same strategy and analyse the past month in Enterprise Mobile. Using my completely not patented method (and a little help from wordle) I’ve analysed the trends in Enterprise Mobility news and will touch briefly on the biggest topics found in each.

As you can see from the word cloud the hottest Enterprise Mobile news topics according to Google last month included:
  • Enterprise Mobile Management (EMM) driven in part by industry analysis reports, for example VDC & Ovum (where interestingly they have a conflicting view on the outlook for the EMM market) and product announcements from companies including VMware and Blackberry.
  • Security is closely related to the EMM topic and this last month's news is generated in part from industry analysis reports (for example Gartner & Check Point) and announcements from organisations such as IBM, SyncDog, and HP to name a few.
  • The news on devices includes announcements from Cisco & Apple, Samsung, Blackberry, and Zebra (to name a couple) and given that this is an Enterprise perspective it's no surprise that the device topic was heavily related to business features, security, printing, etc.
Now onto the top of the top, that is the top news from the last month for some of the top vendors in the Enterprise Mobility arena, in alphabetical order:
  • Adobe - App Analytics bundling
  • Apple - optimization with the Cisco partnership
  • Blackberry - passport silver and new BES version
  • Good Technology - mobility index report for Q2
  • Google - new workplace Glass
  • HP - releases mt42 (IOT enterprise mobile thin client) 
  • IBM  - leveraging Apple partnership in managed mobility
  • Kony - APN mobile competency
  • Microsoft - EMS subscription
  • Mobile Iron - legal news wrt Good
  • Oracle - purchase of Maximyser
  • Salesforce - enterprise Apple Watch apps
  • Samsung - S6 Edge+
  • SAP - partner press release from IntelliCorp/SQALOGIC
Cloud certainly is an underlying theme in the enterprise mobile space with all major players continuing to strengthen their approaches, tools, and messaging. Additionally the hardware and OS manufacturers are talking enterprise features and associated security. Here's hoping that this trend continues with the battleground for the enterprise space driving continued industry innovation.

Disclaimer: Adam works for SAP, his opinions are his own, and all data in this article is sourced from the public domain, thanks Google.

Friday, February 6, 2015

Mobile Maturity

Many have observed that the introduction of new technologies follows a pattern, for example the hype cycle, technology maturity curve, adoption life-cycle, etc. When you think about it mobile computing has been around for a while now. If you need a refresh refer to The History of Mobile Computing. Many organisations are already on, or are currently moving onto their next generation platform and applications. Of course enterprise mobility will not follow exactly the same path as other technology advances. An interesting example is the introduction of personal computers; there are defiantly some parallels when it comes to uptake and the impact that they have had on business, and there are some inherent differences. For example (with the exception of Mac) most PCs in the market shared a common architecture and operating system. Unlike in the mobile space where there have been several shake-ups in terms of the leading manufacturer and operating system. Can we learn something of the future of mobility from how the use of PCs in business has matured?

Prior to the advent of the PC, computers tended to be expensive and used for specialised purposes. A small company would not likely use a computer as the business case wouldn’t stack up. Software design, development, and maintenance were also specialised.

Over time as this sector matured strategies regarding outsourcing and retaining in-house knowledge evolved. Some organisations that had initially outsourced (as they had no choice) built a core team competency to take responsibility for their IT asset. There are cases in the industry where these teams became so successful that eventually they were spun off as separate companies. These new companies could then service the general market or a group of related companies for example: BHP/CSC, GE, Bosch, TCS, and Wipro (to name a few).

In the 1980’s and 1990’s offices moved rapidly from paper to PC based activities. Drawing parallels to their older larger computing cousins the industry saw a rise in new job roles and associated skills for the design, development, and maintenance of the hardware and software. Organisations again evolved their strategies for balancing in-house knowledge with costs.

As mobile device usage has become commonplace for both business and personal use a similar technology maturity is evolving. These days many companies have at least one mobile application, some companies are embracing mobile innovation with labs, entrepreneurial style start-ups, and RAD prototyping. While the evolution of mobile matures, organisations are working through a process of determining what to in-house and what to outsource.

It makes sense that businesses should concentrate on their core competencies, mitigate risk, and strive to reduce costs. Unfortunately IT can sometimes be seen as one big bucket of costs that should be delivered cheaper. To approach this correctly requires a thorough analysis and understanding of the IT landscape, skills, and market. Personally I see the value in retaining business knowledge inside an organisation so part of the challenge of course is to unpick the blurred line between the pure business subject matter expert and the pure IT expert. For more information refer to Resourcing Enterprise Mobility.

What I have seen is that enterprise mobility management and security related tasks are maturing and becoming part of the general IT landscape. In fact in many cases they are now tightly coupled with a self-service trend continuing to proliferate.

Mobile application development is also maturing. UI/UX is seen as a market differentiator and for larger organisations is an area of consideration for in-sourcing. Likewise in the complicated landscapes of large companies the architecture and design of software is a common candidate for in-sourcing. As companies develop mobile applications and gain in-house skills there will be inevitably be discussions regarding the cost effectiveness of this longer term. It wouldn't surprise me to see the mobile application departments of some larger organisations spun off into separate companies in the not too distant future.

A final thought to parallel the personal computer with mobility. Children born from the late 1970’s onwards have never known a world without PCs. When these children grew up they expected PCs to be part of society, they gained skills on these machines from an early age and leveraged these skills to further advance the use of computing. A parallel can be drawn to perhaps children born from the late 1990’s onwards. This generation of workers will never have known a world without mobile computing and its associated landscape of applications. As they join the workforce they will bring their own expectations of mobile computing along with their wealth of knowledge, and enthusiasm. I think we can safely predict exciting times ahead for technology.

Sunday, December 14, 2014

Mobile Integration

It wasn’t that long ago that UX & CX where secondary considerations for applications. Now that the sexy stuff is well and truly at the forefront of mobile applications, it’s easy to overlook the importance of the most complex (and not sexy) parts of mobile application development: the integration!

The vast majority of mobile applications that you use day to day have some form of integration / interfacing to an external system. When you think about it even the simplest of games on IOS and Android are connected to a scoring system or to in-app purchases. Your social networking apps are connected to vast databases of data and selfies! The good news is that as mobile and web frameworks have matured so has the approach to integration. Most applications now have a service library that is abstracted from the user interface and functional logic. This means that many integration tasks are pre-existing and can be leveraged with minimal new development effort.

No need to fear the integration layer, just apply appropriate governance and resources to this area to ensure success. Depending on the scope, tools and standards you adopt on your project there will be many specific considerations for interface design. Additionally there are many sources (books, peer groups, forums) of general information that is well worth investigating.

Once you understand your scope and associated interfaces at a high level you can broadly group them, for example into the following categories:
  • Outbound Interfaces (data travels from the back-end system to the mobile application)
  • Inbound Interfaces (data travels from the mobile application to the back-end system)
  • Cross Application Interfaces (data travels between two or more mobile applications)
  • UI/Service Interfaces (data travels between the UI layer on the device and the service layer on the device)
Consider the differences between interfaces for different types of data. Transactional interfaces where for example a new order is created. Master data interfaces where for example customer phone number changes. Reference data interfaces where values for configuration or a drop down menu need to be maintained.

Additionally the nature of mobile applications brings some unique challenges when it comes to integration:
  • Communications are not reliable
  • CPU is less than desktop
  • Dynamic and storage memory is less than desktops
  • Offline versus Online
  • Data synchronisation
  • Data residency & Housekeeping
  • Security & Encryption 
With a desktop application you can normally assume a relatively good connection experience. With a mobile application, design will need to consider a less than constant connection. There are a number of strategies adopted to handle this and these decisions will influence the interfacing approach. Tightly coupled with this communications challenge is the data synchronisation strategy (which is often different for each data type). For example reference data that doesn’t change often could perhaps be pushed to the mobile applications when the data changes. However data that is needed on demand (such as availability of inventory) could be pulled by the mobile application when required. The cycle of data update via interfaces needs to be considered. Mobile solutions are sometimes one of many channels that will be involved in a given data object. For example if customer details can be maintained in a mobile application and in a desktop GUI how are conflicts to be treated. This is especially critical in offline style applications.

For each in-scope interface it’s important to document key design information. At a high level each interface specification should contain:
  • The data schema – what data fields are being shared between applications, what fields are keys and mandatory
  • The trigger – what makes the interface fire, is it user fired or scheduled.
  • Logic associated with the fields
  • Is the interface synchronous or asynchronous – does it wait for a response
  • What is the error handling logic
  • What is the frequency
  • Security & authentication 
Rest assured that integration for mobile applications will continue to improve and that simply applying an appropriate strategy early in your project cycle will enable the sexy parts of your mobile applications to play seamlessly with all their connected parts. This article is partly extracted from the book “Enterprise Mobile Tips and Tricks”. For more information regarding all facets of mobile application projects download it now for free.

Monday, September 1, 2014

Sticky Not Tricky


In many recent technology success stories a key component is the “stickiness factor”. These super sticky websites and applications grew their user base virally and exponentially. If you haven’t caught on yet don’t worry the concept itself isn’t tricky. In this context sticky describes when users stay longer, and keep returning to use software. In the case of the web, the browser’s homepage (and to a lesser degree favourites) helps a site to be sticky. Increasingly however mobile applications with their installation process, accessibility, and features, have better opportunities to be sticky.

Most people think of stickiness as purely for consumer facing applications. Enterprise applications can make use of sticky techniques to increase usage and drive employee behaviours. The carrot and stick need to be appropriately considered depending on your relationship with your users, organisational culture, and appetite for risk. For example you don’t want to drive the wrong behaviour in your employees by encouraging them to play with their phone rather than doing their job.

So what features make an application sticky? Gamification techniques are often favoured. Some examples of these include achievements, point scoring, leader boards, time/daily based challenges, and obsolescence. (For further information on gamification please refer to the article “Enterprise Gamification is it a thing?”). Additionally providing time sensitive information such as news updates, enabling chat features, and importantly social networking techniques can encourage users to return to your application. Along with the social and gamification possibilities to be truly sticky the application must be usable and as simple as practical.

Why worry about sticky? Stickiness is a key contributing factor to user uptake. Gone are the days of build it and they will come, with user expectations continuing to increase. Let’s face it you want users to be excited and motivated to use your mobile application. Consider marketing and messaging reinforcement, every page view and every second that a user is interacting with you impacts brand loyalty and provides additional opportunities. Leverage your crowd. No matter if you have millions or just hundreds of users. Can you consider a way that you can help them to help you?

Sticky Concepts for Enterprise Mobility
Consider the KPIs that you are driving and factoring these via sticky/gamification techniques into mobile applications. For example imagine a service organisation with a mobile application to capture work events. This organisation is keen for each employee to capture customer success stories. You could simply add a survey to the application; however it might be much more effective to enable your employee to capture a video of the customer’s reaction to their service. Allow employees to reach their KPI in an interactive way and reward the best videos with extra recognition.

Different types of business may be able to offer specific features that make their applications stickier. For example in the financial sector some examples could include:
  • Providing an application feature like balance without log-in could encourage users to keep an app running and refer back to it more often. 
  • Goal tracking for personal finances is a logical way to provide added value that keeps users returning to track their progress.
  • Providing up-to date stock or currency conversion information
In a supply chain business some examples could include:
  • Providing top performer lists and associate rewards
  • Setting real-time watch lists for key events and/or status of key orders or incidents
  • Adding features like online chat for service. 

Sales and Call-centre/help-desk business process have clear targets and readily available statistics that can leverage gamification techniques. If your organisational culture has a competitive streak then adding gamification features like a scoreboard can provide a real talking point. Perhaps the top 5 sales people could be shown in an easily accessible way. In addition adding social type interactions such as “liking” or “sharing” key events can drive stickiness.

For enterprise mobile applications (regardless of whether they are B2E, B2B, or B2C) a user base that is motivated to engage is important to success. Don’t rush in but carefully consider your goals and the culture, along with appropriate techniques and rewards in formulating a useful sticky mobile application.

Friday, August 8, 2014

Kicking-off Your Enterprise Mobility Project

The following is an extract from the book "Enterprise Mobile Tips and Tricks"



The requirements are done, the vendor is selected, and the project kicks off. Once you’ve gone through the RFP process, secured funding, and selected a solution and/or vendor for the mobile enterprise project, you’re ready to get started right? Not quite, there’s still one more step, and that’s to get everyone on the same page.

This is easier said than done as you’ll need to involve both internal, and often external, experts covering areas such as:
  • Business knowledge
  • Backend/existing systems
  • Network communications
  • Infrastructure/Server teams
  • Security, fraud, risk teams
  • Standard Operating Environment
  • Telecommunication providers
  • Device/hardware providers
  • Software vendors
  • Service providers

Multi party integration and communications can make things quite a bit more complex, so it may be best to err on the side of over-communication. In many organisations in this situation they utilise a service provider to herd all the cats. A thorough stakeholder analysis, asking questions and clearly defining requirements and expectations will make for a smoother and faster project.

To begin the ramp up process, both internal and external teams need to start joint preparation for the project kick off. When preparing to dive into the project, each organization is different, so assume nothing. Variables and needs should be covered-off and agreed upon before moving forward. It doesn’t need to take a great deal of time or cost to cover these (can be done via a meeting or conference call or even sent as a document), and it’s imperative for an efficient and well-managed project.

Project Initiation
A couple of key areas of importance in these complex projects are:

Handover
The nature of the project and availability of resources could dictate a formal hand-over or informal sessions. Ideally by this stage, along with the client’s RFP or RFQ document, there is a formal response from the sales team to the customer. Consider the size and nature of the project and ensure to schedule an appropriate amount of time between sales and delivery to fully understand the expectations.
While not always possible, ideally all three parties (customer, vendor sales, and delivery services) are involved in this hand-over process. If there are issues or misunderstandings between the involved parties, be sure to mitigate appropriately.

Methodology
Customers and vendors may very well differ in their project management methodology. A preferred project methodology may not have been designed with mobile projects in mind. Even the decisions on tailoring and agility will have a big downstream impact. So it’s important that all parties are clear on the methodology for the duration of the project. While this can be a challenge, it ensures everyone is going in the same direction at the same speed and measuring against the same benchmarks.

Deliverables & Templates
Like any good project set expectations, clearly define RACI elements; understand timelines, communications mechanisms, roles and responsibilities. A pointer here is to ensure that your deliverables and associated templates are suitable for a mobile project. For example your Design/Blueprint document will need considerations for Screen Flow, Use Cases, Usability Experience, and Integration.
By their nature a mobile project often involves multiple vendors. One vendor might supply the underlying software technology, another providing User Experience, others responsible for integration, and yet another providing hardware.

Prototyping and/or a Proof of concept
Enterprise mobile projects involve technology that is emerging and changing rapidly. Due to this the stakeholders and decision makers cannot be experts across all the technology and possible options. For this reason, along with the need to visualise User Experience options, enterprise mobile projects will benefit greatly from prototyping. Within an enterprise mobile project it can be difficult to get the best value out of a traditional ‘blueprint everything up front’ approach.
Along with not understanding potential pitfalls it would be easy to miss out on leveraging all the possibilities of the new/emerging technology. Some projects may be able to leverage the build tools for prototyping purposes (or just mock-up examples in a drawing program). Utilising tools that are not fit for purpose can be problematic. The installation, environment, setup, training and, accessibility of build tools may make them difficult to leverage.
With a mobility related project some of the true “right once deploy many” MEAP options will let you pull off a prototyping approach. However not all projects, build tools, and even MEAPs offer great prototyping features. Even when all the stars align can you effectively gather feedback from your audience?
Depending on the size of your project and or the vendors involved it may be worth considering a fit for purpose prototyping product. These products enable rapid prototyping on device (or emulator) along with useful feedback mechanisms. While of course there is an associated cost with using these products it may save you money in the long run.

When to use
The adage about spending more time on design and less on build rings true. With prototyping tools the focus can be on design without needing to spend so much time. These types of tools can be leveraged in various project phases for example:
  • Part of RFP/RFQ process to build a mock-up that can be quoted on.
  • During the design/blueprint phase to finalise an agreed functional design.
  • Throughout the build phase to prototype traditional blueprint/designs.
  • Ongoing in support/run phases to formalise change requests
Download the full book "Enterprise Mobile Tips and Tricks"

Thursday, June 12, 2014

Product versus Custom in a Digital World

When contemplating this topic I kept considering an alternate title 'risk versus reward in a Digital World'. Certainly in the Cloud era it's increasingly unpopular to tout customised, coded solutions. And rightly so as for many business processes and associated systems there is a long standing maturity. Consider a few well known examples:
  • Human Resources
  • Customer Relationship Management
  • Purchase to Pay 
Additionally with a lot of well-known Back Office internal facing processes like Accounts Receivable, Accounts Payable, and Customer Service (to name a few). These dependable workhorses are often put out to pasture in offshore fields.

I'm certainly not going to suggest that standardisation is a bad thing for business. Repeatable, measurable process is a key to efficiency. Likewise however innovation is a cornerstone to competitiveness. Unfortunately it's much easier to produce a clear business case for standardisation than it is for innovation. This might drive many organisations seeking to compete on price to reduce costs and forget the importance of innovation. Seen as a risk mitigation strategy, generally it's politically popular to promote a buy not build mantra for IT projects.

When contemplating digital, mobile, and consumer facing solutions the expectation is increasingly bleeding edge. This of course is at loggerheads with the “buy not build” message. None the less a certain degree of differentiation can be achieved by branding and with advances in user centric design. When it comes to enterprise and distributed solutions the challenge is that the entire stack needs to support the demands of the requirement/s.

Here's a rather simplistic look at some of the high level strategies and associated pros and cons:

Buy not build
  • Fit for purpose: low
  • Cost: low
  • Support-ability: high
  • Innovation enabler: low 
Platform technology
  • Fit for purpose: med
  • Cost: med
  • Support-ability: med
  • Innovation enabler: med 
Custom build
  • Fit for purpose: high
  • Cost: high
  • Support-ability: low
  • Innovation enabler: high 

Of course there are methods and sub strategies to mitigate all of the cons of every path. Many COTS packages allow a large degree of configuration. Many platforms come with accelerators or pre-packaged examples. Custom build can be successfully implemented with good process.

A couple of popular mitigations to enable innovation when selecting COTS packages include:
  • Selecting an innovative and/or collaborative vendor
  • Introducing an empowered innovation or process improvement team. 

So how does one choose a particular strategy and mitigate the risks that come with it. If you've ever read my blogs before you know I'm going to bang on about the requirements. Understanding and documenting the requirements will enable selecting an appropriate strategy. These should include broader considerations than just single project’s needs. Think architectural standards, existing assets, ability to execute, and appropriate risk assessments.

When the requirements are not core to differentiation, and there is a good fitting (meets your strategy, standards, business needs) COTS package available it makes sense to buy it. When the requirements are targeting differentiation there will likely be no COTS package that cuts the mustard. The middle road of leveraging a platform can help split the difference.

On the surface a custom built solution may initially seem cheaper. But ensure to compare apples with apples. In reality, for most integrated complex applications, custom built will cost more than buying a prebuilt solution. A popular approach to mitigate the cost is to find the cheapest developers and/or offshore party. This is often successful for well specified, non-integrated and fairly simple applications.

As mentioned in Enterprise Mobile Tips and Tricks an Enterprise Mobile project is unique in its complexity. Combine this with innovation and chances are you will be writing custom code. Digital applications are commonly becoming throwaway items with an ever decreasing shelf life. Components of the digital application are expected to be regularly replaced and enhanced. Therefore for these applications this extra element must be considered when balancing cost, quality, and timeframe.

For digital enterprise mobility ongoing change is the standard. To enable this ongoing flexibility on a complex distributed system requires more than just a series of independent software components and associated business cases and projects. To be successful a planned foundation needs to be laid. The foundation in this case should include a vision of how the ongoing change goals are going to be met along with processes, tools, and appropriate resources. More than just the standard project management there are some key aspects that can assist to ensure ongoing cost effective success:
  • Architectural guidance
  • Documentation & Trace-ability approach
  • Development, Testing & Release management approach
  • Skills (& Vendor) management
  • Ongoing Research & Development 
In human terms the ideal enterprise mobile application is a mix of looks, brains, and personality – perhaps a combination of high profile celebrity, Olympic athlete, and Nobel Prize winner. Digital Enterprise Mobile Projects are expected to have the best of all worlds. A great user experience, bleeding edge features, robust, high performance, seamless integration to complex back end system, and all for a low cost.

In the digital world innovative differentiation when done correctly is a key to success.

Sunday, March 2, 2014

Resourcing Enterprise Mobility


For many organisations, and increasingly for the recruiting agencies that support them, understanding Enterprise Mobility is becoming a key focus. While Enterprise Mobility is not new, it has traditionally been the realm of specialist providers. Over many years hardware manufacturers have supplemented their sales by providing consulting services or value added software to businesses. Additionally solution integrators and niche mobile companies have provided solutions for industry. Early adopters and in particular certain industries (such as logistics and asset management) have been using enterprise mobility for many years. Often these companies have developed in-house skills through projects and support.

As the industry matures there is a shift away from point solutions. Many businesses have adopted a corporate mobile strategy with multiple mobile applications. The term “consumerisation” is often used to describe the proliferation of smart phones and app stores driving demand and innovation back into the business arena. Of course this is a double edged sword with Enterprise Mobility continuing to experience rapid change with hardware, operating systems, and applications evolving rapidly.

What is Enterprise Mobility and what are the Key Skills?

Enterprise mobility is often defined as mobile application/s with integration to back-end business systems. With this as the baseline then to resource effectively it’s useful to know the key components of Enterprise Mobility. These include:

· User Experience

· Graphic & Screen Design

· Mobile Data, Application and Service Layer

· Mobile Device Hardware & Peripherals

· Integration Layer

· Back End System/s

Along with any technology implementation there are key streams that support the project. While these are “generic” in nature there are many peculiarities when it comes to a mobile project and it’s useful to have experienced resources to cover these areas. Examples include:

· Business Process Management

· Test Management

· Architecture & Infrastructure Management

· Release & Code Management

· Security


Key Resourcing Challenges

Given the Enterprise Mobile landscape evolution it’s easy to see that the goal-posts are moving. Experience on mobile projects is sort after but not always easy to find. With mobile technology changing quickly and increasing pressure on enterprises to have an up-to-date mobile presence there is a resource supply/demand problem. The following points are some key challenges that should be considered:

· For recruiters to be effective it’s useful to have a breakdown of the technical components and/or architecture in use. In the changing landscape there are many mergers and acquisitions so it’s not uncommon to find a vendor solution made up of disparate components.

· Along with the technology challenges an additional complexity often overlooked is geography. At a given point in time each geographic region may have different consumer trends, technologies, manufacturers, and standards. This can add to the difficulties when attempting to source key resources.

· Another key challenge is the variety of technology used in the mobile landscape. Take development skills as an example. For some projects .Net is required and in others it will be Java, HTML5, CSS, JSP, or Objective C (to name a few). Increasingly with mobile platform use becoming more popular it may be necessary to have skills in a vendor specific toolkit. For some organisations they may need skills in all the listed examples!

· For Solution Integrators and other companies with a skilled resource pool keeping them up-to-date on changing technology is complicated. Investing in sensible training is important for any organisation, however deciding on which technology to target requires a crystal ball.

· When it comes to mobile applications most people focus on the developer skill-sets, however understanding the intricacies of mobility as it impacts methodology, testing, quality assurance, and architecture are equally important to the success of any mobile project.


Resourcing Strategies

Finding great resources for Enterprise Mobility is certainly not all doom and gloom. Often while underlying technologies are changing much of the skills are transferable. This approach is commonly used in the development space where in-house skills may have been built up in a particular software language. Once an organisation begins to leverage a new technology it is often prudent to retrain resources. Of course this approach needs to be managed carefully to ensure the required standards are met on the next project. To mitigate this risk experienced management/leads along with quality assurance, code management, and principles can be applied. In addition to retraining existing resources the following points are worth considering to help make resourcing smoother:

· Given both the technical complexities and the changing landscape a standard resume search may not yield the right candidates. It’s imperative that recruiters understand the technology components and the resourcing approach along with required skills and the ability to retrain/mentor and guide people with similar/complimentary skills.

· Shifts in the market often bring opportunities to leverage a surplus of complementary skills. For example with companies like Nokia and Blackberry there was a shift in relative market share. Whenever there is a acquisition there are often good employees looking for their next opportunity.

· Consider the global pool and that with the correct governance approach a blended team of onsite and offshore can work effectively. It is important that appropriate measures (standards, communication, reporting, etc.) are put in place to manage outcomes.

· Many companies cycle between in-house and outsourced specialist skills. There are good arguments on both sides. To be effective ensure that appropriate thought is put into the model, especially when changing from one style to the other.



Especially in the area of Enterprise Mobility where often skills are in short supply. It may pay to source based on softer factors. For example attitude, integrity, willingness to work, intelligence, and fit to the specific working environment. Anyone can run a query of key words across linked-in or a resume database. To find the right people it’s important to understand the requirements, the technology stack, the resourcing model, and the potential candidate.

(This article was originally published on Enterprise Mobility Network

Tuesday, September 24, 2013

Enterprise Mobility more than just Hardware and Software

Recently I presented at CEBIT and explained why Enterprise Mobility is more than just hardware and software. For those of you who couldn't attend here is an overview of the presentation:

Intro
Enterprise Mobility is not new, it has been around for many years in one form or another. There are plenty of early adopters out there and experienced exponents will tell you that Enterprise Mobility is more than just software and hardware. Enterprise Mobility is a journey undertaken by business to realise the benefits of a mobile workforce.

Why Mobilise?
Enterprise Mobility is about getting efficient use out of your mobile workforce and the technology available to them. People who perform work away from the desktop use information and they collect data. This data is then used back in the organisation as information. So efficient management of the data/information cycle leads to Less Bad and More Good.

Less Bad
Leveraging Enterprise Mobility has the power to remove a lot of waste from an organisation. One example is a beverage company that delivers drinks to its resellers. Their process involved printing the paperwork for the truck run, loading the truck, delivering the goods and handing a carbon copy of the invoice to the customer for signature and taking payment. Now this sounds ok but of course what happens in real life is that sometimes the goods were damaged, or loaded on the truck wrong, or the customer changed their mind, or a 1000 other things went “wrong”. This of course lead to truck drivers getting out their pen and calculator and manually adjusting the invoice. Once back at the depot there would be a reconciliation nightmare both for cash and for inventory. Now replacing this process with a mobile solution that included barcode scanner, a mobile printer, and a secure credit card payment system meant that all allowed adjustments could be made on the spot and the backend system updated automatically.

More Good
Enterprise Mobility isn’t just about getting rid of the bad things. It’s about increasing good things. Processes like Field Service and CRM are greatly enhanced by a mobile solution. When Sales Reps or field workers have a plan on a piece of paper they cannot adapt quickly to changes. With a mobile solution information can be shared more easily. Between the different people in the field and with the planners back in the office. Work can be more collaborative, accurate, and timely.

Mobile Challenges - Hype
There is no doubt that there are a lot of statistics around about mobility. In fact around 90% of statistics about Mobility say mobility is fantastic. I’m sure you are all familiar with a variety of quotes about statistics one of my favourites is “There are 2 kinds of statistics, the kind you look up and the kind you make up”. Sometimes statistics are quite useful but I’d keep a watchful eye open and always ask the question what does it mean for my business?

Justification
The art form of benefits calculations and business value. It's easy to be swayed by stories of large cost savings or increases in throughput. As an advocate of mobility I believe you can get good business value from mobile initiatives. But you need to do your due diligence. Understand the benefit areas can be wide reaching and include things like reduction in ongoing training and change management. Mobile initiatives can often form the bridgehead for future mobile work and this can be challenging to factor in.

New Technology
Mobile technology can require learning a new language with a whole set of its own acronyms and terminology. HTML5, MEAP, MDM, MDAP, etc, etc. Adding to the confusion an acronym can mean one thing in the mobile arena and something completely different to another audience. I remember having a conversation with someone awhile back about MDM. They thought I was discussing Master Data Management while I was happily referring to Mobile Device Management. The challenge here is of course: "What's the right solution?"

Rapid Change
There is plenty of evidence of rapid change in software and hardware in the mobile arena. Not long ago everyone was using a Nokia, then a Blackberry, now maybe an iPhone or Android device. In a few years who can say Google Glasses or Fujitsu Slates? Change of course is not limited to hardware and software but is most relevant to business process and the way mobile technologies are used.

The Mobile Journey
As with other business change there is beginning to the mobile journey but more often than not no end. Once a new technology and process is introduced new ideas will flourish and the cycle will continue. From steady state to new needs, and requirements.

Business Case
To stay in business it’s important to consider how funds are spent. Organisations of different sizes and types go through a business case process with more or less rigour. Some organisations may be capital heavy and invest in large equipment or plants. In these cases IT spending may be seen as a small insignificant part of the overall investment plan. For others money spent on IT is core to their DNA. Regardless of the company type there are always competing initiatives for funds. As well as getting a place in the investment hierarchy a business case has a number of benefits:
  • Socialises concepts and aligns vision (Needs)
  • Sets scope and boundaries (Requirements)
  • Defines the costs and benefits (ROI)
  • Acts as a reference for future stages of the mobile journey
While a business case for a mobility project can be treated in a similar fashion to any other business case. Here are a few tricks and traps to look out for:
  • New technology is not well understood
  • Replacing paper processes may have greater benefits than replacing an existing system
  • A mobile application could form part of marketing / advertising spend
  • Mobility investments often establish the basis of multiple projects
Product Selection
As mentioned in the challenges a lot of Enterprise Mobility relies on new rapidly changing technology. People often ask me why they should invest in product Y when last week product X was the next big thing. This is similar discussion that many people have around choosing a new mobile phone. Should I wait for the next model? This is another reason why that business case is so important. With an understanding of the drivers and benefits areas you can feel confident in making a decision that will archive your business goals. NASA doesn’t pick the latest mobile technology to go into their mars lander programme. They have a list of requirements and the pick the best fit for these requirements within their budget constraints.

Of course there are a number of technical solutions to mobilising an enterprise so if the technology is new to you consider some of the following:
  • Industry events (get some insight, network, and talk to experts)
  • Similar non-competitive companies (perhaps another geography)
  • Web & Social (plenty of people willing to help)
  • Existing partner network (your solutions partners may have expertise)
  • Research firms (such as Gartner or the newer crowd sourcing alternatives)
  • Back end connectivity (ensure your technology integrates)
  • In house talents (mobility is an exciting area for many people)
  • Platform or point solution (does your case allow for future expansion)
Realisation
The realisation phase of a mobile journey is where the rubber hits the road. The scope of this phase can vary widely depending on the business case, the product selected, and the implementation approach. Ensure that before too much rubber has hit the road all involved parties agree on the way forward. There maybe a big difference between leveraging an existing cloud solution and a more traditional waterfall driven software project. Regardless of how agile (or not) the project is each will (or should) have a a degree of:
  • Design/Confirmation
  • Build/Implement
  • Test/Train
  • Pilot/Deploy
During realisation is of course a key time to be referring back to that business case and most specifically the requirements. Oh and if you're looking for a great result never forget the importance of business and IT change management.
Support
One of the easiest traps to fall into is to leave support to the end of the journey. It's important that support and supportability requirements are baked into the business case. Supporting mobile applications and hardware has a couple of added complexities that traditional desktop support may not have to contend with:
  • Unreliable communications
  • Bleeding edge technology
  • Frequent change
  • BYOD
  • Many layered fault determination
If you have considered support up front then hopefully you have a solution that includes tools to empower your users and the support team. Finally a couple of points on the importance of baking Change Management into the entire journey. From an IT sense consider how to handle software/hardware updates and the impact of change to other systems. From a business perspective consider the people, the process, and how mobility changes the game.

Thursday, June 20, 2013

The History of Mobile Computing


Mobile computing is the culmination of a number of technological advances that have occurred in parallel. Key aspects that have led to the current explosion of mobile computing include general computing, user interface, display, communications, storage, battery, and culture. I've collected some of the key milestones into the above timeline for consideration. (You can click the image to open a larger version). Please let me know of any items worthy of inclusion or alteration.

Mobile computing is used when there is a need for computing power away from a desk or office environment.  Initially this became evident in military and advanced transportation scenarios. For example when calculating ballistics in ships and submarines or to help carry out checklists on spacecraft. These days with mobile computing being ubiquitous everyone can use the power of mobile computers to assist with business and personal tasks.

Between the abacus and the pocket calculator there weren't a lot of leaps directly in mobile computing. However the complimentary technologies where falling into place to support the current mobile computing that we enjoy today. Also I find interesting that throughout the years inspiration in the form of science fiction predicted or prompted advances in technology. For example Star Trek is credited as inspiration for the development of the mobile phone. Famously the film a space odyssey 2001 was referenced in law suits in relation to the development of the tablet computer.

Now with growing power and sophistication mobile computing is often discussed in terms of being the new desktop or the new internet. For more thoughts on this and other topics please refer to my blog on the future of mobile computing.



Sunday, June 2, 2013

One Fujitsu at CEBIT



Thanks to Fujitsu Australia's involvement in CEBIT many people have a new and wider perspective of Fujitsu's products and services. Located prominently, right beside the entrance to hall three. Fujitsu had a high visibility booth modeled around the Fujitsu infinity logo. A great example of "One Fujitsu" the exhibition showcased products and services from across the Fujitsu group, this included:
  • Fujitsu servers
  • Storage
  • Desk-based computing
  • Mobile computing
  • Tablet and slate computing
  • Scanners
  • Business and Application Services
  • Enterprise Mobility
  • Cloud and Hosting solutions
Here's a quick overview video encouraging people to visit the booth. Fujitsu also had fantastic participation and involvement from partners including:
Leading up to the event social channels such as Twitter, Linked-in, and blogs where engaged to increase awareness and encourage participation.

The CEBIT social team and partners actively re-tweeted Fujitsu's involvement which spread the message further. Throughout the three days Fujitsu partners including SAP and I Know IT helped spread awareness by live tweeting information from the event. Additionally Fujitsu and partners educated a wide audience with more than 30 presentations.


Presentations where well attended and included the following topics:

  • Why Cloud, Why Now?
  • Scanning and Archiving
  • A DIY Cloud in Kit Form?
  • Mobility - More than Mobile Apps
  • Fujitsu and the DC PODFactory

With more than 30,000 attendees there where many enthusiastic and interested visitors. One visitor that would be familiar to many was Senator Stephen Conroy, pictured below with the Fujitsu Group's Executive Director of Sales Mike Inge.



Sunday, May 19, 2013

An Enterprise Mobility Journey

Enterprise Mobility is more than just software or hardware it's a journey undertaken by business to realise the benefits of a mobile workforce. There is a beginning to the journey but more often than not no end. As with the introduction of other initiatives this journey tends to be circular. If you start from identifying a need, work through realisation, and move into support eventually new needs will arise. Of course that's why it's important to underpin all of this with a view to ongoing change management. Here is one way of categorising the key aspects of an Enterprise Mobility Journey:
  • Business Case
  • Product Selection
  • Realisation
  • Support
Enterprise Mobile Business Case
To stay in business it’s important to consider how funds are spent. Organisations of different sizes and types go through a business case process with more or less rigour. Some organisations may be capital heavy and invest in large equipment or plants. In these cases IT spending may be seen as a small insignificant part of the overall investment plan. For others money spent on IT is core to their DNA. Regardless of the company type there are always competing initiatives for funds. As well as getting a place in the investment hierarchy a business case has a number of benefits:
  • Socialises concepts and aligns vision (Needs)
  • Sets scope and boundaries (Requirements)
  • Defines the costs and benefits (ROI)
  • Acts as a reference for future stages of the mobile journey
While a business case for a mobility project can be treated in a similar fashion to any other business case. Here are a few tricks and traps to look out for:
  • New technology is not well understood
  • Replacing paper processes may have greater benefits than replacing an existing system
  • A mobile application could form part of marketing / advertising spend
  • Mobility investments often establish the basis of multiple projects
For further reading refer to these articles:

Enterprise Mobile Product Selection
At the outset it's worth mentioning that no one has a working crystal ball and it's clear to most that mobility is an area of rapid change. Often people ask me how can they trust product Z when last week product X was the leader. This is the same argument many people have when they are looking to buy a new personal mobile device or other technology. "Should I buy model X now knowing that in a few months perhaps a new model will be better?" My response is to harp back to the business case and requirements. If you know that the delivered features will enable you to achieve your business goals then you can feel comfortable. Consider when NASA built the Mars rovers they didn't look for the most recent or powerful mobile device, they used a clear list of requirements.

Of course there are a number of technical solutions to mobilising an enterprise so if the technology is new to you consider some of the following:
  • Industry events (get some insight, network, and talk to experts)
  • Similar non-competitive companies (perhaps another geography)
  • Web & Social (plenty of people willing to help)
  • Existing partner network (your solutions partners may have expertise)
  • Research firms (such as Gartner or the newer crowd sourcing alternatives)
  • Back end connectivity (ensure your technology integrates)
  • In house talents (mobility is an exciting area for many people)
  • Platform or point solution (does your case allow for future expansion)
For further reading refer to these articles:

Enterprise Mobile Realisation
The realisation phase of a mobile journey is where the rubber hits the road. The scope of this phase can vary widely depending on the business case, the product selected, and the implementation approach. Ensure that before too much rubber has hit the road all involved parties agree on the way forward. There maybe a big difference between leveraging an existing cloud solution and a more traditional waterfall driven software project. Regardless of how agile (or not) the project is each will (or should) have a a degree of:
  • Design/Confirmation
  • Build/Implement
  • Test/Train
  • Pilot/Deploy

During realisation is of course a key time to be referring back to that business case and most specifically the requirements. Oh and if you're looking for a great result never forget the importance of business and IT change management.
For further reading refer to these articles:

Enterprise Mobile Support
One of the easiest traps to fall into is to leave support to the end of the journey. It's important that support and supportability requirements are baked into the business case. Supporting mobile applications and hardware has a couple of added complexities that traditional desktop support may not have to contend with:
  • Unreliable communications
  • Bleeding edge technology
  • Frequent change
  • BYOD
  • Many layered fault determination
If you have considered support up front then hopefully you have a solution that includes tools to empower your users and the support team. Finally a couple of points on the importance of baking Change Management into the entire journey. From an IT sense consider how to handle software/hardware updates and the impact of change to other systems. From a business perspective consider the people, the process, and how mobility changes the game.

Friday, May 10, 2013

Enterprise Mobility Challenges

I wish I could tell you that mobilising an Enterprise was always easy. Like with most things worth doing there are challenges to success. Now I don't want to put you off mobility in any way! I did however want to group the tricks and traps into some sensible categories. Here is what I have come up with as the Challenges to Enterprise Mobility:
  • Hype
  • Justification
  • New Technology
  • Rapid Change

Hype
There are a lot of statistics around about mobility. It wouldn't surprise me to hear that there was a large increase in the number of statistics about mobility while you are reading this sentence. That's not to say that the statistics are untrue. Just that often they can be taken out of context. No doubt the % of people employed in an organisation that use smart phones has increased.  This usage is nearing saturation in a lot of the developed world. What I'd encourage people to think about is "What does this mean for business?"

Justification
The art form of benefits calculations and business value. It's easy to be swayed by stories of large cost savings or increases in throughput. As an advocate of mobility I believe you can get good business value from mobile initiatives. With tough economic times there is always more pressure to have a solid business case. So while soft benefits are great for gathering momentum you may need hard facts to win over the bean counters. Also when the rubber hits the road it's often important to be able match functionality to the benefits that you need to achieve. "What is the Return on Investment?" For more on specific benefits refer to this article on The Benefits of Enterprise Mobility.

New Technology
Mobile technology can require learning a new language with a whole set of its own acronyms and terminology. HTML5, MEAP, MDM, MDAP, etc, etc. Adding to the confusion an acronym can mean one thing in the mobile arena and something completely different to another audience. I remember having a conversation with someone awhile back about MDM. They thought I was discussing Master Data Management while I was happily refering to Mobile Device Management. The challenge here is of course: "What's the right solution?"
For specific thoughts on how to chose some aspects of mobile technology please refer to this article on HTML5 vs Native.

Rapid Change
There is plenty of evidence of rapid change in software and hardware in the mobile arena. Not long ago everyone was using a Nokia, then a Blackberry, now maybe an iPhone or Android device. In a few years who can say Google Glasses or Fujitsu Slates? Change of course is not limited to hardware and software but is most relevant to business process and the way mobile technologies are used.
I've put some thoughts on how mobile computing is changing in The Future of Enterprise Mobility.


I'd love to hear your thoughts and experiences on the challenges of Enterprise Mobility....

Saturday, May 4, 2013

The MAP to BYOD?


Recently I had the pleasure of talking with Sara, Brad, and Rob at Mocana. A team with a strong security & data loss prevention (DLP) background that are now utilising their underlying technology to provide mobile application security. I had a great discussion about their Mobile App Protection product MAP. The tool looks feature rich, is easy to use, and is maybe just the 'map' you need to find your way through the BYOD maze.
Essentially the MAP solution allows applications to be "wrapped" with a range of policies to enable secure access and provide DLP. This means in a BYOD situation a wrapped corporate application with specific restrictions (such as communications, firewall settings, copy and paste restriction) can sit beside personal applications that enjoy their usual settings.

I was treated to a demo of the solution and got to see a walkthrough of the different options and settings. From a user-friendly dashboard an administrator is able to upload a finished mobile application (that's apk for Android and ipa for Apple), select policies and associated settings, wrap the application, and finally download the application for distribution. There are a bunch of policies including:
  • Expiry
  • VPN
  • Passcode
  • Firewall
  • Geofencing
  • And more!
As well as individually wrapping applications a Federation concept enables multiple applications to share policies simplifying maintenance and communications. The application was wrapped very quickly well under 10 seconds and the file size increased by a few hundred kb.
A couple of points for consideration: Core Apple iOS applications cannot be wrapped, however typically there is an alternative software offering (email clients, browsers) that can be protected. In some cases this may help with the separation of personal/corporate activities. As an application is wrapped and then distributed the policies and settings cannot be updated without repacking and distributing the application. While this is not particularly different to the way most applications work on the Apple App store and Google Play it was just one of the areas that Mocana has for consideration in the R&D path.

Talking with Mocana I got a sense that they were customer driven. The product settings and features have been built over time based on actual customer needs and specific requests. I also got some insights into their product roadmap which includes additional policies, further federation features, and single sign on. This is a company that provides security solutions to OEMs, government and military applications. So I was pleasantly surprised by the user interface and little features like the protection indicator on the wrapped application. If you want to know a bit more checkout their website or this video.

Wednesday, April 3, 2013

Enterprise Gamification is it a thing?

Let me start by making my feelings clear. I hope Enterprise Gamification is a thing. I mean I work in enterprise mobility and I like games so I couldn't really think of a better combination (accept maybe sushi and beer or tropical island resort and cocktails). Anyway as an experienced exponent of computer game playing, and some beta testing, along with a few flash games I made 10 years ago plus my experience with enterprise systems I feel I'm adequately positioned to briefly explain what this gamification thing could be.

Drilling down let's look at the two key parts and what they do. An enterprise system typically aims to make a business more efficient and effective at achieving its goals and provide shareholder value. These systems enable business process; provide a central knowledge repository, and an audit trail. Games tend to be fun, addictive, reward behaviour, and keep score.

So then Gamification of the Enterprise is leveraging the techniques of gaming in an enterprise setting. So how can games be combined with enterprise systems? Some people would say that working is the opposite of gaming. That is one is fun and the other is not. What if we could make work fun, I think that would be good thing. Some of the key aspects to consider are:
  • Business goals
  • Key Performance Indicators
  • Positive and negative activity
  • Actors and Use Cases
  • Technology platform
  • Scoring and reward mechanism
  • Change management
  • Monitoring Success
With any enterprise systems or mobility project it's good to start with the business goals and align your technology with these directions. Each business, division, or organisational element may have different goals so there is unlikely to be a one solution that fits all.

KPIs have been designed for a reason and they are likely to be the best starting point when considering gamification. Note that the KPI itself (for example DIFOT) maybe a roll-up of individual transactions and activity. Whereas the transactions related to the KPI may be most appropriate for scoring in a gamification sense. Consider carefully that in games negative behaviour is also highlighted and the timeframe for scoring may need to be short enough to enable a "reset". If a staff member has been doing poorly for a time period they may need an opportunity to start fresh.

Different roles within the business will be aligned with particular use cases, business process, and key performance indicators. Gamification perhaps aligns best with repetitive tasks in a short lifecycle. Long term goals are less likely to make good candidates for gamification. If you have a multiple year sales cycle then tracking these sales in a scoreboard will not make for an addictive gaming experience. However tracking requests to provide assistance and assistance provided may result in a better outcome. Just like with many KPIs and many games, scoring can be done on a group level, an individual level, or a combination of both.

What's this all got to do with mobility? Well a mobile platform is the perfect vehicle (pardon the pun) to enable enterprise gamification. Sharing information is instant, scoring is instant, and the success can be tracked at any time. Let's take a hypothetical service scenario for a company that services widgets. The business goal is to fix issues the first time on time. KPIs track monthly how many issues are resolved, the resolution time, and how many times a refix is required. In the as-is business the service technicians receive a plan of work, go on site, and fix the issue. If they are not sure of something they ring up the office.
In the gamification scenario the service technicians have a mobile application where they see and update their job. They can request assistance from other technicians with appropriate skills who are currently free. They instantly get statistics on how many times they have helped others and their other KPIs. The leading technicians each month are rewarded with a voucher for their contribution to the company.

This leads me onto the reward mechanism. In the case of games the score is often the reward in itself. In many games a good score leads onto unlocking additional features, advancement, and general encouragement to keep playing. In business this needs careful consideration. Not everyone can be promoted because they did a good job. Someone who is the best at servicing widgets might not make the best widget servicing manager. However achieving a good score can form a part of an annual review, part of the bonus structure, be a trigger to get additional training, be bragging rights, or even a voucher for the company cafeteria.

Like with any new technology or business process change, the change management aspects can be pivotal to the success of the initiative. Involving and communicating with the user community in a sensible way encourages participation and allows some room when things don't go exactly as planned. As gamification is likely to be new to many organisations it makes sense to pilot it first with careful monitoring. The last thing you want to do is drive the incorrect behaviour. Ensure that the gamification is kept in context and don't get carried away. Some business cultures have more staff turnover and/or competitiveness than others and gamification can be introduced in very different ways. Remember that games are supposed to be fun.

Finally I'll finish with some quick ideas for gamification in the enterprise. Please let me know if you have some other ideas to make this Enterprise Gamification a thing:
  • Encouraging employees to help each other
  • Completing tasks in a successful or timely way
  • Identifying issues/problems
  • Taking a photo to highlight a success or an issue
  • Social communication
  • Active participation in training activities

Monday, March 18, 2013

Enterprise Glass

Google Glass is looking like a great leap forward in ubiquitous computing. My previous article covering computing uses and form factors will probably still hold true until a step change with input devices occurs. Most of the excitement around Glass is in the consumer space with amazing looking first person videos of sky diving and the like. What I wanted to write about was the potential for glass in the enterprise.

Augmented Reality
According to Wikipedia: "Augmented reality (AR) is a live, direct or indirect, view of a physical, real-world environment whose elements are augmented by computer-generated sensory input such as sound, video, graphics or GPS data."

AR is already making big inroads in the Business to Consumer (B2C) space especially for marketing/advertising scenarios. Not long back I was in Thailand and noticed a lot of people running around a Uniqlo store looking for butterflies. AR also has some potential in the Business to Enterprise (B2E) space using a mobile device to 'look' at equipment or similar. What really makes Glass a practical alternative is the hands free operation with the screen always where you need it. Makes me think of 'The Terminator' and obviously the military use similar technology in helmets for aircraft and such. In many enterprise environments safety glasses are already standard equipment so why not leverage them with powerful targeted information?

Glass in the Enterprise
Ok Sergei, Steve, Babak, and team here are some ideas that I can quickly come up with for Google Glass in the Enterprise, send me a set and I will happily come up with some more:

StyleExampleDescription
B2ETrainingNew staff are inducted to the office, OH&S policies, firescapes, bathrooms, etc using an interactive augmented reality application.
B2EHRCombined with facial recognition provide the ultimate 'whisper in the ear' to identify staff and associated metadata.
B2EMeetingsUse with IM /meeting sharing apps for a unique perspective on remote meetings. Connect to whiteboards and other equipment.
B2ELogisticsCombine with OCR/Scanning/RFID to aid with stock takes, bin counting, receipting, proof of delivery.
B2EAssetsIdentify assets, schematics, parts. Request/Enable remote assistance when repairing.
B2ERetailStaff can be instant experts on their own products. With overlayed pricing and detailed product information + onselling recommendations.
B2BRealestateInspect realestate with guided room checklists, record results. Provide virtual property tours.
B2BConferenceRecognition for attendees, AR product information, competition entry, location awareness, photography.
B2BEventsProvide targeted buyers (e.g. fashion) with glass and let them sit back and watch the show with AR provided product information.

As you can see there are a variety of opportunities to leverage and launch investments in Social, Mobile, Analytics, and Cloud (SMAC). I'd love to hear your suggestions for more ideas for Glass in the Enterprise.

Google does it again
This is the second time in my life I can recall where I had an idea that Google launched as a new offering in an amazing way. The first was around 10 years ago I was making cartoons on my animated flash website MonkeyStyle and used a collection of satellite data to allow my character to zoom into his target. Not quite Google Maps but hey it was similar in concept! In the last couple of years I drafted a science fiction novel about Augmented Reality Contacts - now they are real!