Boosting Empathic Bandwidth
Comments: 5 - Date: January 31st, 2008 - By: Schwern - Categories: empathy
Table of contents for Text Lacks Empathy
- Text Lacks Empathy
- We Don’t Write, We Speak With Our Fingers
- Emotional Projection
- Boosting Empathic Bandwidth
Tags:empathy, tools
With all this talk on the blog about all the issues of textual communication the answer would seem to be to avoid text all together. That it’s just doomed and try to do what you can over the phone or face-to-face. I say no, text is not doomed. Text has issues we don’t always appreciate, and that causes problems, but text itself can be used for empathic communications.
When you’re faced with a touchy situation, or one that might be ripe with potential miscommunication like a geek talking to a business guy, it’s often a good idea to boost the emotional bandwidth. Rely more on all that implicit communication we do when speaking rather than having to remember to add it back in explicitly to text.
Here’s some simple rules of thumb for how to boost your bandwidth, from the least to most effective.
- Face-to-face is better than remote.
- Video is better than not.
- Audio is better than text.
- Real-time is better than delayed communications.
- Private is better than public.
- Personal relationship is better than not.
They are, of course, generalizations and each has specific situations where the reverse is true, but it’s a handy set of tools. Each of these is a whole topic in and of itself and I’ll discuss each of them in detail later.
bonus multiplier!
Originally I was going to list out communication technologies ordered from least to most empathic, but then I realized it’s more interesting to examine the characteristics of each and what makes them more or less empathic. Knowing the rules of thumb allows you to combine them. For example, both IM and IRC are real-time but IM is typically private whereas IRC you’re usually talking in a public channel.
The ordering of significance gets a little fuzzy at the low end, and it’s all arguable. Details aside, it does allow one to evaluate different communications strategies. You now have a framework, which you’re free to adjust to suit. For example, I can say that it’s probably better to have a phone call with somebody you know (private, audio, personal, real-time) then to talk with a stranger in the middle of the hallway (face-to-face, video, audio, real-time).
mailing lists are the least empathic
The least empathic form of communication would be mailing lists and web comments. They have none of the above characteristics. They are remote, textual, delayed, public and impersonal (not everybody knows each other). This might explain all the flame wars.
If you’re in a touchy situation, or you find email just isn’t the job done, consider applying one of the above. For example, I will often reply with private email to someone I’m having an argument with on a mailing list if there seems to be a misunderstanding taking it from public to private. Or find them on IM or IRC taking it from delayed to real-time.
face-to-face isn’t important, but it is handy
You’re probably wondering why I put face-to-face dead last, it would seem to be the most empathic. And it would, if I hadn’t already extracted out the critical elements already: video, audio and real-time. Once those are accounted for, what’s left? Smell? Touch is powerful, but complicated and we usually don’t employ it. There are some intangibles, like “punching distance” which another post, but for the most part being face-to-face with someone isn’t all that much better than a good video chat.
I will admit, I do have a bias at work putting face-to-face so low. So far I’ve been saying mostly negative things about textual communications. The seeming conclusion that the best way to communicate is to talk face-to-face and Internet communication is just doomed. Not so, we can make Internet comms just as clear and emotional as face-to-face. I want to lay out and examine the issues of textual communication. Then they can be examined and solved. I’ve got a whole Internet full of rampant problem solvers who just need to be made aware of the problem.
This is not to say face-to-face isn’t a simple and powerful tool when available. In an office setting I found it very useful to get up off my ass and walk over to talk with somebody when confusion was evident bringing every empathic communication element to bear. What might have taken hours to resolve over email would be done in five minutes.




Pingback by Khaos » Blog Archive » Smells A Bit Odd... - 1 February 2008 @ 14:40
[…] was reading the most recent post on geek2geek. In it Schwern discusses face-to-face communication and suggests that video […]
Pingback by Khaos » Blog Archive » When We Touch - 1 February 2008 @ 15:45
[…] still thinking about Schwern’s post and the following […]
Comment by Adrian Howard - 16 February 2008 @ 22:02
I think there’s quite a bit more to face-to-face communications when you’re working in groups. There’s body language, ambient noise (or lack there of). Hearing that guy across the room quietly swearing at the screen for five minutes at time without asking for help. Etc. There’s a lot of continuous/ambient communication that you don’t get from having a cam up in a corner of the screen and a disembodied voice.
There’s a *whole* bunch of CSCW research that shows productivity drops when you have distributed teams. Excuse me while I dig out some references from a post I made last year on the XP list…
There’s also a fair bit of research out there on software development specifically. For example:
“Teams in these warrooms showed a doubling of productivity.”
“One key finding is that distributed work items appear to take about two and one-half times as long to complete as similar items where all the work is
colocated”
“Our findings reveal that: software developers have different types of coordination needs; coordination across sites is more challenging than within a site; team knowledge helps members coordinate, but more so when they are separated by geographic distance; and the effect of different types of team knowledge on coordination effectiveness differs between co-located and geographically dispersed collaborators.”
“Our results show that, compared to same-site work, cross-site work takes much longer and requires more people for work of equal size and complexity. We also report a strong relationship between delay in cross-site work and the degree to which remote colleagues are perceived to help out when workloads are heavy”
“Based on the empirical evidence, we have constructed a model of how remote communication and knowledge management, cultural diversity and time differences negatively impact requirements gathering, negotiations and specifications. Findings reveal that aspects such as a lack of a common understanding of requirements, together with a reduced awareness of a working local context, a trust level and an ability to share work artefacts significantly challenge the effective collaboration of remote stakeholders in negotiating a set of requirements that satisfies geographically distributed customers”
I could go on
Now - of course - none of this means that you can’t develop good products with distributed teams. What it does seem to be saying, and this matches my experiences, is that developing with distributed teams is harder.
Comment by Adrian Howard - 16 February 2008 @ 22:05
And the links from that last post that seem to have vanished after I hit submit (preview anybody?) were:
* http://possibility.com/Misc/p339-teasley.pdf
* http://doi.ieeecomputersociety.org/10.1109/TSE.2003.1205177
* http://www.cs.cmu.edu/~kraut/RKraut.site.files/articles/Espinosa07-TeamKnowledge&Coordination.pdf
* http://tinyurl.com/yqs5dp
Comment by Schwern - 17 February 2008 @ 18:35
Preview added, by your command.
Leave a comment