-
Step 1
Poll the staff. Answers will have no meaning if they are comprised of questions that are never really asked. Make sure that the staff knows they have a hand in what ultimately becomes the FAQ’s.
-
Step 2
Include any manuals or instructional material. Access to all written documentation concerning a project is a given whenever FAQ’s are developed. If the manuals are good, many of the questions that staff will have about the implementation of any part of the project will be included in the manual. For non readers, use the manual to direct them to specific areas where their questions have already been answered and documented.
-
Step 3
Create an opportunity for feedback. Without an opportunity to comment, staff may feel left out of the process. Providing this type of vehicle will encourage buy in.
-
Step 4
Revise FAQ’s often. Use the feedback to fine-tune any parts of the FAQ’s that were not clear. This may also mean taking out some answers all together and starting over. This is a good thing. It lets staff know that the project is not being ruled with an iron fist and that feedback is valued.












