What needs to be in place? re you the kind to have a policy for everything? if anything comes up do you refer people to your policy – hard a fast? Are you flexible? Do you review your policies from time to time to see what is still valid?
When developing policy keep the following in mind:
Do not set policy based on offenders. If you define permissions, access and distributions based on a few that tend to violate or not follow guidelines, you will lock out innovative types or drive them to go int stealth mode.
Do not set policy based on your best users. The bar will be too high for the average person. You may demand an understanding of the software that the average teacher may not have. Do not expect everyone to be able to keep up with the software like your superstars.
Set policy as needed. Do not start creating policies for things that do not need to be unified, managed, focused, duplicated or expanded. They may not be needed policies. Look for areas of confusion. Where people need a little help knowing what is best. Look for areas where a wide range of options might make tool use divergent. Policy is to get people on the same page and keep them within the boundaries.
No Comments Yet