This is a response to comments that Jürg Meier made recently on something I posted a while ago. Jürg is a very smart and personable guy, whom I had the pleasure of meeting in person at ARMA Switzerland’s inaugural event on November 29, 2011. I urge you to check him out on twitter and here, where he works.
I was going to simply reply to Jürg’s comments on my blog, but I figured that the points he brought up are pretty substantial and would be of interest to a broader audience. I asked Jürg if I could paste his comments into a post and respond to them. You’re reading this so either: a) Jürg agreed; or 2) I’m in deep doo-doo.
From the original post: “Users know what business process they’re involved in. …”
JM: Chris, not sure here. What about knowledge workers, who “often advance the overall understanding of that subject through focused analysis, design and/or development” (Wikipedia). Are they in a business process? Perhaps, but more often than not in a very large one, like a product development, an IT or marketing project. These people send email, word and powerpoint docs back and forward, take notes. Notes? Karl Alexander Mueller, Nobel price winner in physics 1987, discovered a material for high-temperature supraconductors. He took the decisive note a few years earlier at a congress – on a single page of his pocket notepad.
Moreq2010 comes up with a similar example. In the introduction chapter, they show a hand written shopping list and the resulting cash register receipt. They consider only the latter as a record.
I would say that regardless of what the duration or intended outcome of a process is, it’s still a business process with measurable business objectives. Projects and cases (as in case management) cross multiple business processes and can be of several years duration. Product development takes ages, is complex, involves large numbers of people and huge volumes of content. However, it can still be tied to business processes and the participants (usually) know what they’re doing. In that type of scenario I think I would recommend using a case aggregation for the users to plunk their content into, and apply appropriate retention to the aggregate.
I would assume that Müller knew what he was working towards when he wrote the decisive note in his pocket notepad (how different is the pocket notepad from a tablet these days?). If my assumption is correct then it stands to reason that the note is part of the research documentation, which must be filed and retained. The big question in my mind is related to ownership of the intellectual property; does it belong to Müller, to IBM, or to both?
Another question that I have concerns an outcome that is unintended, but beneficial nonetheless. I’m sure we all remember what Sildenafil was originally intended for, and what its current use is. What, if anything, are the impacts on categorization and retention? Research & knowledge based processes are really tricky to deal with, but I think the key is that you can apply (business) rules & automation to the mundane aspects, use aggregations to capture the content, and let the participants do what they are engaged to do. I would certainly rather have medical / pharma researchers figuring out cures than worrying about where to file something.
The Moreq2010 shopping list / receipt example is analogous to an order / invoice example. Each document provides a part of the complete picture, and therefore is required. I also think that particular example is nonsensical unless for some official reason (e.g.: personal taxes) you need to hold on to the receipt. Frankly, I need to keep the list to prove to my wife that I didn’t bugger something up when she “let” me go shopping for her.
JM: In my experience, it is really a question of who will consume the information. There are the usual suspects:
– long-term (historical) archive
As you pointed out during your speech at the Swiss ARMA Chapter inaugural meeting, different people have different views on the same information. So, it would be compelling to classify information multiple times by different consumers… and I’m inclined to say: as late as possible. Only if we know about the purpose of the classification, we can do it right. E.g. for legal, they actually only know what they are looking for upon a litigation. By then though, they know very well what they need.
But what’s wrong with classifying as soon as possible, and adding additional classifications as they are identified, if that’s the case. The classification with the longest retention drives how long any content needs to be kept. This only works when classification and retention/disposition are segregated. In litigation situations simply applying a hold / freeze will do the job. There’s no reason to apply additional classification to the content because you create a legal case file aggregation and dump the content into it.
Content that has archival value, but no risk is easy – just keep it. I mean, I know we’ll want to keep all of my blog posts for the next 300 years or so. J It’s tougher when content that has archival value has some potential risk associated to it (privacy issues, legal exposure). I think at that point it’s really a judgement call. Frankly, I’m in favour of preserving because I’d like to think that sometime in the future there are going to be people that are interested in what we’ve been thinking and doing, and that the information they want is available. I’m also hoping that we’re not so stupid that we evaluate everything in terms of whether or not we’re going to get sued.
JM: However, the case of “late classification” does not answer one key question: for how long should we retain? The only reliable basis here is law and the retention schedule. And for that, by nature, we must classify upfront. That isn’t too difficult for “real business processes” (e.g. selling a ticket), but becomes tricky with output from knowledge workers. Here, to some extent, we need their support. Classifying draft/final is a good start, formally assigning it to a project would be very helpful, as well as identifying ownership and the document type.
For the most part I agree with this paragraph. For the knowledge workers, especially those that are involved in a lot of trial and error, I think we can come up with some reasonable classifications and retentions for them to use. Imagine how different things would be if the people that were working on Sildenafil tossed everything away once they realized they weren’t going to achieve what they set out to do.
This was originally posted on the AIIM Community on November 18, 2011.
I’m not an expert on cloud computing, I’m just some guy that likes to be able to access the content I need to do my work, from wherever I happen to be, using whatever device I feel like using at the moment. Take this post, for example; it was written on a laptop and a tablet, in a dining room and a swimming pool (not really in the pool since my tablet isn’t waterproof though that would be mega-cool).
I agree with Billy Cripe’s thoughts that Agile can (ought to) be applied in the development of cloud based ECM solutions. However, as Billy correctly states, “Managing content is not the goal of most businesses.” Most businesses exist to make money by providing products and/or services that consumers want. Businesses rely on information in order to get their stuff done, whatever their stuff is. In order to fully exploit information, the tools (i.e.: information stores) that the businesses rely on need to be connected to each other (so do the people – the tools need to facilitate this). Content / information management tools (cloud or not) need to be part of bigger picture business solutions. We need to build solutions that deliver “I need to share this” in the context of why it needs to be shared (answer why you need to share and you’ll likely figure out who and what).
No sane person can argue the value and validity of the cloud. Except me. I’m not daft enough to think that cloud computing doesn’t have value or is not a valid approach to take. However, I do think that we’re not going to realize the full potential of the cloud (and by extension, content) if we simply limit its scope to content management. Yeah, I know that there are other things that are done in the cloud, such as CRM, payroll, and accounting.
Content Wherever I Am
One of the cool things about content in the cloud is that my content is wherever I am. (Okay, so it’s not really my content, it’s my organization’s content.) That’s not the point, though. The point is that I can work with content wherever I happen to be, using whatever device I choose. This does assume that the chosen content repository is able to be synched appropriately. Wouldn’t it be cool, though, that if in addition to being able to work with the content and share it with collaborators (the work variety, not the WWII Nazi variety) the content could also be appropriately tagged, filed, and placed under retention at the point that I plunk it into the repository? I.e.: Cloud repositories need to become extensions of ECM and ERM systems, probably through federation.
Correctly Connecting Corporate Content
Content is spread throughout an organization; cloudification just increases the spread. When I say content, I mean anything that is stored on digital media that serves any legitimate business activity. (For obvious reasons I am excluding physical content.) A key to widespread cloud acceptance is to be able access / leverage content in order to execute a business activity, regardless of where the various pieces of content reside. An agent in a social services organization should not have to know or care that a citizen’s information is spread over a number of repositories that could be on-premises, in a private cloud, and in a public cloud. The agent is there to service the needs of the citizen, not to figure out some (likely) convoluted architecture just to try and find stuff.
CMIS is a step in the right direction, but where CMIS falls short is that it doesn’t address non-CMS (think ECM) repositories. What we need is something that allows connecting everything that we need, when we need it. Device and location should not be factors. In fact, the only thing that a user should worry about is whether or not they have the right content to do the job. Governance, classification, and security ought to be just taken care of.
Speaking of Governance…
Until the governance issues get sorted, I doubt very much that we’ll see widespread adoption of public cloud services. Smaller organizations, organizations with lax regulatory / privacy regulations, and organizations that can bully providers into rock-solid SLA’s may be able to go full public cloud, but I doubt they will. I think the reality is that organizations will end up having hybrid environments of cloud and on-premises.
When I say governance I am not only referring to the poo that legislators, regulators and litigators throw in our way. Governance needs to address issues such as:
- what can / should be stored in the cloud
- service level agreements
- disaster recovery / business continuity
- classification / categorization
- retention & disposition (thanks to @JamesLappin & @AlanPelzSharpe for bringing this up)
Governance of cloud content has to deal with all of the things that we need to deal with for on-premises stored content, with the added complication that we also have to deal with where the damn box is and if some foreign government can get at it whenever they bloody well feel like it. Canada’s Anti-terrorism Act and the United States’ PATRIOT Act are not going to be very helpful in encouraging organizations to move to the cloud in a big way.
- Hybrid (cloud / on-premises) will be in the majority
- Governance (internally & externally imposed) has to be figured out
- Integration / interoperability are critical
- Privacy concerns and government snooping are major inhibitors (@ron_miller wrote a pretty good piece about this)
- If we’re not careful we’ll just move the mess from our hard drives to someone else’s
- Some Systems of Record will end up in the cloud, if they’re not already there
- Services are where it’s at
I couldn’t decide which song I wanted to use for this post, so you’re getting three:
A couple definitions for those that think it should be “on-premise”
Big Data? Big Whoop!
Over the past couple of days I’ve been seeing a number of posts and tweets about Biiiiig Dataaaaaaa (ring announcer voice in my head)! What is “Big Data”? Check out the definition in this executive summary; or as I and others like to say, “It’s as big as a piece of string is long”. I certainly understand the idea behind “Big Data”, but do we really need a new term for something that, let’s face it, isn’t new at all?
In a comment to this post I used the phrase “E2.0 meets BI”. To be more accurate I should have said “E2.0 fuels BI”. This whole “Big Data” thing is nothing more than reporting and analytics, but with more data than we had before. Those of us who have a stake in the BI domain have often wished for more raw data on which to base our decisions. Now that we have it, and are getting more of it every second, we’re freaking out and giving one or more major vendors in the space an opportunity to define something new. Two things, and only two things, have really changed:
- The available amount of raw data is way beyond what it was only a short time ago;
- The Cloud and SaaS jeopardize access to some of the raw data.
If you’ve got the resources (i.e.: $’s) dealing with #1 one is a matter of scaling. Dealing with #2 is tougher, especially if any of your data sources are not entirely under your control (Cloud, SaaS). The challenge, however, is not insurmountable:
- Rationalize your requirements and identify what is absolutely critical to your business (i.e.: leave the “it’s just cool” stuff out or defer for later);
- If you rely on hosted data sources negotiate appropriate access and up-time agreements;
- Find out if your hosted providers can provide some of the ETL for you;
- Trim your datasets where possible;
- Identify your true timing requirements (real-time, near-real-time, periodic);
- If you have retention / disposition policies on your data sources, enforce them; if not, define and enforce them.
The funny thing is, when I made my living in BI projects, 5 of the 6 points noted above where standard things we did. Maybe nothing really has changed all that much, other than my segue into RIM. Oh well.
There has been plenty of chat about going paperless, motivated by a variety of reasons including economics, the environment, efficiency, and convenience. They’re all valid reasons, but I don’t think that we will ever become paperless, whether at home or at work, in our lifetimes. The best, I think, that we can expect is to reduce the amount of paper we consume.
On a recent project we (the client and I) debated the idea of going paperless. The best that we could actually come up with was to transition from a mix of paper and electronic records to electronic records only, over the next n years. Paper will still be used for draft versions and for circulation of the some content. The client holds monthly meetings where materials numbering in the hundreds of pages are circulated to attendees in 3-inch thick binders. Theoretically the client could transition to a variant of an e-Council model, but that would necessitate acquiring the correct equipment and a very significant change management effort. My gut tells me that this may well happen, but as a result of attrition rather than a conscious effort to actually go paperless. The potentially affected users are in an ageing demographic and of a nature not to be messed with. Trust me.
I am an annotator; I like to make notes, circle stuff, and highlight things. Sometimes I make notes that question the sanity and intelligence of the author of a document. Yes, I know that there are plenty of tools out there that would allow me to do all of these things electronically, but I won’t use them. I have this thing about reading long-ish documents on a screen, any screen. It’s a comfort thing; I like to lean back and put my feet on my desk when I review long documents. Also, when I do question someone’s sanity or intelligence in a note on a document, I’m not certain that I want it recorded electronically and stored in some repository. [2013-10-10: I now use tools on my tablet for this, coupled with cloud storage.]
I may give ebooks a try in the future, but there is something comforting about having a 900-page plus tome on your lap while you’re reading in bed (I am currently reading Fall of Giants by Ken Follett, if you’re interested). I also like the way a full bookshelf looks. My wife would appreciate me switching to ebooks just so I’ll turn the damn light off and let her sleep. [2013-10-10: Other than during takeoff and landing, e-books on my tablet are my preference now.]
I absolutely agree that invoices, claims, benefits applications, and other form based transactions can be processed more efficiently electronically than they can be on paper. However, there is still an ageing demographic to contend with, as well as the fact that not everyone has access to the required technology. A government department that I worked with several years ago serves senior citizens. Their mandate is to provide benefits such as education and property tax relief, dental benefits, and other benefits that people on fixed incomes require. In addition to many of the beneficiaries having issues with adapting to and using technology, many of these people live in rural or remote areas with less than modern technical infrastructures, some have none.
Economically, going paperless makes tons of sense. If a paperless process is more efficient, it stands to reason that it is less expensive to run. Also, storing paper costs more in real estate costs than storing the same content electronically. We can throw in the costs of running and managing network storage, but it’s there anyways so the incremental cost as compared to what it would cost to store paper is likely negligible.
The environment aspect is the one that I find most fraught with gotchas. Generally, the paper we use is made from recycled materials and then recycled again once we’re done with it. But what about the other tools that we need to deal with the paper? I’m referring to the printers, fax machines, scanners, photo-copiers, and all the consumables they require. I’m not an expert in this area, nor do I ever plan to be one, so I will leave it to someone better qualified than I to comment. One thing that I did read somewhere (I forget where) related to the environmental impact of going paperless. The gist of the issue was the additional environmental impact of replacing paper with the technology and tools required to replace the paper. This struck me as either disingenuous or ill-informed, depending on the author’s intent. We’re already using the technology and there’s more coming every day.
We won’t be paperless, but there will be less paper.
I originally posted this on AIIM’s Information Zen site (now defunct), but thought I’d update it a bit and repost it here…
Leaving legal aspects out of the discussion for the moment, does it really matter whether or not content is a record? If content is not declared a record, is that content less valid or valuable than if it were considered a record? I am referring to the business value of content. I am referring to an organization’s ability to leverage the content in order to reduce wasted effort, to increase customer satisfaction, to drive profitability, to reduce expenses, and to keep everyone’s butt out of the slammer.
If I do take legal issues into consideration, does the “recordness” of content make a difference, provided I can back up everything I say about the content’s use, access, authenticity, and provenance? Personally, I don’t think it should; I know it does, but that’s just because too many people out there haven’t fully caught on to this new invention called the computer yet.
If within the context of discovery, an organization is told to produce certain content, said organization cannot reply “but we never declared it as a record” as a rationale for not including it in the discovery. So even from a legal point of view, the “recordness” of content is becoming, in my opinion, less critical. I believe that as we grow more and more comfortable with electronic content, content’s status as a record will become less important. The fact is, with the proper tools and procedures we can secure, audit, and authenticate non-record (electronic) content every bit as well as if the content were declared a record. With the proper tools we can manage the lifecycle of any piece of content very effectively. Let’s face it; the lifecycle of content is not very complicated: get it, use it, dispose of it.
If the “recordness” of content is becoming less important, do we still need Records Managers? We do, but I think we need to change their titles, job descriptions, and the amount of authority they have in organisations. There is some interesting discussion about the RIM profession happening on the ARMA Linkedin group and on the AIIM ERM Community site.