Writing
Notes on AI employees
64 pieces for operators on one-process builds and the parts that still need a person. RSS
· Build
How to pick the first process
The first AI employee should take a pile you can name in hours, not a strategy project you cannot finish in a quarter.
· Build
Map the workflow before you build
If you cannot walk a stranger through the steps, you are not ready to connect a model to your tools.
· Build
Connect to tools you already use
The point is to take work off the team, not add another tab they will forget to check.
· Build
Escalation that does not lose context
People should receive a case they can decide, not a chat log they have to reconstruct.
· Build
Testing an AI employee before go-live
Go-live is not a feeling. It is a test set, a miss rate you can explain, and a person who still owns the weird cases.
· Build
Handover docs your team will actually read
If the write-up needs a second notebook, it will not be open at 2am. Day 7 is a page and a call, not a binder.
· Build
Monitoring an AI employee in production
Pretty charts do not replace a person who can explain why a case failed. Watch the paths a stranger will shout about.
· Build
What breaks in week two
Launch week hides the cases you did not sample. Week two puts them on the table. That is normal if you are watching.
· Build
Build vs buy an AI employee
Do not buy a platform to avoid naming a process. Do not build a platform to avoid using the tools you already pay for.