New project announcement
I shipped skillcraft.ai - a tool that helps you find the best learning resources tailored to your goals. All you need to do is tell it what you want to learn, and I’ll find the right resources to get you there.
Up to date
Published
3 min read

Trevor I. Lasn

Building tools for developers. Currently building skillcraft.ai and blamesteve.lol

Take Your Writing Seriously

It’s not just about getting the message across; it’s about doing so in a way that’s easy for others to follow. Good writing shows respect for your team and your work.

When you send out poorly written communication, you’re saying, “My time is more valuable than yours.” You might not mean it that way, but that’s how it comes across. The message isn’t just in the words you choose but in how much care you put into them.

A sloppy, hard-to-read email means someone else is going to spend extra time decoding it. Multiply that across an entire team, and you’re wasting hours of productivity. And for what? To save yourself a few seconds? That’s a bad trade.

Your writing style impacts more than just your own communication—it sets a tone for the team. If you write sloppy messages, other team members will think it’s okay to do the same. Before you know it, everyone’s writing half-baked emails that are hard to follow, and team communication deteriorates.

Imagine this scenario: You’re leading a project, and you write a vague, typo-filled message to a teammate. They reply with their own unclear response. Now you’ve both wasted time trying to figure out what the other meant, and progress has slowed.

Think about a bug report in a software project. If a developer logs a bug with poor writing—missing details, unclear descriptions—the person assigned to fix it will need to ask for clarification. That back-and-forth eats up valuable time, and a bug that could’ve been solved quickly drags on.

Compare that to a detailed, well-written bug report that’s clear from the start. The developer can jump in, understand the issue immediately, and fix it without delay.

Set a Higher Standard

I’m not saying you need to write like Hemingway in every Slack message. But writing clear, thoughtful communication shows respect for your team. It says, “I value your time and want to make sure this is easy to understand.”

Here are some basic tips I follow:

  • Proper grammar and punctuation.
  • Proofread before sending.
  • Avoid abbreviations that might confuse others.
  • Break long messages into smaller paragraphs for readability.

These might seem like small things, but they add up. Clear, concise writing improves team communication, cuts down on misunderstandings, and saves everyone time.

In many ways, your writing is a reflection of your professionalism. If you take the time to write well, people notice. They’re more likely to take you seriously because it shows you care about the details.


Found this article helpful? You might enjoy my free newsletter. I share dev tips and insights to help you grow your coding skills and advance your tech career.


Check out these related articles that might be useful for you. They cover similar topics and provide additional insights.

Reflections
7 min read

Can Scrum Be Salvaged?

Scrum is failing engineering teams and what it's actually costing us

Nov 14, 2024
Read article
Reflections
4 min read

Become a Better Engineering Manager with JQL

Using Jira queries to understand engineering trends and drive improvements

Feb 11, 2025
Read article
Reflections
4 min read

A Great Product Doesn't Need Marketing

Great products speak for themselves, without the need for massive marketing campaigns

Sep 18, 2024
Read article
Reflections
5 min read

A Company Is Not a Family. It's a Sports Team

'We're not just a company, we're a family!' It's a nice sentiment, sure. But it's also a load of crap.

Oct 5, 2024
Read article
Reflections
5 min read

Minimum Viable Documentation

How to create essential documentation that actually gets read and used.

Sep 27, 2024
Read article
Reflections
4 min read

Why I Value Firebreak Sprints for Managing Technical Debt

How scheduled developer freedom weeks can revolutionize your codebase and team morale

Apr 8, 2025
Read article
Reflections
3 min read

When Tasked with a Problem, Start with the Bigger Picture

When faced with a challenge, I always step back to see the whole picture first. It's like pausing a complex strategy game to study the map. You might lose a few seconds of play time, but you gain a crucial understanding of the battlefield.

Oct 3, 2024
Read article
Reflections
5 min read

Advice to New Engineering Managers

Tips for being an effective engineering leader and how to avoid common pitfalls

Feb 15, 2025
Read article
Reflections
5 min read

When Should You Actually Worry About Tech Debt?

Technical debt isn't the monster under your bed, but it can become one if ignored too long.

Sep 12, 2024
Read article

This article was originally published on https://www.trevorlasn.com/blog/take-your-writing-seriously. It was written by a human and polished using grammar tools for clarity.