Find where work waits between calls.
Quorum measures chat threads, code reviews and issues by size and time to first reply, per team, channel and repository. It keeps counts and timestamps, never what anyone wrote.
Where async work gets stuck.
Threads that keep growing, reviews nobody has picked up and days with no room to focus. Quorum finds them from counts, timestamps and calendars, never from what anyone wrote.
Threads that outgrew async
A thread’s estimated cost comes from its size: assumed time to write each message and for others to read it. If an eligible open thread passes the estimated cost of a 30-minute call with the same people, Quorum flags it for review — once.
Where work waits
Time to a first reply or review, in working hours, per team, repository and Slack channel. Never per person: “who answers slowest” is a question Quorum declines to answer.
Protect focused work
See focus days and meeting interruptions per team, using calendar data to spot when time for independent work starts shrinking.
Know when a call would be cheaper.
A long thread can take more effort than a short conversation. Quorum models reading and writing time from message counts and compares it with a call involving the same people. Your team decides whether a call would help. The model and its sources are public.
What triggers it
A thread that has run past four hours, involves three to twelve people, has been touched in the last two days, carries no resolution, and has overspent the call. All five, or nothing happens — a governance tool that nags gets muted in a week.
Who hears about it
The team’s manager, once, in Slack — what the thread has cost, what the call would, and two buttons. Not everyone in the thread: twelve DMs is more interruption than the thread was causing. Neither button books anything, because Quorum holds read-only calendar scopes.
What it never reads
Slack threads and GitHub conversations are kept as counts, timestamps and explicit directory mappings; message and comment text is neither read nor stored. No individual message counts or communication rankings are produced.
See where work waits for a reply.
Across locations and time zones, a slow handoff can hold up the next step. Quorum tracks the time from a conversation starting to wait to its first reply from someone else, in working hours. Results are reported per team, repository and Slack channel, never as individual response scores.
Counted in working hours
In your workspace’s own time zone and working day. A review requested on Friday evening and given on Monday morning waited minutes of working time, not sixty hours.
A clear line for slow
A scope is flagged when its median first response takes more than 1 working day, or when 25% of its conversations are still waiting past that line. Where the line comes from.
Never about one person
Withheld below 5 conversations or 3 people, so a team’s figure is never one person’s habits under another name. Message text is never stored — only counts and timestamps.
Agree response times, then check them.
A team, a repository, a Slack or Teams channel, or a Jira, Linear or GitLab project can each have a target: a first response within so many working hours for a share of its conversations. The suggested default is 8 working hours for 80% of them. Why those numbers.
Reminders that name conversations
When a conversation nears its target with no answer, the owner of the scope hears about it once: the conversation’s title and link, never who should answer it.
A weekly line per agreement
Once a week, each agreement’s recent adherence goes to the team’s manager, or to an administrator for a channel or repository. Withheld below the same floors as response times.
Agent-written work, measured apart
Pull requests and issues opened by AI coding agents are told apart from people’s by the account type, so you can see whether agent work waits longer for a review — per repository or project, never per person.
Plan a pilot.
Tell us where your team writes: Slack, Microsoft Teams, GitHub, GitLab, Jira or Linear. We’ll suggest where to start.