A Plea for Empathetic Communication
It's impossible to over-communicate
Sounds a bit strong, but if you think through your real-world experiences, this shouldn't surprise anyone. No matter how hard you try, your message will be missed by someone ...
Problem: It's all their fault!
Rely on Web 2.0, and ...- ... they won't subscribe to the RSS feed; they don't understand the concept, and have no other information sources that supply feeds
- ... they won't sign up for the email notifications; that feature is hidden, no one told them about it
- ... they won't read / browse / search the wiki; there are too many unfinished pages in there, and they don't consider it reliable
- ... they can't find it using intranet search - they don't know where this feature is located. And even if they did, the results aren't as targeted and "right-on" as Google
- ... they didn't read the email, it got lost in their inbox with 100 other new messages today
- ... they didn't see, therefore, didn't read the attachment
- ... they did not check their voice mail
- You are having a face to face conversation, but it's not sinking in because they are checking their Blackberry and thinking about the currently unfolding interruption ...
Problem: It's all your fault!
If you can get them to the electronic content, you still have to create content that actually communicates the correct information. Even if they are capable of subscribing to RSS feeds, or opening a document attachment - if the content does not convey with clarity, they won't catch your drift. Worse yet - if the first one or two samples don't convey anything, they will stop listening to everything. Solution #1: Practice practice practice - The only way to get better at anything is to keep iterating.Observation: It's no one's fault - it just is ...
Think about it - don't you receive messages in your inbox that are not clear / difficult to read, or hear about things after the fact or through the grapevine? And don't you glance at your Blackberry during meetings? When you set your phone to vibrate, you avoid distracting others (good!) but you are invariably distracting yourself (who just called ....?) Fact is, we are all swimming in a sea of information, bombarded with messages from all sides - and we're bombarding others as well. A little humility and a lot of empahty go a long way ...- Get feedback - if your medium or your content are not effective, find out why. Ask your intended audience what works best for them. Majority rules, so if you have a few email holdouts that don't know how to set up an RSS reader, do it for them. Better yet, do it with them - and show them what else they can subscribe to!
- Understand what the current corporate / organizational / local culture is, and play to that. You don't have to accept the status quo - but don't tilt at windmills just because wiki is a cool sounding word that would look good on your resume. Introduce change judiciously, and don't let it override the goal at hand - you need to get the status of this project updated!
- Never undrestimate the power of face time. When you craft a beautiful, concise, complete summary of the upcoming meeting, and someone still insists on calling you up and talking about it - don't look on this with disdain - it's an opportunity! What was it about the email / document that was incomplete? Was I not clear? Also, since most recipients of project updates are getting them for a reason (stakeholders!!), it's a great opportunity to make sure they get the big picture, understand the original objectives, and are still in support of the initiative.
- Projects end, but relationshps go on. It's always good practice to improve your communications and connections with the various technology and business process teams, in and out of the company. These is always a "next time", and next time could be that much easier if you are consistently building your foundation of clarity, openness, completeness.
- I have nothing to say and I am saying it and that is poetry (April 6, 2005)
- eMail on Blackberry Changes Definition of Acceptable eMail (September 19, 2005)
- Gee, this social network - presence - IM - knowledge management - collaboration stuff really works (September 25, 2005)
- Success, Failure, and Insights after 12 Months of Internal Web 2.0 (March 10, 2008)
- Optimizing the Wrong Part of Knowledge Management (March 16, 2008)
- RSS: Underappreciated Web 2.0 in the Enterprise (May 1, 2008)
- Opportunistic Insights from the RSS Stream (June 5, 2008)
Technorati Tags: blackberry, blog, documentation, Knowledge Management, people management, project management, Web 2.0, wiki,
Labels: blog, documentation, Knowledge Management, people management, RSS, Web 2.0, wiki
posted by James P. MacLennan at 10:10 PM
| Permalink
| 0 Comments
