Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Communication E-mail Best Practices
Search
Sperasoft
June 30, 2013
Technology
80
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Communication E-mail Best Practices
Sperasoft workshop on Best Practices of E-mail Communication.
Sperasoft
June 30, 2013
More Decks by Sperasoft
See All by Sperasoft
Code and Memory Optimisation Tricks
sperasoft
0
130
The Theory of Relational Databases
sperasoft
0
130
Automated Layout testing using Galen framework
sperasoft
0
130
Sperasoft talks: Android Security Threats
sperasoft
0
300
JPoint 2015: Java technology conference overview
sperasoft
0
85
RxJava: Functional Reactive Programming on Android
sperasoft
0
290
Effective Мeetings
sperasoft
0
170
Unreal Engine 4 Introduction
sperasoft
0
270
JIRA Development
sperasoft
0
280
Other Decks in Technology
See All in Technology
分析の民主化を支えるメタデータ整備の実践
kakehashi
PRO
4
1.4k
遠藤な_めぐろLT #38 「社内のAI活用推進」@麻布台_20261009
endonanana
0
130
Metadata - Section 1: HTML Basics
mohab1
0
120
スキマバイトという雇用形態は存在しないので、雇用期間1日のアルバイト契約を事業者とワーカーが結ぶ手続きを支えるのがタイミーなんです
akitoshiga
0
200
Post AI時代のリファクタリング実践記 / Refactoring in the post AI era
kaminashi
1
230
JAWS-UGグッズ職人仕事の流儀
kentapapa
0
100
LambdaWebFunctionsを試してみた / exploring-lambda-web-functions
koukihosaka
1
340
Browser Spec: Testing Hotwire with Ruby
takahashim
1
120
AIがコードを書く時代に、エンジニアは何で自分の価値を証明するのか / In an era where AI writes code how do engineers prove their value
carta_engineering
3
1.1k
Claude の新機能を、 出た日に触って社内に届けるまで
rfdnxbro
1
180
Claude Code本は、どのように執筆チームで書かれたか
oikon48
1
380
ブラウザとサーバーから考えるAI時代のフロントエンド監視
shogo4131
3
940
Featured
See All Featured
Making the Leap to Tech Lead
cromwellryan
135
10k
Lightning talk: Run Django tests with GitHub Actions
sabderemane
0
300
Designing Powerful Visuals for Engaging Learning
tmiket
1
610
Pawsitive SEO: Lessons from My Dog (and Many Mistakes) on Thriving as a Consultant in the Age of AI
davidcarrasco
0
260
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
508
140k
The Language of Interfaces
destraynor
162
27k
New Earth Scene 8
popppiees
4
2.7k
Into the Great Unknown - MozCon
thekraken
41
2.8k
Technical Leadership for Architectural Decision Making
baasie
3
600
Exploring anti-patterns in Rails
aemeredith
4
540
How to audit for AI Accessibility on your Front & Back End
davetheseo
0
600
VelocityConf: Rendering Performance Case Studies
addyosmani
331
25k
Transcript
Communication & E-Mail Best Practices
General Politeness ! Always be polite ! Keep
emotions under control ! Think twice prior to communication ! Use words “please” and “would”
Acknowledge & Respond • Acknowledge all e-mails you receive •
Need time? - use “I will get back to you ASAP!”
Keep Paragraphs Short • Keep paragraphs short within 5 lines
• Get straight to the point. No long intros! • Use text blocks - keep ideas focused
Keep It Clean • Avoid fonts smaller than 10 or
larger than 12 points • Small fonts are difficult to read • Large fonts require extensive scrolling • Use spaces & breaks to separate blocks of text
ü Use as few words as possible ü Pay attention to sentence
structure ü Your point must be clear and direct ü Use only formal language, no slang ü Always use Spell Checker Concise. No Jargon. Check Spelling.
Use Formatting to Emphasize ! Use bold & underline
to emphasize ! Use bullets and tables to attract attention ! Organize text using lists and tables ! Always use corporate message templates
Create an Effective Subject Line Remember to include: • "Action
Requested“ or "Response Requested" • "FYI" or "Read Only" • Project name • Required action • The due date
ü Ask only one question per your e-mail main subject ü Avoid
mixing several questions in one e-mail ü Use separate e-mails for separate issues Ask One Question Only!
Don’t Forget! • Always include a signature line • Use
mailing lists • Use the CC & BCC lines • Add attachments • Re-read one more time
Always Follow Up No reply? – FOLLOW UP! No action?
– FOLLOW UP! Need update? – FOLLOW UP!