As a tech writer, it’s hard to tell how users get to your docs at all. They might be clicking on in-product help links, searching the web, or getting sent links from support. But you can get proactive about it too. Help users of your product get their questions answered by meeting them where they are—on social media sites like Twitter. You may already rely on marketing, sales, support, and search engines to bring users to your documentation, but social media is a direct option. You can tweet about anything from general topics that answer common user questions to drier topics that are important for people to know. Read on to learn how!
Security communicators can learn some lessons from national disaster communication. Motherboard interviewed Eli Jacks, chief of the National Weather Service’s Fire and Public Weather Services branch in The National Weather Service Wants You to Be Scared of This Blizzard, and Jacks shared many important elements of their communication strategy.
Several months ago, I saw Dr. Rosalind Picard give a talk on Affective Computing. I took notes and thought a lot about what she said but let my thoughts fester rather than follow up on them. Then last week, I read Emotional Design by Donald A. Norman, which reminded me of Dr. Picard’s work and my initial thoughts about affective computing.
There are two elements to affective computing:
- People interact with technology and devices as though it has a personality (and devices and interfaces without personalities can be distasteful to use).
- Cameras, wearables, and other technology can be used to determine the emotions and affective responses of a person using technology with surprising accuracy.
Websites and applications are personalized by tracking your browsing history, collecting advertising preferences, device usage, and demographic data. Using affective computing, they could soon be personalized by tracking your emotions.