TL;DR: Work assigned to several people with no owner, no queue and no deadline does not get done late. It gets done whenever somebody feels awkward enough to chase it. A deal approval waits eleven days because three people were tagged and none of them owned the answer. A renewal list goes under a keyboard. A compliance module sits at "in progress" for 76 days. In every case the people were competent, the intentions were real, and the task had no clock attached. Urgent work wins, the cost of the delay lands somewhere it cannot be traced back, and the delay never appears in any report as itself.
Nobody Owns the Queue
A sales rep in Austin submits a deal on a Tuesday. It needs three approvals: finance for the discount, legal for the redlined contract, the VP of Sales for the three-year term.
He tags all three in Slack, because he has learned that tagging one produces a slower answer than tagging everybody.
Finance asks a question on Wednesday and does not come back. Legal is at an offsite nobody flagged. The VP replies on Thursday with "fine by me, what did finance say?"
The quote releases on day nine. The customer signs on day eleven, which is the third of the month, so a $142,000 deal that had been worked since April lands in the following quarter.
Every approver said yes. Nobody said no to anything. The deal was not rejected, disputed, or even seriously questioned. It sat.
What it sat on was not a decision. It was the absence of anyone whose job it was to notice that it was sitting.
The Same Shape, Six Times
This is not a SaaS problem, or a sales problem. It is what happens whenever work is handed to people who have every intention of doing it and nothing telling them when.
Deal approval. Three approvers, 106 non-standard deals a year, eleven-day median. Fourteen deals worth $1.4M released after the quarter they were sold in.
Insurance renewals. Dana in Charlotte printed a renewal report each month and walked sections to five account managers. They had good intentions and six pending claims each. The list went under a keyboard. 176 policies lapsed with no outreach call. $168,000 in commission.
Onboarding. Claire in Bristol tracked 34 milestones per new hire across a 90-day programme, checking at weeks 1, 4 and 12. Weeks 2, 6 and 8 were, in her own assessment, aspirational. Four hires in seventeen reached their probation review without completing mandatory compliance training. The spreadsheet had said "in progress" for 76 days.
Accounting. Karen in Portland produced 412 engagement letters every January. The review step that would have caught the 23 carrying last year's fees competed with January volume and lost. The firm honoured every one.
Facilities. Sarah in Sydney checked 40 property tabs weekly when she had time between tenant complaints. She got through 14 last Monday. Twenty-three deferred services became emergency callouts at AUD $8,100 each.
Engineering. A documentation project produced 14 SOPs and then stalled, because the three people who held the knowledge were also the three people running the firm and nobody had 60 spare hours.
The shared structure: named people, real intentions, no queue, no owner of the waiting, and no moment at which the delay becomes anybody's problem. The task competes with urgent work. Urgent work wins. It always wins, because that is what urgent means.
Why Assigning Is Not Delegating
Three reasons this survives in businesses run by capable people.
Assigning to several people assigns it to nobody. When three approvers are tagged, each one can reasonably assume another is closer to it. The rep tags all three precisely because he cannot tell which is first, and in doing so removes the last trace of individual responsibility. A task with three owners has, functionally, none. It is worse than a task with one wrong owner, because a wrong owner at least produces a redirect.
Waiting generates no signal. An overdue invoice arrives as a chaser. An unhappy customer telephones. A deal sitting in an approval queue produces nothing at all: no document, no alert, no mounting sense that something is wrong. The absence of an event is the hardest thing for a busy person to notice, which is why the delay is discovered rather than detected, usually by the person who was waiting.
The cost lands somewhere else. The eleven days do not appear in any report. What appears is a quarter that closed $1.4M light, and that gets attributed to pipeline, or to the market, or to a rep who did not push hard enough. The lapsed policy shows up as churn. The failed compliance training shows up as turnover. Nothing in a P&L is ever labelled "the four days this waited for legal", so the pattern is invisible at exactly the level where somebody could act on it.
Worse: the process looks functional from the outside. There is a channel. There are named approvers. There is a policy about what needs approval. An auditor would find a documented process and conclude it works. It does work, eventually. The word doing the damage is "eventually".
This is why "be better about checking Slack" fails as a solution. The approvers are not inattentive. They are three senior people approving nine deals a month alongside the jobs they were hired for, and any one of them prioritising the queue would simply move the delay to whichever of the other two did not.
Giving the Work a Clock
Across the Blueprint series, every agent that closed a gap like this did the same three things.
One named owner per decision. Not a channel, not a committee. The deal desk agent routes the discount question to finance and only to finance, the contract to legal and only to legal. Nobody can assume somebody else has it, because nobody else has been asked.
A clock on the silence. Twenty-four hours without a response produces a reminder carrying the deal value and the days remaining. Forty-eight produces an escalation to someone senior. The waiting becomes visible to a person who can do something about it.
Parallel, not sequential. The three approvals on that Austin deal were independent, and the order in which they happened was determined by who opened Slack first. Sending them at once removes a dependency that never existed. This single change moves the median from eleven days to two.
Dana's agent triggers renewal outreach 90 days out, so the conversation happens while the policy is still winnable. Claire's agent escalates a stalled milestone after 48 hours rather than at the next scheduled check-in. Sarah's agent dispatches four weeks before a service is due, and six for compliance items.
The mechanism is always the same: the routine happens without a person remembering it, so the person only sees the exception. The approver still approves. The account manager still has the conversation. What goes away is the waiting.
The mechanism is always the same: the routine happens without a person remembering it, so the person only sees the exception. The approver still approves. The account manager still has the conversation. What goes away is the waiting.
Your Queue
Find the work in your business that several people can action and nobody owns. Approvals. Sign-offs. Referrals passed between departments. Change orders. Anything where the next step belongs to a group.
Then ask three questions.
If this stalls, who finds out, and when? If the answer is "the person waiting, eventually", it has no owner.
What happens on day three? If nothing happens on day three, nothing happens on day eleven either.
When it does go wrong, what does it get recorded as? A slipped quarter, a lost client, a failed audit. Never as the four days it spent waiting, which is why you have never fixed it.
The delay is not a discipline problem. Everyone in these stories was competent and meant to act. It is a design problem, and the design is missing exactly one thing: somebody, or something, whose job it is to notice that nothing has happened yet.
Every Blueprint in the archive closes a gap like this one. Architectures, build guides, cost breakdowns, failure modes. Free to read. Free to build from.
55 agent designs. Your version of the tagged Slack message is probably already in there.
Subscribe to AdAI News. New blueprint every week.
by SP, CEO - Connect on LinkedIn
for the AdAI Ed. Team
