# Communication at Work: Eight Habits Worth Practicing First

Canonical URL: https://headwayskills.com/knowledge/communication/communication-at-work/
Markdown URL: https://headwayskills.com/knowledge/communication/communication-at-work.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving communication at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

What good communication at work actually looks like day to day - eight concrete habits, from leading with your point to raising the awkward thing early.

## Key facts

- Title: Communication at Work: Eight Habits Worth Practicing First
- Category: Communication
- Primary skill: Communication
- Related skills: Professional Behaviors, Teamwork
- Primary keyword: communication at work
- Source page: https://headwayskills.com/knowledge/communication/communication-at-work/

## What this page covers

- What good communication at work actually looks like day to day - eight concrete habits, from leading with your point to raising the awkward thing early.
- Practical guidance for communication at work
- How this topic connects to Communication

## Detailed explanation

Communication at work is the everyday exchange your job runs on — emails, updates, meetings, corridor questions — and doing it well is less about being articulate than about a handful of small decisions: what to say first, which channel to use, when to check you understood, and how to raise something uncomfortable.

Most people are told they need "good communication" long before anyone tells them what that means in practice. It usually arrives as a line in a job ad, or a sentence in a review that sounds like praise and correction at the same time. What follows is the practical version — eight habits you could try this week, and the reason each one works.

## Eight habits that carry most of communication at work

Search this topic and you find two kinds of article: explainers that sort communication into verbal, nonverbal, and written categories, and numbered improvement lists whose lengths vary far more than their contents — Harvard's professional development division has eight, Forbes Advisor and Workday have ten each, Asana twelve, Justworks eighteen. Read a few and the same core repeats: listen actively, be clear and concise, watch nonverbal cues, hold one-on-ones, give constructive feedback. It is sound advice, and most of it is written for someone running a team. What follows is the same ground from the other chair — the exchanges you personally have, most days, with people who are not your reports.

### 1. Lead with the point, then the reasoning

Most people build up to their point, because background-first is the order they thought it in. At work that order costs the reader time and often costs you the point, since the reply tends to arrive before the last paragraph does. Put the decision, the request, or the answer in the first sentence, then supply the reasoning for whoever wants it. The same rule runs the [subject line](/knowledge/communication/email-writing/): "Need your sign-off on the vendor list by Thursday" tells someone what to do with the email before they open it, where "Quick question" tells them nothing. Every list on this topic says be clear and concise; the operative part is the ordering, not the word count.

### 2. Match the channel to the message

You make this choice dozens of times a day and rarely deliberately. Pumble's guide to workplace communication states the rule plainly: real-time conversation for the nuanced topics, asynchronous written channels for the updates that need a paper trail. So anything sensitive, complex, or negotiable belongs in a conversation, where a misreading gets caught in seconds; anything that is genuinely one-way or needs a record belongs in writing. Both mistakes are common and both are expensive — the difficult message compressed into chat because a call felt like too much, and the twelve-message thread that a two-minute conversation would have closed. Written does not have to mean text, either: an asynchronous video with a screen share often explains a complex thing better than either a document or a meeting.

### 3. Say it back before you respond

[Listening well](/knowledge/communication/active-listening-workplace/) is the most-repeated advice on this topic and the least specific. The specific version is a single sentence, said before you reply. Prezentium's guide to active communication gives the wording directly: "What I hear you saying is x. Do I have that right?" It feels awkward the first two times and then stops feeling like anything. What it buys you is timing — it catches the misunderstanding in the thirty seconds before you act on it rather than the three days after, when it has already turned into rework. Training Industry made the same case in 2025, framing the pairing of active listening with clear feedback as a way to head off conflict rather than merely a courtesy.

### 4. Pin down the ask before you agree to it

"Can you take a look at this?" is not yet a task. Before you say yes, get four things straight: who is actually asking, what specifically is wanted, when it is genuinely needed — a date, not "ASAP" — and what a finished version looks like. Then write your understanding back in a sentence and let them confirm it. This feels like friction in the moment and removes most of the rework later, because the expensive version of the conversation is the one you have after doing the wrong thing well. It is the habit the tip lists consistently miss: they cover clarity in the messages you send and say almost nothing about the requests you receive.

### 5. Mind the second channel

Tone, posture, expression, and pace run alongside your words, and when the two disagree, people believe the delivery. Indeed's and Forbes Advisor's guidance both single out nonverbal cues as the thing most worth watching, in both directions. Reading it means noticing when a room goes quiet or someone's answers get shorter, and adjusting before you have lost them. Sending it means checking that your delivery agrees with your content, since agreement said through a clenched jaw communicates the jaw. [Remote work](/knowledge/communication/virtual-communication/) narrows this channel rather than removing it: on video it becomes your face and your visible attention, and in writing it survives as register, which is why a three-word reply so often reads as irritation you never felt.

### 6. Say the awkward thing early

