Nobody Chased It Because Everyone Thought Someone Else Would

When a job passes through more than two pairs of hands, something almost always gets lost. Not the job itself - the conversation about the job. The update that was relayed verbally. The customer request that was messaged to a colleague. The decision made in a phone call that nobody wrote down. Each of those moments felt handled at the time. But when the job reached the next stage, the context wasn't there. The action didn't happen. And when someone finally asks who was supposed to follow up, it turns out everyone assumed someone else had it covered.

This is not a people problem. It is a systems problem. And it gets worse, not better, as a business grows.

How Growing Teams Create Accountability Gaps

A small operation with three or four people can run on informal communication because everyone knows what everyone else is doing. The owner is close enough to every job to catch the things that fall through. If something needs to happen, they can make sure it happens.

That model breaks down at around six to eight people. At that point, the owner can no longer track every job in their head. Information about live jobs starts moving between people in ways the owner cannot see - text messages, WhatsApp groups, email threads that copy some people but not others. The team is communicating constantly. But the job record stays empty.

Research from Grammarly's 2025 Productivity Shift report, cited across multiple workplace communication analyses, found that 69% of workers reported that poor communication had caused them to miss a deadline. The same survey data showed that 46% of professionals had missed important messages entirely. In a service business running multiple live jobs at once, those numbers translate directly into customer complaints and margin erosion.

The problem is not that people are careless. The problem is that the conversations about jobs are happening in the wrong place.

Where the Conversation Actually Happens

Take a concrete example. A customer calls the salesperson handling their account and requests a change to the delivery arrangement - they need goods sent to a different site address than the one on the order. The salesperson says that's fine and sends a quick message to the operations manager.

The operations manager reads it and intends to update the order. But three other jobs are active that afternoon. By the following morning, the message has slipped out of view. The delivery goes out to the original address.

This scenario plays out in every industry Zigaflow works with. An electrical contractor's estimator passes a note to the site team about a design change. A furniture dealer's salesperson tells procurement about a revised product specification. An AV integrator's project lead relays a commissioning update to the engineer on-site. Each of these conversations happens - but none of them happen on the job. They happen around the job, in channels that are invisible to anyone who wasn't directly in the conversation.

The result is a job record that looks complete but isn't. The next person to act on that job has no idea what was agreed. It is a version of the same problem explored in Your Business Runs on Knowledge That Lives in One Person's Head - but instead of knowledge leaving when a person leaves the business, it disappears every time a conversation happens off the record.

Why Adding More Channels Does Not Help

The instinctive response is to create more structure around communication. Send a follow-up email. Create a checklist. Hold a handover meeting. These approaches help at the margins but do not solve the underlying problem, which is that context lives in the wrong place.

When a message about a job sits in someone's inbox, it is only accessible to the people who received that email. When the job moves to the next stage, those people may not be involved. A procurement manager acting on a purchase order cannot see what the salesperson promised the customer last week. An invoicing administrator preparing the final bill cannot see the variation that was agreed verbally on-site.

Pumble's Workplace Communication Statistics for 2026, aggregating data from multiple workplace research reports, found that 53% of professionals reported wasting time at work due to communication issues - time spent reconstructing what had been agreed, re-asking questions that had already been answered elsewhere, and chasing colleagues for context that existed but was inaccessible.

That wasted time concentrates most heavily in businesses where information about a job lives in multiple disconnected places. The job management system holds the order. The email client holds the customer's special instructions. The project manager's phone holds the on-site update. When something goes wrong, nobody can reconstruct the full picture quickly.

What Changes When Communication Lives on the Job

The principle behind Zigaflow's Mentions feature is straightforward: keep the conversation in the same place as the job it is about. When a team member needs to alert a colleague to something specific on a live job, they @mention them directly within that job record. The colleague receives a notification, responds in context, and both the alert and the response stay attached to the job for everyone to see.

This matters for three reasons.

First, it removes the assumption problem. When a team member is explicitly mentioned on a job record, there is no ambiguity about who needs to act. The message did not go to a general inbox. It went to a specific person, attached to a specific job.

Second, it creates a visible audit trail. Any team member who opens the job can see what was discussed, when, and by whom. There is no need to track down a phone message or search through an email thread. The job tells its own story.

Third, it survives personnel changes. When a colleague is on leave, off sick, or has moved on from the business, their conversations about live jobs remain visible to whoever picks up the work. Context does not disappear with the person.

The Real Cost of Assumptions

Most accountability failures in service businesses do not come from negligence. They come from the reasonable assumption that someone else had it covered. That assumption is almost always made in good faith. The person who relayed the message genuinely believed the recipient had noted it. The recipient genuinely intended to act on it. The system - built on informal communication around jobs rather than on jobs - made a gap inevitable.

Getting communication onto the job record is not about monitoring people. It is about making sure the right context reaches the right person at the right time, without relying on individual memory or goodwill to keep it alive.

When a job that involves six people produces a single, shared record of every decision made and every action requested, fewer things fall through. Not because the team has changed - because the place where the conversation happens has. If you want to see how this works in practice, the Zigaflow demo walks through exactly that.

Sources

• Workplace Communication Statistics for 2026Pumble · accessed 2026-08-01
• The Hidden Costs of Poor Communication in the WorkplaceNewZapp · accessed 2026-08-01

Related pages