If you’re running the IT department for a business, one thing’s for sure: your intranet has to be foolproof, goofproof and lightning fast. After all, your intranet is the way you connect employees to resources, and resources to business divisions and business visions to departments, and departments back to employees. But the most important part of making your Intranet truly useful to all of the people it needs to service is that is works where they do.
If you haven’t already started expanding into the world of mobile intranets, there’s probably a good reason for that. And it isn’t because you don’t want to or don’t have the time. It’s because you’re not sure that your company is ready for it or that this new way of connecting your employees to work on the go is going to work, for security reasons and for usability reasons. One thing’s for certain. You’ve got to make a decision. And soon. Or you’ll be left behind by all of your competitors. If you’re considering travelling down the path of complete mobility for your employees and resources here are some tips on implementing the best practices for enabling a mobile optimized Intranet without sacrificing your user interface, your sanity or your security.
- Make sure you are focused on and employing standards compliant interfaces like HTML 5. If you just made a face, then you probably already implement these device agnostic services but if you try to implement a mobile optimized Intranet without deploying services that will work anywhere, any time and on any device, you’ll find that you wasted loads of time and money for only some of your personnel to have complete and accurate access to your Intranet.
- Make sure your mobile options are operable on the devices you’ve issued to your staff and other personnel. If all of your personnel are utilizing Blackberry devices then you might be able to skip over the switch to HTML5, but you certainly won’t be able to gloss over the fact that your mobile solution must work on all Blackberry devices. Of course, it may be simpler to replace a few old, worn out Blackberrys than to create a system that works for even the oldest models.
- Decide whether you are aiming for an apps based environment or a web based module and stick to your guns. There’s been a lot of debate about whether mobile intranets in businesses should be app based or web based. While it’s up to you, you should consider that your main goal and purpose in this project is to offer mobility to all of the employees in your company. And if your company has thousands of employees an app based mobility option that only works on iPhone or that works with Droid but only on some Droid devices, may not be up to snuff when it comes to best practices. After all, the best practice possible in this situation is to make the mobility option as accessible as possible to everyone who works for the company.
- Take your level of security into consideration. And don’t forget to consider your ability to manage the security functions. The problem with security on mobile Intranets is that even if you implement RIM or similar authorization and secure services into your mobile Intranet you can’t control who sees the information once it’s accessible via phone. If an employee loses their cell phone or other wireless device, which is 75 percent more likely to occur than the loss of a laptop computer, then you may have a major security breach on your hands. Additionally, you need to consider the strength of the security options available for this type of technology in the here and now. While RIM secure access is top of line for some email based mobility projects, an entire Intranet of personal, private and proprietary data is another story entirely. You should never implement any mobility measures into your Intranet until you are certain that the technology is tested and proven, even if that means waiting an additional week, or month, or 6 months to launch mobility for the business you support. The lag behind the competition will be worth the wait to ensure that your company’s information is safe.
- Have a security plan and an emergency plan. You know how to handle the situation if your Intranet is breached now. But do you know how you would handle a breach if it came through a mobile source? The answer is that you probably don’t realize that the protocol will be different and the amount of time you have to respond to the problem will also be different.
If you’re considering adding mobility to your Intranet it’s important to remember that security and usability should always be at the top of your list when it comes to best practices!