Enterprise Collaboration Made for MobileWe've all seen the mobile snowball effect in the enterprise. It's driven in part by the consumerization of IT and the bring your own device movement. The more we use mobile, the more opportunities to conduct business on the go become available, so the more we rely on mobile. This is great, but brings with it some challenges.

As I mentioned last month’s piece about getting back to the basics, this is the year when we figure out "the right mobile strategies and align them with business needs across different mobile personas, device types and intranet applications."

Since the start of this year, 17.4 percent of web traffic has come through mobile which is more than a 6 percent increase since 2012, according to Statista. And last year ComScore reported that 40 percent of Internet time is spent on mobile devices -- this is likely higher today.

For the enterprise, what’s interesting about this is the shift towards a mobile workforce. We’re seeing expanded opportunities for collaboration across geographies, time zones, travel, etc.

So what do we keep in mind when implementing a mobile solution for collaboration in the enterprise?

Your Audience Knows What it Needs

Are they using corporate devices on the road? Or their mobile phones on the bus on their commute? Do they review documents, electronically sign documents or edit documents? Are they more spreadsheets or Word docs?

Don’t just take a solution out of the box. While that may seem like the cheaper option, it will cost in terms of adoption and return on the investment. When your solution is tailored to users, you’ll see a lot more success. We spend a lot of time up front getting a 360-degree understanding of the audience. Today, this means understanding their mobile usage in addition to everything else.

Failure is a Real Risk

The thing about enterprises looking to enhance mobile collaboration is that there’s risk involved in a poor execution. If we don’t do it right, our employees will be reluctant to adopt the new tools and methods.

In fact, users are going to be reluctant no matter what you do. Our human, knee-jerk reaction to change is usually that it’s bad, until you can prove otherwise. Without making a workflow substantially better, you run the risk of creating a fragmented experience across your enterprise, with some users using the new workflow -- which makes best use of your systems, using your company’s security best practices -- and others not.