Communication
How to Ask for Help Without Sounding Helpless (The 3-Part Ask)
Three parts, in order. Context, what you tried, the specific ask. Stop making your manager do two jobs.
Read the piece →Topic
Communication
Email/Slack tone, response times, escalation, and writing like a professional.
Clear writing is leverage. It reduces rework, short-circuits drama, and makes you look — to borrow the phrase — “ahead of the problem.” The craft is mostly subtraction: fewer words, one idea per paragraph, the point at the top rather than the bottom. A good professional email is closer to a memo than a letter.
Channel choice matters more than most people think. Slack is for the quick ping, the live thread, the thing that rots if it sits overnight. Email is for the decision, the paper trail, the message that needs to survive being forwarded. A doc is for anything over three paragraphs or anything that needs a comment thread. Picking the wrong channel is how small misunderstandings turn into meetings.
Tone is the invisible variable. You don’t have to be warm, but you can’t be curt by accident. Read everything back once before you send it — imagine it landing in someone’s inbox after a hard morning. The extra ten seconds is the cheapest reputation insurance you’ll ever buy.
Start here
The one to read first.
All 29 posts in communication
-
The coffee-chat script that isn't creepy
Most early-career coffee-chat requests miss because they're either too vague or trying too hard. Here's the script that works — and the one that doesn't.
-
A reader asks: my coworkers never use video — should I?
Camera-on vs. camera-off feels like a small question. It isn't. Here's how to read a team's unspoken norm and match it without losing yourself.
-
Saying no without saying 'no'
Saying no in an office isn't about courage. It's about the five or six phrases that say no while keeping the working relationship intact.
-
The 3-line Slack that gets faster answers
A simple three-line Slack format that gets you an answer in minutes instead of hours — and makes your colleagues glad you pinged them.
-
How to write a project brief your PM doesn't rewrite
If your PM rewrites your briefs, the issue isn't writing quality. It's structure. A six-line template and the two sentences that tend to break.
-
A reader asks: I'm the only non-native English speaker on my team
Being the only non-native speaker on a team is isolating in a specific way. Here's what actually helps — and the moves that look like help but make it worse.
-
When to Slack vs. Email: The Junior's Decision Tree
Stop guessing which app to use. A simple framework for choosing between instant messaging and formal email.
-
The pronunciation and names trick: respect that costs nothing
If you can learn software acronyms, you can learn people's names. Getting this right is a tiny effort with an outsized signal.
-
The email signature nobody notices (until they do)
Most early-career signatures are too long, too formal, or too apologetic. Here's what a clean one looks like, and why a partner once remembered mine.
-
A reader asks: is there a right way to push back on a deadline?
Pushback done badly sounds like an excuse. Pushback done well sounds like a request for a tradeoff. Here's the wording most first-year employees are missing.
-
The 'One Thank You' Message That Strengthens Your Network
How to send a professional thank you message that actually builds a relationship instead of just checking a box.
-
First job defaults: the OS checklist that keeps you steady
Install these twelve reliable defaults in your first job so the noise is manageable and your manager stops asking what you did this week.
-
How to give updates like a pro: the status OS template
Status updates are the single most visible thing you do at work. Here's the format that makes yours land instead of getting skimmed.
-
Status update template: the six-line update that buys you trust
A short weekly status update you can send in Slack or email that prevents surprises and keeps you aligned.
-
How to ask for help politely in email (without sounding helpless)
Email help requests that don't get responses usually share the same flaws. Here's the format that gets a faster yes without making you look like you didn't try.
-
How to ask questions at work (script and examples)
Exact wording for asking questions without sounding clueless — and without wasting anyone's time.
-
The secret to good 1:1 meetings (how to make every session count)
A practical 1:1 system: agenda, scripts, and follow-ups that build trust in your first 90 days.
-
Assume positive intent until the receipts pile up
A practical workplace communication rule for new grads: assume positive intent at first, but change your behavior when the pattern is clear.
-
Gen Z at work: the real friction (and why I'm optimistic)
A fair look at the friction points — and the systems that help new grads succeed in their first 90 days.
-
The one-line ask that gets answers before lunch
How new grads can craft requests that busy colleagues actually respond to fast, by leading with the decision and deadline every time.
-
Office etiquette: the quiet signal that shapes your early career
A first-job lesson: your professionalism is a system — attire, punctuality, and how you show up in the room (and the chat).
-
How to present work: the show-your-thinking method
Walking a room through your work is a distinct skill from doing the work. Here's the format that earns credibility instead of losing it.
-
What is an executive summary? (and how to write one)
A simple structure for a one-page summary that leaders will actually read.
-
A simple rule for CC'ing people (so you don't start a war)
Learn how to use the CC field to clarify ownership without accidentally triggering a corporate power struggle.
-
How to ask for help without sounding helpless
A simple 3-part framework for interns learning how to ask for help at work without creating extra work for everyone else.
-
The first-week coffee chat: how to actually be useful
Stop trying to be interesting in your first-week networking calls and start gathering the intel you need to survive.
-
Should you send an email or a Slack?
A quick decision guide for professional communication: urgency, audience, paper trail, and the part nobody tells you about — which Slack channel.
-
Stakeholder map: who actually influences your first wins
New hires need a stakeholder map that tracks reviewers, blockers, and sponsors, because org charts only show titles.
This topic maps to Chapter 7 — Communication that lands of the book. See the full chapter →