Lead with the ask, separate observations from interpretations, write decisions down, and put status in writing while reserving meetings for disagreement. Four mechanical habits, all learnable, and together they account for most of what people mean by "good communicator."
Communication gets filed under soft skills, which makes it sound like a personality trait you either have or do not. It is not. The people described as easy to work with are almost always doing a small number of specific, copyable things — and the people described as difficult are usually missing the same handful.
Below: how to write an update people actually read, the observation-versus- interpretation distinction that makes disagreement survivable, when to write and when to meet, decision records, before-and-after rewrites, escalation without damage, and how to evidence any of this on a resume.
Key Takeaways
- The three-line update, and why most updates fail
- Observation versus interpretation — the disagreement fix
- A message-or-meeting decision table
- Decision logs: one minute each, and they end recurring arguments
- How to escalate without surprising your manager
The three-line update
Start Here
What changed, what is blocked, what is next. Most updates describe activity instead of change, which is why nobody reads past the first line.
A list of what you did is a timesheet. Your manager is reading to find out whether anything moved, whether anything needs them, and what to expect. Give them those three things and the update takes ninety seconds to write and fifteen seconds to read.
Changed: the migration finished for two of four regions. Blocked: waiting on vendor credentials for the third, chased twice, will escalate Thursday if nothing. Next: region four starts Monday regardless.
If nothing changed, say so in one line rather than manufacturing content. "No movement this week — still blocked on the same credentials" is a complete and useful update, and it makes the blocker visible for a second time, which is exactly the point.
Send it on a fixed cadence, twice a week rather than daily. Predictability is what makes an update valuable: a manager who knows something arrives every Monday and Thursday stops asking, which is the outcome you actually want.
This is also the cheapest available fix for a micromanaging manager. Constant checking is usually anxiety about visibility rather than doubt about your work, and reliable proactive reporting removes the reason for it. Most people respond to being managed too closely by pulling away, which reduces visibility and makes the behaviour worse — supplying more information than is asked for, before it is asked for, inverts that loop within about a month.
Observation versus interpretation
Key Takeaway
An observation is checkable. An interpretation is arguable. Nearly every conversation that goes badly at work started as the second when it could have been the first.
"The report arrived after the deadline twice this month" is an observation. "You do not take deadlines seriously" is an interpretation about character, and the only available response to it is defence. Same underlying concern, completely different conversation.
The pattern generalizes. State what happened, state the effect on the work, then ask rather than conclude. "When the spec changed after sign-off, I had to redo the analysis and it pushed my week to Saturday — can we agree a cut-off?" That is three facts and a request, and none of them requires anybody to accept a judgment about themselves.
This matters most upward. Disagreeing with someone senior is survivable when you bring something they can verify and a proposal they can accept or reject on merits. It becomes political the moment it is your assessment against theirs with no checkable facts in between.
One honest limit: this technique makes disagreement safer, not safe. In an organization where raising problems is reliably punished, careful phrasing does not fix a structural issue — it just buys you a slightly better version of a conversation you should probably be having somewhere else.
Message or meeting?
Rule of Thumb
Meetings for disagreement and feedback. Writing for everything else. Most organizations have this exactly backwards, which is why calendars fill and nothing is recorded.
| Situation | Which | Why |
|---|---|---|
| Status and progress | Write | Readable later; no scheduling cost |
| A decision with disagreement | Meet | Needs real back-and-forth |
| Feedback that may land badly | Meet | Tone does not survive text |
| A request with a deadline | Write | Creates a record of the ask |
| Anything sensitive or personal | Meet | Then confirm in writing after |
| Recurring information sharing | Write | A standing meeting for this is waste |
The last row is where most calendar time hides. A weekly meeting whose only function is people taking turns to say what they did is a written update wearing an hour of everyone's time. Replacing one of those gives a ten-person team back roughly forty hours a quarter.
Before and after: messages rewritten
Quick Win
Each rewrite moves the ask to the front and swaps an interpretation for an observation. Both changes take seconds and change the response you get.
A request buried in context
Before: Hi — hope you had a good weekend. So we have been working through the Q3 numbers and there have been a few complications with the regional splits, and the finance team mentioned they may need to revisit the allocation methodology, which has knock-on effects for the deck. Anyway, I was wondering whether you might have any thoughts on this?
After: I need a decision by Thursday on whether we use the old or new allocation method for the Q3 deck. Context below — happy to recommend if useful.
Raising a problem with a colleague
Before: I feel like the design team is not really taking our deadlines seriously and it is making it impossible for us to plan anything properly.
After: The last three handovers arrived two to four days after the agreed date, which pushed our QA into the release weekend each time. Could we look at whether the dates are realistic, or whether we need to stage the handover differently?
A status update
Before: This week I worked on the migration, attended the planning sessions, did some analysis for the finance request, and continued working through the backlog items.
After: Changed: migration live in 2 of 4 regions. Blocked: vendor credentials for region 3, chased twice, escalating Thursday. Next: region 4 starts Monday regardless.
Writing habits show up on a resume too. Documentation you wrote and meetings you replaced are provable bullets. Check yours parses — free, no signup.
Run a free ATS resume check →Writing decisions down
Pro Tip
One minute per entry, and it ends the recurring conversation where a settled question quietly reopens three weeks later.
A decision log needs four fields: the date, the decision, who agreed, and what it depended on. The fourth is the one people omit and the one that matters — decisions get reopened when circumstances change, and knowing what a choice assumed tells you whether it should be revisited or defended.
Keep it somewhere findable rather than in a chat thread. Decisions made in chat are effectively invisible within a fortnight, and on free tiers with limited history they are genuinely gone. A single page anyone can search is enough — the tooling matters far less than the habit.
When a settled question reopens, quote the entry and state the cost of changing now. "We can, and it moves the launch by three weeks." Attaching a price to reversals is the only thing that reliably reduces them, and it converts an argument about who remembers what into a straightforward trade-off.
Escalating without damage
Watch Out
The damage in escalation is almost never the escalation itself. It is the surprise.
Tell your manager first, with what you plan to say. "I want to raise the vendor delay at Thursday's steering group — I will say we are eight days behind and need a decision on the fallback. Wanted you to know before I do." This costs one message and preserves the relationship almost entirely.
Escalate on facts and impact, not on frustration. Three dated examples, the effect on the work, and a specific requested outcome. A general complaint gives the room nothing to act on and reads as venting, which is the reading you least want.
Follow up in writing afterward with what was discussed and agreed. This is the step people skip, and it is what turns an escalation from an event into a record — which matters if the same issue is still live two months later.
Where the problem is your manager, escalation works differently and the relationship calculus changes. That situation has its own considerations, covered in the guide on dealing with a difficult boss .
Evidencing this on a resume
Common Mistake
"Excellent communicator" appears on a large share of resumes, matches no search, and persuades nobody. Name the artifact instead.
Communication is one of the easiest qualities to demonstrate and one of the most commonly asserted. The demonstrable version names something that exists: documentation you wrote, a meeting cadence you replaced, an onboarding process you built, a decision log you maintained, a presentation to a specific audience of a specific size.
"Replaced two weekly status calls with written updates for a 12-person team, cutting recurring meeting time 40%" is a communication bullet. "Strong written and verbal communication skills" is a claim that costs a line and returns nothing.
One mechanical note if you are applying. Workday builds a candidate profile from the flat text of your file and infers experience from date ranges; Greenhouse assembles a structured profile from clean single-column PDFs and takes nothing usable from graphics; Lever and iCIMS behave the same. Your well-written bullets have to survive extraction to be read at all, so keep the layout single-column and verify it before applying.
Where these habits need adjusting
Reality Check
The mechanics are general; the calibration is not. Four situations where applying them unchanged produces the wrong result.
Distributed and async teams
Everything here matters more, and one thing changes: assume good intent about tone. A curt message almost always means someone was busy rather than annoyed, and reading emotion into text is where remote teams most reliably go wrong. When you genuinely cannot tell, ask rather than infer — one sentence resolves what a week of assumption will not.
Cross-cultural teams
Directness, silence, and disagreement carry different meanings across cultures. Silence after a proposal may signal respect, disagreement, or a wait for the senior person to speak first. Reading it through one cultural default and acting confidently on that reading is a communication failure that feels like decisiveness.
Neurodivergent colleagues
Explicit beats implied for everyone and is genuinely necessary for some. State expectations, write decisions down, say directly what you need rather than hinting, and do not treat eye contact or expressive warmth as a measure of engagement. These are the same habits recommended above, applied without exception.
Highly regulated environments
In healthcare, finance, legal, and safety-critical work, written records carry formal weight and retention requirements. Casual channels are frequently the wrong place for anything decision-related. Learn which system of record your organization expects, and use it — a decision logged in the wrong place can be worse than one not logged at all.
Bottom line
Final Word
Ask first, observation not interpretation, write status and meet for disagreement, log decisions, and warn your manager before you escalate.
None of this requires being naturally articulate, which is the useful part. The colleagues everyone finds easy to work with are running a small set of mechanical habits — putting the ask first, saying what happened rather than what it meant, and leaving a record. All five are copyable this week.
Start with the three-line update. Send one on Monday and one on Thursday for a month and watch how much less often you get asked where things are — which is the clearest possible measure that it worked.
Turn communication habits into resume evidence
Documentation you wrote and meetings you replaced are provable bullets. See exactly what an applicant tracking system extracts from your file — free, no signup.
Run the Free ATS Resume CheckAlso useful: quantifying your achievements · remote collaboration tools
Frequently asked questions
Three lines: what changed, what is blocked, what happens next. Most updates fail because they describe activity rather than change — a list of what you did is a timesheet, not an update. If nothing changed, say that in one line rather than padding it.
Separate the observation from the interpretation, and state what you would do instead. "The timeline assumes two weeks for review, and the last three took four" gives them something to check. "I don't think this is realistic" gives them something to defend against.
When it involves a decision with disagreement, feedback that could land badly, or anything requiring genuine back-and-forth. Status, requests, and information should be written. The default in most organizations is inverted, which is why calendars fill and nothing gets recorded.
Put the ask in the first sentence and the context underneath. Most workplace writing buries the request under three paragraphs of background, so the reader has to reach the end to find out what is wanted. Lead with what you need and by when.
A running record of what was decided, when, by whom, and on what basis. It takes a minute per entry and it ends the recurring conversation where a settled question reopens. In distributed teams it is close to essential, because there is no corridor where people remember together.
Tell your manager you are escalating and why, before you do it. "I want to raise this with the steering group on Thursday — here is what I plan to say" preserves the relationship. Surprising your manager in a room with their own manager is the version that causes lasting damage.
Yes, for a different reason than you think. Written records mostly get read later, by someone joining, someone auditing a decision, or you defending one. The value is not readership at the time; it is that the record exists when the question resurfaces months on.
By naming artifacts and outcomes, never adjectives. "Excellent communicator" matches no search and persuades nobody. "Wrote the onboarding documentation used by every new hire in a 60-person department" shows the same quality with something a reader can picture.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.