It's a sad day. My two year old Motorola RAZR died suddenly. No drama, no heroic measures to save it... it just died. It was fine yesterday afternoon and last night when I went to charge it for the night, it was dead. I attempted a battery transplant and found that the battery was healthy, but the phone was DOA. I left it plugged in overnight in the hope that it might come back, but it was over. Cause of death is undetermined. The phone bore many scars from bouncing off concrete, as well as being pummeled by seat belts on a daily basis.
It is currently lying in repose on my desk at home. I think I will remove the battery for future use as a donor organ for my wife's phone. The phone itself will assume a place of honor in my office at work -- alongside my old pager and a couple of Iridium phone mock-ups.
My Q9h survives and is feeling lonely today without its constant companion next to it, competing for airtime on the Bluetooth headset.
A QA1 Karma is on order to take the place of my RAZR. Life, and technology, go on...
Thoughts and musings about issues that are at the edges of the Records and Information Management (RIM) profession.
Monday, September 14, 2009
Saturday, September 5, 2009
OTR: Social Media and Intelligence Gathering
Over at the Day Job, a couple of events that highlight how mainstream social media is becoming... and how what you post can come back to haunt you if you're not careful.
Yesterday morning, I was up a little earlier than usual and decided to browse my Google Alerts at home rather than first thing in the morning at the office. One of the alerts was for the Day Job and highlighted a blog posting claiming that the Day Job had a Windows Mobile 7 cell phone in development. That was interesting because all the focus now is on Android. I followed some links and the source of the blog post was a LinkedIn profile for an individual in China claiming to work for the Day Job and claiming to be working on Windows Mobile 7 code for a code-named device. Yep, in his public profile.
As I followed other links, I came to this post. Seems that a blogger had spent some time mining LinkedIn profiles and came up with numerous tidbits about potential features in Windows Mobile 7, simply based upon what various people said they were working on. Interesting stuff there.
The day before, I had a meeting with a vendor that I had never met before. As we talked, it was pretty apparent that he was familiar with my work and my blog. I asked him and he pulled out a print-out of my LinkedIn profile and commented that he had pretty much read all my blog postings. There was a sudden jolt of reality check. I'm pretty transparent. Had I ever bashed this guy's company in any of that stuff? I didn't think so....
But these two events show that the blogosphere and social media are being utilized to find out information about future plans for companies and their products as well as providing a rich source of information for vendors so they can shape their pitches. Some of that is bad; some good, I suppose. But if you ever think that what you post or Tweet or blog or whatever won't someday come back to visit you, or is just between you and your small group of trusted followers, think again. And if what you do on your day job isn't for public consumption, don't go out and highlight it online to impress people or get the eye of a recruiter -- you may find that you'll be looking for work sooner, rather than later.
Yesterday morning, I was up a little earlier than usual and decided to browse my Google Alerts at home rather than first thing in the morning at the office. One of the alerts was for the Day Job and highlighted a blog posting claiming that the Day Job had a Windows Mobile 7 cell phone in development. That was interesting because all the focus now is on Android. I followed some links and the source of the blog post was a LinkedIn profile for an individual in China claiming to work for the Day Job and claiming to be working on Windows Mobile 7 code for a code-named device. Yep, in his public profile.
As I followed other links, I came to this post. Seems that a blogger had spent some time mining LinkedIn profiles and came up with numerous tidbits about potential features in Windows Mobile 7, simply based upon what various people said they were working on. Interesting stuff there.
The day before, I had a meeting with a vendor that I had never met before. As we talked, it was pretty apparent that he was familiar with my work and my blog. I asked him and he pulled out a print-out of my LinkedIn profile and commented that he had pretty much read all my blog postings. There was a sudden jolt of reality check. I'm pretty transparent. Had I ever bashed this guy's company in any of that stuff? I didn't think so....
But these two events show that the blogosphere and social media are being utilized to find out information about future plans for companies and their products as well as providing a rich source of information for vendors so they can shape their pitches. Some of that is bad; some good, I suppose. But if you ever think that what you post or Tweet or blog or whatever won't someday come back to visit you, or is just between you and your small group of trusted followers, think again. And if what you do on your day job isn't for public consumption, don't go out and highlight it online to impress people or get the eye of a recruiter -- you may find that you'll be looking for work sooner, rather than later.
Wednesday, July 22, 2009
ATR: Information Management Reference Model -- Been There? Done That?
A colleague pointed out this blog post. Seems that the same folks who brought us the Electronic Discovery Reference Model (EDRM) are going to develop the Information Management Reference Model (IMRM). Interesting. Now don't get me wrong, I refer to the EDRM at almost every opportunity -- in fact, my job title is modeled on it. I'm quite pleased to see that the cornerstone of the EDRM is Information Management. If you don't know what you have, you can't find it when you need it. If you don't manage what you have, you will have too much to sift through when you need it.
So I suppose that it is a natural extension of the EDRM to show how that relationship works. The components need to be defined and vendors can then market their services and products around each component of the model. But, haven't we already done this? Sure we have. We like to call it the lifecycle of records. The traditional approach designates the lifecycle as:
Over and above the lifecycle concept, ARMA International has developed the Generally Accepted Recordkeeping Principles, or GARP (I'm missing some Service Marks there). GARP has some commonality with the lifecycle model, but GARP is designed to provide organizations with a core governance model for RIM programs. So it is a bit different. ISO 15489, which predates GARP, provides a bridge between the lifecycle model and the governance elements. So arguably, if you were going to build a Reference Model, you may need a starting point of Governance that provides an overall framework for managing records. Within Creation, you'd want to speak to creating records, capturing records, or receiving records and the attendant processes to determine if the information is, in fact, a record. A key element of any RIM program is not retaining all information (even though some vendors believe that "immutable archives" are the way to go and you therefore have to retain everything forever). Distribution likely has to speak to the means of transport of records in an organization and the manner in which those systems add and retain metadata about the record. Use is somewhat outside of scope of services because it speaks to the value proposition of the record. But there are metadata elements that are created and should be associated with the record. The record also has to be protected and secured during Use. Maintenance is a big catch all and includes mechanisms to store and preserve the information. The application of retention periods comes into play here and it is at this point that the IMRM connects most strongly to the EDRM. Lastly comes Disposition. Disposition will involve the final destruction or transfer of the records. It will be important to note that Disposition largely happens outside of the EDRM -- because Disposition can only happen when the records are not required to be retained for legal proceedings.
My expectation is that someone will want to make a major pitch for a step in the process that might be called "Classification". This would be where various attributes are associated with the record. These attributes could include the record series identifier, the vital records status of the record, and the security classification of the record. I would suggest that this is a process within Creation, but I suspect that the vendor community may want to carve this out. I would also expect a push to carve out "Storage" as a separate process, with "Archiving" seen as an additional process, the rationale being that "storage" is really about making records available during Use and archiving processes are about the Maintenance of the information.
The bottom line, however, is that the IMRM should be pretty easy to define -- it's been done before. The challenge will be to ensure that the Model is not too granular and that terminology is what we expect it to be. After all, us records managers have been there and done that -- and do it every day. The folks at EDRM ought to look us up to help out.
So I suppose that it is a natural extension of the EDRM to show how that relationship works. The components need to be defined and vendors can then market their services and products around each component of the model. But, haven't we already done this? Sure we have. We like to call it the lifecycle of records. The traditional approach designates the lifecycle as:
- Creation
- Distribution
- Use
- Maintenance
- Disposition
Over and above the lifecycle concept, ARMA International has developed the Generally Accepted Recordkeeping Principles, or GARP (I'm missing some Service Marks there). GARP has some commonality with the lifecycle model, but GARP is designed to provide organizations with a core governance model for RIM programs. So it is a bit different. ISO 15489, which predates GARP, provides a bridge between the lifecycle model and the governance elements. So arguably, if you were going to build a Reference Model, you may need a starting point of Governance that provides an overall framework for managing records. Within Creation, you'd want to speak to creating records, capturing records, or receiving records and the attendant processes to determine if the information is, in fact, a record. A key element of any RIM program is not retaining all information (even though some vendors believe that "immutable archives" are the way to go and you therefore have to retain everything forever). Distribution likely has to speak to the means of transport of records in an organization and the manner in which those systems add and retain metadata about the record. Use is somewhat outside of scope of services because it speaks to the value proposition of the record. But there are metadata elements that are created and should be associated with the record. The record also has to be protected and secured during Use. Maintenance is a big catch all and includes mechanisms to store and preserve the information. The application of retention periods comes into play here and it is at this point that the IMRM connects most strongly to the EDRM. Lastly comes Disposition. Disposition will involve the final destruction or transfer of the records. It will be important to note that Disposition largely happens outside of the EDRM -- because Disposition can only happen when the records are not required to be retained for legal proceedings.
My expectation is that someone will want to make a major pitch for a step in the process that might be called "Classification". This would be where various attributes are associated with the record. These attributes could include the record series identifier, the vital records status of the record, and the security classification of the record. I would suggest that this is a process within Creation, but I suspect that the vendor community may want to carve this out. I would also expect a push to carve out "Storage" as a separate process, with "Archiving" seen as an additional process, the rationale being that "storage" is really about making records available during Use and archiving processes are about the Maintenance of the information.
The bottom line, however, is that the IMRM should be pretty easy to define -- it's been done before. The challenge will be to ensure that the Model is not too granular and that terminology is what we expect it to be. After all, us records managers have been there and done that -- and do it every day. The folks at EDRM ought to look us up to help out.
Wednesday, May 20, 2009
OTR: 10,000 Hours
I just read Malcolm Gladwell's book, Outliers: The Story of Success. One of his premises is that it takes at least 10,000 hours of practice or effort in a particular craft to be considered expert. He goes on to provide a variety of somewhat anecdotal examples (ranging from the Beatles to Bill Gates) that lend credence to this theory, but it is a compelling argument.
Back in the day, when I played sports (not well) rather than spectated... I had coaches who believed that you needed to drill and drill and drill in the fundamentals. They referred to it is "muscle memory". They wanted us to instantly react to a situation, rather than think about what needed to happen. Once you get to that point, you perform better and often more safely. That point was never more clear to me than when I was learning a technique to split a double team block as a defensive lineman on my high school football team. The coach showed us the technique, then we practiced it a few times in slow motion to get the footwork and body movement correct. Then it was time for full speed. The whistle blew and my brain engaged... "where are my feet, which way do I move, where do my arms go... " Well, by the time my brain was registering where my feet needed to be, one of the blockers had stepped on my foot and I was being pushed over backwards. My next memory was the sound of ligaments snapping as my ankle was seriously sprained. That cost me three weeks on the sidelines. Lesson learned: the less your brain has to worry about technique, the more it can be aware of other things that add value.
Think about it. when you learned how to drive, you had a million things to think about.... where your feet were, maintaining your lane, watching for traffic, looking at the next stoplight, checking blindspots, etc. Today when you drive, do you even think about all of those things? Hardly. In fact, I would hazard to guess that many of you drove to work today and if I asked you if the first traffic light you came across was green or red, you probably couldn't immediately tell me. Your brain simply reacted to whatever color was showing and unless something unusual happened, you never gave it a second thought.
So it goes in the professional world. Think about how long it has taken you to feel comfortable with your job. Think about how long it takes to build an internal network in your workplace. Yep, same idea and I would suggest that you need at least five years to really start to feel comfortable and really start moving forward. Interestingly, five years tends to correspond to the amount of experience that someone needs before being qualified to sit for a certification exam in some professions. Guess that is more than a coincidence, don't you think? So the next time that someone points to a certificate that they got after 30 hours of training and a quick test they took, I'd suggest that they will need to show you some additional proof of their expertise. Because at that point, they are probably still trying to figure out where their feet go and are not able to step up and add value.
Back in the day, when I played sports (not well) rather than spectated... I had coaches who believed that you needed to drill and drill and drill in the fundamentals. They referred to it is "muscle memory". They wanted us to instantly react to a situation, rather than think about what needed to happen. Once you get to that point, you perform better and often more safely. That point was never more clear to me than when I was learning a technique to split a double team block as a defensive lineman on my high school football team. The coach showed us the technique, then we practiced it a few times in slow motion to get the footwork and body movement correct. Then it was time for full speed. The whistle blew and my brain engaged... "where are my feet, which way do I move, where do my arms go... " Well, by the time my brain was registering where my feet needed to be, one of the blockers had stepped on my foot and I was being pushed over backwards. My next memory was the sound of ligaments snapping as my ankle was seriously sprained. That cost me three weeks on the sidelines. Lesson learned: the less your brain has to worry about technique, the more it can be aware of other things that add value.
Think about it. when you learned how to drive, you had a million things to think about.... where your feet were, maintaining your lane, watching for traffic, looking at the next stoplight, checking blindspots, etc. Today when you drive, do you even think about all of those things? Hardly. In fact, I would hazard to guess that many of you drove to work today and if I asked you if the first traffic light you came across was green or red, you probably couldn't immediately tell me. Your brain simply reacted to whatever color was showing and unless something unusual happened, you never gave it a second thought.
So it goes in the professional world. Think about how long it has taken you to feel comfortable with your job. Think about how long it takes to build an internal network in your workplace. Yep, same idea and I would suggest that you need at least five years to really start to feel comfortable and really start moving forward. Interestingly, five years tends to correspond to the amount of experience that someone needs before being qualified to sit for a certification exam in some professions. Guess that is more than a coincidence, don't you think? So the next time that someone points to a certificate that they got after 30 hours of training and a quick test they took, I'd suggest that they will need to show you some additional proof of their expertise. Because at that point, they are probably still trying to figure out where their feet go and are not able to step up and add value.
Subscribe to:
Posts (Atom)
