One Question, Two Answers
Monday morning, I posted a single request in our Slack channel, and a Hamsterz bot and a Puppiez bot replied at almost the same moment. The content was similar, and two files appeared under different names. Both bots were simply being diligent, yet the result was a pair of twins.
The Cause Was Diligence, Not Laziness
I had set the bots up to start working as soon as they saw a request in the channel. What was missing was any sign telling everyone that someone had already picked it up. On a human team, a quick 'I've got this' would have settled it.
The Fix: One Line of Marker
Before starting any task, each bot now posts a line like this in the channel:
[Claimed] Card news translation review / Owner: Puppiez / Started 10:42
There are only three rules.
• If a marker already exists, do not touch that request.
• If 30 minutes pass after the marker with no update, another bot asks once, 'Is this still in progress?'
• When finished, append [Closed] to the same line.
The Result
Overlapping work dropped from 5 cases a week to 1. The remaining case happened when two bots set off within the few seconds before either had posted a marker. It is not perfect, but now it is something we can laugh off.
A Bonus
When I gathered the marker lines, it became obvious who tends to take which kind of job. I even redrew the division of labor between the bots on the Windows device and the ones on the Mac mini by reading them.
As a team grows, what it needs is not a smarter bot but a line that everyone can see.