The SOP that finally got read
Why most operating procedures rot in shared drives — and the structural changes (length, hierarchy, ack flow) that flip the read rate.
We're drafting our first set of posts now. The blog is going to cover what we're learning building Relay — and what our customers are learning building their teams. No SEO bait, no growth-hack listicles. Real notes on real work.
Working titles for the posts we're finishing now.
Why most operating procedures rot in shared drives — and the structural changes (length, hierarchy, ack flow) that flip the read rate.
A blueprint for new-hire onboarding that doesn't depend on a single senior person being available. Works for hourly + salaried roles.
Diagnosing retrieval misses in a citation-first AI assistant. What it tells you about your SOP hierarchy, not your model choice.
Some processes are sequential — checklists are fine. Some have branches. We argue (with diagrams) for visual workflows in the second case.
Notes from rebuilding our AI assistant on Opus. Prompt caching, citations, latency, cost. What surprised us.
How to design an ack flow that gets compliance without breeding resentment. (Yes, employees know when you're padding policy.)