Policy writing best practices
Anyone can write up or propose a change to a MakeICT policy.
When in doubt, changing a policy is always better than a new policy. Review Category:Rules and policies to see if we can update or add to an existing process.
State what problem you are trying to solve. Policies should be written to eliminate repetitive "what should we do about (insert situation here)" discussions. Sometimes there are easier ways to solve a problem. For example if there's an issue with one person, talk to that one person.
- Tell the admin list that you'd like to change the policy, get some initial feedback
- Copy existing policy from the wiki page into a google doc.
- Save the google doc to the Policy Drafts folder.
- At the beginning, add this helpful info so we all have an "executive summary" of the change.
- Reason for changing
- What's changing
- What's not changing
- What's unsaid
- Set security so anyone with the link can view, admin list can comment, only you can edit.
- Set the editing mode to "suggestions" so google will track the changes you make
- Change as necessary
- Let the admin list know it's available for comment
- Address or incorporate comments as necessary
- Ask that the policy be added to the next board meeting agenda. Save your proposal in the board meeting folder if necessary. This is nice because if more changes come up at the meeting, we'll have a record of what was proposed.
- Attend the board meeting to address questions, if possible
- If your policy is approved, the secretary will make the necessary changes to this wiki
- Pat yourself on the back for helping MakeICT with clear, concise policies!