Hasty Treat - How To Email Busy People

Episode Summary

Executive Summary: The episode offers practical advice for emailing busy people so your message gets opened, understood, and replied to. Wes and Scott emphasize clarity, brevity, scannability, respectful tone, and strong subject lines, with examples of what works and what fails. They also note that good email etiquette reduces friction for both the sender and recipient.

Main Topics: Subject lines that create immediate context: Use subject lines that clearly identify the purpose, urgency, or topic of the email so busy recipients can decide whether and when to open it. Keep the body short, clear, and scannable: Emails should get to the point quickly, use short paragraphs, and structure information so readers can parse it in seconds. Enumerate multiple questions or requests: When an email contains multiple asks, number them so the recipient can answer in-line and avoid missing items. Avoid gimmicks and manipulative language: Excessive hype, clickbait, emojis, fake urgency, and rude follow-ups make people less likely to respond. Be respectful and assume best intentions: Tone matters: rude, accusatory, or demanding emails create resistance, while polite wording encourages help and collaboration. Email thread management and signature hygiene: Continue the same thread for the same topic, and keep signatures minimal to avoid clutter and attachment/search issues.

Key Arguments: Busy people are more likely to respond when they can instantly understand the email’s purpose from the subject line and first few lines. Long, meandering emails lose attention; put the ask up front and remove unnecessary life stories or background. Numbered lists make complex emails easier to answer because the recipient can reply point-by-point. Overly clever, salesy, or insulting language harms trust and makes the email feel spammy or annoying. Emails should be easy to scan, with bolded sections, headings, or a TL;DR when needed. Keeping the same email thread preserves context and helps both sides search and reference earlier messages. Minimal signatures are better than image-heavy ones because they reduce clutter and attachment/search problems.

Data Points: Sponsor coupon: tasty treat - Sentry promo code offered for two months free Free time offered: 2 months - Using the Sentry coupon 'tasty treat' gives two months free Conference/year example: 2019 - Used as an example of a subject line that includes timing/context Example email traffic: 10,000 visits per day - Used as an example of a quantified ask for an affiliate program Number of questions suggested: 2-3 or a small set - Implied best practice is to enumerate a few questions, not send 10 in one email Company scale mention: thousands of engineers - Referenced in discussing Google recruiting emails sent broadly

Pivotal Quotes: "The speed at which I reply is generally due to how easy it is to parse the information and the ask that you have." — Wes: Explaining why concise, clear emails get faster responses "Don't ask a question to ask a question." — Scott: Critiquing vague opener messages like 'Hey' or 'Can I ask you something?' "Don't use gimmicks, things like that." — Wes: Rejecting emojis, fake urgency, and clickbait-style subject lines

Implications: Listeners are encouraged to treat email as a design problem: reduce cognitive load, make the ask obvious, and preserve context. In professional communication, clarity and respect will outperform cleverness and hype.