Growing Your Communication

Communication is being understood the first time, written and verbal. Status that says done, next, and blocked; explanations that pre-empt the reader’s “why?”. It is not about talking more. It is about the reader finishing your update knowing exactly where things stand and what happens next, without a single follow-up question.

This page is how you move yourself up one rung on it. It is a mirror, not a scorecard: find the row just above where you sit, and put your reps there. The standard itself lives in Communication and the Pyramid Principle; this is the path through them.

Where you are now#

Find the line that matches the updates you actually sent last week.

Level	The tell
Intern	Your updates say “making progress” and narrate what you are doing.
Junior	Your updates say done, next, blocked, and you walk the approach before coding.
Mid	You surface material changes immediately and explain the tradeoffs.
Senior	You write so the reader gets it the first time and reframe to the real point.
Lead	You set the team’s communication norms.

What moves you up#

The whole spoke climbs on one shift: write for the reader’s decision, not for your own record of effort.

Lead with the answer. The reader wants the conclusion first, then the support, not a chronological build-up to it. “We will miss Friday, here is why and the new date” beats three paragraphs that arrive there eventually. See the Pyramid Principle.
A status is a state and a number, not an effort. “Been deep in the migration” says nothing. “12 of 15 suppliers migrated, the last 3 need signed terms” says everything. Effort is not progress.
Push status before you are asked. If the reader learns what is happening because they chased you, the update already failed. Surface the material change in the turn it happens, batched onto natural boundaries so you inform without interrupting. See Operating with Clarity.
A blocker without a proposal is a complaint. Say what is blocked, what you recommend, and what you need from whom by when. That turns a problem you are handing back into a decision someone can make.

The habits that keep you stuck#

Everyone has sent the update that felt thorough and told the reader nothing. It usually reads fine, which is why it survives. Catch yourself here:

Bad: “Made good progress on the onboarding funnel today, spent a lot of time on the email step, still working through some issues, will keep pushing.”

Good: “Onboarding funnel: verification step is live and converting at 71%. Blocked on the SMS provider’s rate limit for the last 8% of signups. I want to switch to email-only for that segment; need a yes from you by Thursday or it slips a week.”

The tells that your update is padding:

Effort words standing in for state: “deep in”, “working through”, “making good progress.”
The reader has to ask “why?” to follow it, which means you dropped the reason.
The material change is buried three paragraphs down, or arrives only when asked.
A blocker with no path: what is stuck, but not what you recommend or what you need.

The reps that level it up#

Move a rung by writing the next row’s update before it feels natural, then close the gap with review:

Take the update others actually rely on and write it, then have someone rewrite it with you until no one has to ask “why?”. Do this on a real recurring report, not a practice one.
Walk your approach before you code it. Explaining the plan out loud forces the gaps into the open and builds the habit of being understood the first time.
Rewrite one of your own updates answer-first. Take something you sent chronologically and re-cut it so the conclusion leads. You will see how much was throat-clearing.
State every blocker as blocked + recommendation + ask. Practice it until the shape is automatic, because it is the difference between raising a problem and handing one back.

The one question#

Before you send anything, ask: could someone who was in none of my conversations read this and know exactly where things stand and what happens next?

If yes, it is done. If they would have to ask you a question to act on it, that question is the thing to answer before you hit send.