These are where a product is backed by a human somewhere in the world working a queue. Content moderation is the classic example, where when a user “flags” a social media someone on the other side of the world looks to decide if it’s violating or not.
I’ve seen each one re-implement reviews (QA), task assignment, worker productivity measurement, Slack notifications, SLA/due dates, and so on.
I’ve written a draft of a framework at http://tinyurl.com/opsqueue-framework, but before building anything want to learn more about how other software engineers have solved this problem.
If you’ve implemented human-in-the-loop workflows before, how did you do it?
I don't see custom built todo trackers as adding value to that workflow. What features are you thinking would require something that any of the 100's of SaaS offerings out there don't do that would be needed?
I really liked the "Job Queue" abstraction, because it gave our engineers a good mental framework to think about scalable computter processes. Curious if there's some parallel where the workers are humans instead of ruby processes?
Seems like most of the features are covered there