Communications

Definitions

Empathy
The ability to understand and share the feelings of another.
Click rate
(No. of clicks) / (No. of emails sent - No. of emails bounced)
Open rate
(No. of unique opens) / (No. of emails sent - No. of emails bounced)
Click-to-Open rate
(Emails clicked) / (Emails opened)

Goals

Nothing here!

Questions

How do we communicate to users?
It's probably too general, but it's a good start.
What's the key message? What's the desired headline (8 words or fewer) we want to create? What's the photo op you want?
Like with general communication plans and campaigns, start with the end in mind and be clear what you're trying to convey.
What are our metrics for our communication campaigns/efforts?
If it's not measurable, it doesn't exist!
What are our open and click rates for email campaigns?
Note: email tracking isn't entirely
How are allocating and differentiating our relationship building and revenue-generating communications?
Different communication objectives need different strategies. Sometimes we want to tell stories, build a brand. Other times we want to convert and close sales.
How will life be better if the customer gets their hands on our product?
Sell the value to the user, not the product. Like what every textbook tries to teach, Steve Jobs sold the value of having 1,000 songs in your pocket, not 8GB of hard disk space on the iPod.
What are the user personas we're targeting?
Ought to be aligned with personas from UX research and product strategy, but might sometimes differ.
What's our crisis communications plan?
In a crisis you'd want to quickly communicate. To do so, you'll need a plan, you want to put out reliable information, and you want people to trust that you know your shit.
How do we use Android/iOS notifications, dialogs, and which screens?
Notifications and messages are essential to communications. Chances are they won't read your emails, but more likely they will read notifications. Then again, you wouldn't want that annoying high-pitched "shopee!" sound.

Alarm Bells

They say...
Why I'd be scared
Communications contain words that imply the user needs to "suck it up" for downtime, errors, or unforeseen circumstances.
Too often system owners think they're beyond reproach and as long as they tried their best, users need to accept whatever that happens. The least you can do is not to sound like that.
Communications contain "canned" empathy phrases like "I understand how this can be upsetting to you...".
People can tell it comes across as non-genuine, facetious. Worse if the contents are totally at odds with what your words meant.
We communicate what we do or what people should do.
Focus should always be on the user or customer getting value. How will life be better if the customer gets their hands on our product?
We communicate slowly and at our own pace (read: ultra slow), especially for high severity issues like cybersecurity breaches, data mishandling.
You want to prevent speculation, users getting confused, news getting out where you can't control the narrative, and damage to your brand, reputation, or operations.
Giving too little detail.
Giving too little conveys a lack of openness and sincerity. This is often tempting, but you won't be building any trust for sure.
Too much jargon!
It's easy to slip into spamming technical terms and jargon. Few would take the time to read those. Yet fewer would understand and appreciate it.

Dealbreakers

Symptom
Why I'd be scared
We keep trying to sell what we do, not what value we bring.
Covered above.
We're heavy handed and use a "we-know-better" tone.
Covered above.
We don't communicate quickly when we need to.
People lose trust in us.
We spam people with tons of stuff we think we need them to know.
Our message won't get through if we need it to.
© 2024-2025 Zixian Chen. All views expressed here are solely mine.