I'm going to have an Andy Rooney moment here.
In the town next to the one in which I live, there is an intersection where traffic laws are violated by the minute. (Go to Google Maps and search for 2 West Burlington Ave., LaGrange, IL and click on the StreetView function. Look at the intersection with LaGrange Rd.) If you are traveling east or west on Burlington Ave., at LaGrange Road, you will find not less than four no left turn signs in each direction. The rationale, in one direction (eastbound), is that turning left would put you stopped on the railroad tracks on the other side of the tracks, or force you to run a red light over there (which is what happens all the time). In the other direction (westbound), there is simply no turning lane and waiting for oncoming traffic would back up traffic behind you unnecessarily. In addition, there are signs (westbound) that prohibit right turns on red and permit right turns on green arrow only. Again, these signs are disregarded with abandon.
Now I have lived in this area for 35 years. The traffic rules for this intersection have not changed in those 35 years. And yet, I can sit and watch people disregard those signs almost every time I go through that intersection.
So I have to ask -- are people just that oblivious to signage or are they just so "me" focused that they aren't going to let a little thing like a traffic law prevent them from going about their business?
And here's another one. The other day I was pulling out of a shopping center parking lot. The entrance has been engineered to only permit a right turn out of the lot -- and prohibits people from turning into the lot at that entrance from the other side of the street. There's no stoplight, so traffic crossing opposing lanes is supposed to go to the next stoplight to turn in. I'm sure that there is a traffic engineering term for that sort of entrance / exit, but I couldn't tell you what it is. (I did find this drawing that is similar.) However, as I was about to hit that exit, some clown comes flying in my exit lane from the other side of the street! And flips me off when I blast my horn at him! Had I been a couple of seconds faster, he would have hit me head on. Guess the No Left Turn and Do Not Enter signs weren't intended for him...
Thanks for obliging me in my Andy Rooney moment.
Thoughts and musings about issues that are at the edges of the Records and Information Management (RIM) profession.
Monday, September 8, 2008
ATR: ARMA on YouTube
You just never know what you're going to find on YouTube. Looks like someone from ARMA in Dallas / Fort Worth posted a promotional video for ARMA.
Labels:
ARMA International,
YouTube
Wednesday, September 3, 2008
ATR: Email is so... 1970?
I spent a chunk of time reviewing my email storage recently. I needed a bit more space. I needed to do a better job filing. And I wanted to clean up the detritus of years of email.
But what I walked away with is a sense that email has just made everything bad about snail mail happen much more quickly and without the pain of creating the communication.
In 1970, if you wanted to send a communication to 100 people, you had to type out the memo, then duplicate it in some fashion, then address the memos and send them on their way. It was a slow and expensive process. In the end, each recipient had a unique copy of the memo and could do what they chose with it. Sound familiar? In those thousands of emails that I looked at, I can't tell you how many were replies and forwards. I can't tell you how many appeared to be the same note, sent to a bunch of people, each with a unique reply that led to numerous additional threads and permutations. And each message, each volley, meant another unique document stored across the email platforms of every recipient. Just. Like. Paper.
Email is everything bad about paper-based communications, on an exponentially larger scale. If we are sending the same exact communication to 100 people, why do we need 100 copies of the same document? Can't we just create one copy, place it in a common repository, and let everyone go look at the original? Can't people reply in a manner that allows everyone to see all the replies in a single thread? If they need a local copy, we keep track of the fact that they made a local copy. If they work in another organization, we'll make sure that they get a unique copy for their record, if needed. But they do these things when they deal with the document, not far down the road.
That, to me, is what the promise of this cloud computing thing is all about. We'll see.
But what I walked away with is a sense that email has just made everything bad about snail mail happen much more quickly and without the pain of creating the communication.
In 1970, if you wanted to send a communication to 100 people, you had to type out the memo, then duplicate it in some fashion, then address the memos and send them on their way. It was a slow and expensive process. In the end, each recipient had a unique copy of the memo and could do what they chose with it. Sound familiar? In those thousands of emails that I looked at, I can't tell you how many were replies and forwards. I can't tell you how many appeared to be the same note, sent to a bunch of people, each with a unique reply that led to numerous additional threads and permutations. And each message, each volley, meant another unique document stored across the email platforms of every recipient. Just. Like. Paper.
Email is everything bad about paper-based communications, on an exponentially larger scale. If we are sending the same exact communication to 100 people, why do we need 100 copies of the same document? Can't we just create one copy, place it in a common repository, and let everyone go look at the original? Can't people reply in a manner that allows everyone to see all the replies in a single thread? If they need a local copy, we keep track of the fact that they made a local copy. If they work in another organization, we'll make sure that they get a unique copy for their record, if needed. But they do these things when they deal with the document, not far down the road.
That, to me, is what the promise of this cloud computing thing is all about. We'll see.
Labels:
cloud computing,
email. paper,
Web 2.0
Tuesday, September 2, 2008
ATR: What is a Record?
I'm thinking... hard. We had a presentation today on what comes next in the wonderful world of IT and it looks like we may be off to the cloud and this whole Web 2.0 thing. Now I have never been one to chase the buzzword du jour, but I sense a bit of stickiness in the media hype right now.
I've got some ideas about what the new world may look like, but it starts with thinking about records in a slightly different way. The way I see it, a record is fundamentally two things: something that is communicated and something that has a business purpose. ISO 15489 says that a record is "information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business". The approach that I'm taking indicates that the record has to be communicated in some fashion, which in my mind implies that it is transmitted to someone or something. So arguably, a "note to self" that is recording by pen on paper and put into a file folder is likely not a record, as such (it may well be evidence, however). And that old bugaboo, the voicemail message, now becomes an object that we're going to have to seriously consider keeping as a record.
So why mess with this definition? Well, in this brave new 2.0 world, we will have to start thinking in terms of objects when we talk about unstructured information. And we will need to think of all these 2.0 tools like blogs and wikis as mechanisms for communications and collaboration for these objects. If you think about it, email is simply a push mechanism for a document that is either the body of the document or attached. A blog is a way to broadcast an object (either passively or actively through RSS feeds). A wiki is a way to collaboratively edit a document. And those are examples with text.
My sense is that, in the fairly near future, a person will create an object for business purposes. Perhaps they have a question about something. They will authenticate themselves and designate the audience for their object (individuals or a group of other authenticated persons). The object will be stored and the audience will be notified that there is an object that they need to review. They will follow a link to a single instance of the object and see how the sender wished to be communicated with in return. Perhaps they want the object edited (a wiki). Perhaps they want a discussion (threaded discussion). Perhaps they have a finished product and want comments around their object (a blog). There are many scenarios. What will be consistent is that the object creator will deliver the object to a repository with information about who should see the object, who *may* see the object, who can edit it, what sort of record it is, and any other attributes or metadata that might be helpful.
Other users will have a browser dashboard that allows them to see a worklist (effectively, what has been pushed to them for information or actual work), a reading list (items that they have subscribed to or placed into ongoing searches, newsfeeds, a calendar, and whatever other widgets make sense for their daily jobs. They'll have something that notifies them of items to follow up on. And we'll have to make some fundamental changes to how we work. When you connect to that object, you'll have to do something. Reading and setting it aside for later will require you to decide when it will resurface for work. The good news (at least in my little fantasyworld) is that once you take an action, that action will be stored in the cloud and Inbox clutter goes away. Search will need to be much more effective.
Perhaps they will have a "presence awareness" window that allows the user to see who is available -- and allows textual, voice or video communications. Perhaps their voicemail will be stored as an object and made available for review.
At the end of the day, the user will need to be much more decisive about what is a record and what sort of record the object is. The user will have to make a few more decisions about what they create and receive. And our "connectedness" will need to be nearly seamless. If everything exists in "the cloud", you have to be able to get there to work.
Records management will need to adapt. We will be in the attribute or metadata business and we will need to work with a lot of other folks to develop processes to authenticate information, ensure security, and ensure disposition. The good news is that we'll have a virtual central file room; the bad news is that the end user will have far more power to decide what to keep and what to throw away. So we'll also have to do more compliance monitoring.
So that's what is in my head tonight, keeping me from my pillow...
I've got some ideas about what the new world may look like, but it starts with thinking about records in a slightly different way. The way I see it, a record is fundamentally two things: something that is communicated and something that has a business purpose. ISO 15489 says that a record is "information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business". The approach that I'm taking indicates that the record has to be communicated in some fashion, which in my mind implies that it is transmitted to someone or something. So arguably, a "note to self" that is recording by pen on paper and put into a file folder is likely not a record, as such (it may well be evidence, however). And that old bugaboo, the voicemail message, now becomes an object that we're going to have to seriously consider keeping as a record.
So why mess with this definition? Well, in this brave new 2.0 world, we will have to start thinking in terms of objects when we talk about unstructured information. And we will need to think of all these 2.0 tools like blogs and wikis as mechanisms for communications and collaboration for these objects. If you think about it, email is simply a push mechanism for a document that is either the body of the document or attached. A blog is a way to broadcast an object (either passively or actively through RSS feeds). A wiki is a way to collaboratively edit a document. And those are examples with text.
My sense is that, in the fairly near future, a person will create an object for business purposes. Perhaps they have a question about something. They will authenticate themselves and designate the audience for their object (individuals or a group of other authenticated persons). The object will be stored and the audience will be notified that there is an object that they need to review. They will follow a link to a single instance of the object and see how the sender wished to be communicated with in return. Perhaps they want the object edited (a wiki). Perhaps they want a discussion (threaded discussion). Perhaps they have a finished product and want comments around their object (a blog). There are many scenarios. What will be consistent is that the object creator will deliver the object to a repository with information about who should see the object, who *may* see the object, who can edit it, what sort of record it is, and any other attributes or metadata that might be helpful.
Other users will have a browser dashboard that allows them to see a worklist (effectively, what has been pushed to them for information or actual work), a reading list (items that they have subscribed to or placed into ongoing searches, newsfeeds, a calendar, and whatever other widgets make sense for their daily jobs. They'll have something that notifies them of items to follow up on. And we'll have to make some fundamental changes to how we work. When you connect to that object, you'll have to do something. Reading and setting it aside for later will require you to decide when it will resurface for work. The good news (at least in my little fantasyworld) is that once you take an action, that action will be stored in the cloud and Inbox clutter goes away. Search will need to be much more effective.
Perhaps they will have a "presence awareness" window that allows the user to see who is available -- and allows textual, voice or video communications. Perhaps their voicemail will be stored as an object and made available for review.
At the end of the day, the user will need to be much more decisive about what is a record and what sort of record the object is. The user will have to make a few more decisions about what they create and receive. And our "connectedness" will need to be nearly seamless. If everything exists in "the cloud", you have to be able to get there to work.
Records management will need to adapt. We will be in the attribute or metadata business and we will need to work with a lot of other folks to develop processes to authenticate information, ensure security, and ensure disposition. The good news is that we'll have a virtual central file room; the bad news is that the end user will have far more power to decide what to keep and what to throw away. So we'll also have to do more compliance monitoring.
So that's what is in my head tonight, keeping me from my pillow...
Labels:
cloud computing,
documents,
objects,
records management,
Web 2.0
Subscribe to:
Posts (Atom)
