HR & People
A people-ops manager of one, serving a company of ninety, who answers the same policy question eleven times a week.
[ 01 ]The problem
Policy lives in a handbook nobody reads and a Slack history nobody can search well. Answers drift: two employees get two different parental-leave explanations a month apart. Onboarding is a checklist run by hand, and every exception gets re-decided from scratch.
[ 02 ]How Mynd handles it
The handbook becomes the answer source
Y0 grounds every people question in the current handbook and policy docs — versioned, so the answer cites the section and the effective date.
Onboarding runs as a plan
Each new hire triggers a planned sequence — accounts, intro docs, scheduled check-ins — executed step by step with a visible trace of what's done.
Exceptions get memory
When a real decision is made, it's recorded into the graph. The next similar case surfaces the precedent instead of restarting the debate.
[ 03 ][ example run ]
plan ✦ onboard: new hire — design, remote context ✓ handbook v12 — loaded context ✓ onboarding sequence — 14 steps execute → provision requests filed execute → week-1 schedule drafted, buddy assigned execute → policy answers ready: leave, equipment result ✓ 14 of 14 steps traced · 0 questions re-answered
[ 04 ]of people-ops time returned per week