Examples Of Bad Business Writing

The Kinds of Business Writing That Make People Delete Their Email Without Reading

I see this all the time, mostly on client calls and Slack threads where people try to write professionally and end up producing something that reads like it was generated by a committee that doesn't understand what it's trying to say. The good news is that bad business writing is almost always the same few mistakes repeated by different people. Most of it comes down to one problem: writers treating every email or document like it needs to sound impressive rather than sound useful. You don't need to impress anyone. You need them to know what you're asking for, why, and by when.

Common Examples Of Bad Business Writing

Let me walk through the real patterns I've encountered over the years, not the textbook versions. Problem 1: The vague action request. Here's something I saw last week in a client proposal. It said: "We look forward to collaborating with your team on this exciting initiative and exploring synergistic opportunities moving forward." What does that mean? Nobody knows. The recipient has no idea what action they're supposed to take. They'll either ignore it or send back a confused reply asking for clarification, which wastes everyone's time.

The fix is brutally simple. State the action. State the deadline. State what you need from them specifically. "Please review the attached budget by Friday 3pm and confirm whether it aligns with Q3 targets" takes eight seconds to read and tells the reader exactly what to do. Problem 2: The three-paragraph apology for a two-sentence message. I've read internal memos where someone needed to tell the team that the coffee machine in the breakroom was broken. Three paragraphs. They explained the history of the machine, acknowledged how inconvenient this was, thanked everyone for their patience, and then mentioned the broken machine somewhere around line four. Nobody reads past line two.

This pattern shows up everywhere. The writer is worried about tone. They think being polite means being long. It doesn't. Politeness in business writing means respecting the reader's time. That usually means fewer words, not more. Problem 3: Jargon as a status signal. There's a specific type of writer who uses complex language to sound like they know what they're doing. "Leveraging cross-functional paradigms to drive holistic solutions" is just a fancy way of saying "we're going to talk to the other teams." When I see this in reports, I assume the writer is either hiding a weak argument or doesn't actually understand the topic well enough to explain it simply.

I had a case where a vendor sent me a twenty-page proposal full of terms like "asymmetric value deployment" and "stakeholder alignment matrices." I asked them to rewrite the executive summary in plain English. They couldn't. That proposal didn't get a second look from us. Problem 4: No subject line discipline. Email subject lines like "Quick question" or "Update" or "Thoughts?" are garbage. They convey nothing. A subject line should tell the reader what the email is about and how urgently it needs attention. "Budget approval needed for Q3 vendor payments by Thursday" takes five seconds to write and saves the recipient from opening forty emails to figure out what's important.

Problem 5: The wall of text with no structure. This is the easiest one to spot and the hardest for some people to fix. Paragraphs that are six, seven, eight sentences long with no headings, no bullet points, no visual breaks. The human eye glazes over after about three sentences of dense prose. Your reader is not going to parse a paragraph that looks like a brick. Bullet points exist for a reason. Use them. Short paragraphs exist for a reason. Use them. A wall of text isn't a sign of thoroughness. It's a sign that you haven't organized your thoughts yet.

How to Actually Fix These Problems

The process is straightforward but most people skip steps because they want to hit send. Here's the workflow I use and recommend: Step 1: Write the ugly first draft. Get everything down without worrying about style. You can't edit a blank page. This step is just about dumping your thoughts onto the screen. The goal is speed, not quality.

Step 2: Identify the single purpose of the document. Before you edit anything, answer this question in one sentence: What do I want the reader to do after reading this? If you can't answer it, you haven't figured out what you're writing yet. Go back to step one. Step 3: Cut everything that doesn't serve that purpose.

This is the part most people resist. Every sentence that doesn't move toward your single purpose is dead weight. Delete it. I once had a client delete forty percent of a client-facing document on the third cut and the document got stronger in every measurable way. The client responded faster, asked fewer clarifying questions, and signed the contract two weeks ahead of schedule. Step 4: Read it aloud.

If you stumble over a sentence while reading it out loud, your reader will too. Rewrite it. This takes thirty seconds and catches more problems than any grammar tool will ever find. Step 5: Check the subject line and opening sentence.

These two elements determine whether the rest of your writing gets read. If they're weak, everything else doesn't matter. The subject line states the topic and the required action. The opening sentence states the context and the key point. Everything after that is supporting detail.

When This Approach Doesn't Work

Cut-and-simplify writing works for about eighty-five percent of business communication. Internal emails, project updates, vendor requests, meeting summaries, status reports. The other fifteen percent is where you need to be honest about what you're writing. Legal documents require a different standard. Contracts, compliance filings, regulatory correspondence — these aren't about clarity, they're about precision and legal defensibility. You can't simplify language that exists to create specific legal obligations. The jargon in those documents isn't decoration. It's the actual mechanism that makes the document work. Don't apply the cutting approach to contract language without consulting legal counsel. Another limitation: crisis communications. When you're addressing a serious incident, sometimes you need to acknowledge complexity and show nuance. A purely stripped-down message can come across as cold or dismissive during situations where empathy matters. The rule is simplicity, not emotional void. You can be direct and still sound human.

I learned this the hard way early in my career. I wrote a terse email to a client whose project had failed due to our mistake. It was clear, concise, and completely tone-deaf. The client escalated internally and we lost the account. I learned that brevity and bluntness are not the same thing. Knowing the difference is what separates competent business writers from good ones.

One Specific Edge Case I Deal With Regularly

Multi-layered approval chains. You know the situation: an email goes from a junior staff member to a middle manager to a director to finance, and by the time it reaches the end, the original request has been rewritten so many times that nobody involved remembers what the first sentence said. I've seen this destroy projects where the delay from clarification loops cost us three weeks of turnaround time. The workaround is strict: whoever sends a document into an approval chain writes the requested action at the very top, in bold, and explicitly states what each approver needs to do. "Approver A: confirm budget. Approver B: verify timeline. Approver C: authorize signature." This sounds like overkill until you've watched a six-person approval chain grind to a halt because each person assumed someone else understood the document. It's not glamorous. It won't make anyone's newsletter. But it stops the kind of miscommunication that costs real money in real businesses.