Post
5 min read
Four weeks from first call to first approved task
The rollout plan we use with most teams, week by week, including who needs to be in the room.
Rollouts stall when they start with the whole department. Start with one workflow and the two or three people who already do that work.
Weeks one and two
Map who drafts, who approves and where the finished work goes. Connect read-only access to the systems involved, and nothing else.
Weeks three and four
Run the agent alongside the team, compare drafts with what they would have written, and tune the rules together. Switch it on when the team says it reads like theirs.
Keep reading
Post
6 min read
What a good approval step looks like
Approval only protects you if the reviewer can see what the agent did and why. Here is what to show them.
Post
4 min read
Why we start every connection read-only
Read-only is slower for a week and safer for a year. Here is the reasoning behind our default.
Post
5 min read
Writing policy answers employees actually trust
Employees stop asking HR when answers feel generic. Three habits keep drafted replies specific and human.