The unspoken cost of bad communication
by
Kadhir Mani
(4.1 minutes)
<audio url="https://api.productnow-prod.com/storage/getStorageObject?storageObjectId=41789643-1a1b-4f4a-9a29-d8f80a0b6866"></audio>
<h1 id='e631151b-cf64-4d54-9457-6f44b97a0195'>The silent tax of bad communication</h1><p><span style="white-space: pre-wrap;">One Slack thread starts with “quick question,” drifts through three replies, and ends in a meeting to “align.” That small moment is the tax: time lost, stress added, and work delayed because nobody knows who owns the next step.</span></p><p><br></p><p><span style="white-space: pre-wrap;">The cost is real. Grammarly found workers spend 88% of the workweek communicating and poor communication leads to more stress, lower output, strained relationships, and missed deadlines. Gallup’s research adds that when people know what’s expected of them, engagement and execution both improve.</span></p><p><br></p><p><span style="white-space: pre-wrap;">That’s why bad communication isn’t a soft skill problem. It’s a management failure that quietly slows teams down. Once ambiguity becomes normal, every handoff gets harder, every decision takes longer, and every meeting adds to the backlog of confusion.</span></p><p><br></p>
<h2 id='1aaedf08-b487-4e02-92f8-718999fd2aa8'>How misalignment turns into wasted work</h2><p><span style="white-space: pre-wrap;">Unclear communication doesn't just slow things down, it creates hidden waste: rework, waiting, duplicated effort, and eroded trust. In practice, it shows up in three familiar patterns:</span></p><ul><li value="1"><b><strong style="white-space: pre-wrap;">Vague async ask:</strong></b><span style="white-space: pre-wrap;"> a teammate answers once, the thread bounces back for clarification, and the handoff slips.</span></li><li value="2"><b><strong style="white-space: pre-wrap;">Meeting with no decision goal:</strong></b><span style="white-space: pre-wrap;"> everyone talks, nobody owns next steps, and the team books another meeting.</span></li><li value="3"><b><strong style="white-space: pre-wrap;">People talking past each other:</strong></b><span style="white-space: pre-wrap;"> the same work gets done twice, priorities split, and confidence drops.</span></li></ul><p><br></p><p><span style="white-space: pre-wrap;">When this keeps happening, it's an organizational process problem, not a wording problem. Repeated breakdowns point to weak norms: unclear who decides what, loose goals, and no shared picture of what good looks like.</span></p><p><br></p><p><span style="white-space: pre-wrap;">AI makes this more expensive. When teams can move faster, unclear direction spreads faster too, leading to work done on the wrong thing, or work nobody asked for. Atlassian's data backs this up: most meetings are ineffective, most end without clear ownership, and most simply lead to another meeting.</span></p><p><br></p><p><span style="white-space: pre-wrap;">The result is a team that spends more time coordinating than building, and more time undoing than moving forward.</span></p>
<finite-state-machine data-states="[{"id":"start","label":"Decision Needed","description":"A team needs to make a call on scope, direction, or a tradeoff.","isRoot":true},{"id":"doc_write","label":"Write It Down","description":"Someone drafts the context, options, and recommendation in a shared doc.","isRoot":false},{"id":"doc_review","label":"Review","description":"Stakeholders read, comment, and align on their own time - no meeting required.","isRoot":false},{"id":"doc_execute","label":"Aligned Execution","description":"The team moves forward with shared context. New members can self-onboard from the doc.","isRoot":false},{"id":"nodoc_verbal","label":"Verbal Discussion","description":"The decision is talked through in a meeting or Slack thread - nothing is written down.","isRoot":false},{"id":"nodoc_misremember","label":"Misremembered","description":"Different people walk away with different versions of what was decided.","isRoot":false},{"id":"nodoc_made","label":"Decision Made","description":"A decision is assumed but it was never formally captured or confirmed.","isRoot":false},{"id":"nodoc_questioned","label":"Decision Questioned","description":"Someone raises a concern. Others are not sure what was actually agreed.","isRoot":false},{"id":"nodoc_revisit","label":"Revisit Meeting","description":"The team books another meeting to re-litigate the same decision.","isRoot":false},{"id":"nodoc_chaos","label":"Rework and Chaos","description":"Work is undone, redone, or abandoned. Trust erodes. The cycle repeats.","isRoot":false}]" data-edges="[{"id":"e1","source":"start","target":"doc_write","label":"Doc-driven path","conditional":true},{"id":"e2","source":"doc_write","target":"doc_review","label":"Share for review","conditional":false},{"id":"e3","source":"doc_review","target":"doc_execute","label":"Team aligned","conditional":false},{"id":"e6","source":"start","target":"nodoc_verbal","label":"No-doc path","conditional":true},{"id":"e7","source":"nodoc_verbal","target":"nodoc_misremember","label":"No record kept","conditional":false},{"id":"e8","source":"nodoc_misremember","target":"nodoc_made","label":"Assumed agreement","conditional":false},{"id":"e9","source":"nodoc_made","target":"nodoc_questioned","label":"Doubt surfaces","conditional":false},{"id":"e10","source":"nodoc_questioned","target":"nodoc_revisit","label":"Escalate","conditional":false},{"id":"e11","source":"nodoc_revisit","target":"nodoc_chaos","label":"No resolution","conditional":false},{"id":"e12","source":"nodoc_chaos","target":"nodoc_verbal","label":"Try again verbally","conditional":false}]" data-title="How Communication Style Shapes Outcomes" data-height="520"></finite-state-machine>
<h2 id='af92a174-6fa6-4c50-a961-0ad41d539460'>Why the AI era rewards written clarity</h2><p><span style="white-space: pre-wrap;">AI makes speed cheap and ambiguity expensive. When teams can generate ideas, code, and drafts faster, unclear intent spreads faster too, creating rework, missed handoffs, and noisy meetings.</span></p><p><br></p><p><span style="white-space: pre-wrap;">That’s why writing things down first matters more than ever. It helps in three concrete ways:</span></p><ol><li value="1"><b><strong style="white-space: pre-wrap;">Better thinking before discussion</strong></b><span style="white-space: pre-wrap;"> — Writing forces you to put the idea on the page, where it can be tested and challenged before anyone gets in a room. Research backs this up: students in writing-based labs improved their critical thinking scores; those who didn’t write saw no similar gain.</span></li><li value="2"><b><strong style="white-space: pre-wrap;">Faster alignment without extra meetings</strong></b><span style="white-space: pre-wrap;"> — A shared doc makes intent, owners, and next steps visible to everyone, without pulling them into another call. GitLab runs on this model, and Atlassian found 54% of workers regularly leave meetings without knowing what they’re supposed to do next.</span></li><li value="3"><b><strong style="white-space: pre-wrap;">Better memory for onboarding and revisits</strong></b><span style="white-space: pre-wrap;"> — Docs capture the “why” behind a decision, not just the outcome. That means new teammates can get up to speed on their own, and old decisions don’t have to be relitigated from scratch. Only 8% of organizations consistently capture knowledge from people who leave, writing is the fix.</span></li></ol><p><br></p><p><callout icon="megaphone" color="#EF4444">Written clarity isn’t just good hygiene anymore. On an AI-enabled team, it’s a force multiplier for better thinking, faster coordination, and stronger memory.</callout></p>
<h2 id='998f5b3f-b63c-4d52-9372-ebb1a36b23e5'>How to make doc-driven habits stick</h2><p><span style="white-space: pre-wrap;">The best doc habits are straightforward, repeatable, and easy to start. Here are five we think are worth trying:</span></p><ol><li value="1"><b><strong style="white-space: pre-wrap;">Write before review.</strong></b><span style="white-space: pre-wrap;"> Put the argument, options, and open questions in writing before any meeting or review. It forces clearer thinking, and leads to a better discussion. Amazon does this with six-page memos read silently at the start of every meeting.</span></li><li value="2"><b><strong style="white-space: pre-wrap;">Use decision docs for real choices.</strong></b><span style="white-space: pre-wrap;"> When a decision affects scope, budget, or timing, write it down: what was decided, who owns it, when, and why. This makes future handoffs faster and gives teammates the context they need later.</span></li><li value="3"><b><strong style="white-space: pre-wrap;">Send short pre-reads before meetings.</strong></b><span style="white-space: pre-wrap;"> Keep them focused: context, proposal, tradeoffs, and what you're asking for. People who read ahead make better decisions than people who hear it for the first time live.</span></li><li value="4"><b><strong style="white-space: pre-wrap;">Replace status meetings with written updates.</strong></b><span style="white-space: pre-wrap;"> Send a short written update each week, and only meet when a real decision or blocker needs the group. GitLab runs this way, documentation is the default, meetings are the exception.</span></li><li value="5"><b><strong style="white-space: pre-wrap;">Keep a searchable decision log.</strong></b><span style="white-space: pre-wrap;"> A simple log of past decisions becomes a useful resource for onboarding, reviews, and post-mortems. Only 8% of organizations consistently capture knowledge from people who leave, a log is a lightweight way to fix that.</span></li></ol><p><br></p><p><span style="white-space: pre-wrap;">The guardrail: keep it simple. If a template slows the team down, cut it. If a habit stops the same question from being asked five times, keep it. The goal is a doc nobody has to ask for, not a doc nobody reads.</span></p><p><br></p>
<h2 id='543f782c-ee05-4910-ac06-522636fed166'>What do you think?</h2><p><span style="white-space: pre-wrap;">We'd love to hear from you! What do you think? Does this resonate?</span></p><p><br></p><p><span style="white-space: pre-wrap;">Which habit would remove the most friction on your team? Where does writing still slow alignment instead of speeding it up? And as AI gets better at drafting, what part of your doc flow should stay human?</span></p><p><br></p><p><span style="white-space: pre-wrap;">Get in touch: </span><a href="https://" rel="noreferrer"><span style="white-space: pre-wrap;">hello@productnow.ai</span></a></p>
<p><br></p><collapsible-card data-icon="file-text" data-title="References" data-default-collapsed="true"><ol><li><web-citation data-url="https://www.atlassian.com/blog/workplace-woes-meetings" data-title="Atlassian Workplace Woes: Meetings"></web-citation></li><li><web-citation data-url="https://www.atlassian.com/blog/state-of-teams-2024" data-title="Atlassian State of Teams 2024"></web-citation></li><li><web-citation data-url="https://www.gartner.com/en/newsroom/press-releases/2024-05-14-gartner-survey-reveals-eighty-four-percent-of-marketers-report-experiencing-high-collaboration-drag-from-cross-functional-work" data-title="Gartner survey on collaboration drag"></web-citation></li><li><web-citation data-url="https://www.microsoft.com/en-us/worklab/work-trend-index/ai-at-work-is-here-now-comes-the-hard-part" data-title="Microsoft Work Trend Index: AI at work"></web-citation></li><li><web-citation data-url="https://go.grammarly.com/2024-state-of-business-communication-report" data-title="Grammarly 2024 State of Business Communication Report"></web-citation></li><li><web-citation data-url="https://www.gallup.com/workplace/356045/q12-question-summary.aspx" data-title="Gallup Q12 Question Summary"></web-citation></li><li><web-citation data-url="https://pmc.ncbi.nlm.nih.gov/articles/PMC1885902/" data-title="Peer-reviewed study on writing and critical thinking"></web-citation></li><li><web-citation data-url="https://www.sec.gov/Archives/edgar/data/1018724/000119312518121161/d456916dex991.htm" data-title="Amazon 2017 shareholder letter"></web-citation></li><li><web-citation data-url="https://www.cnbc.com/2018/04/23/what-jeff-bezos-learned-from-requiring-6-page-memos-at-amazon.html" data-title="Bezos on six-page memos at Amazon"></web-citation></li><li><web-citation data-url="https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/" data-title="GitLab async handbook"></web-citation></li><li><web-citation data-url="https://handbook.gitlab.com/handbook/company/culture/all-remote/handbook-first/" data-title="GitLab handbook-first"></web-citation></li><li><web-citation data-url="https://handbook.gitlab.com/handbook/company/culture/all-remote/onboarding/" data-title="GitLab onboarding handbook"></web-citation></li><li><web-citation data-url="https://www.apqc.org/resource-library/resource/navigating-great-retirement-km-ai/html" data-title="APQC: Navigating the Great Retirement — knowledge capture survey"></web-citation></li></ol></collapsible-card>
