Many founders notice this pattern. A client calls about a site issue—why wasn’t the change communicated? The procurement team swears they informed the site. The site engineer says they never got the message. Three people, three versions, one frustrated client. Nobody planned this communication breakdown. It just evolved.
I’m Milind Bibikar, and I work with mid-sized B2B engineering and project companies.
Why does this happen?
First, information travels through too many handoffs.
Head office tells the project manager. Project manager tells the site supervisor. Site supervisor tells the engineer. Somewhere between steps two and three, critical context disappears.
The message arrives, but the urgency doesn’t. “Boss ne kaha tha batane ko”—but what exactly needed to be communicated got lost in translation.
Second, site teams operate in survival mode. They’re managing immediate crises—material shortages, labour issues, weather delays. A message from head office feels less urgent than today’s concrete pour. “Abhi yeh khatam kar lete hain, baad mein dekhenge.” By the time they look at it, the client already knows there’s a problem.
Third, there’s no single source of truth. Head office has their records. Site has their diary. Client has their understanding. When versions don’t match, everyone believes their version is correct. Nobody’s lying. Everyone’s working from incomplete information.
One founder’s day is explaining to clients why the site team didn’t know what head office approved. Another founder’s team has direct client-site communication channels with clear escalation protocols.
Same project complexity. Entirely different client experience.
The question isn’t “Why don’t people communicate better?” The better question is: “Do we have systems that make miscommunication impossible?” Because if every project requires you to translate between your own teams, scaling becomes nearly impossible.
