You spent years in school learning to write essays. Five paragraphs, thesis statement, supporting evidence, conclusion. Then you entered the workforce and discovered that nobody reads essays. They read emails, Slack messages, and reports — all of which follow completely different rules.

Professional communication is a distinct skill set that formal education barely touches. Most people learn it through trial, error, and occasionally painful feedback.

Here’s what would have been useful to know from the start.

Emails That Get Read

The average office worker receives 121 emails per day. Most are scanned, not read. If your email doesn’t communicate its purpose in the first two lines, it’s effectively invisible.

Put the action item first. “I need your approval on the Q3 budget by Friday” as the opening line. Not buried in paragraph three after context that the reader may never reach.

Use subject lines that summarise. “Meeting Tuesday” tells the recipient nothing. “Request: 15-min review of Q3 budget - by Friday” tells them exactly what’s needed and when.

Keep it short. If your email is longer than a phone screen, most recipients won’t finish it. For longer communications, write a short email with a document attached.

One email, one topic. Combining three requests in one email means at least one will be forgotten. Send separate emails for separate actions.

Make the response easy. “Does Tuesday at 2pm or Wednesday at 10am work better?” is easier to answer than “When are you free this week?” Reduce the effort required to respond and you’ll get faster responses.

Slack and Chat Etiquette

Real-time messaging has its own grammar that nobody explains:

Don’t send “Hi” by itself. The message that says only “Hi, Michael” and waits for a response before stating the purpose wastes both people’s time. Combine your greeting and your message. “Hi Michael — do you have the client’s updated contact details? I need them for the invoice.”

Thread your replies. In busy channels, replying in threads keeps conversations organised. Replying in the main channel creates noise for everyone.

Use status messages. “In a meeting until 2pm” or “Focus time — slow responses” manages expectations without requiring individual explanations.

Don’t expect immediate responses. Chat is not a phone call. People have the right to respond when it suits their workflow, not the moment your message appears.

Giving Updates

Whether in standup meetings, status reports, or casual check-ins, most people give terrible updates. They’re either too detailed (a chronological account of everything they did) or too vague (“things are going well”).

The formula for a useful update:

What’s done. Completed items, briefly. “Finished the client proposal, sent it for review.”

What’s next. Upcoming focus areas. “Starting the competitor analysis this afternoon.”

What’s blocked. Issues that need input or action from others. “Waiting on access credentials from IT — submitted the request Monday.”

That’s it. Three sentences. The detail lives in project management tools and documents, not in verbal updates.

Disagreeing Without Conflict

Professional disagreement is essential and normal. Bad ideas need to be challenged. But the way you disagree matters enormously.

Disagree with the idea, not the person. “I see this differently” is productive. “You’re wrong” is combative. The difference is subtle in logic but significant in reception.

Lead with understanding. “I understand the reasoning — the timeline pressure is real. My concern is…” shows you’ve listened before responding. People are more receptive to disagreement when they feel heard.

Use questions. “Have we considered what happens if the supplier doesn’t deliver on time?” raises the concern without directly opposing the plan. Questions feel collaborative; statements feel oppositional.

Offer alternatives. Disagreement without an alternative is just criticism. “Instead of A, what about B?” gives the conversation somewhere productive to go.

Know when to stop. If you’ve made your point clearly and the decision goes against you, accept it. Continuing to argue after the decision is made damages relationships and accomplishes nothing.

Managing Up

Communicating with managers and senior leaders requires a different approach than communicating with peers.

Be concise. Leaders typically have less time and more context-switching than individual contributors. Get to the point quickly.

Lead with the conclusion. “The project will be two weeks late because of the vendor delay. Here’s my plan to minimise the impact.” Don’t build up to bad news. State it, then explain.

Bring solutions, not just problems. “We have a problem” creates work for your manager. “We have a problem, and I recommend we address it by doing X” demonstrates initiative and reduces their cognitive load.

Calibrate detail. Your manager doesn’t need the same level of detail as your team. Adjust the granularity of your updates based on who’s receiving them. A board member needs headlines. A project team member needs specifics.

Written Communication Clarity

Across all written formats, clarity comes from structure and simplicity.

Short sentences. Complex ideas don’t require complex sentences. Break long sentences into shorter ones. Each sentence should contain one idea.

Active voice. “The team completed the analysis” is clearer than “The analysis was completed by the team.” Active voice is shorter and more direct.

Avoid jargon with mixed audiences. Technical terms are fine among technical colleagues. With broader audiences, plain language communicates better. “The system is slow” is understood by everyone. “We’re experiencing latency issues in the API gateway” is understood by engineers.

Format for scanning. Bold key terms. Use bullet points for lists. Break long text into sections with headers. Most professional communication is scanned before it’s read — make scanning productive.

I’ve spoken with consultancies like Team400 that work across multiple industries, and they consistently note that the biggest productivity bottleneck in most organisations isn’t technology or strategy — it’s communication. Teams with clear communication habits outperform teams with superior tools and unclear communication almost every time.

The Compound Effect

Communication skills compound. Clear emails lead to faster responses, which lead to faster decisions, which lead to better outcomes. Concise updates build trust, which leads to greater autonomy, which leads to career advancement.

The people who communicate most clearly are often perceived as the most competent — even when their technical skills are average. Fair or not, this is how professional environments work.

Invest in these skills. They’re more career-relevant than most technical certifications and more enduring than any specific tool or platform knowledge.

The good news: they’re learnable. Pay attention to communication that works well, notice what makes it effective, and apply those patterns to your own writing and speaking.

It gets better with practice. Like everything else worth doing.