Heyo Quartz! David Smooke here, founder/CEO of HackerNoon (https://hackernoon.com/ https://hackernoon.cv/). We're a tech publishing platform with 40K+ contributing writers, 3M+ monthly readers, 13 employees, and $1.5M+ in yearly revenue. The pattern is simple: Writing handles information transfer. Meetings handle nuance and real-time problem-solving. Most companies invert this. Leaders constantly use HackerNoon to showcase their writing publicly. But does that discipline carry over internally—to the briefs and messages that determine whether teams ship or sit in meetings? Our internal meeting structure forces writing discipline: * Developers: 1x weekly (Thursday show-and-tell) * Sales: 1x weekly * Editorial: every other week * Marketing: every other week * All hands: 4x a year The constraint creates behavior. For example, developers ship code Tuesday and Wednesday because Thursday is their only meeting slot. Written specs carry the coordination load and leave QA for end of week instead of weekends. What good leadership writing looks like: Async-first documentation. We keep Slack threads going for months, write detailed meeting notes, and document action items so context doesn't gets lost. Constraints before creativity. Define budget, timeline, and scope upfront so teams can execute instead of endlessly brainstorming. The AI paradox: Tools like Claude/ChatGPT/Gemini make it easier to generate more words, but not clearer thinking. I'm seeing founders use AI to produce longer memos that still don't answer: Who owns this? What's the deadline? What does success look like? When will this project complete? AI amplifies whatever discipline you bring to it. Our writing-heavy review process: Year-end reviews require 2-4 hours of written self-evaluation before our 1:1. This surfaces actual thinking, not just opinions. The meeting becomes 10x more productive—we spend zero time gathering information and 100% on navigating disagreement, discussing growth, addressing sensitive dynamics. The ROI is measurable: A 45-minute writing investment that prevents three 1-hour meetings with 6 people saves 17.25 person-hours. Do that weekly and you've saved 900 person-hours annually. Why most leaders avoid this: Clear writing requires hard decisions; vague writing preserves deniability. Happy to discuss specific examples from managing a remote-first media company with minimal meeting overhead. Kind Regards, David Smooke. Founder/CEO, HackerNoon
Poor leadership writing leads to unnecessary meetings by pushing unresolved thinking further down the line. When direction is vague, decisions are implied rather than stated, or ownership is unclear, teams schedule meetings to interpret intent, negotiate scope, or realign their understanding. While each meeting might seem necessary on its own, they collectively drain focus, slow down progress, and lower morale. Effective leadership writing does the opposite. It replaces ambiguity with clear decisions. Good writing clearly defines the problem being addressed, the important constraints, what is included and excluded from the scope, who is responsible for the outcome, and what a successful result entails. When these elements are explicit, teams don't need meetings to ask "What are we doing?" or "Who is in charge?" They can simply take action. The hidden cost of poor writing is escalating ambiguity. A vague initial document results in an unclear handover. This unclear handover leads to rework. Rework then necessitates status meetings. These meetings reveal further confusion, which in turn triggers more meetings. Time is lost not due to laziness, but because clarity was never fully established from the start. Asynchronous work and AI further magnify this issue. Asynchronous environments rely on written documents as the main source of truth. If leadership writing is imprecise, confusion spreads more rapidly and lingers longer. AI can instantly scale unclear instructions, transforming a single vague message into ten slightly different interpretations. AI acts as a force multiplier, amplifying either clarity or confusion equally. Leaders can address this by taking more time during the writing process. They should send fewer messages, but ensure each one is decisive. Before sending, they should ask: What decision am I making? What decision am I explicitly not making? Who is responsible for the next step? What does success look like? If these answers are not present in the writing, they will inevitably surface later as meetings. Effective leadership writing is not about being wordy; it is about being intentional. It is the most cost-effective method for aligning teams and the most dependable way to prevent meetings from being scheduled in the first place.
The biggest time saver for our agency has been recording the meetings we have into a transcript using AI. After the meeting, we use a prompt to create a TL:DR of the meeting, a summary of the meeting, and task lists for everyone involved in the meeting. These task lists can go into everyones CRM's or when every they organise there time. This seems unrelated, but it drastically reduced the number of meetings we actually need to have becuase there are simple records with tasks to address them which means we almost never have to circle back to previous discussions.
Do not be afraid of being verbose. Brevity has its place, but not for scoping out projects. Do not be afraid to list in extreme detail every need. Agile stories are often too brief. Do compartmentalize and organize the details so they are easy to refer back to. But everyone on a project should have every detail somewhere in their email and/or a PDF.
When I built the online branch of my business, Legacy School, I discovered that a company's written forms of communication would directly affect how fast it could accomplish its goals. In other words, if your written communication is poor, you will end up with an abundance of meetings. On the other hand, if your written communications are performed at a high level, you will have fewer meetings and have better success as a result. When direction is unclear, you will see an explosion of added appointments on everyone's calendar. When no one has ownership, you will see "quick check-ins." When the decision is not documented (no notes), you may find yourself revisiting a decision three or four times. When you do not finish your thought process and are forced to rely on a meeting to complete that thought, it can end up as a crutch. The financial impact of this can be staggering. Studies show that employees spend 30-40% of their week in meetings. When multiplied by 52 weeks, that converts to significant dollar amounts for a company. Rather than wasting time trying to clarify something that should have been stated clearly during the initial planning process, you are actually wasting money. Therefore, we view writing as a part of our infrastructure. For every project that we work on, we write a simple one-page piece that identifies the goal, restraints, a designated owner, and how we will measure success. If we cannot form our thoughts on paper, we are not yet ready for a face-to-face meeting. Utilization of asynchronous work and the use of AI to complete tasks will require an even greater reliance on writing. AI may allow leaders and employees to generate numerous words, but it does not lead to improved thinking. Therefore, leaders need to slow down, process, and communicate their thoughts with intention. My rule is simple: if a meeting feels necessary, try rewriting the brief first. Nine times out of ten, the meeting disappears.
Clear writing reduces meetings because it forces decisions to be made before they hit a calendar invite. With established teams, shorter communication works best, but what I see more often now is AI-generated fluff where a few sentences turn into a long essay that hides the actual point. When the message lacks clarity on ownership, intent, or next steps, teams default to meetings to resolve confusion that should have been addressed in writing. Async work and AI amplify this problem because volume increases while signal drops, and people mistake length for thoughtfulness. I have also seen situations where AI is used to create the appearance of productivity, flooding inboxes with updates that add visibility but not progress. Good leadership writing is concise, opinionated, and decisive, it names the problem, assigns responsibility, and closes the loop so teams can execute without another call. Please, not another fifth kick-off call!
Most meetings provide a classroom for uncompleted thinking. In most cases, leaders have provided an opportunity to learn from the same information they did not clearly write down. I've been working with people for many years to help them structure their arguments. In most cases, when individuals are unable to complete their thought process (their argument), many questions arise. The meetings are held to address the remaining questions. Leadership writing is very similar to instructional writing. Leadership writing provides definitions of problems, limitations, and expectations of the outcome. Leadership writing also identifies potential questions before others ask them. Async work does not include the "safety net" that was previously in place because leaders do not have the opportunity to explain anything after the team has completed the work. Additionally, AI will continue to add volume, but will not make judgments regarding the quality of the work completed. Leaders must complete their thinking before sharing it with anyone else. The key takeaway from this is that clarity is not a matter of style; it is a discipline. Writing requires leaders to make decisions. Meetings are typically used to avoid making decisions. If leaders make their decisions first and then write about those decisions, the meetings will diminish on their own. However, if leaders use writing to begin exploring an idea rather than to provide conclusions, their calendars will fill with meetings. Writing effectively is not a function of using fewer words. Effective writing is a function of having fewer unanswered questions circulating throughout the organization.
Poorly written leadership communication often leads to confusion, which in turn causes unnecessary meetings. In my experience, vague directions, unclear ownership, and poor project handoffs create compounding ambiguity. This often results in teams holding multiple meetings just to clarify what was originally unclear in the written instructions. Asynchronous work and AI tools only amplify these issues, as unclear communication can still lead to misunderstandings, even when technology is used to streamline processes. Good leadership writing, on the other hand, provides clarity, defines ownership, and ensures decisions are made upfront. Clear and precise writing establishes project constraints and expectations, reducing the need for time-consuming meetings and preventing rework. Leaders can improve this by being more thoughtful in their communications, ensuring messages are direct, actionable, and clear. This will align teams more effectively and reduce inefficiencies.
My three decades in architecture confirm that bad writing creates meetings; ambiguous project scope, budget, or timeline directly translates to costly rework and endless clarification sessions. As founder of Keiser Design Group, my shift to focusing on client vision ensures their "must-haves" are clearly documented from the outset, minimizing misunderstandings. Good leadership writing, as outlined in our "Avoiding Common Mistakes When Working with Commercial Architects" guidance, carefully defines the project vision, budget, and timeline. Without this precise documentation, teams face ambiguity, necessitating reactive discussions instead of proactive execution, undermining our Integrated Project Delivery approach. In an async world, AI can quickly amplify unclear directives, turning minor ambiguities into significant project roadblocks if initial human input isn't precise. Leaders must provide comprehensive, written blueprints--like our structured "Five Phases of Commercial Building Design"--to eliminate guesswork and empower teams. This commitment to written clarity allows us to shift from constant explanation to actively delivering client visions, as demonstrated in successful changes like the Maumee Bay Brewing Company project. We ensure all partners know what to expect, fostering transparency and authenticity over unnecessary meetings.
The best way for managers to write well is to adopt a purposeful, transparent tone. The writing must be direct and provide each team member with a clear understanding of what is expected of them and the project's end objective. This allows the manager to define their expectations and vision, ensuring there is no confusion about the project's goal and how to achieve it. When an organization provides vague direction and unclear responsibilities, it creates uncertainty and hesitation among employees, reducing their willingness to act. Hesitation leads to indecision, and when projects are delayed, they stall. When a task's responsibility is unclear, accountability for completing it also decreases. Poor communication during project handoffs can lead to the loss of important information, resulting in additional confusion. As a result, the organization develops a cycle of confusion that requires numerous, often frustrating, meetings to realign the team's focus, using valuable time and resources that could have been used to complete project work. While asynchronous work environments allow employees to work independently at times, they can create gaps in communication and lead employees to miss context. Because employees cannot interact in real time with colleagues, they may misinterpret electronic messages, creating misunderstandings that hinder project progress. The increasing use of AI to process information may make it even more difficult to communicate effectively. While AI can process large amounts of data, it cannot replace the nuances of human communication or the context in which employee decisions are made. Organizations should develop clear guidelines for using asynchronous communication and emphasize the importance of including context and detail in electronic communications. Managers can improve communication clarity by developing a structured approach to delivering messages to employees. Managers can create separate channels for different types of communication to further improve communication efficiency with employees. They should solicit regular feedback from employees regarding the effectiveness of communication to continually assess whether the communication strategy is working for employees, and adjust accordingly.
Async work suffers when product & marketing teams communicate poorly. They hold meetings masquerading as collaboration. Half-baked ideas are shared as text messages, turning async collaboration into confusion and sync overload. Schedule another meeting to sort it out...because nobody can ask questions or clarifications in real-time when a thought should've been written well in the first place. Clear leadership writing (onedaybriefs and written pre-reads) kills async ambiguity and lets everyone async confidently. Async tools & AI will exacerbate poor communication...but they'll also supercharge good communication. Thoughtful writing produces clean outputs, less back-and-forth, and empowered execution. Leaders who invest the time in crisp, clear written direction cut needless asynchronous meetings. You execute faster + better decisions with less calendar pressure & zero headcount.
Operations Director (Sales & Team Development) at Reclaim247
Answered 15 days ago
Meetings happen operationally when teams don't trust that intent has been communicated clearly. Unclear writing results in messy execution, customer pushback, and compliance risk. And those things generate reactive meetings to "correct" the problems downstream. We experienced this first hand with meetings being required due to verbal handoffs and ambiguous escalation policies. Teams found themselves constantly clarifying with one another. Creating a single source of truth with structured leadership writing eliminated that. Effective leadership writing makes it clear who is responsible for what, what has already been decided, and where there is discretion. That certainty eliminates CYA meetings and knee-jerk checking in with each other. Auditability and accountability also increase, which matters when working in regulated claims environments. Meetings naturally decrease when employees feel empowered to act.
I have discovered that meetings are generated where writing creates ambiguity. That ambiguity grows quickly in a creative marketplace. Once, we provided fairly open-ended guidance to our artists on what was acceptable to list in their marketplaces. While the guidance seemed very flexible, that flexibility led to many disagreements, and support teams spent several hours on calls trying to determine each other's intent. The written words did not limit or guide their decision-making. When we rewrote the guidance with specific rules, examples, and edge cases, things began to change. Questions went down. Syncs internally went away. People stopped asking what we "really" meant. The takeaway here is that writing must be able to travel without its author. In an asynchronous work environment, leaders cannot always be present to provide additional context. When writing allows the reader to interpret what has been written, meetings arise to address the ambiguity it creates. Clear writing does not stifle creativity; it preserves it by establishing boundaries that can be relied upon. Each sentence that takes doubt out of the equation will save time further down the road. Meetings did not cease because we prohibited them; they continued. Meetings ceased because the work no longer required them, as the thought that should have occurred prior to initiating them had already occurred. Clarity will scale exponentially greater than conversation can cross cultures and borders.
It takes time for poorly written instructions to trigger an emergency meeting, but first, a problem develops due to poor communication. After that, a meeting will be scheduled to address some of the problems that developed due to poor communication. Poorly written work orders have caused many jobs to pause for safety reasons, delayed my crews' schedules, and led to many phone calls with finger-pointing. The real cost of the delayed job was not the hour spent in a meeting; it was the time wasted while the crew waited for clarity about what was expected of them. One poorly written instruction can delay a crew for half a day. If you provide clear direction to your team in writing, you eliminate the need for many of these "downstream" corrections. Through writing, you identify the responsible party, the steps involved in completing the task, and the task's limitations and constraints before the start of the task. Writing clearly includes: Identifying who is making decisions and who is going to execute the decision. Identifying what "done" looks like and how completion will be determined. Identifying what should NOT be done in relation to the execution of the task. Identifying when to cease execution of the task and when to escalate the task. The increased use of asynchronous work environments underscores the importance of strong writing skills. Because of the use of asynchronous work environments, you can no longer fix misunderstandings about a task by having a conversation with your coworker in the hallway. Instead of talking to your coworker about the misunderstanding, if the writing did not travel with the person who needed to read the writing, the leader needs to travel to discuss the issue with their team member. Writing effectively is less expensive than moving individuals to different locations to clarify expectations that were not identified through writing.
Most meetings are designed to address decisions that have been made but not finalized; good documentation can help fill this gap. I see most of the leaders I speak with sharing updates on their projects or organizations and describing the activities they have completed. However, these updates rarely include the actual choices or decisions made. As such, teams often meet to discuss what really matters - this meeting issentially tatakesp the task of thinking through the items for which the update did not provide an answer Asynchronous work has increased the burden on organizations as delays continue to grow and misalignments increase. Additionally, while AI provides a great opportunity to improve the speed at which we write documents, it also creates the problem of producing "confident" text that avoids responsibility for decision-making and trade-offs. Effective writing that supports leadership identifies the decision(s), rather than simply the background information. It clearly states the priorities, constraints, and open questions for further discussion. When this is accomplished, there will be less need for team meetings to determine the leader's intentions. One of the metrics I track to gauge the effectiveness of my writing is the time it takes for a decision to be made after it is written down. As my writing improves, the time to make a decision decreases, and, subsequently, the number of meetings I am required to attend also decreases. In my experience, good writing is not about being brief; it is about being complete. If a person were going to ask it in a meeting, then it should already have been addressed in the document. If a meeting is required because the document does not provide sufficient information to support a decision, the meeting will likely be very costly.
Unclear writing in regulated work not only creates meetings, but it also creates risks. A poorly written initial policy memo prompted a series of review calls, during which each team had its own interpretation. No progress was made until the decision-makers clarified their intentions, which took several weeks. Clear writing eliminates the number of reviews by eliminating uncertainty. Clear writing shortens the approval chain. Additionally, clear writing limits your liability. Effective Leadership Writing Does: Clearly states the decision. Sets boundaries and exceptions References applicable laws or regulations Identifies who will be accountable for the final action Tools and AI for asynchronous use make it easier to spread clarity and confusion. Poorly written content spreads rapidly, as does well-written content. Therefore, leaders cannot depend upon their charisma and ability to explain things in person anymore. The page is the leader. When the page is unclear, meetings become a means to mitigate risks. When the page is clear, meetings are unnecessary. Meetings are eliminated because teams do not have to meet, not because there are fewer meetings.
In personal injury law, unclear communication is often how insurance companies try to lowball clients, forcing protracted negotiations or trials to prove what should be obvious. My mission at Slam Dunk Attorney is to flip this script with "direct communication" and "championship-level preparation," ensuring every message reduces friction, not creates it. Bad communication from the opposing side directly causes more "meetings" -- whether it's battling disputed liability in court or lengthy back-and-forth on low settlement offers. Our approach, like providing "solid justifications" with specifics about injuries and long-term implications, is our "good writing" that prevents unnecessary rounds of debate. With our global team, including Ilse in Mexico City, clear written communication becomes even more critical; it's our asynchronous meeting. Leaders must demand that communication be precise, actionable, and anticipate next steps, just as we "deliver results, not excuses" for our clients.
In the high-stakes world of finance, vague communication is a silent killer of opportunity and a catalyst for endless, unproductive meetings. At Jets & Capital, we explicitly designed our communication strategy to eliminate ambiguity, starting with our strict vetting process. Our clear, upfront designation of attendees into 85% "allocators" and 15% "fundraisers" is a direct response to the problem of unclear thinking; this explicit written guideline pre-qualifies expectations, preventing countless wasted conversations and meetings that would otherwise occur if the audience composition wasn't so precisely communicated and enforced. This precision ensures that every attendee knows exactly who they'll be connecting with, fostering a "no pressure environment" focused on genuine collaboration rather than blind pitching. The emergence of async work and AI doesn't create new problems as much as it magnifies existing ones when leaders lack clarity. For us, AI can be a tool to refine how precisely we articulate our event's value proposition for specific groups, ensuring our message is always calibrated to attract the right "high-caliber guests" and minimize misinterpretations. Leaders must communicate with meticulous detail, defining the specific value for each audience segment and the desired outcomes of any interaction. For example, by explicitly stating "85% allocators" and emphasizing "networking first" rather than "endless panels," our written communications set clear expectations that significantly reduce the need for follow-up meetings to clarify purpose or qualify attendees.
Look, good leadership writing has to be surgical. There is a massive difference between telling a team to improve performance and telling them to shave 200ms off API latency by Friday. Vague direction is basically a debt the company pays back with interest through endless clarification meetings. When people aren't sure who owns what, they schedule a meeting just to cover their backs. We've seen this a lot while scaling engineering teams. Ambiguity doesn't just slow you down; it creates this culture where nobody moves without a group huddle. AI and async work have brought in this new kind of friction I call polite noise. AI is honestly too good at spitting out long, professional-sounding blocks of text that don't actually say anything. If a leader uses GenAI to fluff up a simple order, they're just forcing the team to waste time digging for the point. In an async setup, if your writing isn't self-contained, a five-minute fix turns into a three-day ordeal. I tell leaders to use AI to simplify, not expand. If the output is longer than what you put in, you're basically inviting someone to book a meeting. If you want to stop the friction further down the line, you need a document-first mandate. If a decision isn't written down with a clear definition of done, it simply doesn't exist. We follow a pretty simple rule: if a doc needs more than two follow-up questions before the team can actually start, the writing failed. Real clarity means being explicit about what you aren't deciding yet and who has the final say. When you take away that fear of overstepping, people stop feeling like they need a meeting for every little thing. It's easy to forget that being clear is actually a form of empathy. When a leader spends an extra ten minutes thinking through a message before they hit send, they're protecting their team's focus and mental well-being. You're saving them from the chaos of a fragmented calendar.
I've noticed meeting volume decrease almost immediately when leaders replace verbal instructions with concise written briefs that focus on decisions. Once, a weekly cross-team sync vanished after I sent a one-page document with the objective, owner, non-goals, and a deadline for the decision. Clearly, there was nothing left to live "clarify." The reason of bad writing is a lack of decision-making and ownership that is vague enough to force teams to meet to bring to the surface what should have been obvious. Async work and AI exacerbates this because it unclear input, which drives confusion, is scaled and the opposite of resolved. Great leadership writing is succinct and precise. It states the decision, owner, the boundaries, and what will not be revisited. Leaders that allocate time to write this way, foresight focused time to write, and trade it for prolonged attention def. to be saved across the organization. Best regards, Ben Mizes CoFounder of Clever Offers URL: https://cleveroffers.com/ LinkedIn: https://www.linkedin.com/in/benmizes/