Remote Work Communication: More Talking Does Not Solve It — Clarity Does

When Turkish companies closed their offices in early March 2020, most managers reached for the same lever: more meetings. A mid-sized textile exporter in Gaziantep — around 280 employees, shipping over 40 containers abroad each year — moved from two team check-ins per week to daily calls almost overnight. The production manager’s reasoning was straightforward: ‘People don’t know what to do, we need more communication.’ Three weeks later the complaints had multiplied rather than shrunk. ‘The calls are eating half the day and nothing gets decided.’ The problem was never the quantity of communication. It was the quality of the decisions embedded in it.Remote work does not create communication problems — it makes existing ones impossible to hide. In an office, ambiguity gets absorbed through corridor conversations, a glance across a desk, or the informal ‘did you mean X or Y?’ that takes thirty seconds. None of those mechanisms survive a distributed setup. When a task arrives with the phrase ‘handle it as you see fit’ or ‘finish it soon,’ every recipient fills that gap with their own interpretation. The gap is not filled randomly; it is filled in the direction of least resistance, which is usually not the direction the sender intended. Adding another meeting to correct the resulting misalignment does not fix the underlying architecture — it just adds one more layer of potential ambiguity on top.My core argument here is intentionally uncomfortable: in a remote environment, the single most important variable determining communication effectiveness is not channel choice, meeting cadence, or tool selection — it is decision clarity per message. By decision clarity I mean something specific and testable: can the recipient derive their next concrete action from this message using only one interpretation? If a reasonable person could read the same message and arrive at two different to-do lists, the communication is unfinished — regardless of how long the meeting ran or how detailed the email was. This is not a soft-skills observation; it is a structural diagnosis. A project coordinator at a construction firm in Istanbul told me: ‘I thought everyone understood, then I saw them doing completely different things.’ That sentence is the precise failure mode of low-clarity remote communication.Building decision clarity in practice requires three mechanical habits, not personality change. First, every task assignment must close four variables in a single message: what needs to be done, who owns it, by when, and what ‘done’ looks like. Leaving any one of these open invites the recipient to guess — and guessing under time pressure produces the wrong priority. Second, every meeting must have a written agenda circulated before it starts; meetings without agendas become idea exchanges where nothing is recorded and no commitment is made. Third, every meeting must end with the facilitator reading the action list aloud and explicitly asking anyone not on that list what their next step is. The last habit feels pedantic until you see what it prevents: the person who left the meeting thinking ‘that was someone else’s job’ and did nothing. The Gaziantep textile firm implemented all three consistently; within a month, daily calls dropped back to three per week, and ‘I didn’t know what I was supposed to do’ disappeared almost entirely as a complaint.There is a real boundary to this framework and it deserves honest acknowledgment rather than a footnote. Decision clarity mechanisms fail when the manager giving the assignment has not yet made the decision. Vague tasking is frequently the symptom of unresolved authority, conflicting priorities at the leadership level, or avoidance of an uncomfortable conversation. In those cases, a better-structured Slack message does not help. The problem is not communication design — it is leadership decision-making. Remote work does not cause this failure; it exposes it with painful speed. At a mid-size logistics operation in Ankara, I watched two team members argue over Teams about whose instruction to follow, because two different managers had assigned conflicting tasks to the same person. The tool was not the issue. The authority structure was.Turkey’s SME reality in 2020 adds another dimension that most international frameworks ignore. A significant portion of small and medium businesses entered the remote period without a coherent communication infrastructure. Some teams ran entirely on WhatsApp groups; others had just discovered Zoom; others were still managing through email chains with no versioning. In this fragmented environment, ‘communicate more clearly’ as standalone advice is insufficient. Clarity requires a protocol — an agreed map of which channel carries which type of message. The simplest version works: instant decisions on WhatsApp, formal task assignments confirmed by email, meeting summaries distributed to all stakeholders within two hours. Without that protocol, a decision made on a WhatsApp call at 22:00 will not reach the team member who was not on the call, and the coordination loss compounds across days. Technology is not the constraint here. The constraint is the five-minute conversation required to agree on the protocol — and most teams skip it because it feels administrative.Remote communication is ultimately a management writing practice. The manager who once made decisions verbally in a hallway now has to encode those decisions into text with enough precision that a reader in a different room — or a different city — can act on them without a follow-up question. The Gaziantep firm we started with understood this eventually. The shift was not adding tools or increasing meeting frequency. It was spending three minutes at the end of each meeting writing down who does what by when and sharing that list immediately. For any manager currently navigating a distributed team: before you schedule the next check-in, look at your last five task assignments and ask whether each one closed all four variables. The gap between what you intended and what your team understood almost certainly lives in the ones that did not.

This article was originally published in Turkish by Gökhan MERCANOĞLU on January 11, 2020. The English edition has been reviewed and edited by the author.


For data governance, the critical question is not which system to use. The real question is which problem will be solved, which data can be trusted, and which action will be accelerated. Without these answers, solutions look modern but only digitize old habits.


Gökhan Mercanoğlu
İş Zekâsı ve Raporlama