Working from home or on the move being a mobile worker is on the rise. A quick google and countless pages tell of employer/employee satisfaction. Large companies and small business can all thrive from the “remote worker” but providing its done right. For, as many success stories there are, there’s also horrible fails.
But with the advent of recent hardware/software changes telework is an easy thing to introduce for employees, its benefits for employer office space wise, and employee not facing the dreaded commute are amongst the main advantages. But, how can both maintain good productivity?
Sadly, although some employees may expect “teleworking” as a perk, the productivity can fail. Employers offering the facility working from home can start to notice “failings”. As with anything there’s good/bad practices.
As an occasional teleworker for a continental company I can see these, but good practices get rid of the failings. Bridging the space between the office and home worker is the real key important factor, provision of equipment, and availability on Skype or some other conferencing tool, is not just the answer, there’s some liability on the employee themselves, to be effective and productive working remotely.
Sounds a silly, subject to check but even today there are still some blind spots with internet access, slow speeds and unreliable connections. If you’re offering home/telework as an employer, ensure that the user has an adequate internet access speed to be capable of doing the work. Certain providers effectively “block” some some forms of home working by adding security to the router and disallowing VPN types, or recognise your using bandwidth for business not home purposes. Get the employee to check they’ll be able to work out of office. A simple trial connection to the office and the software the user will need over a day or two should suffice, but be prepared for changes too.
Without doubt a good solid base landline /cable connection is needed, although 4G is nice, it’s not reliable. I live near five schools, and come lunchtime try and get a 4G signal as the kids are on lunch, as the local mast gets hammered, is a lottery connection wise. Mobile data is fine, but consider the environment, you should be fine in a town or office, but not if your working in an environment, that’s like a cellar in an old stone building! Check in advance of your visit that internet connectivity is possible for you, or that there’s some alternative arrangements connection wise.
Seeing staff grumble their internet connection is down, on social media when they have no backup is not what employers or clients want to be seeing. After all your expectation is going to be what is this person doing remotely without a connection? Colleagues working for larger companies have the “luxury” of having the internet provided for them by the employer, its not always the case and internet connectivity by the home worker is the top priority, you should not want to hear that “my connections dodgy today” from end users..
Also the watch out for the café culture free wifi is handy, but firstly sending data over an unsecure connection (more on this later) is a bad idea. Also, be aware of your environment, do you really want a skype call from the local burger joint, where kids are screaming in the background, and the shouts of the bar / café staff? Think how this would look professionally.
Remote workers benefit pure and simple from VPN, not only does it offer a secure encrypted connection (getting around the internet access from free wifi we mentioned earlier). It allows access to the corporate/company domain facailities remotely.
Yes the employee has their company issued machine at home, or may even use their own if you allow BYOD, but do you really want your data saved on a remote machine? Simple answer NO, it should be stored on the corporate network. Or, at least somewhere accessible to the company such as cloud or local domain storage, in the even of loss/thief or accidental damage to the device.
Ok, you can protect a device with for example bitlocker, so if the device gets lost, stolen the information is unusable, but it’s still lost! If stored locally on the device hard drive. Encourage use of cloud storage and saving to the domain, its fine to have a local copy but lose the device, drop and damage it and you’re up the creek without the proverbial just keeping things local.
For the BYOD brigade use RDS or remote apps, even let the employee remote into a desktop device on the office for security sake. IT should basically not allow external devices onto the network, unless they’ve been checked. Maintaining domain access via a networking method is a good way of avoiding risks, as the network defences are the same both internally and externally for users.
The moment someone has a different machine the toll of IT support starts to rise with the can I have this installed, product X doesn’t work the same when I’m at home. Provision of a familiar environment always sounds like your clamping down on the end user, and to a degree you are. Otherwise, ensure that the end user has some base IT knowledge so they can map to drives they have permission or access to. They don’t need to be a Bill Gates of knowledge, work on the car principle as I call it. You need to have knowledge of changing the oil, water and wiper blades to maintain its running, but when something goes wrong, the user has to be able to tell you where the knocking sound is coming from at least, so the mechanic can know where to look at resolve the issue quickly.
Sadly too many remote workers have a lack of Basic IT skills, ensure that you offer training or assess their capabilities, before you let them work remotely. Again this avoids end user frustration not being able to complete tasks, and a whole lot of time for your ICT staff.
Keeping the remote user on the same phone network eases having to remember mobile numbers, enables you to transfer calls, so you or other clients don’t have to ring or give out alternative home/mobile numbers of remote workers to contact. Remember VOIP will run on phone and device , so the teleworker when away from the device can still be contactable. Voip generally uses less bandwidth as does teleconferencing, if your office uses it, the remote work can simply join in on conference calls as they would frm their own desk.
Again the remote worker should consider their environment, if making a business call listening to “little Martin” screaming in the background, or being on the receiving end of remote workers taste in streamed music is a no no.
This is classed as one of major tools of tele/remote work, but in honesty it’s a blessing and a curse. Some folk simply don’t use Skype correctly, and as such is a constant source of distraction, with the bleep/bloop ring tone breaking the users concentration from their task.
Software has safety features, such as informing others your available, busy etc. Use them, don’t ignore them. Being in contact and knowing what remote workers are doing is essential, the manager should know that they are busy finalising an urgent report, and therefore keep other minor interruptions clear of the worker.
As with any two edge sword, they should also wonder why the remote worker isn’t available when they’ve or clients have tried to contact them too.
If you’re going to conference with clients, don’t do it from the local burger emporium, or the living room with the tv/radio on. It sets a very unprofessional presence, if you’re working from home, ideally have a home office, or at least a real quiet corner so you can focus on the call.
Really that’s up to what the user and the company needs. Office 365 is a real boon, with the ability to share work, pick up others work and continue. You’re not bound to the device, and can pick up and work on the bus, from home, hotel etc.
Ensure remote users know how to work with a shared file system, again a number of times there’s been “I can’t edit the spreadsheet, as Fred’s in it” I’ve had to fend off, purely because users left files open and did another task, or the internet connections dropped leaving the file lock marker and IT wasn’t notified.
At the end of the day the worker is remote NOT ISOLATED they should report problems to IT and be able to contribute in their solution.
Remoting the remote worker for “repairs” to issues is easy Windows10 has facilities built in, or other products such as TeamViewer make ICT ‘s job of being their easier. Make sure you facilitate for such events. A remote worker without that the facility to work remotely is a waste of time effort and money.
All of the above fits nicely into cloud, VPN to the corporate domain servers ensures access and security of information, working hand in hand with the collaboration and ability to share work. DaaS accessibility to workers etc.
Onedrive/Drop box all allow the saving of information securely and remotely allowing other access if required. Cloud is something that should be explored not ignored for true remote working.