It's been an interesting week. This past Tuesday through Thursday at work we had the IT Leadership meetings. Yep, I'm now an IT "leader". Those geek numbers must be coming back to haunt me. The company has all of the direct reports to the CIO, plus the next level down and select others come to a series of meetings at the home office. Thankfully, it isn't "death by Powerpoint". There is an attempt made by all of the featured groups to be creative in delivering their messages. It was interesting, although I'm not sure all the messages were effectively delivered.
We also did a bit of team building and had a fair amount of time for socializing, so I was able to put a few faces to names.
(I also found out that a high school classmate -- actually, a guy who was usually in my homeroom -- is a peer of mine. There are a couple other guys that I knew in high school who work for our company as well -- effectively one percent of our graduating class works here.)
I sat through more than one presentation where I was lost in a sea of acronyms and IT-speak (actually a peculiar dialect specific to my employer, I guess). But I followed most of it and had some of it interpreted for me.
My little corner of the world sometimes feels like a stretch in the IT world, but at least I am making connections.
Today, I was on a panel discussion for the Chicago Bar Association and Chicago-Kent College of Law. The audience was a room full of lawyers looking for CLE credit. We had what seemed like several hundred slides for seven panel members. I managed to elicit some laughs and still deliver a clear message without being beat up by the lawyers. I guess that is a good day.
The whole week was really long. Several 12 hour days and lots of intensive listening and focused concentration. The week went by very quickly and I have a lot of work piled up. So no real gems of wisdom beyond a sense that I can hold my own with IT and lawyers. I guess that's a pretty good week.
Friday, February 15, 2008
Monday, February 11, 2008
Laptop-free Mondays
You would think, that after a dozen or so years of lugging a laptop with me everywhere that I go, that I would remember the darn thing in the morning. Well, not today. Herein will be one of the problems that accompany transitioning to my upcoming "workplace mobility".
In years past, I would typically bring my laptop with me as a security measure (i.e. I didn't want to worry about having it stolen off my desk) or "just in case" (something came up where I needed to get to an internal system). Most of the time, it would never leave my computer bag. In general, if I needed to do some work, I would usually be able to get to email from my home computer using a VPN connection. Well, the new employer doesn't work that way -- you pretty much need to be connected to the network using only your work-issued computer. So when I work from home, I have to plug the thing in using my docking station and my KVM (keyboard, video, mouse) switch. So the laptop sits under my monitor and tends to be out of sight...
Anyway, that's where it was when I walked into work this morning.
This is the second time in six months that I have found myself away from home and reached into an empty backpack. The first time, I was at O'Hare Airport and had a very sickening feeling when I reached back and found the side zipper wide open as I walked from my car to the terminal. (First thought, "Did it fall out?!!!" Second thought, "Oh @%#&%#@!! It's on my desk!") That one had a happy ending in that my family literally rode to the rescue (and I am always at the airport very early). That little mistake cost me a Nintendo Wii and months of merciless ribbing from the family.
So this morning, after the expletive, it quickly dawned on me that I had left the darn thing sitting happily at home in its docking station. Today was a fairly light day at work, meeting-wise, but I needed to snail mail some stuff to co-workers and deal with some stuff that had piled up on my desk. We're having IT leadership meetings the rest of the week and I won't be at my desk very much.
So what to do? Fortunately, I have my handy Motorola Q9h. Email was merrily arriving in that, so I wasn't completely cut off from the world. If something blew up, I could at least get hold of people and see what was going on.
I also had a backpack full of stuff (which is why I didn't notice any lightness from not having the laptop in there). I've been trying to get through my backlog of reading and I had picked up a bunch of stuff at a seminar on Friday. There were also quite a number of things to file.
So I decided to tackle those tasks. It was very disconcerting sitting there with with a dead computer screen behind me. My Q would buzz every now and then and I retained a sense of connectedness, but I avoided spending time responding to emails. I looked, decided if it needed an immediate answer, and generally went back to my desk. Things got filed and things got read. My morning meeting came round and I spent a few minutes touching base in person and by phone with some folks. It was actually lunch time before I knew it.
After lunch, I tidied up a bit more and decided that there were a few emails that I needed to respond to as well as some that needed to be sent. But the morning was remarkably productive, all things considered. I left the office in the early afternoon and dealt with email once I got to the home office.
I'm thinking maybe this should be my normal approach to Monday morning... One of the things that I tend not to do very much is really sit down and be planful about my week. I could have done that this morning for this week, absent the all day meetings that will kill the balance of the week. I tend to walk in and boot my laptop before my coat is off. I'm reading email and responding before my "Grabber" breakfast sandwich has cooled off. I guess sometimes, you simply need to turn off the connectedness for a while and think. New lesson learned for the day...
In years past, I would typically bring my laptop with me as a security measure (i.e. I didn't want to worry about having it stolen off my desk) or "just in case" (something came up where I needed to get to an internal system). Most of the time, it would never leave my computer bag. In general, if I needed to do some work, I would usually be able to get to email from my home computer using a VPN connection. Well, the new employer doesn't work that way -- you pretty much need to be connected to the network using only your work-issued computer. So when I work from home, I have to plug the thing in using my docking station and my KVM (keyboard, video, mouse) switch. So the laptop sits under my monitor and tends to be out of sight...
Anyway, that's where it was when I walked into work this morning.
This is the second time in six months that I have found myself away from home and reached into an empty backpack. The first time, I was at O'Hare Airport and had a very sickening feeling when I reached back and found the side zipper wide open as I walked from my car to the terminal. (First thought, "Did it fall out?!!!" Second thought, "Oh @%#&%#@!! It's on my desk!") That one had a happy ending in that my family literally rode to the rescue (and I am always at the airport very early). That little mistake cost me a Nintendo Wii and months of merciless ribbing from the family.
So this morning, after the expletive, it quickly dawned on me that I had left the darn thing sitting happily at home in its docking station. Today was a fairly light day at work, meeting-wise, but I needed to snail mail some stuff to co-workers and deal with some stuff that had piled up on my desk. We're having IT leadership meetings the rest of the week and I won't be at my desk very much.
So what to do? Fortunately, I have my handy Motorola Q9h. Email was merrily arriving in that, so I wasn't completely cut off from the world. If something blew up, I could at least get hold of people and see what was going on.
I also had a backpack full of stuff (which is why I didn't notice any lightness from not having the laptop in there). I've been trying to get through my backlog of reading and I had picked up a bunch of stuff at a seminar on Friday. There were also quite a number of things to file.
So I decided to tackle those tasks. It was very disconcerting sitting there with with a dead computer screen behind me. My Q would buzz every now and then and I retained a sense of connectedness, but I avoided spending time responding to emails. I looked, decided if it needed an immediate answer, and generally went back to my desk. Things got filed and things got read. My morning meeting came round and I spent a few minutes touching base in person and by phone with some folks. It was actually lunch time before I knew it.
After lunch, I tidied up a bit more and decided that there were a few emails that I needed to respond to as well as some that needed to be sent. But the morning was remarkably productive, all things considered. I left the office in the early afternoon and dealt with email once I got to the home office.
I'm thinking maybe this should be my normal approach to Monday morning... One of the things that I tend not to do very much is really sit down and be planful about my week. I could have done that this morning for this week, absent the all day meetings that will kill the balance of the week. I tend to walk in and boot my laptop before my coat is off. I'm reading email and responding before my "Grabber" breakfast sandwich has cooled off. I guess sometimes, you simply need to turn off the connectedness for a while and think. New lesson learned for the day...
Monday, January 28, 2008
Email: What Hath the Internet Wrought?
I've been thinking a lot about email lately. I'm convinced, that after the personal computer, there have been few technical innovations that have so rapidly been adopted and have so radically changed the work environment. While the World Wide Web really caused the Internet to explode in growth, email delivered the Internet into every office with a real business purpose. So let's look at my personal timeline for a minute...
1988: Pat gets his first computer at work. It is a word processor for letters, forms, and academic papers.
ca. 1991: Pat discovers a 1200 baud modem and places where you can download software over dialup connections.
1992: Pat goes to work at Household International and is introduced to PROFS. email becomes part of everyday life, but it is only within the company and does not integrate calendaring.
1993: Pat discovers Chicago Online, part of the then-fledgling America Online. The service very quickly allows email to be sent to other services like Compuserve and GEnie.
1994: Corporate email finds the Internet.
1995: The Internet takes off.
So as I sit here today, email has been a part of my business life for just over 15 years. I would estimate that the transition from paper-based mail to email began in earnest about 1995. By 1997, email had effectively killed off paper-based mail and internal memoranda (at least in my life). So we have just over 10 years of hardcore, business to business communications via email. But that transition happened so quickly. While some folks had email prior to 1990, I would suggest that it moved from occasional tool to everyday workhorse for most companies between 1994 and 1996. That's a radical change in something less than four years, in my estimation. This development is really only eclipsed by the development of the personal computer. Arguably, if you mark the birth of the PC as 1981 (when the IBM PC was released), the PC started to enter mainstream businesses in force in the 1984 to 1986 timeframe. (Yes, the Apple and Tandy computers were around earlier, but they tended to be seen as curiosities.) By 1988, they were becoming ubiquitous in many companies. The next 8 years radically changed the workplace. Then the Internet and email changed it again.
So enough of this history lesson. Why is email on my mind? Well, in the past month, I've had two opportunities to speak about email management. Email management is very much top of mind for many records managers. We've had this stuff around for ten years or more and yet very few of us are managing it well. I sit here today with three personal email addresses and one business address. In a given day, my personal email addresses will collect perhaps 30 to 40 actionable emails (exclusive of spam and Listserve posts). I'll delete a lot of those (many are subscriptions or promotions for various things that I've asked for), respond to some, and save for reference others. At work, I see perhaps 15 to 20 emails a day, but that number is growing and the vast majority are business emails that require a response. Now based upon some statistical data, I'm actually somewhat behind the curve. Last month, I was on a panel discussion following a presentation by Michael Osterman of Osterman Research. His company's research indicates that the average employee receives and sends something like 140 email messages a day. I suppose that if I read all those Listserve postings, I might hit those numbers... Nonetheless, that's a lot of correspondence.
And think back to those days of yore... did anyone ever deal with 140 inbound and outbound personal letters a day? For the vast majority of us, I would say absolutely not. Many years ago, at one of my prior employers, the Records Management department received all of the company's paper mail. The Records staff would open all incoming mail that was not strictly "personal and confidential", review the mail, and determine if it should be copied, routed and filed, then send the original to the addressee. Outgoing mail was copied and distributed according to strict rules, but every piece of business correspondence was filed by Records in that manner. Email completely changed that process. In the early days, the same rules were applied to email as paper mail, except the recipients were required to send a paper copy of every email to Records for filing. That lasted less than a year. First the volume became too great, then the users didn't have the time to print and route the email. There were no tools that could manage the volumes effectively and anarchy took hold. We were later able to rein in the email to some extent, but email became a tsunami of records.
If you recall my earlier blog post on typing, I said that "...if everyone is a typist, everyone creates and files records. Welcome to full employment for records managers!" That is never more true than with email. My mother was a traditional secretary. She learned shorthand and typing in high school and would go into her boss' office to take down what he wanted to say in every letter. She would take the dictation, then transcribe the dictation into letters. He would glance at the letter, sign it, she'd make and file a copy, while mailing the original. To our thinking today, that's a terribly inefficient way to do business -- but it also meant that every piece of correspondence had to have good reason to be sent. It also enabled the sender to think about what was going to be sent -- first, while dictating, then, when it came back for signature. Days and weeks might pass between sending a letter and receiving a response. FedEx and the fax machine accelerated that a bit, but email changed the dynamic completely. That means that everyone has become a typist and a file clerk with volumes of correspondence never dreamed of in the past -- and with risks never dreamed of in the past. In the old days, it was pretty hard to accidentally distribute sensitive information to hundreds of people. Today, one keystroke can ruin a career. One email can help to destroy a company:
"Mike -- It might be useful to consider reminding the engagement team of our documentation and retention policy."
That was from Nancy Temple's infamous email in the Arthur Anderson / Enron debacle. The implication, of course (and never substantiated) was that Ms. Temple was providing cover for the Enron team to destroy records. But this is typical of many email messages. The context is not totally clear. The intent is really unknown. The tone is what you hear inside your head when you read it. And it is easy to infer both good and bad intent. As the author, you know what you meant -- but in the haste to get a response out and get on to the next message, you write something that is misinterpreted. And then things get interesting. For every problem solved by email, it seems that another comes along to take its place.
Today, I look at my personal email volumes and know that things are way out of hand. I probably keep too much of it (personally), but that has more to do with inexpensive disk space than anything else. Searches take forever and folder structures just don't cut it. At work, the volumes grow equally fast and we're really wrestling with solutions that meet our retention requirements, while not messing too much with the end users. The other presentation that I participated in this month allowed me to speak to user requirements. at the end of the day, I simply haven't found that holy grail of email management. Automatic classification has some promise, but it won't work for every organization and very often doesn't enable the granularity that is needed. In addition, the proliferation of personal email in the business environment is bordering on insane. With my new employer, I have tried very hard to keep personal email out of my Inbox. But it is very hard to do. And I have run across many people who don't separate business from personal -- their work computer is their only computer. So capture of every inbound email means that a lot of personal email would be saved.
Ten to twenty years of email for some employees also means that most have evolved their own habits (for good or bad) around email management. The far end of that spectrum represents employees who likely recall the old days of paper filing and might have retained some good habits. At the other end of the spectrum are employees fresh from school who have ten years of personal habits -- many of which may never involve use of the Delete key -- or involve overzealous application of the delete key.
The next several years will involve massive change management to get the proper behaviors embedded -- or it will mean that we simply capture everything and try to sort out the spam, garbage and personal email, while retaining what is important. At any rate, it will mean a significant educational effort for just about every employee in every organization -- and that assumes that we can get the genie back in the bottle.
The legal lessons are out there. Most email users have scars from mis-sent email messages or online flame wars. Yet the old habits die hard -- probably simply because the volumes are not going down and employees are pushed to be ever more productive in a global, semi-synchronous world.
It's closing on Midnight here in Chicago. Day has not quite broken in Europe. It is lunchtime in India and mid-afternoon in China. My Motorola Q is buzzing merrily through the evening as I receive messages from around the world. My personal Inboxes are reminding me that something new has arrived in my personal world. And as I write this, I'm periodically responding to personal and business email. As I sleep, those Inboxes will store more email and the cycle will repeat. PDAs and wireless communications allow you to receive and send email from anywhere at any time. That is the promise and the curse of email. It enables a global workforce and business. But it can also sit on your hip 24 hours a day reminding you that the company never sleeps -- and the sun never sets on records management. I guess we better figure this one out.
1988: Pat gets his first computer at work. It is a word processor for letters, forms, and academic papers.
ca. 1991: Pat discovers a 1200 baud modem and places where you can download software over dialup connections.
1992: Pat goes to work at Household International and is introduced to PROFS. email becomes part of everyday life, but it is only within the company and does not integrate calendaring.
1993: Pat discovers Chicago Online, part of the then-fledgling America Online. The service very quickly allows email to be sent to other services like Compuserve and GEnie.
1994: Corporate email finds the Internet.
1995: The Internet takes off.
So as I sit here today, email has been a part of my business life for just over 15 years. I would estimate that the transition from paper-based mail to email began in earnest about 1995. By 1997, email had effectively killed off paper-based mail and internal memoranda (at least in my life). So we have just over 10 years of hardcore, business to business communications via email. But that transition happened so quickly. While some folks had email prior to 1990, I would suggest that it moved from occasional tool to everyday workhorse for most companies between 1994 and 1996. That's a radical change in something less than four years, in my estimation. This development is really only eclipsed by the development of the personal computer. Arguably, if you mark the birth of the PC as 1981 (when the IBM PC was released), the PC started to enter mainstream businesses in force in the 1984 to 1986 timeframe. (Yes, the Apple and Tandy computers were around earlier, but they tended to be seen as curiosities.) By 1988, they were becoming ubiquitous in many companies. The next 8 years radically changed the workplace. Then the Internet and email changed it again.
So enough of this history lesson. Why is email on my mind? Well, in the past month, I've had two opportunities to speak about email management. Email management is very much top of mind for many records managers. We've had this stuff around for ten years or more and yet very few of us are managing it well. I sit here today with three personal email addresses and one business address. In a given day, my personal email addresses will collect perhaps 30 to 40 actionable emails (exclusive of spam and Listserve posts). I'll delete a lot of those (many are subscriptions or promotions for various things that I've asked for), respond to some, and save for reference others. At work, I see perhaps 15 to 20 emails a day, but that number is growing and the vast majority are business emails that require a response. Now based upon some statistical data, I'm actually somewhat behind the curve. Last month, I was on a panel discussion following a presentation by Michael Osterman of Osterman Research. His company's research indicates that the average employee receives and sends something like 140 email messages a day. I suppose that if I read all those Listserve postings, I might hit those numbers... Nonetheless, that's a lot of correspondence.
And think back to those days of yore... did anyone ever deal with 140 inbound and outbound personal letters a day? For the vast majority of us, I would say absolutely not. Many years ago, at one of my prior employers, the Records Management department received all of the company's paper mail. The Records staff would open all incoming mail that was not strictly "personal and confidential", review the mail, and determine if it should be copied, routed and filed, then send the original to the addressee. Outgoing mail was copied and distributed according to strict rules, but every piece of business correspondence was filed by Records in that manner. Email completely changed that process. In the early days, the same rules were applied to email as paper mail, except the recipients were required to send a paper copy of every email to Records for filing. That lasted less than a year. First the volume became too great, then the users didn't have the time to print and route the email. There were no tools that could manage the volumes effectively and anarchy took hold. We were later able to rein in the email to some extent, but email became a tsunami of records.
If you recall my earlier blog post on typing, I said that "...if everyone is a typist, everyone creates and files records. Welcome to full employment for records managers!" That is never more true than with email. My mother was a traditional secretary. She learned shorthand and typing in high school and would go into her boss' office to take down what he wanted to say in every letter. She would take the dictation, then transcribe the dictation into letters. He would glance at the letter, sign it, she'd make and file a copy, while mailing the original. To our thinking today, that's a terribly inefficient way to do business -- but it also meant that every piece of correspondence had to have good reason to be sent. It also enabled the sender to think about what was going to be sent -- first, while dictating, then, when it came back for signature. Days and weeks might pass between sending a letter and receiving a response. FedEx and the fax machine accelerated that a bit, but email changed the dynamic completely. That means that everyone has become a typist and a file clerk with volumes of correspondence never dreamed of in the past -- and with risks never dreamed of in the past. In the old days, it was pretty hard to accidentally distribute sensitive information to hundreds of people. Today, one keystroke can ruin a career. One email can help to destroy a company:
"Mike -- It might be useful to consider reminding the engagement team of our documentation and retention policy."
That was from Nancy Temple's infamous email in the Arthur Anderson / Enron debacle. The implication, of course (and never substantiated) was that Ms. Temple was providing cover for the Enron team to destroy records. But this is typical of many email messages. The context is not totally clear. The intent is really unknown. The tone is what you hear inside your head when you read it. And it is easy to infer both good and bad intent. As the author, you know what you meant -- but in the haste to get a response out and get on to the next message, you write something that is misinterpreted. And then things get interesting. For every problem solved by email, it seems that another comes along to take its place.
Today, I look at my personal email volumes and know that things are way out of hand. I probably keep too much of it (personally), but that has more to do with inexpensive disk space than anything else. Searches take forever and folder structures just don't cut it. At work, the volumes grow equally fast and we're really wrestling with solutions that meet our retention requirements, while not messing too much with the end users. The other presentation that I participated in this month allowed me to speak to user requirements. at the end of the day, I simply haven't found that holy grail of email management. Automatic classification has some promise, but it won't work for every organization and very often doesn't enable the granularity that is needed. In addition, the proliferation of personal email in the business environment is bordering on insane. With my new employer, I have tried very hard to keep personal email out of my Inbox. But it is very hard to do. And I have run across many people who don't separate business from personal -- their work computer is their only computer. So capture of every inbound email means that a lot of personal email would be saved.
Ten to twenty years of email for some employees also means that most have evolved their own habits (for good or bad) around email management. The far end of that spectrum represents employees who likely recall the old days of paper filing and might have retained some good habits. At the other end of the spectrum are employees fresh from school who have ten years of personal habits -- many of which may never involve use of the Delete key -- or involve overzealous application of the delete key.
The next several years will involve massive change management to get the proper behaviors embedded -- or it will mean that we simply capture everything and try to sort out the spam, garbage and personal email, while retaining what is important. At any rate, it will mean a significant educational effort for just about every employee in every organization -- and that assumes that we can get the genie back in the bottle.
The legal lessons are out there. Most email users have scars from mis-sent email messages or online flame wars. Yet the old habits die hard -- probably simply because the volumes are not going down and employees are pushed to be ever more productive in a global, semi-synchronous world.
It's closing on Midnight here in Chicago. Day has not quite broken in Europe. It is lunchtime in India and mid-afternoon in China. My Motorola Q is buzzing merrily through the evening as I receive messages from around the world. My personal Inboxes are reminding me that something new has arrived in my personal world. And as I write this, I'm periodically responding to personal and business email. As I sleep, those Inboxes will store more email and the cycle will repeat. PDAs and wireless communications allow you to receive and send email from anywhere at any time. That is the promise and the curse of email. It enables a global workforce and business. But it can also sit on your hip 24 hours a day reminding you that the company never sleeps -- and the sun never sets on records management. I guess we better figure this one out.
Friday, January 11, 2008
Show Your Work!
Every now and then, I find myself lapsing into phrases and language that I learned as a child. It freaks me out when I say something that was a hallmark of my father.
The ten your old (whom we have met here before) has her struggles with Math. So from time to time, she comes into my office to have me check her homework. I can tell this is painful for her because she knows that the very first thing I'm going to tell her is, "Show your work!" "But Dad," she protests, "we don't have to do that today!" And that one word, "today", and its inflection says so much. She may as well pack me off in the wheelchair to the Irrelevant Parents' Home.
Nonetheless, what I also perceived as a pain in 1972, and she perceives as a pain in 2008, carries value. When you ask for help, it shows that you have tried an approach and enables the person helping you to see where you went wrong.
So now, to today's homily...
I've been a subscriber to the Records Management Listserve since 1993. Back then, I think the subscriber base was well under 100 and email was a new thing for many people. The original Listserve was put together by records managers for educational institutions (mainly because they were among the few people out there with Internet email at the time). Anyway, over the years I have noticed a mis-use of that forum that bugs me every time I see it. That is, the person who posts something to the effect of, "I've been told to do a [insert a variety of RIM projects]. Could everyone send me a copy of what they have done?" And this can range from university students writing term papers to rookie records managers writing RFPs to experienced records managers looking for forms. I have, on occasion, written to the person committing the etiquette breach and asked them to consider how their post appears to 1500 or 2000 colleagues. My experience is that while some folks will be helpful, these sorts of requests are often met with a very stony silence. When I have written these folks, I sometimes will get a very defensive reply -- and sometimes these folks are hurt that "no one responded -- I don't understand why when you ask for something, there are all sorts of replies". My response to that generally looks like this:
Young Grasshopper,
A long line of stern women in severe black dress once pounded into my thick skull that the path to knowledge is best found when you show the path already taken. In their direct terms, they told me to "SHOW YOUR WORK!" These same teachers also informed me that following the same path as others did not allow you the experience of discovery and the opportunity to blaze new trails. In their terms, "EYES ON YOUR OWN PAPERS!"
Now Grasshopper, in the business world we like to use the term "benchmarking". I have heard you propose to me that what you are doing is simply "benchmarking". And that may be so. I have often used the term myself, but I am very selective in choosing benchmarking partners. The best sort of benchmarking is when all parties share their approaches equally -- and particularly when the person receiving the most value from the process shares his or her findings with all the participants. My teachers would say, "IF YOU BRING A TREAT TO CLASS, MAKE SURE THAT YOU HAVE ENOUGH TO SHARE WITH THE ENTIRE CLASS."
And so, young Grasshopper, I offer you this advice: When seeking the wisdom of others, demonstrate that you are worthy of that wisdom. Show that you are willing to find your own path and that you have done your own work. Share your bits of knowledge with everyone and when others share with you, ensure that everyone benefits from your learning.
The guru is out.
The ten your old (whom we have met here before) has her struggles with Math. So from time to time, she comes into my office to have me check her homework. I can tell this is painful for her because she knows that the very first thing I'm going to tell her is, "Show your work!" "But Dad," she protests, "we don't have to do that today!" And that one word, "today", and its inflection says so much. She may as well pack me off in the wheelchair to the Irrelevant Parents' Home.
Nonetheless, what I also perceived as a pain in 1972, and she perceives as a pain in 2008, carries value. When you ask for help, it shows that you have tried an approach and enables the person helping you to see where you went wrong.
So now, to today's homily...
I've been a subscriber to the Records Management Listserve since 1993. Back then, I think the subscriber base was well under 100 and email was a new thing for many people. The original Listserve was put together by records managers for educational institutions (mainly because they were among the few people out there with Internet email at the time). Anyway, over the years I have noticed a mis-use of that forum that bugs me every time I see it. That is, the person who posts something to the effect of, "I've been told to do a [insert a variety of RIM projects]. Could everyone send me a copy of what they have done?" And this can range from university students writing term papers to rookie records managers writing RFPs to experienced records managers looking for forms. I have, on occasion, written to the person committing the etiquette breach and asked them to consider how their post appears to 1500 or 2000 colleagues. My experience is that while some folks will be helpful, these sorts of requests are often met with a very stony silence. When I have written these folks, I sometimes will get a very defensive reply -- and sometimes these folks are hurt that "no one responded -- I don't understand why when you ask for something, there are all sorts of replies". My response to that generally looks like this:
Young Grasshopper,
A long line of stern women in severe black dress once pounded into my thick skull that the path to knowledge is best found when you show the path already taken. In their direct terms, they told me to "SHOW YOUR WORK!" These same teachers also informed me that following the same path as others did not allow you the experience of discovery and the opportunity to blaze new trails. In their terms, "EYES ON YOUR OWN PAPERS!"
Now Grasshopper, in the business world we like to use the term "benchmarking". I have heard you propose to me that what you are doing is simply "benchmarking". And that may be so. I have often used the term myself, but I am very selective in choosing benchmarking partners. The best sort of benchmarking is when all parties share their approaches equally -- and particularly when the person receiving the most value from the process shares his or her findings with all the participants. My teachers would say, "IF YOU BRING A TREAT TO CLASS, MAKE SURE THAT YOU HAVE ENOUGH TO SHARE WITH THE ENTIRE CLASS."
And so, young Grasshopper, I offer you this advice: When seeking the wisdom of others, demonstrate that you are worthy of that wisdom. Show that you are willing to find your own path and that you have done your own work. Share your bits of knowledge with everyone and when others share with you, ensure that everyone benefits from your learning.
The guru is out.
Subscribe to:
Posts (Atom)
