Behind the Scenes: Don’t Build A Policy From Scratch!

 

 

 

 

This is the fourth in a our series about how Softchoice is implementing BYOC. We hope you find the series interesting and look forward to your comments and thoughts on your own experiences.

Recently our team met to create our Softchoice BYOC Acceptable Use Policy that will be tied to this program. Not what you’d classify as a “fun” meeting. I’m pretty sure that there isn’t a person out there that likes writing out policies and it’s something that’s really hard to start. So hopefully this blog post can reduce the pain of your organization’s policy building meeting. Thanks to finding the right guidance from Gartner and InfoTech Research, our team was able to bang out a first draft in under an hour!

According to Gartner’s BYOC Checklist the major areas a policy needs to cover are:

  • Language to explain the employee’s responsibility to have a suitable machine available for company use at all times
  • Minimum specifications for hardware and OS
  • Who will pay – and how much – for hardware, software and third-party support
  • What is and isn’t supported by IT
  • Remote-access policies
  • Security policies
  • Levels of permissible data access
  • Safe storage of company data
  • What to do if the system is lost or stolen
  • What to do at termination of employment
  • Financial liabilities of enterprise and user
  • Data cleansing from notebook hard drive

These are things that can’t be decided by just an IT team. So it’s important to include in this meeting someone from your Finance department, HR department and the person in charge of security. So what was the secret to us getting the draft completed in under an hour? We used Info-Tech’s BYOC Acceptable Use Policy Template which had all the wording we required laid out for us, and all we had to do is insert “Softchoice Corporation” and then tweak some areas to fit they way we wanted to implement the program. The template policy had a lot more policies than the team thought it needed, so they ended up removing some of the rules. But overall, to have a starting point and all the wording laid out for our team to edit and tweak was a huge benefit. It also brought up some things that they hadn’t even thought about, which was great!

Do you have any policy tips to share? Any questions about our process? Sound off in the comments below.

Related Posts

Telemerge Talks Telepresence With PrintFleet CCO David Morrow Previously employed with Xerox, KPMG, Telus and Konica Minolta, David Morrow is currently a creative and goal-oriented Chief Commerical Officer at PrintFleet Inc. During h...
Top 3 Reasons Your Wireless Sucks “Our wireless sucks. I’m truly embarrassed, when my client asks for internet access in our boardroom. I’m constantly having to reconnect to the wireless. IT must not reali...
CYOD Through the Eyes of IT During the initial stages of rolling out a Choose Your Own Device pilot at Softchoice, one major stakeholder in shaping the program was our help desk team. Our IT departme...

About Lesley Morris

Lesley is a Communications Lead at Softchoice with over 15 years of technology marketing experience, and provides thoughtful content that creates insights, ideas and knowledge.