Turn the last thirty questions you were asked into an FAQ

Most FAQ pages are written by someone guessing what people will ask. The real list is already sitting in your inbox and your chat history.

Copy out the last thirty or so questions, as they were asked, and take the names off.

Below are real questions staff have asked [ADMIN / IT / HR] recently.
1. Group the ones that are really the same question.
2. For each group, write a short FAQ entry: the question in plain words,
   then a two or three line answer.
3. Where I haven't told you the answer, don't make one up. Write
   "NEEDS ANSWER" and tell me what I'd need to decide.
4. At the end, list the groups by how many questions they cover, biggest
   first.

Questions: [PASTE]
Things you can use for answers: [PASTE POLICY EXTRACTS, IF ANY]

The count at the end tells you what goes at the top. If twelve of the thirty are "how do I book a meeting room", that's entry one.

Expect a lot of "NEEDS ANSWER". Some of those are things nobody's ever decided, and it's better to find that out now than after you've published a guess.

Read every answer before it goes live, because it'll smooth over a rule that has an exception. Put a review date and a name on the page. An FAQ nobody updates turns into a trap quite quickly.

If most of your questions are IT ones, turning resolved tickets into knowledge base articles gets you there too.