When collaboration comes up in company conversations, everyone seems to be talking about the same thing — until you press for specifics and realize no one is. The procurement manager means ‘I send information on time.’ The project lead means ‘everyone shows up when something goes wrong.’ The distance between those two definitions became visibly costly across Turkish SMEs from March 2020 onward. Once offices closed and teams scattered across different cities and home desks, ‘I finished my part’ stopped being an adequate answer. The pandemic exposed something that had always been true but easy to paper over with physical proximity: finishing your own part is the prerequisite for collaboration, never its definition. The real definition — holding the shared context when the piece next to yours falls apart — had never been written into anyone’s job description.Consider a mid-sized construction and project management firm in Konya: 295 employees, a portfolio weighted toward domestic residential projects and public tenders. Before the pandemic, collaboration in this company ran largely on physical coordination. What the site supervisor said at the morning stand-up was reflected on the ground by afternoon. Disputes between site measurement data and the accounting department’s reporting cycle were resolved in hallway conversations before they could compound. After March 2020, that mechanism stopped. The site supervisor speaking on a Teams screen left sub-questions that used to dissolve in corridors to sink instead into message threads nobody reopened. The breakdown was not technical — Teams or Zoom were adequate tools. The breakdown came from employees having no habit of stepping outside their task boundary. Everyone hit their personal deadlines. But the connective tissue holding the project’s shared context together existed in no one’s formal role.The cleanest question to expose whether your team actually collaborates or simply hands off sequentially is this: what do you do when the part next to yours breaks down? There are three realistic answers. First: ‘Not my responsibility — I flagged it to whoever owns that.’ Second: ‘I noticed it, made a partial intervention, but my own deadline came first.’ Third: ‘I spent two hours keeping the shared picture intact, adjusted my own plan accordingly, and told my manager.’ In Turkish SME practice, the first answer is the most common — and, strikingly, the most defended. The ‘finish your own work’ culture runs deep in sectors like construction and manufacturing, where individual accountability ties directly to physical output. That culture has a legitimate function: clear ownership, traceability, a named party when something runs late. But its invisible cost is this: even when every individual delivers, the project still somehow does not close, because the space between the parts belongs to nobody.A representative scenario from the Konya firm in 2020 captures this dynamic precisely. During the documentation phase for a public tender, an eight-day gap accumulated between site measurement data and the accounting department’s reporting cycle. The site team had submitted their measurements. Accounting had prepared their report. But the project coordinator who should have matched the two datasets was on a short work trip, and no one held the bridge. Before the pandemic, this gap would have closed in three sentences in the office. In the remote working arrangement it became eight days, because no one said ‘this is not my formal task but I will hold it until the coordinator returns.’ The financial impact was direct: the invoice tranche slipped to the next payment cycle, hitting cash flow at a moment when the firm was already navigating currency pressure and tightening supplier terms. The problem was not a software gap. It was a behavioral gap.A necessary caveat belongs here, and placing it at the end of the argument rather than safely after the thesis is deliberate. Interpreting collaboration as ‘everyone helps everyone’ is equally dangerous. That reading dissolves clear ownership lines and produces the structure where everyone is nominally responsible and no one actually answers for anything. Turkish SMEs fall into this trap too: ‘we failed as a team’ becomes a socially acceptable cover for individual accountability that was never properly assigned. Real collaboration lives between these two extremes. Individual responsibilities stay sharp. But the ownership reflex for the gaps between those responsibilities also develops. That reflex is not built through a workshop. It is built by watching the leader model it. When the manager finishes their own part and retreats to their office, the team learns exactly where the boundary is supposed to sit.Where do you start on a Monday morning? The first step is distinguishing where your team genuinely collaborates from where it simply delivers in sequence. Map a current project and next to each handoff point write one question: ‘When this delivery is done, does the owner of the next stage take on the shared context — or does the context float in the air?’ The second step is naming who holds the gaps — not in a role description but in an acknowledged behavioral norm. The third step is auditing leadership behavior directly: in your last three team meetings, who volunteered information that was not strictly required of them? Who quietly picked up the broken piece that was not theirs? If you cannot name a person, the norm does not yet exist. In 2021, with remote work no longer a temporary measure, the incidental information flow that physical offices provided needs deliberate substitutes. A fifteen-minute weekly ‘what am I not seeing?’ conversation across the site-to-accounting boundary is not a sophisticated intervention. It is what prevented that eight-day gap from becoming sixteen.The Konya firm’s invoice process was not fixed by a smarter piece of software. It was fixed by a twice-weekly fifteen-minute bridge call between two people whose formal roles did not overlap but whose work did. The question of who holds the space between the parts — the space both parties can legitimately call ‘not my job’ — was answered not with a tool but with a norm built on mutual agreement and visible leadership. When collaboration discussions collapse into arguments about which platform to use or which training to run, the actual fracture point gets missed. Collaboration is a question of intent and norm before it is a question of capability or tooling. You finished your part — I know. Now: what do you do when the part next to yours breaks?
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 26, 2021. The English edition has been reviewed and edited by the author.