A handbook for everyone on the team.
Your company already has a way of doing things. Put it in a handbook that people and AI employees can both learn from.
Start with what your team knowsWhat we know. How we work.
Working here
Time off · expenses · who to ask
Our customers
Product knowledge · support standards
How we do the work
Team procedures · reviews · handoffs
Start with the questions people already ask.
A new colleague needs context before they can be useful. So does an AI employee. Your policies, product knowledge, and team conventions are a natural place to start.
“What’s the vacation policy?”
If you connect an employee to Slack, give it the handbook context to help with questions like this. The answer should come from your company’s policy, with a person to ask when the policy leaves something unclear.
Begin with pages you already have. Add the answers your team keeps explaining: how to submit expenses, where product information lives, or who owns a decision.
Write the work down the way you’d teach a colleague.
A standard operating procedure is a description of how your team does a job. What starts it? What should someone check? What does a good result look like?
Those instructions belong beside the company knowledge they depend on. People and AI employees can work from the same procedure, with responsibilities that suit each of them.
Use plain language and a real example. Include when to ask for help.
Preparing an expense for approval
Example procedure · Finance
- 1.
Read the request
Check the receipt, amount, and reason for the expense.
- 2.
Check the policy
Compare it with the company’s expense guidelines.
- 3.
Ask about gaps
Request missing information before continuing.
- 4.
Prepare the review
Send the summary and receipt to the person who approves it.
Decide where the work changes hands.
Once the instructions are clear, choose who does the work and where it needs a review. An employee might prepare an expense summary while a person keeps the approval decision.
Prepare
The employee checks the request against your handbook.
Review
The assigned person receives the summary and decides.
Continue
Approved work moves on; questions go back for clarification.
Handbook pages explain the work. Configured steps connect the actions, reviews, and waits; Wallfacer calls that process a playbook. When work must wait for approval, we help configure that step during setup.
Let the handbook grow with the work.
Start small. When a question comes up twice, add the answer. When a review catches a missing check, update the procedure.
Every page keeps its revision history. Employees can read the relevant instructions and search for more context as they work.
A change passes its tests, but no one checked the screen on a phone. Add the missing check to the handbook.
handbook / mobile-review.md
- Before requesting review:
- Added line: Run the changed flow in the Simulator.
- Added line: Attach a phone-sized screenshot to the pull request.
- Added line: Describe anything you could not verify.
We’ll build the first pages with you.
Bring the handbook you have, or just a job you want help with. We can work alongside your team to write the instructions, connect the right tools, and walk through the process together.
Use a starting process, adapt it, or bring your own.
Plan your first employee