# Notes from building Forematter

> Notes from building Forematter: why it works the way it does, and what we think about onboarding and company knowledge. By Jack Stovell.

Source: https://forematter.com/notes/

- [Every answer needs a named owner](https://forematter.com/notes/every-answer-needs-a-named-owner/) ([Markdown](https://forematter.com/notes/every-answer-needs-a-named-owner.md)): Jack on why a handbook owned by everyone is owned by no one: give every policy, page and answer one named owner (the person who'd get asked anyway) and a review date, and make owning mean review, answer and retire.
- [Why Forematter won't guess](https://forematter.com/notes/why-forematter-wont-guess/) ([Markdown](https://forematter.com/notes/why-forematter-wont-guess.md)): Jack on why Forematter never guesses: sourced answers with date and owner, gaps sent to a named person only if the employee chooses, replies saved so the gap closes.
- [You are the HR department](https://forematter.com/notes/you-are-the-hr-department/) ([Markdown](https://forematter.com/notes/you-are-the-hr-department.md)): Jack on why, in a small UK company, the founder or office manager is the HR department, and why the fix is writing each answer down once with an owner, a review date and one findable home.