Bad news, a mistake you made, a deadline about to slip, a decision you disagree with — each of these gets harder and more expensive the longer it sits. Early, it is information. Late, it is a problem somebody else discovers. The mechanics are unglamorous: say what happened, say it plainly, skip the preamble, and bring what you propose to do about it. Most people know this and still do not do it, which is a useful signal in itself. When a habit is this obvious and still this hard, the obstacle is usually not communication. If you keep finding yourself sitting on things, it is worth knowing [where the real block sits](https://assessment.headwayskills.com/) before trying to solve it with better wording.

### 7. Argue the issue, not the person

Disagreement at work is not a failure of communication; avoiding it usually is. The distinction that keeps a disagreement productive is narrow and absolute: stay on the topic. "That estimate looks optimistic to me" is a conversation. "You are always optimistic about estimates" is a different conversation, and nobody wins it. Hear the other side out fully before taking a position, slow the exchange down [when the temperature rises](/knowledge/teamwork/how-to-handle-conflict-at-work/), and once the group decides, commit to the decision even if it was not yours. Being visibly loyal to a decision you argued against is one of the faster ways to become someone whose objections get taken seriously.

### 8. Talk about people as if they can hear you

The simplest test in this whole list: would you say it the same way if the person were standing behind you? What you say about absent colleagues travels, and it tells everyone present exactly what you would say about them. It is the same reason indirect routing corrodes so quickly — taking a complaint to a third person instead of to the person, or letting a habit of complaint settle into your default register. Neither reads as harmless to the people watching. The upside runs the same way and is badly underrated: specific credit, given to someone who is not in the room to hear it, gets remembered and costs nothing.

## Why a few of these are harder than they look

Notice which of the eight you would find hardest. It is rarely the one you understand least — none of the mechanics above are complicated — and far more often the one that asks something of you beyond knowing the words. Three things sit underneath this list.

**Communication**, treated as something you practice rather than something you are, has a compact core: a genuine wish to understand the other person, the main point first, brevity, adapting to whoever is receiving it, and a deliberate choice between talking and writing. Half the habits above are that core aimed at a particular target — the inbox, the meeting, the request. The other half are the situations the core has to survive: disagreement, a correction, an apology. Work on the core and all of them move together.

**Professional Behaviors** is what makes the phrase *at work* do something. The same sentence lands differently here, because a workplace runs on norms nobody hands you on day one — turning up on time to the meeting you called, keeping to the etiquette of a video call, knowing what belongs in a confidential file and what belongs in a group chat, speaking about absent people in a way you would repeat to their face. It also names the patterns that quietly cost people standing: staying passive when you have something to add, going indirect instead of direct, and letting complaint become a habit.

**Teamwork** decides whether any of this holds under pressure. Most of what you say at work goes to people you depend on and who depend on you, and trust between them accumulates less through what gets said than through what stays consistent: meaning what you say, doing what you committed to, disagreeing about substance while staying plainly on the person's side. It is also where the hardest version of habit seven lives, since telling a colleague their part is late — specifically, and without delay — is a communication problem only on the surface.

All three are behaviors rather than dispositions, which is the only reason a list like this is worth writing: the ones you have not built are ones nobody taught you, not ones you lack. They are also measured directly, sitting inside the **twelve workplace skills** the free Work Skills Test scores — so the three you have just read about are not something you have to assess by feel. You can see [how each of yours scores](https://assessment.headwayskills.com/) today.

Somewhere in the eight you probably ran a quiet sort — that one's fine, that one's occasional, that one brought a specific conversation to mind. The sorting is the useful part. A vague sense of being "not great at communication" can sit unexamined for years, where a named list of two or three habits is something you can actually work on.

Nothing on your list is fixed. These are behaviors, and behaviors answer to practice; you can build every one of them and still sound entirely like yourself, since the aim is not a different manner, only a clearer one. It does compound, though. The further into a career you go, the more of your work reaches people who know you mainly through what you write and say, and the more a gap between what you meant and what landed costs you. Which is an argument for starting while the stakes are still small — and the only thing left to settle is where.

## Working out where to start

Deciding where to start is much easier with something to look at. The Work Skills Test is a **free** self-assessment of the twelve workplace skills this article draws on, communication among them: you answer honestly about how you actually work, and you get a reading on where each skill sits today and which one would repay attention first. There is nothing to prepare beforehand. If two or three of the eight habits above are already on your mind, this is the quickest way to find out whether communication is genuinely the thing to practice, or whether something underneath it is doing the blocking.

**[Take the skills test](https://assessment.headwayskills.com/)**

*Seven minutes, on your own, whenever it suits you.*

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

What good communication at work actually looks like day to day - eight concrete habits, from leading with your point to raising the awkward thing early.

### Which Headway skill does this connect to?

This guide connects primarily to Communication. It also relates to Professional Behaviors, Teamwork.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/communication.md
- https://headwayskills.com/knowledge/professional-behaviors.md
- https://headwayskills.com/knowledge/teamwork.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/communication/communication-at-work/

Preferred summary:
"What good communication at work actually looks like day to day - eight concrete habits, from leading with your point to raising the awkward thing early."

## Change log

- 2026-07-07: Content collection version published.
